JSON Formatter
Format, minify, validate, repair and explore JSON with tree inspector
Formatters, encoders, decoders and inspectors for the data developers paste all day.
Grouped by what you want to get done. Star a tool to find it again on the homepage.
Format, minify, validate, repair and explore JSON with tree inspector
Format, validate and convert YAML to JSON or JSON to YAML
Beautify and format SQL queries with configurable dialect and indentation
Format, minify and validate XML documents with syntax highlighting
Prettify or minify HTML markup with configurable indent size
Format or minify CSS stylesheets and SCSS/LESS snippets
Prettify or minify JavaScript and TypeScript code in browser
Encode text or files to Base64 and decode Base64 strings back to data
Encode or decode URI components and full URLs
Decode JWT header, payload, verify expiry and inspect claims
Generate RFC4122 v4 UUIDs in bulk with casing and separator options
Generate MD5, SHA-1, SHA-256 and SHA-512 hashes of any text
Generate TypeScript interfaces, Zod schemas, Go structs or Python dataclasses from JSON
Generate realistic fake JSON, CSV or SQL test data from custom field definitions
Compare two code files or text blocks and show a colour-coded diff
Query a JSON document with JSONPath expressions and see matching values live
Explain any cron expression in plain English and preview its next run times
Write Markdown in a live editor and see the rendered HTML side by side
Convert HTML to Markdown or Markdown to HTML
Search every HTTP status code with a plain-English explanation of what it means
Often used alongside these, from other categories.
The strings a developer pastes into an online tool are disproportionately production data: an API response, a signed URL, a JWT from a real session, a config file with credentials in it. That is the argument for these tools running in the tab rather than on a server, not convenience, but the fact that a formatter has no business seeing your bearer token. Everything here is parsing and printing, which is exactly the class of work a browser does well.
JSON, XML, YAML and SQL formatters have to parse the input before they can print it. If the output looks right, the syntax is valid; if it errors, the message points at the first thing the parser could not reconcile. Reaching for the formatter is often the fastest way to find a missing comma.
Base64 and URL encoding are reversible transformations with no key and no secret. A JWT's payload is Base64, which means anyone holding the token can read every claim in it. The signature is what makes a JWT trustworthy, and verifying it needs the key: decoding it does not.
A UUID v4 is random and effectively unique; a password generator is aiming at entropy against guessing; a hash is deterministic and will give the same output for the same input forever. Picking the wrong one, a hash where you wanted a random token, is a real and common bug.
Comparing two formatted JSON documents line by line reports noise whenever key order differs. Format both sides first so the comparison is between contents rather than between styles of writing the same content.