CSV, short for Comma-Separated Values, is the most common interchange format for tabular data. Each line of the file is a record, and within a line, individual fields are separated by a delimiter - usually a comma. The first line is often a header row naming each column. Because CSV is just plain text, it can be opened in any spreadsheet, database, text editor, or programming language, which is why it remains the default export format for CRMs, ad platforms, and email tools.
Despite its simplicity, CSV has no single formal standard, and that causes real friction. Fields that contain commas, line breaks, or quotes must be wrapped in double quotes and escaped, but not every program does this consistently. Different tools also disagree on delimiters - European locales frequently use semicolons because the comma is a decimal separator - and on character encoding, where a missing UTF-8 byte-order mark can turn accented names into garbage.
For anyone importing lead lists or exporting campaign data, understanding CSV quirks prevents silent data loss. A common failure is a name like "Smith, Jr." splitting into two columns because it was not quoted, shifting every subsequent field. Verifying the delimiter, checking the header row, and confirming the encoding before import saves hours of cleanup later.
CSV converts cleanly to and from richer formats. Converting CSV to JSON is useful for feeding APIs, CSV to SQL generates insert statements for databases, and CSV to Markdown or HTML produces readable tables for documents and web pages. When a comma delimiter is problematic, switching to TSV (tab-separated values) or another delimiter avoids most quoting headaches.