Developer tools
Format, encode, and inspect the little things that keep work moving.
Developer tools
4 useful little tools. All free. All yours.
About developer tools
Encoding, hashing, and formatting are the small operations that sit between one system and another. Doing them in a browser tab is convenient, but most online formatters and hash tools post your input to a server, which is a genuine problem when the payload is a token, a webhook body, or a customer record. Everything here runs locally through the standard Web Crypto and text APIs.
Common reasons to reach for these
- A minified or machine-generated JSON payload needs reading.
- A query parameter has to be percent-encoded correctly.
- A Base64 blob from a log or config file needs decoding.
- A file or string needs a SHA-256 checksum to verify integrity.
Encoding is not encryption
Base64 and percent-encoding are reversible transport formats with no secret involved. Anyone holding the encoded string can decode it, so Base64 is not a way to protect a credential. Its purpose is to move binary data safely through channels that expect text. Likewise SHA-256 is a one-way digest for verifying that content has not changed, not a way to store passwords without a dedicated password hash.
Strictness and round-tripping
The JSON formatter parses with the browser's native parser, so it rejects trailing commas, comments, and single-quoted keys that some editors tolerate. That strictness is useful: if it fails here, it will fail in most parsers. Encoding tools round-trip through UTF-8, so non-Latin scripts and emoji survive an encode followed by a decode unchanged.