Why doesn't Ctrl+Alt+J format my JSON in Sublime Text?

Pretty JSON binds Ctrl+Alt+J on Windows/Linux and Cmd+Alt+J on macOS, but only when the file's syntax mode is set to JSON. If the tab opened as Plain Text, click the language label in the bottom-right and switch to JSON. Also check that the binding has not been remapped or overridden by another plugin in Preferences → Key Bindings.

What is the difference between formatting and minifying JSON?

Formatting (beautifying) adds indentation and line breaks so nested data is easy to read and edit. Minifying removes all whitespace to produce the smallest valid JSON, which is ideal for network transfer or storage. Both keep the exact same data — only the whitespace differs.

Can I format JSON in Sublime without installing a plugin?

Sublime's built-in Reindent command (Edit → Line → Reindent) adjusts whitespace but does not parse JSON, so it cannot validate or repair broken input. For true formatting and validation you need a plugin such as Pretty JSON, or an external tool such as a browser-based JSON Formatter.

Does the browser JSON Formatter send my data to a server?

No. Parsing and serialization use the browser's native JSON engine, so your JSON never leaves the page. It is safe to format private API responses, tokens, or config files without uploading anything.

How to Format JSON in Sublime Text: Plugins and Beyond

Sublime Text has no native one-click JSON formatter, so formatting JSON in Sublime means installing a plugin like Pretty JSON or JSON Reindent — and accepting the trade-offs that come with editor extensions, shortcut conflicts, and silent acceptance of invalid input. Sublime Text ships with JSON syntax highlighting and a built-in syntax checker that flags obvious problems, but the moment you paste a minified API response, you are on your own to find a plugin, configure a key binding, and trust that the formatting step also validates the structure. Pretty JSON (Ctrl+Alt+J by default on Windows and Linux, Cmd+Alt+J on macOS) re-indents, validates, and folds; JSON Reindent only re-indents without validation, which is faster but silently keeps broken JSON; HTML-CSS-JS Prettify wraps the js-beautify engine and handles JSON when you flip its json flag to true. Each of these works in a fully set-up Sublime installation, yet every one of them assumes the input is already valid UTF-8 JSON, hides errors behind generic "parse failed" messages, and falls apart the moment a comment, trailing comma, or single-quoted string slips in. That gap is exactly where a browser-side tool that combines formatting, minification, and line-and-column error reporting becomes the safer fallback.

What Sublime Text Actually Gives You for JSON

Out of the box, Sublime Text recognizes the .json extension and applies the JSON grammar, which gives you syntax highlighting and a basic syntax check on save. There is no menu command, no default key binding, and no profile setting that beautifies a JSON document. The closest built-in feature is the Reindent command under Edit → Line → Reindent, which adjusts indentation based on the current file's tab width but performs no parsing — it happily re-indents strings, comments, and broken structures alike.

If you open a file that Sublime does not recognize as JSON (a clipboard paste into a new tab, for instance, often lands as "Plain Text"), the formatting plugin commands will refuse to run. The fix is to click the language label in the bottom-right status bar and switch to JSON explicitly. This is the first trap: people paste, press the shortcut, see nothing happen, and assume the plugin is broken when in fact the syntax mode is wrong.

Sublime JSON Plugins Worth Installing

Three plugins cover almost every Sublime JSON workflow. Pick based on whether you also want validation.

Plugin	Validates JSON?	Default shortcut	Best for
Pretty JSON	Yes (raises a dialog on parse error)	Ctrl+Alt+J / Cmd+Alt+J	Everyday reformatting of files you trust
JSON Reindent	No — only re-indents	Often unbound or Ctrl+Shift+J	Speed on already-validated payloads
HTML-CSS-JS Prettify	Yes (via js-beautify)	Ctrl+Shift+H	Projects that also touch JS, CSS, and HTML

Install any of them through Preferences → Package Control → Install Package, then search by name. Pretty JSON is the most popular pick because it combines beautification, validation, and folding in one shortcut. JSON Reindent is the lightweight alternative when you have already validated the payload with another tool — for example, after running python -m json.tool yourfile.json on the command line. HTML-CSS-JS Prettify needs its json setting flipped to true in the plugin preferences before it will touch JSON files; otherwise it silently skips them.

Limits and Pitfalls of Plugin-Based Formatting

Plugin-based formatting has three recurring failure modes that are easy to miss until they bite.

Shortcut conflicts. Pretty JSON's default Ctrl+Alt+J overlaps with a built-in Sublime binding on some platforms and with other plugins. When the shortcut stops working, the fix is to open Preferences → Key Bindings and remap it to something like Ctrl+Alt+F or Ctrl+Shift+I.
Silent acceptance of bad JSON. JSON Reindent does not parse — it only adjusts whitespace. If you feed it a string with a trailing comma, it returns text that looks formatted but is still invalid. Pretty JSON pops a dialog on parse errors, which is more helpful, but the dialog text is short and lacks line or column numbers.
Encoding assumptions. Pretty JSON and HTML-CSS-JS Prettify both assume the document is UTF-8. Files saved with a byte-order mark (BOM) or in another encoding can produce odd indentation, broken characters, or a hard parse failure with no clear pointer to the offending byte.

None of these are deal-breakers on a clean, well-configured workstation, but they explain why a Sublime-only workflow sometimes feels fragile, especially on borrowed machines, in CI environments, or when handing a JSON document to a teammate whose setup differs from yours.

Format JSON in Your Browser with JSON Formatter

When the editor path gets in the way, the fastest reliable option is a browser-side JSON Formatter that formats, minifies, and validates in the same pass — and reports the exact line and column when something is wrong.

Paste or type your JSON into the input box.
Pick an indent style (2 spaces, 4 spaces, or Tab), then click Format to beautify — or click Minify to compress it to a single line.
If the JSON is invalid, read the line and column shown in the error and jump back to your editor to fix it; otherwise copy the formatted or minified result with the Copy button.

Because the tool uses the browser's native JSON parser and serializer, the output is canonical JSON that round-trips losslessly — only the whitespace changes. Minifying strips every space and newline so the payload is as small as possible for network transfer or storage; formatting restores newlines and indentation so nested objects and arrays become readable. Everything happens locally: the JSON never leaves the page, so it is safe to format API responses, access tokens, or private config without uploading data to a backend.

Why JSON Fails to Validate (and How to Fix It)

JSON is standardized as RFC 8259 and ECMA-404, which is stricter than JavaScript object literals in a few common ways. Most "why won't this parse" moments trace to one of these.

Mistake	Looks like JavaScript?	Valid in JSON?
Trailing comma after the last item	Yes	No
Single-quoted strings or keys	Yes	No — JSON requires double quotes
Unquoted object keys	Yes	No — keys must be quoted strings
Comments (// or /* */)	Yes	No — JSON has no comments
undefined, NaN, Infinity, Date	Yes	No — only six value types exist

The browser formatter points to the first problem with a precise line and column, which turns a fifteen-minute hunt into a two-second fix. One subtle limit worth flagging is not a bug in the formatter but a property of JavaScript itself: integers are parsed as IEEE-754 doubles, so any value larger than 9,007,199,254,740,991 (Number.MAX_SAFE_INTEGER) loses precision. A snowflake ID like 12345678901234567890 comes back as 12345678901234567000. If exact large integers matter — Twitter/X IDs, 64-bit database keys, invoice numbers above nine quadrillion — keep them as strings in your JSON rather than bare numbers.

A Practical Workflow for Sublime JSON Tasks

The honest answer is to use both. Keep a JSON plugin installed in Sublime for the 80 percent of cases where the input is already valid and you just want to tidy it up before saving; open the JSON Formatter in a browser tab the moment a payload refuses to parse, the encoding looks suspicious, or you need to minify before pushing to a server. Because the formatter is stateless and runs locally, it works on locked-down machines, guest profiles, and CI runners where installing a Sublime plugin is not an option.

For debugging sessions, formatting is what you reach for — a 5,000-character single-line response becomes a browsable tree the moment it is pretty-printed. For shipping, minifying is not just cosmetic: stripping indentation can shrink a typical API payload before gzip compression, which matters on mobile clients and metered connections. Both directions round-trip through the same engine, so the structural data is preserved exactly while only the whitespace changes.

Typical day-to-day uses cover debugging an API response, cleaning up a config file such as package.json or tsconfig.json, shrinking a payload before storage, and simply checking whether a blob is valid JSON at all before feeding it to code. Keeping the browser formatter as a fallback means the difference between a stuck Sublime session and a finished task in roughly the time it takes to paste, click, and copy.