Guide

THE TOOLBOX / DATA & DEVELOPER UTILITIES

Format, validate & inspect JSON,
without touching a server.

Pretty-print, validate, minify, sort keys, search, and browse JSON in Tree View locally in your browser—preserving 64-bit integers, duplicate keys, and private API tokens.

● Paste JSON or load a sample to validate and format.
0 B0 lines

0 / 1,000,000 UTF-16 code units · 0 UTF-8 bytes

Preserves 64-bit integers, -0, duplicate keys, and escape sequences verbatim inside a local Web Worker.

DEVELOPER REFERENCE

RFC 8259 precision & CLI equivalents at a glance.

Operation / Edge CaseSujon Tools BehaviorTerminal Equivalent
Pretty-print (2 spaces)Formats objects & arrays in a local workerjq '.' payload.json
Minify / Compact JSONStrips all insignificant whitespacejq -c '.' payload.json
Sort Keys A–ZRecursively sorts keys up to 200 levels deepjq -S '.' payload.json
64-bit ID (9007199254740993)Preserved verbatim without float roundingpython3 -m json.tool

1. Safe for 64-Bit IDs & Financial Numbers

Unlike naive JSON.parse formatters that corrupt Twitter/Discord Snowflake IDs or high-precision decimals, our lexical tokenizer keeps every numeric token intact.

2. Strict RFC 8259 Validation

Instantly pinpoints trailing commas, single quotes, unquoted keys, and raw control characters inside strings before you ship a config or API payload.

3. Zero-Egress Local Web Worker

Production logs, JWTs, and customer PII stay strictly inside your browser tab with zero network requests and non-blocking worker execution.

Frequently Asked Questions

Does this JSON formatter upload my API payloads or tokens to a server?

No. All JSON tokenization, validation, pretty-printing, key sorting, tree inspection, and minification run 100% locally inside your browser using a background Web Worker. Zero payloads leave your device.

Why do 64-bit integers change value in other online JSON formatters?

Most online formatters run JSON.stringify(JSON.parse(input)), which converts every number into a 64-bit float and silently rounds integers above 9,007,199,254,740,991 (Number.MAX_SAFE_INTEGER). Our lexical worker preserves exact 64-bit Snowflake IDs and -0 verbatim.

Why is my JSON failing validation on trailing commas or comments?

Strict JSON defined by IETF RFC 8259 forbids trailing commas after the final item, single-quoted strings, unquoted keys, and // or /* */ comments. Wrap all keys and strings in double quotes and remove trailing commas.

How does the interactive Tree View work?

After formatting valid JSON, click Tree View in the output header to browse nested objects and arrays as collapsible nodes with color-coded strings, numbers, booleans, and nulls.

How does alphabetical key sorting handle duplicate keys?

Enabling Sort Keys A–Z sorts object keys recursively up to 200 levels deep while preserving duplicate keys in their original encounter order and leaving array order untouched.

What is the maximum JSON file size supported?

You can paste or open local UTF-8 .json files up to 1,000,000 characters. Heavy formatting runs in a cancellable Web Worker so your browser tab stays responsive.