JSON formatter and validator

Shows the line, column and cause when JSON is broken, and pretty-prints or minifies it when it is not. Paste an n8n workflow and it counts the nodes and finds the keys written into it before you share it.

Input

At every level, by character code as jq -S does: capitals first, accented letters after z. Applies to Format and Minify.

Validation

Nothing yet. Paste JSON, drop a file or load the example.

Paste an n8n workflow and it counts the nodes, maps the connections and looks for keys written into the parameters.

Let’s make it yours

Need a version of this with your brand on it, wired into your own systems? Bulk jobs, an API, a panel or an automation — tell us about it and we will scope it together.

Let’s make it yours →

A JSON validator that tells you what is wrong

JSON.parse calls a trailing comma “Expected double-quoted property name” and points at the bracket after it. This tool names the actual mistake — a trailing comma, a single quote, a comment, an unquoted key, a bracket that never closes — with its line and column, and shows the line with a caret under the character. Repair fixes the common cases in one go and validates the result again.

Paste the text or drop a .json file on the editor. Format indents with two spaces, four spaces or tabs, the way any JSON beautifier would; Minify puts everything on one line, and key sorting orders every object by character code, as jq -S does. Numbers and escapes stay exactly as written, so a 19-digit ID is never rounded, and a key that appears twice is kept and reported. Nothing you paste leaves your browser.

If what you paste is an n8n workflow, the formatter becomes an n8n workflow analyzer. It counts nodes by type and lists triggers, disconnected and disabled nodes and the credentials in use. Then it looks for secrets in the n8n workflow — OpenAI, GitHub, AWS and Slack keys, tokens and passwords typed into parameters — and flags pinned customer data and the instance ID. The sanitised copy strips all of these. Webhook paths stay so the file still imports; change them before you post it.

Made by KARSH

A software company based in Erzurum and Istanbul. Web, mobile, desktop, automation and AI. karsh.app

Questions

How do I find where my JSON is broken?

Paste it. The validator checks as you type and shows the line, the column and the reason; Go to error puts the cursor right on the character.

What does Repair fix?

Trailing commas, comments, single and curly quotes, unquoted keys, Python values such as True and None, and invisible spaces. Where the intent is unclear, as with a missing comma, it does not guess; it points at the error instead.

Is my JSON uploaded anywhere?

No. Validation, formatting and the n8n analysis all run in your browser; the text never leaves your device and is not stored.

Where do I get an n8n workflow's JSON?

Open the workflow in n8n and choose Download from the ⋯ menu at the top right. Copying nodes on the canvas with Ctrl+C and pasting them here works too.

Is it safe to share an n8n workflow?

Credentials only go into the file as references. The real risks are keys typed into parameters, pinned execution data and webhook paths; the leak check finds them. The sanitised copy removes the keys, the pinned data and the instance ID; webhook paths stay so the file still imports, so change them before sharing.

More tools

[06]

Quote

MAG1 / 6

Six questions, two minutes. At the end I show you what I understood — every line is editable before it goes anywhere.

What would you like built?

Only what you type into this form, and which tool you sent it from, is stored.