Developers paste an odd amount of sensitive material into random websites: production JSON with customer data, config files, API responses, code in need of a diff. Every one of those pastes is an upload to someone’s server, and none of it needs to be, because formatting, diffing, encoding, and converting are pure computation that a browser tab does locally. This pillar maps the developer tools on this site, all client-side, starting with the one used most, the JSON analyzer.
In this guide
Why client-side matters more for dev tools
The text a developer pastes into a utility is rarely lorem ipsum: it is a fragment of production, an API response with real emails, a JWT, a connection string that should never have been in the clipboard at all. “Paste your JSON here” sites built on server processing turn each of those pastes into a disclosure, and several companies have learned that policy the hard way and banned online formatters outright. Client-side tools dissolve the policy problem: the page is static, the work happens in your tab, and the network tab proves it. The same privacy logic powers the PDF family; for developer data it is not caution, it is hygiene.
The daily drivers
- JSON analyzer: validate, format, and inspect structure; the first stop for “why does my API response not parse”, expanded fully in the JSON guide.
- Diff checker: exact line-by-line comparison of two texts, the honest answer to “what changed between these configs”, a question with its own guide.
- Base64 encoder and decoder: the bytes-to-text bridge that APIs, auth headers, and data URIs all speak; where encoding ends and hashing and escaping begin is drawn out in the security basics guide.
- URL encoder and decoder: the %20 family, with the full story in the URL encoding guide.
- CSS minifier and its formatter twin: shrink for production, expand for reading.
Converters and translators
The second family translates between dialects. The curl converters take the curl command every API doc provides and rewrite it as code: curl to fetch for JavaScript, curl to Python requests, and curl to PHP, which between them cover the “the docs gave me curl, my project speaks something else” moment that opens half of all API integrations. On the data side, CSV to JSON and JSON to TSV move records between the spreadsheet world and the API world, and C# classes from JSON writes the boilerplate types a payload implies. Each conversion is mechanical, which is exactly why a tool should do it: mechanical work is where humans introduce typos.
The Unix corner
Two small tools earn their keep on any server. The chmod calculator translates between permission notations, the rwx checkboxes and the cryptic 755, a translation explained properly in the chmod guide. And the crontab generator builds schedule expressions without the field-order guesswork; cron’s five-field minilanguage deserves, and has, its own five-minute explainer. Both tools exist because their notations are write-rarely, read-rarely: nobody remembers syntax they touch four times a year, and nobody should have to.
How to verify the no-upload claim
Developers should not take “nothing leaves your browser” on faith, and the verification is pleasantly short: open developer tools, switch to the Network tab, then paste and process something. A client-side tool produces no outgoing request at the moment of processing; everything it loaded arrived with the page. The stricter version: load the page, disconnect from the network entirely, and use the tool, which works because there is nothing left to fetch. This is a sixty-second audit anyone can run on any tool claiming to be client-side, including ours, and the fact that you can run it is the point.
Frequently asked questions
Are browser tools fast enough for big files?
For the text sizes these jobs involve, easily: formatting a few megabytes of JSON or diffing long files is interactive on any modern machine. Browsers run the same class of engine your editor does; the gap closed years ago.
Why not just use my IDE for all this?
When the IDE is open and has the plugin, do. The browser tools cover the rest of life: the machine without your setup, the colleague without the plugin, the quick check mid-conversation, and the formats your editor never learned.
Is pasting a JWT or API key into a client-side tool safe?
Safer than a server-side one by construction, since the value stays in your tab. The honest answer still has a second half: secrets in clipboards get pasted in wrong windows, so rotate anything that was mishandled, whatever tool was involved.
What is the difference between the minifier and the formatter?
Direction. Minification strips whitespace for production delivery; formatting adds it back for human reading. Same information, opposite audiences, which is why the two ship as a pair.