Pretty-print the JSON from DevTools

Paste a payload, see the shape, convert only when the sibling matches. Formatter ≠ CSV ≠ YAML ≠ JWT.

A Slack dump that is almost JSON, a crontab that looks like Spring’s six fields, a CSV an analyst wants from an API array — developer pages here are inspect and reshape, not a SaaS IDE.

Do not open the wrong sibling

• JSON formatter pretty-prints and validates. Trailing commas and smart quotes fail for a reason.
• JSON ↔ CSV wants an array of objects. Nested objects become string cells; they are not exploded into Excel columns.
• JSON ↔ YAML is config, not a table.
• SQL and XML formatters do not execute queries or call endpoints.
• Markdown preview is a read-side render, not GitHub Flavored Markdown plus mermaid CI.
• Cron parser previews in UTC for a 5-field expression. It does not explain Quartz ? / L or a 7th year field.
• Regex tester is JavaScript RegExp in this tab — not PCRE2, not a production rate-limit.

JWT decoder lives with security: decode only, no signature verify. Code beautify is a generic pretty-print, not Prettier with your repo config.

Formatters do not execute

JSON / SQL / XML / generic beautify change whitespace. Cron is five fields, UTC — Spring’s six-field seconds-first line will not preview correctly here. JWT is decode-only; alg:none is a warning, not verification. Markdown preview is not full GFM.