Category

Developer tools

Format, validate, encode, hash, and inspect code data.

19 tools in this shelf

About Developer tools

The developer shelf covers data wrangling: formatting and validating JSON, XML, HTML, and SQL, minifying CSS and JavaScript, encoding and decoding Base64 and URLs, generating hashes and UUIDs, and decoding JWTs. It is for developers debugging an API response, students learning data formats, and anyone handed a wall of minified code.

A good habit is validate, then format, then transform. A validator tells you whether the data is even parseable; a formatter makes it readable; only then do minification, encoding, or hashing make sense. Formatting a broken payload first just produces nicely indented broken data.

Two tools deserve a caution. Hash generators like MD5 and SHA-256 are one-way fingerprints for checking integrity, not encryption — you cannot recover the original from a hash. And the JWT decoder reads the token's payload without verifying its signature, so it is for inspection during development, not for deciding whether a token should be trusted.

Frequently asked questions

Should I format or validate JSON first?

Validate first. The validator reports syntax errors and their position; the formatter then makes valid JSON readable. If validation fails, fix the reported error before formatting, or you will just reformat the same broken structure.

What is the difference between the JSON formatter and the JSON minifier?

The formatter expands JSON with indentation for humans to read and debug. The minifier does the opposite, stripping whitespace for the smallest payload to send or store. Use the formatter while working and the minifier when shipping.

Is a hash the same as encryption?

No. A hash is a one-way fingerprint: the same input always gives the same hash, but the hash cannot be reversed to recover the input. Encryption is reversible with the right key. Use hashes to verify that data has not changed, not to protect secrets.

Does decoding a JWT prove it is valid?

No. Decoding only reads the payload; it does not verify the signature or expiry. A decoded token can still be forged or expired, so never accept a token as trustworthy on the basis of decoding alone.