Developer Tools
The small utilities that come up constantly during debugging — encoding, timestamps, hashes, colours and formatters — without a round trip to a server.
Encoding, hashing, time, colour, regex and formatting utilities that come up in everyday work.
Encoding, and what each one is for
Base64, URL percent-encoding and HTML entities all make text safe to carry somewhere, but they solve different problems and are not interchangeable. Base64 turns arbitrary bytes into printable ASCII so binary can travel through a text-only channel. Percent-encoding escapes characters that have reserved meaning inside a URL. HTML entities stop markup characters from being parsed as markup.
None of them is encryption. Base64 in particular is trivially reversible, so it protects nothing — if you find a secret that is merely Base64-encoded, treat it as plaintext that has been exposed.
Why these run locally
The values developers paste into utilities like these are often exactly the values that should not leave the machine: a JWT from a staging environment, a token from a log, a hash of something sensitive. Every tool here runs in your browser, so those values are never transmitted. The JWT Decoder in particular only reads the token — it decodes the header and claims for inspection and deliberately does not verify the signature, which would require the signing key.
You can confirm this the same way you would audit any client-side claim: open the network panel and watch while you use a tool, or disconnect from the network after the page loads and keep working.
Timestamps and hashes
Timestamp conversion trips people up because the unit is rarely stated. A value around 1.7 billion is epoch seconds; the same moment in milliseconds is a thousand times larger. The converters show both alongside the ISO 8601 form and your local time so the ambiguity is visible rather than assumed. Hashes are computed with the browser’s native Web Crypto API, which means the same digests you would get from any standard implementation.