These are the small, repetitive jobs that come up constantly while building software — formatting a blob of minified JSON so you can actually read it, decoding a JWT to see what's inside without writing a script, generating a UUID, or diffing two versions of a config file. None of them are hard problems, but they're annoying enough to context-switch for, so having them all in one place, working instantly with no install, saves the actual friction.

Everything here runs client-side in your browser — the tools don't send what you paste to a server, which matters when what you're pasting is a real API response, a token, or a connection string from a project you're debugging.

Which tool should I use?

{ }Format and validate a JSON payload

JSON Formatter

🔑Decode a JWT to inspect its payload

JWT Decoder

#️⃣Generate hashes (MD5, SHA-256, etc.)

Hash Generator

🔍Test a regular expression against sample text

Regex Tester

🔄Compare two versions of text or code

Diff Checker

🙈Generate a .gitignore for your stack

.gitignore Generator

Your files, handled carefully

Formatting, validation, encoding and hashing all run entirely in your browser via JavaScript — nothing you paste in (including API keys, tokens or credentials you're debugging) is ever transmitted to or stored on our servers.

Frequently Asked Questions

Is it safe to paste a real API response or token into these tools?

For the formatting/decoding tools (JSON Formatter, JWT Decoder, etc.), processing happens entirely client-side in your browser — nothing is sent to a server. As general practice, still avoid pasting live production secrets into any third-party tool if you can substitute a redacted sample instead.

Can I use these tools in a CI pipeline or script?

These are interactive browser tools for quick manual checks, not an API — for automation, use the equivalent library or CLI in your language of choice.

Why does JWT Decoder show the payload without needing the secret?

A JWT's header and payload are only Base64-encoded, not encrypted, so anyone can read them without the signing secret — the secret is only needed to verify the signature is valid, which is a separate step.

Do these tools support very large files?

Most handle typical development-sized payloads (up to a few megabytes) smoothly; extremely large inputs may render more slowly since everything processes in-browser.

Related guides

JWTs Explained: What's Actually Inside That Token

A JWT looks encrypted. It isn't. Here's what the three parts actually contain, and the one mistake that leaks secrets straight into them.