Read, re-delimit, or convert a CSV: which step comes first?
Choose between browsing a large CSV, changing its delimiter, turning rows into JSON, or building CSV from plain lines.
A CSV problem is usually one of four: you cannot open it, your tool expects a different separator, you need JSON, or you have plain lines that need columns. Naming the step prevents the common mistake of re-exporting a file that could simply be re-delimited.
Browse first when the file is large or unfamiliar
Open the viewer when you need to see what is inside without loading a spreadsheet. It pages through big files, filters rows and exports what you filtered, which is enough to decide whether the data is worth converting at all.
Change the delimiter when rows are right and punctuation is wrong
Semicolon exports from European locales and tab-separated exports from databases are still CSV in spirit. The delimiter converter swaps comma, semicolon, tab and pipe without touching values, so quoting stays intact.
Convert to JSON or from text only at the edges
Use CSV to JSON when a script or API needs objects, and Text to CSV when you have pasted lines that need columns. Both validate structure first: mismatched header counts are reported instead of being guessed.
Tools covered in this guide
- CSV Viewer
Browse huge CSV files as a fast table with filter and export.
- CSV Delimiter Converter
Switch CSV files between comma, semicolon, tab, and pipe delimiters.
- CSV to JSON
Convert CSV rows to a JSON array with header validation.
- Text to CSV
Turn plain pasted lines into structured CSV rows and columns.
- SQL Formatter
Format SQL readably with dialect, keyword-case, and indent options.
Frequently asked questions about CSV handling
Will changing the delimiter break quoted commas?
No. The converter rewrites separators at field boundaries and keeps quoted fields quoted, so a comma inside a value stays part of that value.
Can I open a very large CSV in the browser?
The viewer is built for large files and reads them locally, but available memory still matters. A huge file is easier to filter than to export whole.
Should I convert CSV to JSON before cleaning it?
Clean and inspect in CSV while rows are easy to see, then convert once. Converting first makes column problems harder to spot.
More guides
- CSV to JSON or JSON to CSV: which direction do you need?
- JSON, HTML, CSS, JavaScript, or SQL: which formatter?
- Turn lines into a comma list, CSV, or combined text?
- Basic meta, Open Graph, or Twitter Card: which tags do you need?
- Bold, italic, cursive, or blackletter: which Unicode style?
- Canonical or hreflang: which duplicate problem are you fixing?