Tools for frontend: JSON, Base64, UUID, JWT, color
Format JSON, encode Base64, mint UUIDs, inspect JWTs, hash files and pick HEX/RGB. Local in the browser.
Paste an API body into the JSON formatter when a response looks “fine” but a client throws. Pretty-print finds the missing comma; minify is for copying into a fixture.
Base64 is for data URLs and embedding small binaries in JSON. UUID v4 is for client ids; v7 if the backend will store them as keys. JWT decode is for reading claims, not for trusting a token.
The color page copies HEX, RGB and OKLCH and shows contrast on white and black. Pair SHA-256 with a downloaded artifact when a release note publishes a checksum.
A front-end pass often needs a JSON body you can read, a Base64 asset, a UUID for a fixture, a JWT you must inspect, a hash of a file, and a colour that meets contrast. This page lists those tools in that order of a typical debug. The converters underneath each jump into one mode, such as pretty-print or SHA-256, instead of the whole studio.
FAQ
Do snippets leave the browser?
No. Formatters and the decoder run locally.
Can I verify a JWT signature?
Not here. Decode only. Verification needs the secret or public key on a server.
v4 or v7 for a new table?
v7 if you want insert-time order in the index. v4 if order must not leak.