This JSON has no list to show as a table - it is a single value. Switch to Tree or Code view.
Open a JSON file or paste JSON to see it as a collapsible tree, highlighted code or a sortable table. Validate it with exact error lines, fix it in one click, query it with JSONPath and export to CSV, Excel, YAML or XML - all in your browser. Working with other data? Try the XML Viewer, YAML Viewer, CSV Viewer or the Plist Viewer for Apple .plist files.
Something went wrong. Please try again.
Still having trouble? Please contact us and we'll be happy to help!
This JSON has no list to show as a table - it is a single value. Switch to Tree or Code view.
Shortcuts: Ctrl + F search, Enter / Shift + Enter next and previous match, Ctrl + S download, arrow keys move through the tree.
JSON (JavaScript Object Notation) is a plain-text format for structured data.
It is the everyday language of web APIs, and it also stores settings, app data and exports.
A JSON file holds one value - usually an object in { } with named keys, or an array in [ ] with a list of items. Values can be text in double quotes, numbers, true, false, null, or more objects and arrays.
The format is defined by RFC 8259 and ECMA-404. Files end in .json and are served as application/json; close relatives are JSON Lines (.jsonl), GeoJSON for maps, and files like package.json or manifest.json.
Any device with a web browser can open JSON on this page - no app needed.
Right-click the file, choose Open with and pick Notepad to see the raw text. For a readable tree, drag the file onto this page in Edge, Chrome or Firefox.
Select the file and press Space for a Quick Look preview, or open it with TextEdit. To browse it as a tree, open this page in Safari or Chrome and drop the file in.
Open this page in Safari, tap browse and pick the file in the Files app. A JSON attachment from Mail or Messages can be saved to Files first.
Open this page in Chrome, tap browse and choose the file from Downloads or your file manager. It opens right here - nothing is uploaded.
Any modern browser works on Linux and Chromebooks too. In a terminal, python3 -m json.tool file.json or jq . file.json pretty-prints a file.
Open the JSON, press Export and pick a format.
CSV and Excel use the table: any list of objects becomes rows, and nested objects are flattened into columns like address.city.
YAML and XML convert the whole document, keeping the nesting. Check the result in the YAML Viewer or XML Viewer, and open spreadsheets in the Excel Viewer.
Going the other way? The CSV Viewer, Excel Viewer, YAML Viewer and XML Viewer can all export JSON. Lists can also be saved as JSON Lines, one record per line, for logs and data pipelines.
Most broken JSON comes from a handful of small mistakes.
The viewer points to the exact line and column, and Auto-fix repairs most of them:
| Mistake | Broken | Valid JSON |
|---|---|---|
| Trailing comma | [1, 2, 3,] | [1, 2, 3] |
| Single or smart quotes | {'a': 'b'} | {"a": "b"} |
| Unquoted keys | {name: "x"} | {"name": "x"} |
| Comments | // note | removed |
| Missing comma | {"a": 1 "b": 2} | {"a": 1, "b": 2} |
| NaN or Infinity | {"x": NaN} | {"x": null} |
| Python values | True, None | true, null |
| Single backslash | "C:\data" | "C:\\data" |
| Missing bracket | [{"a": 1} | [{"a": 1}] |
A hidden byte order mark (BOM) at the start trips up many parsers - this viewer removes it for you. Several objects one after another are not one JSON document, but they open fine as JSON Lines when each sits on its own line.
If the viewer says the file is binary, it is not text at all - often a ZIP, image or database with a .json name. It tells you what the file really is, so you can open it in the right tool from our file viewers.
Numbers longer than about 15 digits (some IDs) lose precision in JavaScript. The viewer warns you when that happens - store such IDs as strings.
All four store data as plain text, but they suit different jobs.
| JSON | XML | YAML | CSV | |
|---|---|---|---|---|
| Best for | APIs, web apps, settings | Documents, feeds, office files | Config files, CI, Kubernetes | Spreadsheets, data exports |
| Nesting | Yes | Yes | Yes | No - flat rows |
| Value types | Text, number, true/false, null | Text only (types via a schema) | Text, number, true/false, null | Text only |
| Comments | No | Yes | Yes (#) | No |
| Size | Compact | Verbose | Compact | Smallest |
| Open it in | This viewer | XML Viewer | YAML Viewer | CSV Viewer |
$.products[0].price, or run queries with filters in the Query tab.Drop the .json file onto this page, click browse, or paste the JSON text. It opens at once as a collapsible tree, and you can switch to highlighted code or a table.
It works on Windows, Mac, iPhone, Android and Chromebooks with nothing to install.
Open the JSON and switch to Code view - it is pretty-printed with 2 spaces and colour highlighting.
Under Options you can pick 4 spaces, tabs or minified, and sort keys A-Z. Copy the result or download it as a .json file.
Every file is validated as it opens. If something is wrong you get the exact line and column, a short explanation and the broken line with a marker.
Press Auto-fix to repair trailing commas, single quotes, comments, unquoted keys, NaN and Python values, or Show in editor to fix it by hand.
Open the JSON, press Export and choose CSV or Excel (XLSX). Any list of objects becomes rows and columns, and nested objects are flattened into columns like address.city.
Preview it first in Table view, then check the file in the CSV Viewer or Excel Viewer.
Yes. The file is read and checked in a background worker, and the tree, code and table only draw the rows on your screen, so files of 100 MB and more stay smooth.
The real limit is your device memory - very large files need a desktop browser.
JSONPath is a query language for JSON, like XPath for XML. Open the Query tab and type an expression such as $.products[*].name or $..[?(@.price > 10)] to list every match with its path.
Clicking any row in the tree also shows and copies its path.
Yes. A .jsonl or .ndjson file with one JSON value per line opens as one list you can browse, query and export.
GeoJSON, HAR, package.json, .webmanifest and source map files are plain JSON and open as they are.
No. The JSON is read and shown by your own browser and never leaves your device, so it is safe for API responses, tokens, config files and customer data.
Recent files are only remembered if you switch that option on, and only in this browser.