Text & encoding tools
Decode a bearer token, encode Base64, compute hashes, test regex, compare two documents, or clean up a long list. All of it runs in the browser including the tokens you shouldn't be pasting into someone else's site in the first place.
Files are processed on your own device nothing is uploaded to a server.
- Base64 encode & decodeText or files, with a URL-safe variant and data URI output included.
- URL encode & parserEncode and decode addresses, or take a URL apart into host, path, and a parameter table.
- Escape & entitiesHTML entities, JSON strings, backslashes, and CSV fields both directions in one place.
- Number base converterBinary, octal, decimal, hexadecimal, plus text to byte sequences and back.
- Decode bearer tokenRead a JWT down to its time claims and check its signature the token goes nowhere.
- Hash & checksumMD5, SHA-1, SHA-256, SHA-384, and SHA-512 of text or files, ready to compare.
- Regex testerTest a pattern against real text, inspect its capture groups, and try the replacement.
- Compare textSee which lines were added and removed between two versions, side by side.
- Format & validate JSONPretty-print or minify JSON, sort keys, and find errors down to the line and column.
- Clean up listsSort, drop duplicates and blank lines, add numbering, or join everything into one line.
- Change case & slugTitle Case, camelCase, snake_case, all the way to a slug that's safe for a URL.
- Word & character countCharacters, words, sentences, paragraphs, and estimated reading time updating as you type.
- Password generatorStrong passwords from the browser's cryptographic randomness, with the entropy spelled out.
- UUID & random IDsUUID v4 in bulk, or random strings for API keys and filenames.
- Placeholder textClassic lorem ipsum, or Indonesian-language text to fill out a design.
- Unix time converterEpoch numbers turned into readable dates the natural companion to a token's exp claim.
Related tools
Questions that come up often
What people most often ask before handing over a file privacy, size limits, and when quality actually drops.
Where does the text I paste end up?
Nowhere. Text tools get used most often for exactly the most sensitive things access tokens, file hashes, snippets of config so all of it is handled inside your browser. What you paste isn't stored, isn't logged, and never appears in the page's address.
Is it safe to paste a bearer token here?
It is, because the token goes nowhere. It's decoded inside the tab and no network request carries its contents you can confirm that in the Network tab of DevTools. That said, a token that has already leaked elsewhere should still be revoked.
Base64 is encryption, right?
It isn't, and this matters. Base64 is only a way of rewriting data so it survives being passed around as text anyone can reverse it without any key at all. Never use Base64 to hide something.
Where is the hash computed?
On your device, using the browser's Web Crypto. Even large files are read from disk in chunks, so checksumming a few hundred megabytes doesn't upload anything.
Why is my JSON rejected when it looks fine?
Usually because of something you can't see: a trailing comma on the last element, curly quotes pasted in from a document, or a comment, which JSON simply doesn't allow. The JSON tool points at the line and column, so there's nothing to guess.
Are the passwords generated here stored anywhere?
No. They're generated on your device, never sent to a server, never stored, and never appear in the page's address. Closing the tab erases them completely so copy one into your password manager first.