Cadmeo

Code Tools for Developers

These are code tools for formatting, encoding, inspecting and styling: 45 of them, covering CSS, JSON, XML, hashes, tokens and the tags a page needs to publish. Every one runs in your browser.

45 tools

CSS and styling

Formatters and minifiers

Encoding and hashing

Web and SEO

What these code tools cover

The 45 tools split into four groups. Eighteen generate CSS, from gradients and shadows to grid and flexbox layouts. Ten format or minify code, covering JSON, XML, HTML, CSS, SQL and JavaScript. Eight handle encoding and hashing, including Base64, URL encoding, SHA-256 and JSON Web Tokens. Nine cover web and search metadata, such as robots.txt, hreflang and structured data.

Nothing here is a browser inspector panel. If you are looking for the panel that opens with F12, that is built into your browser rather than hosted on a page. These tools do the jobs you would otherwise reach for a scratch file or a throwaway script to do.

Every formatter parses before it prints, so an invalid document is reported with a line and column rather than silently mangled. The encoders handle Unicode correctly in both directions, which is where the browser btoa function fails: it works on Latin-1 and throws on any character above 255.

Formatter, viewer or validator

Three tools can act on the same JSON document and they answer different questions, which is the most common confusion in this category.

Formatter, viewer or validator, matching a situation to the tool that answers it
What you wantThe tool
Readable text to paste somewhere elseJSON formatter, which pretty-prints or minifies and hands back text
To explore a large document on screenJSON viewer, which renders a collapsible tree and counts each branch
To know why a document will not parseJSON validator, which reports the line, the column and the likely cause
To read a token without verifying itJWT decoder, which shows the claims and checks the expiry against now
To prove a download was not corruptedFile checksum calculator, then hash compare to check it against the published value
A CSS effect without writing it by handThe 18 CSS generators, each copying out a complete rule

Frequently asked questions

Is Base64 encoding a way of protecting data?

No. Base64 is a transport encoding with no key, and anyone holding the string can decode it. It exists so binary data survives channels that expect text. Use it for that, and use real encryption when the content needs protecting.

Does the JWT decoder verify the signature on a token?

No, and it deliberately cannot. Verifying a signature needs the signing secret or the public key, and pasting either into a web page would be a serious mistake. The decoder reads the header, the payload and the claims, and checks the expiry, which is what inspection usually calls for.

Will minifying my CSS or JSON break anything?

No, when the input is valid. The minifiers parse the document first and remove only whitespace and comments that carry no meaning, leaving strings untouched. Measure the compressed size before deciding it was worth it, because gzip already removes most of what minification targets.

Why does the hash of my file differ from the hash of its contents pasted as text?

Because the two inputs are different bytes. Hashing a file covers every byte including the trailing newline and any byte-order mark. Pasting the contents into a text box usually changes line endings or drops that mark, and any single-byte difference changes the whole digest.

Do these tools send my code anywhere?

No. Every tool here runs as JavaScript in your own tab, and the site has no application backend to receive anything. That matters most for the token and checksum tools, where the input is a live credential or a file you have reason to keep private.