Local-firstYour text never leaves your browser. No upload, no account, no server.
Most online text tools send whatever you paste to a server, run the work there, and send a result back. Your words sit in someone else’s logs, backups and databases, and you have to trust a privacy policy.
Local-first means the opposite: the whole tool is downloaded to your browser and runs on your own device. Nothing you type is transmitted anywhere — not to us, not to anyone. There is no server that could receive it, which is a stronger guarantee than a promise not to look.
Three consequences worth knowing:
Paste JSON and get it back indented and readable, or collapsed to a single line for a config file. If it will not parse, the error names the exact line and column rather than an unhelpful character offset, which is usually the whole reason you opened a formatter in the first place. Because it runs entirely in your browser, you can paste an API response containing customer data or an access token without it leaving your machine.
Yes, in the sense that nothing is transmitted. Parsing and formatting happen in your browser and there is no server to receive the data. Most online formatters POST your payload to a backend; this one has no backend at all.
Because JSON genuinely forbids it, even though JavaScript object literals allow it. The same applies to single-quoted keys and comments — all common in config files, none of them valid JSON.
It removes every space and newline between tokens while leaving values untouched, so the result parses identically and is usually 20 to 40 percent smaller. Use it when the JSON is going into a config value or a query string.
No. Key order is preserved exactly as parsed, and numbers, booleans and nulls keep their types rather than becoming strings. Only whitespace between tokens changes.