JSONBeautify JSON Linter

Changelog

JSONBeautify — Free Online JSON Formatter, Validator & Minifier Guides · Updated 2026-10-11 · All guides

A page that never changes is a page nobody maintains. This one is dated from the actual commit history rather than the build clock, so you can tell the difference between an active tool and an abandoned one.

2026-10-08

  • Ad tiers are now chosen by rendered fill, not by whether the ad tag loaded. Those are different events: a script can load successfully and still return nothing, which left empty grey boxes on the page and a layout that shifted around them. The check now waits for a real creative with non-zero dimensions. Cosmetic for a user; honest accounting for whoever reads the numbers later.
  • Sitemaps are generated from the build output, and only for domains that actually resolve. A hand-maintained sitemap drifts the moment a page is renamed, and one stale lastmod value teaches crawlers to distrust the field everywhere else on the site.

2026-10-06

  • Colour-contrast fixes to meet WCAG 2.1 AA across all pages on this domain. Muted text and the accent-coloured controls failed the 4.5:1 ratio against the dark background. That mattered here specifically because the failure modes are colour-coded — the green/red validation status and the repair result were the least readable text on the page, which is exactly the information you look at when something is wrong.

2026-10-03

  • Four guides added in one content batch: alternatives, best practices, diff tools, and patterns and gotchas. The gap this fills is the one every tool page has: the tool answers "format this," none of them answer "what should my API return for a missing field," which is a decision the formatter can't make for you.

2026-10-01

  • JSON Diff tool page (/json-diff/) added: two documents in, a path-level report out with JSON Pointer locations, capped at 64 levels deep — beyond that the subtree is reported as changed rather than recursed into forever. Related-guides blocks appeared beneath the guides at the same time, so a page points at its neighbours instead of being a dead end you have to back out of.
  • Three guides published: the cheatsheet, JSON in JavaScript, 2024–2026, and the NDJSON guide.
  • 404 and contact pages generated at build time. A 404 that returns status 200 is a soft 404, and it is one of the more common reasons a small site fails an ad-network review for a reason that is entirely avoidable. The contact page exists so "report a bug" is a route rather than a rumour.

2026-09-16

  • Sitemap lastmod values refreshed and lockfile updated. No behavioural change — this line is here precisely because a changelog that only lists interesting days is a changelog hiding something.

2026-09-15

  • ads.txt and app-ads.txt publisher records added. These declare who is allowed to sell ad space on this domain. Without them, ad buyers see an unclaimed domain, some inventory gets filtered out before it is ever bid on, and the small amount of revenue that pays for the domain and hosting quietly isn't there.

Something broken, a repair that mangled your input, or a claim on this site that is wrong? Tell me — defect reports are the most useful mail this site gets.

Developer Sponsor / Partner
Copied to clipboard!