Input JSON
Showing
Node Details
Select a node to view details
Flatten nested JSON into clean CSV columns — download Excel-ready .csv files in one click
Select a node to view details
Format, validate, and explore JSON — 100% client-side, private by design
Paste XML, get clean JSON — attributes, repeated elements and text nodes handled correctly
Turn CSV rows into JSON arrays of objects — quoted fields, custom delimiters and types handled for you
Flatten nested JSON into clean CSV columns — download Excel-ready .csv files in one click
Compress JSON to a single line and watch exactly how many bytes you save
Compare two JSON documents semantically — key order and whitespace never count as differences
Escape JSON strings for embedding — or unescape stringified logs back into readable JSON
One-click repair for broken JSON, JSON5, JS objects, Python dicts and truncated LLM output.
Turn any JSON payload into clean TypeScript interfaces or type aliases — merge arrays, detect optional fields and unions.
Parse YAML configs — K8s, Docker Compose, GitHub Actions — into clean JSON, then explore and edit visually.
Generate clean, idiomatic YAML from any JSON — smart string quoting, compact list style, 2 or 4 space indent.
Serialize JSON to well-formed XML — @_ attributes, repeated elements, text nodes and safe tag names.
Infer a standards-compliant JSON Schema from example data — formats, required keys, unions and additionalProperties control.
Query any JSON with live JSONPath evaluation — wildcards, recursive descent, slices and filters, all in your browser.
Paste a root array, an object wrapping one ({"data": [...]}), or a single flat object — the converter finds the rows automatically.
Deep properties become dot-path columns: user.name, address.city. Arrays serialize to compact JSON strings so no data is lost.
Cells containing commas, quotes, or newlines are wrapped and escaped correctly — the output imports cleanly into Excel, Sheets, and databases.
The optional BOM switch makes Chinese, Japanese, and accented characters open correctly in Microsoft Excel instead of turning into mojibake.
Drop a JSON array of objects, an object containing an array, or even a single object into the input panel.
Check the flattened result in the table or CSV preview. Use "View in Table" on any deep node to scope the export to a nested array.
Click "Copy CSV" for the clipboard or "Download CSV" for an Excel-ready .csv file — enable the BOM option if you open it in Excel.
How formatjson.net compares to traditional server-based JSON formatters and converters
| Capability / Standard | formatjson.net (Client-Side Workbench) | Traditional Server-Based Tools |
|---|---|---|
| Data Processing & Privacy | 100% local in-browser JavaScript — payloads never leave your device | Often uploads JSON/XML/CSV to remote backend servers |
| Confidential API Keys, JWTs & PII | Safe by design — zero network transmission, works offline via Service Worker | Risk of server access logs or third-party data retention |
| Broken & Truncated LLM JSON Repair | 1-click lexical state machine fixes comments, single quotes, trailing commas, Python literals & unclosed brackets | Fails with syntax error on non-strict JSON |
| 64-Bit Snowflake IDs & Leading Zeros | Preserves unsafe integers (> 2^53 - 1) and leading-zero codes ("00123") without precision loss | Silently truncates 64-bit IDs or strips leading zeros |
| Deep Nested Array Exploration | Interactive spreadsheet drill-down ([n items] →) with breadcrumbs, 3-state sorting & inline cell editing | Flat root-only tables or read-only trees |
| Large File Responsiveness | Chunked lazy tree (200 nodes/batch) + paginated table + 150 KB highlight guard | Main-thread DOM freeze on multi-megabyte files |
Nested objects expand into dot-path columns — {"user":{"id":1,"name":"Alice"}} produces user.id and user.name columns. Array values are serialized as compact JSON strings so the structure stays recoverable.
Yes. Paste any JSON and use "View in Table" on the array you want — the CSV export follows that scope. Top-level arrays are detected automatically even when wrapped inside an object like {"data":[...]}.
Cells are quoted per RFC 4180 (commas, quotes, and newlines are safe), and the optional UTF-8 BOM tells Excel exactly how to decode the file — Chinese, Japanese, and accented text stays intact.
Arrays are serialized into a single cell as a compact JSON string, e.g. ["a","b"]. This preserves the full value without exploding one record into multiple rows.
No. Everything runs locally in your browser — there is no upload, no row limit imposed by a server, and no data ever leaves your machine.