About

The problem this solves

Searching for “json formatter” produces a page of results that mostly look the same: a wall of adverts, a cookie banner, a newsletter modal, and — somewhere below the fold — a text box. Paste your config into it and you have just sent your production settings to a stranger's server, because most of those tools do the work in a backend.

DevToolery was built the other way round. The tool is the first thing on the page. There are no adverts, no banner and no modal. Most importantly, there is no backend: every tool runs as JavaScript in your own browser, so what you paste never travels anywhere.

How it is built

The whole site is static files. There is no application server, no database and no logging pipeline, because none of those things are needed to format JSON. Your browser downloads some JavaScript and runs it. That architecture is why the privacy claim holds: it is not a policy we promise to follow, it is a thing the system cannot do.

You can check this. Open your browser's network panel, use any tool, and watch the request list stay empty.

What we will not do

• Add analytics that follow you between pages.
• Introduce an account system so we can email you.
• Move a tool behind a paywall once people rely on it.
• Claim a tool does something it does not — see the limitations block on every tool page.

Where the limits are

Running locally means inheriting the browser's constraints. Very large files will exhaust a tab's memory where a server-side tool would stream them. Some things are genuinely impossible here: DevToolery cannot verify a JWT signature without your key, cannot resolve a DNS record, and cannot fetch a remote JSON Schema. Each of those is stated on the relevant tool rather than quietly approximated.