Base64
Decode a payload you found in a log or a request body, or encode a value that has to travel through a header.
Encoding tools for macOS
Decode what you copied, without a website.
Base64, URLs, HTML entities, JWTs and hashes — run on the clipboard, on your Mac. The strings you paste into an online decoder are usually the ones you would least like to leak.
Download on theMac App Store
Free download · macOS 14 or later
· No account required
JWT decoding
A token pasted into a website is a token you have to rotate.
Most JWT debuggers are honest about running in the browser — but you still typed a production credential into a page you did not write, on a machine you do not control the extensions of. Camel decodes the header and payload on your Mac, so the claims are readable and the token stays where it was.
- Read sub, exp and custom claims straight from the clipboard
- Check which environment issued a token before you debug the wrong one
- Nothing is transmitted, so nothing has to be rotated afterwards
Camel reads the token; it does not verify the signature. That stays with the service that holds the key.
Everything in the submenu
Encode, decode, hash.
URL encoding
Turn a wall of %20 and %2B back into a link you can read, or escape a value before it goes into a query string.
HTML entities
Encode text that has to sit safely inside markup, or decode a string that arrived with & and " baked in.
JWT decode
Read the header and payload of a JSON Web Token without handing the token to a website.
SHA-1, SHA-256, SHA-512
Hash whatever is on the clipboard when you need a checksum, a cache key or a fixture that has to match.
MD5
Still required by plenty of legacy systems and file manifests, so it is here too.
Because every action reads and writes the clipboard, the workflow is the same wherever the text came from: copy it in Terminal, a browser, an API client, a log viewer or a chat message, run the action from the menu bar or a global shortcut, and paste the result straight back into whatever you were doing.
FAQ
Good to know.
Is it safe to decode a JWT with Camel?
Decoding happens locally on your Mac and the token is never transmitted. That is the difference from an online JWT debugger, where a production token you paste has to be treated as leaked and rotated.
Which encodings does Camel handle?
Base64 encode and decode, URL encode and decode, HTML entity encode and decode, and JWT decoding for the header and payload.
Which hashes can it produce?
SHA-1, SHA-256, SHA-512 and MD5, computed from whatever is on the clipboard.
Does it verify a JWT signature?
No. Camel decodes the header and payload so you can read the claims. Verifying the signature is a job for your backend, which has the key.
Does any of this need an internet connection?
No. Every encoding, decoding and hashing action runs inside the app and works offline.
Keep tokens off other people’s servers.
Free on the Mac App Store, with 50+ other text tools in the same menu.
Download on theMac App Store