How do I open a CSV file in Excel without garbled characters?

Use Excel's "Data > From Text/CSV" import wizard (not File > Open), which lets you specify the file encoding (choose UTF-8) and delimiter before loading. Alternatively, add a UTF-8 BOM to your CSV file — our formatter does this with the "Excel compatibility" toggle. For Google Sheets, simply use File > Import, which correctly auto-detects UTF-8 without needing a BOM.

Can I convert CSV to JSON or other formats?

Yes. Use the "Download as JSON" button to convert the parsed CSV to a JSON array of objects (each row becomes an object with header fields as keys). For SQL, use "Copy as INSERT" to generate INSERT statements. For Markdown, use "Copy as Markdown Table" to generate a GitHub-Flavored-Markdown-compatible table. Each export format respects the parsed header row and delimiter settings.

What is the difference between CSV and TSV?

CSV uses commas to separate fields; TSV uses tab characters. The practical difference: commas appear frequently in natural text (addresses, descriptions, names with suffixes like "Doe, Jr.") and require quoting. Tab characters almost never appear in data values, so TSV rarely needs quoting, making it simpler to parse and less error-prone. TSV is the preferred format for data that contains text-heavy fields. DSV (Delimiter-Separated Values) is the generic term that includes CSV, TSV, semicolon-delimited, pipe-delimited, and any other character-delimited format.

How does the formatter handle very large CSV files?

Files up to 50 MB are processed entirely in the browser with streaming parsing — the file is read in chunks using the FileReader API, and the table view uses virtualized rendering to efficiently display only the visible rows. Beyond 50 MB, use the "Preview" mode which reads only the first 1,000 rows for formatting preview while preserving the ability to validate the full file's structure (row count, header consistency). For production-scale CSV processing, pair our formatter with command-line tools like csvkit or xsv.

How do I detect and fix the delimiter in an incorrectly parsed CSV?

Our formatter auto-detects the delimiter by analyzing the consistency of field counts across the first 20 lines with each candidate delimiter (comma, semicolon, tab, pipe). If auto-detection guesses wrong, manually select the correct delimiter from the dropdown and the table re-parses immediately. A quick manual check: scan the raw text for the delimiter character — if commas appear inside field values without accompanying double-quotes, the file likely uses a non-comma delimiter.

Developer Tools2026-05-10

CSV Formatter: Format, Validate, and Beautify CSV Data Online

CSV (Comma-Separated Values) is the oldest and most universally supported data interchange format — it predates JSON by decades, has no official governing body (RFC 4180 is the closest thing to a standard, and it is an informational memo, not a strict specification), and every tool from Excel to pandas to PostgreSQL implements it slightly differently. The result: CSV files that look fine but fail to parse correctly due to the wrong delimiter, inconsistent quoting, missing headers, or invisible encoding issues. Our CSV formatter solves these problems by parsing your CSV data — regardless of which variant it uses — and presenting it in a clean, aligned table view with properly escaped fields. It auto-detects delimiters (comma, tab, semicolon, pipe), identifies header rows, normalizes quoting, and validates against RFC 4180 conventions. The tool runs entirely in your browser and comfortably handles files up to 50 MB and 500,000 rows. For Excel users, it adds or removes the UTF-8 BOM (Byte Order Mark) that Excel requires to correctly interpret non-ASCII characters, preventing the dreaded "Mojibake" garbled text that occurs when opening UTF-8 CSV in Excel without a BOM.

table_chart

CSV Formatter

Free · No registration

Try this tool for free →open_in_new

Step-by-Step Guide

Paste, Upload, or Drag-and-Drop Your CSV

Paste CSV data directly into the text area, upload a .csv or .tsv file, or drag and drop a file from your computer. The parser auto-detects the delimiter by analyzing the first few lines — it looks for the character (comma, tab, semicolon, or pipe) that produces a consistent number of fields across lines. The detected delimiter is shown at the top of the output, with a dropdown to manually override if detection was incorrect.

Review and Configure Formatting Options

Use the settings panel to: (1) toggle "First row is header" detection — the tool highlights the header row in blue; (2) select the output delimiter if you want to convert between formats (e.g., comma to tab-separated); (3) enable "Add UTF-8 BOM" for Excel compatibility; (4) set quoting strategy — quote all fields, quote only fields containing the delimiter, or minimal quoting; (5) align columns for readability in the table view.

Copy, Download, or Export the Formatted Result

Click "Download CSV" to export the formatted data as a clean .csv file (with your chosen delimiter and quoting options). Click "Copy" to copy the raw CSV text to your clipboard. The table view supports sorting by clicking any column header and searching within the data using Ctrl+F. For large files, the "Download as JSON" option converts the CSV to a JSON array of objects, which is often easier to process programmatically.

Tips & Best Practices

check_circle

RFC 4180 defines these rules for CSV: (1) each record is on a separate line delimited by CRLF ( ); (2) the last record may or may not have a trailing line break; (3) the first line may be a header line with the same number of fields as the records; (4) each line should contain the same number of fields; (5) fields containing commas, double-quotes, or line breaks must be enclosed in double-quotes; (6) a double-quote inside a quoted field is escaped by doubling it ("").

check_circle

The UTF-8 BOM problem: Excel on Windows requires a BOM (Byte Order Mark, the bytes EF BB BF at the start of the file) to correctly display UTF-8 characters like accented letters, Chinese characters, or emoji. Without the BOM, Excel assumes the file is encoded in the system's default code page (e.g., Windows-1252), and non-ASCII characters display as gibberish. Our formatter adds the BOM when you enable "Excel compatibility mode."

check_circle

European CSV files commonly use semicolons (;) as delimiters instead of commas because many European locales use the comma as the decimal separator (e.g., 3,14 for pi rather than 3.14). A comma-delimited number "3,14" in a semicolon-delimited file is unambiguous. If your data contains both commas as decimal separators and commas as delimiters, switch to semicolon or tab delimiters.

check_circle

Large CSV files (>100 MB) in the browser: our tool processes files in chunks using the FileReader API with streaming parsing. For files approaching 50 MB, expect a processing time of 1-3 seconds on modern hardware. For truly massive datasets (500 MB+), use command-line tools: `csvkit` (Python), `xsv` (Rust, handles GB-scale CSVs with sub-second queries), or `q` (SQL queries directly on CSV).

check_circle

CSV field values can contain newlines — a quoted field can span multiple lines. This is valid RFC 4180 but confuses many CSV parsers and makes line-by-line processing impossible. Our formatter correctly handles multi-line quoted fields and displays them in the table with the newline character shown as a visual indicator.

check_circle

Always validate that every row has the same number of fields as the header. An off-by-one error (e.g., a trailing delimiter creating an empty field at the end of each row) is a common cause of silent data corruption when importing CSV into databases. Our validator flags rows with inconsistent field counts and highlights the affected cells.

check_circle

For TSV (Tab-Separated Values), the rules are simpler: tabs separate fields, and there is no standard quoting mechanism because tabs almost never appear in data values (unlike commas). TSV is preferred in bioinformatics, log processing, and any context where data values frequently contain commas. Our formatter converts seamlessly between CSV and TSV.

check_circle

When preparing CSV data for a database import (MySQL, PostgreSQL, SQLite), ensure: (1) NULL values are consistently represented (empty fields without quotes are typically interpreted as NULL, while empty quoted fields "" are interpreted as empty strings); (2) date formats match the database's expected format (ISO 8601 YYYY-MM-DD is safest); (3) boolean values are standardized (true/false, 1/0, or t/f depending on the database).

Frequently Asked Questions

RFC 4180 (2005) is an informational memo that documents the most common CSV conventions, but it is not an official IETF standard — there is no formal CSV standard. Most CSV implementations follow RFC 4180's rules (commas as delimiters, double-quote escaping, CRLF line endings), but many deviate: European systems often use semicolons, some implementations allow backslash escaping instead of double-quote doubling, and line endings vary between LF (Unix), CRLF (Windows), and CR (legacy Mac). Our formatter is flexible enough to handle all common variants.

CSV may be simple in concept, but its lack of a formal standard means every CSV file is a potential parsing puzzle. Our formatter handles all the variants — delimiters, quoting, encoding, and BOM — so your data loads correctly the first time. Paste your CSV and see it formatted into a clean, readable table in seconds.

Try this tool for free →open_in_new