Launch
JSONfmt
Visit
Example Image

JSONfmt

Private in-browser JSON formatter

Visit

JSONfmt is a free JSON formatter, validator and diff tool that runs entirely in your browser: paste or drop a file to prettify, minify and validate with precise error positions, or compare two documents side by side. No accounts, no uploads, private by design.

Example Image
Example Image
Example Image
Example Image

Comments

Running entirely in the tab is the right call for formatting API payloads that may contain tokens. The precise error positions in the validator and the side-by-side diff for comparing two responses would cover most of my debugging.

Built JSONfmt because every online formatter I tried either phoned home or pushed a signup wall. Everything here runs locally in the tab.

The status line that says valid, 137 bytes, and 12 lines, next to the line numbers, is the part I would look at first when a payload will not parse. The Diff tab is what I would open when two API responses are almost the same and I do not want to upload either of them.

Does the diff ignore key order? Two API responses with the same data but keys in a different order are where most text diffs show pure noise. Also curious how it holds up with a 10+ MB file, since everything stays in the tab.

Does the validator accept JSONC, the JSON with comments and trailing commas that tsconfig.json and VS Code settings files use? Right now most validators reject those files, so a toggle for it would make JSONfmt useful for config files as well as API payloads.

One check I would want in the validator: large integers. JSON.parse silently rounds anything above 2^53, so a 64-bit ID in a payload can come back with different digits after prettify. Does JSONfmt keep the original digits, or at least warn about it? Duplicate keys are a similar trap, since most parsers keep the last value without saying so.

Formatting payloads locally matters when they contain auth tokens, so the no-upload design is a real selling point over most online formatters. The diff view would be even more useful with an option to ignore key order, since reordered keys in two API responses are what usually turn a diff into noise. A JSONC mode for tsconfig-style files would be a nice addition too.

Keeping JSON formatting fully in the browser is the right call, since people paste API responses with tokens in them all the time. A handy addition would be a sort-keys option and a clear error pointer showing the line and column of invalid JSON.

Premium Products

Comments

Running entirely in the tab is the right call for formatting API payloads that may contain tokens. The precise error positions in the validator and the side-by-side diff for comparing two responses would cover most of my debugging.

Built JSONfmt because every online formatter I tried either phoned home or pushed a signup wall. Everything here runs locally in the tab.

The status line that says valid, 137 bytes, and 12 lines, next to the line numbers, is the part I would look at first when a payload will not parse. The Diff tab is what I would open when two API responses are almost the same and I do not want to upload either of them.

Does the diff ignore key order? Two API responses with the same data but keys in a different order are where most text diffs show pure noise. Also curious how it holds up with a 10+ MB file, since everything stays in the tab.

Does the validator accept JSONC, the JSON with comments and trailing commas that tsconfig.json and VS Code settings files use? Right now most validators reject those files, so a toggle for it would make JSONfmt useful for config files as well as API payloads.

One check I would want in the validator: large integers. JSON.parse silently rounds anything above 2^53, so a 64-bit ID in a payload can come back with different digits after prettify. Does JSONfmt keep the original digits, or at least warn about it? Duplicate keys are a similar trap, since most parsers keep the last value without saying so.

Formatting payloads locally matters when they contain auth tokens, so the no-upload design is a real selling point over most online formatters. The diff view would be even more useful with an option to ignore key order, since reordered keys in two API responses are what usually turn a diff into noise. A JSONC mode for tsconfig-style files would be a nice addition too.

Keeping JSON formatting fully in the browser is the right call, since people paste API responses with tokens in them all the time. A handy addition would be a sort-keys option and a clear error pointer showing the line and column of invalid JSON.

Premium Products