How to Open a JSON File (Without Installing Anything)

A client of mine — a bookkeeper, sharp, runs her whole practice out of spreadsheets — once got as far as the checkout page for a $29.99 program called something like FileOpener Pro. Her new invoicing app had handed her an export.json, Windows had responded with the "how do you want to open this file?" shrug, and a search result had convinced her this was a specialist problem needing specialist software. She called me before clicking buy. The actual fix took ninety seconds and cost nothing, and it's the same fix for every .json file you'll ever meet.

So: how to open a JSON file, on any device you own, without installing anything. That's the whole agenda.

The label is scarier than the contents

Here's the thing nobody tells you at the "how do you want to open this?" prompt: a .json file is plain text. Not a database, not an executable, not some proprietary blob. Text. It's an envelope with an intimidating official stamp on the front and a perfectly ordinary letter inside — the .json extension is just the stamp, telling software what dialect the letter is written in.

That prompt appears because your computer has no default app assigned to the extension, not because anything is wrong with the file. (If you want to know what the dialect itself looks like, our primer on what JSON is covers it in ten minutes.)

You're maybe thinking your file is different — it's 40 MB, it came out of a medical records system, the export dialog had seventeen warnings. I thought that about my first one too. It's still text.

Step 1: the ninety-second version — use your browser

The fastest opener is the one already running. Drag the .json file into a browser tab, or right-click it and choose Open with → your browser. You'll see the contents immediately — Firefox even renders local JSON as a collapsible view on its own, while Chrome gives you the raw text.

Raw text is fine for a peek. It is not fine for actually finding anything, because most exported JSON arrives as a single unbroken line.

Step 2: make it readable — a viewer, not a wall of text

For a view you can navigate, copy the file's contents and paste them into our JSON Viewer. It parses instantly into a tree you can fold and unfold — click an object shut, drill into the one array you care about, ignore the other 4,000 lines. This works identically on Windows, Mac, Linux, and (this surprises people) on your phone's browser, which matters the day a .json attachment lands while you're nowhere near a desk.

If you'd rather have flat, indented text — say, to paste into an email or a ticket — run it through the JSON Formatter instead. Same data, different reading posture: the tree is for exploring, the formatted text is for quoting.

One habit worth stealing: I open every unfamiliar export in the viewer before doing anything else with it. Two minutes of folding tells you what the data actually contains, which is cheaper than discovering it later. Here's the receipt: that bookkeeper's "unopenable" file turned out to include full client addresses she didn't know her app was exporting — we caught it in the tree view before she forwarded the file to a third party.

Step 3: if you need to change it, mind your editor

Need to edit a value, not just read it? Any plain-text editor works — Notepad on Windows, VS Code if you have it. The trap is word-processor-adjacent apps. TextEdit on the Mac, in its default rich-text mode, will happily convert your straight quotes to curly ones the moment you touch the file, and curly quotes are invalid JSON. You save, the file breaks, and nothing tells you why.

The safer route for a quick edit is our JSON Editor, which validates as you type — an unbalanced bracket or bad quote gets flagged the second you create it, instead of at 2 a.m. when the import job fails.

Step 4: if it needs to end up in a spreadsheet

Half the time, "how do I open this JSON file?" secretly means "how do I get this into Excel?" Don't fight the raw text; convert it. The JSON to CSV converter turns an array of objects into rows and columns — each key becomes a column header — and the resulting .csv opens in Excel or Google Sheets with a double-click. The full Excel story, including Excel's own built-in import and when to use which, is in our guide to opening a JSON file in Excel.

When the file won't open anywhere

Sometimes the file, not the opener, is the problem. If every tool you try complains, the JSON is probably malformed — a trailing comma, a stray single quote, a truncated download. Paste it into the JSON Validator and you'll get the exact position where parsing failed, instead of a generic refusal. From there, our guide on fixing invalid JSON walks through the five mistakes that cause nearly all of it, and the viewer's Repair & clean button can fix the common ones automatically.

The one case where installing something makes sense

Fair's fair. If you're opening JSON files every day — you're a developer, or becoming one — a real editor like VS Code earns its disk space with syntax highlighting and folding built in. That's a workflow upgrade, though, not a requirement. For the file sitting on your desktop right now, the browser you're reading this in is enough.

The takeaway

Nobody needs FileOpener Pro. A .json file is a plain-text letter in an official-looking envelope: read it in your browser, explore it properly in the JSON Viewer, edit it somewhere that validates, and convert it to CSV when a spreadsheet is the real destination. Ninety seconds, zero dollars — same as it was for my bookkeeper, whose invoicing app, I'm happy to report, she still uses and no longer fears.