CSV vs TSV vs JSON: Differences and Examples
August 22, 2026 · Updated October 23, 2026 · RividTech Experts Team
CSV separates columns with commas, TSV separates them with tabs, and JSON uses named keys and values. CSV and TSV fit flat tables and spreadsheet imports. JSON also represents nested objects, arrays, numbers, booleans, and null, making it useful for APIs and structured records.
This guide compares the three formats, shows when each is the better fit, and points you to private, browser-only converters on RividTech so your files never leave your machine.
The same records in CSV, TSV, and JSON
These examples contain the same two products. Their IDs are text because the leading zeros matter.
CSV example
id,name,price
00142,"Desk lamp, brass",24.50
00977,Notebook,8.00
The comma in Desk lamp, brass is part of a value, so that field needs double quotes. The header names the three columns. CSV itself does not specify whether 24.50 is a number or text; the importer decides.
TSV example
id name price
00142 Desk lamp, brass 24.50
00977 Notebook 8.00
The gaps between fields above are literal tab characters. The comma in the product name needs no CSV-style quoting because tabs separate the columns. Paste this sample into the CSV & TSV preview to see it as a table, or use TSV to CSV when an importer requires commas.
JSON example
[
{ "id": "00142", "name": "Desk lamp, brass", "price": "24.50" },
{ "id": "00977", "name": "Notebook", "price": "8.00" }
]
The keys repeat in each object instead of appearing in a separate header. All values here are strings to match the text in the CSV and TSV examples. A JSON number such as 24.5 would be unquoted, but IDs such as "00142" must stay quoted to retain their zeros. RividTech’s CSV to JSON converter keeps values as strings so it does not guess types or alter IDs. The JSON to CSV converter turns object keys back into table columns.
What CSV is good at
CSV (comma-separated values) is a plain-text table: one row per line, fields separated by commas. Spreadsheets, databases, and BI tools all speak it. It is compact, human-readable in a text editor, and easy to diff in version control for small files.
-
Best for: flat tables, Excel/Google Sheets exchange, bulk imports into databases.
-
Watch out for: commas inside fields (need quoting), newlines inside cells, and locale-specific separators (some regions use semicolons).
When a file “looks like CSV” but opens as one column, the delimiter is often wrong. Check the separator expected by your importer before rewriting the file by hand.
What TSV is good at
TSV (tab-separated values) is the same idea as CSV, but fields are separated by tab characters instead of commas. That single change removes most of the pain when your data already contains commas - addresses, product names, free-text notes - because you rarely need to quote fields.
-
Best for: copy-paste from spreadsheets, logs and exports that already use tabs, pipelines where commas are common in values.
-
Watch out for: tabs inside field values (uncommon but possible), and tools that assume CSV by default.
Converting either direction is straightforward with CSV to TSV and TSV to CSV. To inspect a .tsv file without converting it, use the TSV preview, which detects tabs and keeps IDs as text.
What JSON is good at
JSON is a structured data format, not just a table. It supports nested objects, arrays, numbers, booleans, and null - not only strings. APIs, config files, and modern web apps prefer JSON because hierarchy is part of the model, not something you fake with column names.
-
Best for: API request/response bodies, nested records, typed values, application config.
-
Watch out for: large flat tables can be verbose; not every spreadsheet tool imports nested JSON cleanly.
When you need a table from nested data, Flatten JSON first, then JSON to CSV . Going the other way - a flat export into an API-friendly shape - is what CSV to JSON is for.
Side-by-side comparison
-
Structure: CSV/TSV = flat rows and columns. JSON = nested objects and arrays.
-
Types: CSV/TSV are text until something else parses them. JSON can carry numbers, booleans, and null natively.
-
Escaping: CSV needs quotes around commas and newlines. TSV mostly avoids that. JSON uses backslash escapes and strict syntax.
-
Tooling: spreadsheets love CSV/TSV; developers and APIs love JSON.
-
Size: for wide flat tables, CSV/TSV are usually smaller than pretty-printed JSON.
Practical decision guide
Use this as a quick rule of thumb:
-
Sharing a simple table with non-developers → CSV (or Excel if formatting matters).
-
Data is full of commas or came from a tab export → TSV .
-
Feeding an API, storing nested records, or keeping types → JSON.
-
Need both worlds → convert. Flat table in, nested out (or the reverse) with the converters above.
Does converting CSV to JSON create nested data or restore types?
Converting a table to JSON does not recover information that was never in the file. A column named user.name can remain a literal key; it does not necessarily become a nested user object. A value such as 00142 could be an ID, while true could be a boolean or a text label. Choose these meanings explicitly in the system that consumes the data.
Going from nested JSON to a table also requires a choice. RividTech’s JSON to CSV converter keeps nested values as JSON text inside a cell. Use Flatten JSON first when you need separate columns such as user.name and user.city.
Converting without uploading your data
Format choice often means a quick conversion. RividTech runs those conversions entirely in your browser - no account, no server-side file upload. Common paths:
-
CSV to JSON for API-ready arrays of objects; it reads both CSV and TSV.
-
JSON to CSV and JSON to TSV for spreadsheet-friendly exports.
-
CSV to TSV / TSV to CSV when only the delimiter needs to change.
For a deeper look at why client-side tools matter for sensitive exports, see Why Browser-Only CSV Tools Are Safer for Your Data .
Getting started
Pick the format that matches your next consumer - spreadsheet, database, or API - then convert only if you must. Start from the full tool list or jump straight into CSV to JSON , JSON to CSV , or CSV to TSV .