Convert flat JSON arrays and CSV tables locally in your browser with custom delimiters, bounded table previews, and explicit data-change acknowledgments.
Optional prefixing changes exported values, including headers. Spreadsheet apps differ; this does not guarantee safety.
0 / 500,000 UTF-16 code units · 0 UTF-8 bytes
File limit: 500,000 bytes · Up to 5,000 data rows and 100 columns. Requires a non-empty array of flat objects.
100% browser-local RFC 4180
Add data or load an example to get started.
Conversion rules
JSON → CSV converts values to text; missing and null values become empty fields. CSV → JSON keeps values as strings, preserving leading zeros (e.g. "00123").
THE DETAILS
RFC 4180 CSV conversion, type safety, and formula-injection defense.
1. Step-by-Step Workflow
Select JSON → CSV or CSV → JSON, choose your field delimiter (Comma, Semicolon, or Tab), and paste your data or open a local file. Review live row, column, and output-size KPIs, use Swap ↔ to round-trip output back into the opposite format, and copy or download the validated result.
2. IETF RFC 4180 Quoting Rules
Compliant with IETF RFC 4180, any field containing the active delimiter, a double quote ("), or a line break is enclosed in double quotes, and embedded double quotes are escaped by doubling them ("").
3. OWASP CSV Formula Injection Defense
Opening untrusted CSV exports in Excel, LibreOffice Calc, or Google Sheets can trigger formula execution if a user-supplied cell begins with =, +, -, or @. Enable the apostrophe prefix option to neutralize formula-like cells before exporting.
4. Local Privacy & Related Data Tools
Financial exports, user rosters, and database dumps stay 100% inside your browser tab. Need to pretty-print nested JSON, format SQL queries, or generate TypeScript interfaces? Try the JSON formatter, SQL formatter, and JSON to TypeScript generator.
JSON ↔ CSV Type Mapping & CLI Matrix
Input Construct
Converted Result
Notes / CLI Equivalent
null or missing key in JSON
Empty CSV cell (,)
Flagged for explicit acknowledgment
CSV string 00123
JSON "00123"
Preserves leading zeros as text
Embedded comma / quote
"Ada, ""Countess"""
RFC 4180 standard escaping
Terminal JSON → CSV
Header + rows
jq -r '(.[0]|keys_unsorted), (.[]|[.[]]) | @csv'
Common CSV & JSON Pitfalls
Duplicate or Empty CSV Headers
When converting CSV to JSON, the first row is used as object property keys. Duplicate header names would silently overwrite earlier columns, so the validator requires every header column to be unique and non-empty.
Ragged CSV Row Lengths
A data row with fewer or more fields than the header row usually indicates an unquoted comma or a wrong delimiter selection (e.g., semicolon CSV opened in comma mode).
Sparse Keys Across JSON Objects
If later objects in a JSON array introduce new keys not present in the first object, the converter collects the union of all keys across every row so no column is dropped.
Nested Arrays or Objects
Flatten nested JSON structures before converting to CSV, or use the YAML ↔ TOML ↔ JSON converter when preserving hierarchical data.
Frequently Asked Questions
Is my customer CSV or JSON dataset uploaded to any server?
No. All CSV parsing, RFC 4180 escaping, table preview rendering, and JSON serialization execute 100% locally in your browser. Zero spreadsheet rows or JSON objects ever leave your device.
How does the converter protect against CSV formula injection in Excel or Google Sheets?
Spreadsheet applications evaluate cells starting with =, +, -, @, Tab, or CR as executable formulas (DDE / CSV Injection). Enabling the optional apostrophe prefix prepends a single quote to those fields so spreadsheets treat them as literal text.
Why are nested JSON objects rejected when converting to flat CSV?
A CSV table is a two-dimensional grid of scalar cells. To prevent silent data loss or [object Object] corruption, the converter requires an array of flat JSON objects and alerts you whenever null or primitive type conversions occur.
How are leading zeros and numeric strings handled during CSV-to-JSON conversion?
CSV cells have no native data-type tags, so all fields are preserved as exact JSON strings. This guarantees that postal codes ("00123"), phone numbers, and 64-bit IDs never lose leading zeros or numeric precision.
Which delimiters are supported besides commas?
You can switch between Comma (,), Semicolon (;) commonly used in European locales, and Tab (\t) for TSV files. The example loader and output downloader adapt to your selected delimiter.