Developer Tools
Everyday developer utilities — format JSON, encode and decode Base64 and URLs, generate hashes and convert number bases — all client-side and instant.
About Developer Tools
This category gathers thirty-eight of the small utilities that developers open a dozen times a week and never want to install, now including a full JSON toolkit — viewer, validator and editor — and HTML, CSS and JavaScript beautifiers and minifiers. It covers formatting and inspection with the JSON formatter and JSON minifier, encoding with Base64 encode and URL encode, and debugging helpers like the JWT decoder and regex tester. If you are reading an API response, untangling a redirect chain, decoding something a log spat out, or converting data between formats, one of these will finish the job faster than writing a throwaway script.
Pick by the shape of the problem. Broken or unreadable data usually means the JSON formatter first, since it pretty-prints valid JSON and points at the spot where invalid JSON goes wrong. Data that needs to change format is a job for JSON to CSV or CSV to JSON. Anything that looks like gibberish is probably encoded: try Base64 decode, URL decode or HTML decode depending on whether you see padding characters, percent signs or entities. Timestamps that arrive as a long integer go into the Unix timestamp converter, and a cron line nobody can read goes into the cron expression parser, which spells the schedule out in English. The URL parser breaks a long link into its parts, the number base converter handles hex and binary, and the markdown previewer shows how a README will render before you push it.
What these tools have in common matters as much as what they do. They are free and need no sign-up, and they run entirely client-side: the payload you paste, the token you are inspecting and the config you are debugging stay in your browser and are never uploaded. That is the point for a developer tool — you should be able to drop a staging API response into a textarea without wondering where it went. The one thing to remember is that the JWT decoder decodes and displays a token; it does not verify its signature, so never treat a decoded token as proof of anything. For hashing, see hash and security.
Frequently asked questions
Is my data sent to a server when I use these tools?
No. These tools run entirely in your browser, so the JSON, tokens and text you paste never leave your device. The one exception is What's My IP, which by its nature has to ask a server what address your request came from.
Does the JWT decoder verify the token signature?
No. It decodes the header and payload so you can read the claims, but it does not check the signature against a secret or public key. A decoded token proves nothing about authenticity, so never use it as a security check.
Why does the JSON formatter reject my JSON?
Almost always because it is not strictly valid JSON. Common causes are trailing commas, single quotes instead of double quotes, unquoted keys, comments, or a JavaScript object literal copied from source code rather than real JSON output.
Can I use these tools offline?
Mostly yes. Once a client-side tool's page has loaded, it keeps working without a connection because the logic runs in your browser. Tools that need to look something up over the network, like What's My IP, will not.

