JSONCraft is an independent project run by one developer. This page describes how the tools and content actually get built — what runs in your browser, how each tool is verified, and what the site does and doesn't do.

What runs in your browser

Every tool on this site runs entirely client-side. JSON, YAML, CSV, TOML, and XML you paste — and any files you load — are parsed, formatted, validated, diffed, converted, and visualized in your browser. There is no upload step, no account, no server-side computation in the tool path.

Ads come from Google AdSense (publisher ID ca-pub-8761907366448308). AdSense uses cookies and shares limited data with Google's ad network when you consent. The cookie banner is a real consent gate: AdSense scripts do not load until you accept. If you decline, no ad cookies are set. Ad slots are clearly marked Sponsored.

How tool reliability is verified

Every tool is covered by an automated end-to-end test that runs on every deploy. The "Last verified — N tools passing" line in the footer is set by CI: it reflects the date of the last green run and the count of tools that passed. If a test breaks, the footer reflects that on the next build, and the broken tool is fixed before the line goes back to all-passing.

How content is written

Tool behavior is implemented and verified by hand against the source specifications: RFC 8259 for JSON, the YAML 1.2.2 spec, RFC 4180 for CSV, the TOML 1.0 spec, and the XML 1.0 / 1.1 W3C recommendations. Edge cases (BOM handling, duplicate keys, lossless round-trip) are covered by tests that pin the spec-mandated behavior.

Long-form guides under /docs/ are drafted with AI assistance and lightly reviewed before publishing. The technical facts in those guides — what a spec says, how a parser handles a corner case — are independently verifiable.

Comparison pages ("X vs Y") were previously published with light review. Those pages have been removed because the project couldn't maintain the factual bar they required without becoming a developer-tool-review site, which isn't what JSONCraft is. If a comparison page redirected you here, please use the actual products to compare them.

What the site doesn't do

• Paid placements, sponsored editorial, or guest posts. AdSense ads are clearly marked Sponsored and separate from editorial.
• Paraphrase competitor blog posts.
• Send your data anywhere. The tools work on whatever you paste or load locally; nothing leaves your browser.

How content stays current

When a spec is revised in a way that affects parser behavior, the affected tool is updated. The CI test suite catches behavioral regressions on every deploy, and visible errors are fixed on the next deploy.

Reporting errors

If you spot a factual error, a broken tool, or content that's outdated, email support@jsoncraft.dev. The operator typically replies within 24 hours on weekdays. Substantive corrections are published with a Corrected YYYY-MM-DD note next to the affected paragraph.

Funding and monetization

JSONCraft accepts no payment for tool listings, no affiliate revenue, and no sponsored editorial content. Monetization is via Google AdSense display ads (where approved) and occasional Buy Me a Coffee tips. Ad slots are clearly marked Sponsored and separate from the rest of the page.