Cron Expression Explainer
Read back, in English, when a cron runs.
Never uploadedFormat, validate and minify JSON. Errors point at the exact character.
Or load the sample. Nothing is uploaded - this runs in your browser.
Two spaces, four spaces, or minify to strip whitespace entirely.
The formatted result updates as you type, with size before and after.
No. Parsing and formatting happen in your browser with the built-in JSON engine, so you can paste production payloads, API responses or anything containing credentials without it leaving your machine.
That's the browser's own parser telling you exactly which character broke it. Count to that offset in your input - it is almost always a trailing comma, a single quote instead of a double, or an unquoted key.
All insignificant whitespace and newlines. The data is identical; it just stops being readable. Useful for shrinking a payload before embedding it somewhere.
No, and deliberately. Those are JSON5/JSONC extensions, not JSON. If a parser accepted them here you would find out the hard way when a stricter one rejected your file.
Format, validate and minify JSON entirely inside your browser. Because parsing uses the browser's own JSON engine rather than a server, you can safely paste API responses, config files and payloads containing tokens - none of it travels anywhere. Syntax errors report the exact character offset, which is usually enough to spot the real culprit: a trailing comma, a single quote where a double belongs, or an unquoted key. Comments and trailing commas are rejected on purpose, because they are not valid JSON.
The last couple are from other categories - there are 81 tools here in total.
Read back, in English, when a cron runs.
Never uploadedReadable SQL across five dialects.
Never uploadedEncode or decode Base64, UTF-8 safe.
Never uploadedRead a token's header and claims locally.
Never uploadedGitHub-flavoured markdown to clean HTML.
Never uploadedShrink PDFs to fit email, chat, or upload limits.