JSON ↔ Config File Tools

8 tools · free · nothing uploaded

Config formats are flat and JSON is not, so every tool here has to take a position on how nesting survives the trip. Each one exposes that choice instead of hiding it — __ or dots for dotenv, brackets or repeats for query strings — and the reverse tool reads the same convention back.

Start here

JSON → .env Flatten to KEY=value, with the quoting rules dotenv parsers actually follow. .env → JSON Read a .env back, re-nesting on __ or dots and keeping values as written. JSON → INI Sections and key = value, for anything reading an .ini or .cfg. JSON → .properties Java .properties with the Unicode escaping the format requires. JSON → query string Bracket, dot, repeat or comma nesting — the four things servers disagree about. Query string → JSON Paste a whole URL and get its parameters as structured JSON.

Everything else in Config formats

INI → JSON — INI / .cfg sections to nested JSON.
.properties → JSON — Java properties back to nested JSON.

Why these run in your browser

There is no server-side processing here and no upload step: the page loads, and from then on the parsing, converting and rendering happen in this tab using your machine's CPU. That has three consequences worth knowing about. Your data stays on your machine, which matters when the JSON is a production payload with real customer records in it. There is no file-size limit imposed by us, only by how much memory your browser will give the tab. And once the page has loaded, it keeps working with the network off.

The trade is that very large documents are bounded by browser memory rather than by a beefy server — somewhere past 50 MB a textarea gets sluggish, and dropping the file in is better than pasting it. The privacy page spells out what is and is not collected.