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.
THE TOOLBOX / DATA & DEVELOPER UTILITIES
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.
0 / 1,000,000 UTF-16 code units · 0 UTF-8 bytes
-0, duplicate keys, and escape sequences verbatim inside a local Web Worker.DEVELOPER REFERENCE
| Operation / Edge Case | Sujon Tools Behavior | Terminal Equivalent |
|---|---|---|
| Pretty-print (2 spaces) | Formats objects & arrays in a local worker | jq '.' payload.json |
| Minify / Compact JSON | Strips all insignificant whitespace | jq -c '.' payload.json |
| Sort Keys A–Z | Recursively sorts keys up to 200 levels deep | jq -S '.' payload.json |
64-bit ID (9007199254740993) | Preserved verbatim without float rounding | python3 -m json.tool |
Unlike naive JSON.parse formatters that corrupt Twitter/Discord Snowflake IDs or high-precision decimals, our lexical tokenizer keeps every numeric token intact.
Instantly pinpoints trailing commas, single quotes, unquoted keys, and raw control characters inside strings before you ship a config or API payload.
Production logs, JWTs, and customer PII stay strictly inside your browser tab with zero network requests and non-blocking worker execution.
Inspect streaming logs in JSONL Viewer, compare two payloads in Diff Checker, or decode auth tokens in JWT Decoder.
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.
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.
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.
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.
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.
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.