Free tool · No sign-up · Nothing leaves your browser
Free hash generator and Base64 encoder
Make MD5, SHA-1, SHA-256, SHA-384 and SHA-512 hashes of text or files, encode and decode Base64 and web addresses, and read what is inside a JWT. Everything runs in your browser.
Hashed as UTF-8, exactly as typed. A space or line break at the end changes every hash.
Up to 200 MB. The file is read on your device and never uploaded.
Used to sign webhooks and API requests. Leave it empty to skip.
Hashes of empty text
- MD5 Not for security use
- SHA-1 Not for security use
- SHA-256
- SHA-384
- SHA-512
- HMAC-SHA-256
MD5 and SHA-1 are broken: use them only to spot accidental changes, never for passwords, signatures or certificates. For anything new, use SHA-256.
Type or paste here to encode.
Or paste Base64 here to decode it.
File to Base64
An image, icon, font or any file up to 10 MB. It is read on your device and never uploaded.
Use encodeURIComponent for a single value you add to an address, such as a search term or a page to return to after login: it encodes / ? & = and # too. Use encodeURI on a complete address: it keeps those characters, so the address still works, and only encodes spaces and characters that cannot appear in a URL. Form data writes spaces as +, which decodeURIComponent leaves as it is.
This decodes the token in your browser and sends nothing. It does not verify the signature, so a token that reads fine here may still be forged, altered or revoked. Tokens are secrets: never paste a live token into a site you do not trust.
Paste the whole token: three parts separated by dots. "Bearer" in front is removed.
Header
Payload
Times and standard claims
What a hash is
A hash function turns any input, from one word to a 4 GB video, into a short fingerprint of fixed length. The same input always gives the same hash, and changing a single character changes it completely. You cannot turn a hash back into the input. That makes hashes useful for checking that a download arrived intact, that two files are identical, or that a webhook really came from the service that signed it.
Which hash to use
- SHA-256 is the default choice for checksums, file integrity and, as HMAC-SHA-256, for signing webhooks and API requests.
- SHA-384 and SHA-512 give longer outputs. Use them where a standard or a service asks for them.
- MD5 and SHA-1 are not safe for passwords, signatures or certificates. Researchers can create two different files with the same hash. They are still fine for spotting accidental changes and for matching old published checksums.
Never store passwords as a plain hash of any kind, not even SHA-256. Use a slow, salted password hash such as Argon2id or bcrypt, which most frameworks provide; in PHP it is password_hash(). To make strong passwords in the first place, use the password generator.
Base64 and URL encoding are not encryption
Base64 turns bytes into plain characters so they can travel in email, JSON or a data URI inside HTML and CSS. Anyone can decode it. URL encoding swaps characters that have a meaning in web addresses, such as spaces, &, ? and #, for % codes, so a value cannot break the address it sits in. That matters when you build tracking links with the UTM builder or write rules with the redirect generator.
Reading a JWT safely
A JSON Web Token has three parts: a header, a payload and a signature. The first two are only Base64url-encoded, so anyone holding the token can read them. This tool shows them with readable dates and tells you if the token has expired. Reading is not verifying: only the server with the key can check the signature. Treat a live token like a password, because whoever holds it can act as you until it expires.
Working on structured data too? The schema generator writes valid JSON-LD for your pages.
Questions
Can a hash be turned back into the text?
No. A hash is one-way. But short or common inputs, such as most passwords, can be looked up in huge precomputed tables, which is why a plain MD5 or SHA-1 of a password is unsafe. Passwords need a slow, salted password hash such as Argon2id or bcrypt.
Why does my hash not match another tool?
Almost always a hidden difference in the input: a space or line break at the end, Windows line endings, or a different text encoding. This tool hashes text as UTF-8, exactly as typed, with each line break as a single newline character. For an exact match on a file, hash the file itself.
Is MD5 still safe to use?
Not for anything security related. Researchers can make two different files with the same MD5 or SHA-1 hash, so neither can prove a file or signature is genuine. Both are still fine for spotting accidental changes, such as checking a download against a published MD5 checksum.
Is Base64 a form of encryption?
No. Base64 only rewrites bytes as letters, digits and a few symbols so they survive email, JSON and web addresses. Anyone can decode it in a second, so never use it to hide a password or an API key.
Is it safe to paste a JWT here?
This page decodes the token in your browser and sends nothing to Clixcel. Still, a live token works like a password until it expires, so prefer test or expired tokens, and never paste one into a site you do not trust.
Are my files uploaded?
No. Files are read in your browser with the File API and never leave your device, for both hashing and Base64.
Need developers who get security right?
We build websites, web apps and integrations with safe logins, signed webhooks and secrets kept out of the code.