Formatting JSON in Notepad++ no longer requires installing a third-party plugin, because Notepad++ ships with built-in menu actions and modern companion tools that parse, beautify, and minify any JSON document in the current buffer. The classic recipe — drop the JSON Viewer plugin through Plugin Manager — broke in 2019 when Notepad++ 7.7 retired the bundled Plugin Manager list, leaving JSON Viewer and JSTool behind manual downloads that often fail to load on 64-bit builds and rarely update alongside the editor. Today the most reliable path is a hybrid: keep Notepad++ for editing and language highlighting, but hand the JSON to a browser-based formatter when it is time to beautify, minify, or find that one missing comma. The JSON Formatter does exactly that work — no installation, no restart, no plugin updates — and the parsed JSON stays in your browser tab rather than travelling to a remote API. This guide covers both workflows so you can choose whichever fits the moment: an in-editor action when the JSON is small and well-formed, a paste-and-copy round trip when it is large, awkwardly quoted, or stubbornly invalid.
Why the Notepad++ Plugin Approach Stopped Working
For most of Notepad++'s history, "how to format JSON in Notepad++" had one answer: open Plugins → Plugin Manager → Show Plugin Manager, install JSON Viewer, restart, then hit Plugins → JSON Viewer → Format JSON. Two releases after that recipe became muscle memory, the editor's maintainer retired the Plugin Manager list in Notepad++ 7.7 to fight malware-loaded plugin mirrors. The JSON Viewer and JSTool plugins still exist on GitHub, but installing them now means downloading a 32-bit or 64-bit DLL, dropping it into %AppData%\Notepad++\plugins, restarting the editor, and hoping the .dll ABI matches your build. The 64-bit Notepad++ experience — the default since v8 — is that the plugin copies into the right folder and silently refuses to load, because the editor logs "API: Can't load plugin" and offers no upgrade path. For a deeper walk through the surviving plugin-based options, the format JSON in Notepad++ plugins and alternatives guide covers the active forks.
There is also a fallback that does not require any plugin. Notepad++ ships with a JSON language definition that supplies syntax highlighting and brace matching, and the menu bar exposes Plugins → JSTool → JSFormat on systems where the JSTool plugin happens to ship. The action runs a tidy pass over the buffer, but it does not validate, does not report line and column on failure, and treats JavaScript object literals as input rather than the stricter JSON grammar — so a trailing comma survives a JSFormat pass and breaks the very next JSON.parse. These are the rough edges the JSON Formatter tool exists to clean up.
The Two Reliable Workarounds Inside Notepad++
When the JSON lives in a buffer you do not want to leave, two editor-side moves still work without any third-party plugin. The first is to set the Language menu to "JSON" so Notepad++ applies its JSON tokenizer; that gives you accurate brace matching, fold points on objects and arrays, and a clear visual difference between strings, numbers, and unquoted keys — which alone catches a surprising share of authoring mistakes. The second is the macro approach: open Macro → Start Recording, press Ctrl+Shift+Home to select the buffer, run Plugins → JSTool → JSFormat when the plugin is present, save the macro, then bind it to Ctrl+Alt+J via Settings → Shortcut Mapper → Macro commands for one-keystroke reformatting.
Both of these are reasonable, but neither tells you where an invalid JSON document is broken. For that you need an actual parser. The cleanest division of labour is: edit and scan in Notepad++, validate, beautify, and minify in a dedicated tool. Paste the buffer into the JSON Formatter, pick an indent, click Format, copy the result, and paste it back over the original. The whole round trip takes longer to describe than to perform.
Format, Minify, or Validate JSON in Your Browser
Open the JSON Formatter in any modern browser tab and the interface drops you straight into a single input box — no project setup, no npm install, no waiting on a build step. The complete in-editor flow for turning minified or noisy JSON into a readable document is:
- Paste or type your JSON into the input box on the JSON Formatter page.
- Pick an indent style — 2 spaces, 4 spaces, or a tab — that matches the surrounding code style in your Notepad++ buffer.
- Click Format to pretty-print the JSON with the chosen indent, or click Minify to compress the same data back onto a single line.
- Read the parser error and the line and column it points to if the input is invalid; otherwise click Copy and paste the formatted or minified result back into your Notepad++ buffer.
Indenting with the same style your team already uses matters more than it sounds, because a 2-space-beautified JSON file dropped into a tab-indented codebase produces noisy diffs on every save. The tool preserves structure and values exactly; only whitespace is changed. If you paste a payload that contains a Twitter-style 19-digit snowflake ID, keep that value as a quoted string on the way in — JavaScript parses any integer above 9,007,199,254,740,991 as a double, and the formatter will faithfully reflect that precision loss.
When to Format vs When to Minify
Formatting and minifying are not interchangeable. They produce the same canonical JSON, but they serve opposite purposes, and choosing the right one is what makes the difference between a 5,000-character log line and a readable tree.
| Goal | Action | When it fits |
|---|---|---|
| Reading or debugging a payload | Format with 4-space indent | Inspecting an API response, tracing a config issue, reviewing a teammate's pull request diff |
| Matching a project's existing style | Format with 2-space or tab indent | Saving alongside other source files that already use that indent |
| Cutting payload size before transfer | Minify to a single line | Embedding JSON in a URL fragment, storing it in a single DB column, posting to a webhook |
| Reducing bundled static assets | Minify then let gzip handle transport | Mobile clients on metered networks, dashboards that ship JSON as a static file |
The size drop from minification alone is substantial before compression; HTTP compression picks up the rest. For an in-editor debugging session in Notepad++, the right pick is almost always Format. For a payload that is leaving your machine, the right pick is almost always Minify.
Pinpointing JSON Errors by Line and Column
The reason a formatter is worth opening for a document you could otherwise scan by eye is that it replaces "I think there is a stray comma somewhere in here" with "line 47, column 12". When you click Format on invalid input, the JSON Formatter stops parsing at the first syntax error and surfaces the message plus the exact position. That position lands you inside Notepad++ on Ctrl+G → Go to line, ready to fix.
The handful of errors this catches cover most real-world cases. A trailing comma after the last item in an object or array is legal JavaScript and illegal JSON. Single-quoted keys and values are legal Python and legal JavaScript, illegal JSON. Unquoted object keys are legal in either of those languages, illegal in JSON. Stray line or block comments copied out of source code break every JSON parser because JSON has no comment syntax. Each of these is a two-second fix once you see them highlighted by an actual parser rather than guessed at by scrolling.
The JSON Rules That Trip People Up
JSON is a much stricter format than the JavaScript object literal syntax it descended from. The JSON Data Interchange Format, RFC 8259, pins the grammar to six value types — object, array, string, number, boolean, and null — and forbids the rest. That means no undefined, no NaN, no Infinity, no Date objects, and no functions. Strings must use double quotes and must escape control characters; the whole document must be a single top-level value, which an array of values or a single object satisfies but a bare string does not for many parsers.
Keeping those rules in mind turns almost every "why won't this parse" moment into a quick scan. The remaining edge case lives in numbers: JSON's number grammar places no upper bound, but the JavaScript engine that powers most browser-based formatters parses with IEEE-754 doubles, and any integer above Number.MAX_SAFE_INTEGER loses precision. If your schema includes big IDs, write them as strings in the source JSON — that one habit prevents the kind of bug that survives testing and only surfaces in production.
The Notepad++ side of the workflow stays cheap: keep the file in the buffer, run a Format pass through the JSON Formatter, paste the canonical version back, and save. No plugin manager, no DLL juggling, no editor restart.
If you're weighing options, How to Minify a JSON File Without Losing Data covers this in detail.