Converters
Base64, hex, URL, Unicode, hashes, JWT and QR codes. Everything runs in your browser, nothing is sent to a server.
Text and base64
Type in either field, the other one updates. Text is encoded as UTF-8, so Cyrillic and emoji come out the same as in Python and Go.
File to base64
Hashes, Base64, JWT and QR code
All the tabs compute in the browser. The CSP policy lets this page connect only to its own site, so nothing you enter leaves it. MD5, SHA-1, SHA-256 and SHA-512 hashes are computed for text and for a file: a file up to 256 MB is read whole, a larger one in 8 MB chunks.
Base64 only changes how bytes are written, there is no key: every 3 bytes become 4 characters. A JWT is decoded from base64url, and the exp, iat and nbf times are shown as dates in the browser's time zone. The QR code is built on the page and downloads as a PNG up to 2048 pixels or as an SVG.
Examples
- The MD5 of the string "hello" is 5d41402abc4b2a76b9719d911017c592. That pair sits in the databases of "decrypter" sites, and given the hash they return "hello". The hash of a random 16-character password is not in such databases.
- The word "Привет" takes 12 bytes in UTF-8, and in Base64 it is 0J/RgNC40LLQtdGC, 16 characters.
- A network "Dacha" with the password kot;123 gives the string WIFI:T:WPA;S:Dacha;P:kot\;123;; The semicolon in the password is escaped with a backslash; without it the phone would read the password as "kot".
Common mistakes
- People check the checksum by the first and last characters. The "Compare with the checksum from the site" field compares the whole string, and a match of a few characters proves nothing.
- People store passwords as MD5 or SHA-1. Those are fast hashes, and a leaked database is brute-forced on graphics cards; passwords need bcrypt, scrypt or Argon2.
- People hide keys and passwords in a config as Base64. The string decodes without a key.
- People put secrets in JWT data. Anyone who has the token can read its header and payload; the signature protects them from edits and doesn't hide them.
FAQ
- Can MD5 or SHA-256 be decrypted?
- No, a hash has no inverse operation. "Decrypter" sites look the hash up in their own databases of ready-made "string and its hash" pairs and find only what is already in them: common passwords, dictionary words, short character sets.
- How do I check the checksum of a downloaded file?
- On the "Hashes" tab choose the file and paste the checksum from the site into the "Compare with the checksum from the site" field. The algorithm is detected by length: 32 characters for MD5, 40 for SHA-1, 64 for SHA-256, 128 for SHA-512; case and spaces don't matter, and a line from sha256sum works too. On Windows the same checksum is computed by the command certutil -hashfile file SHA256.
- Is Base64 encryption?
- Base64 only changes how bytes are written, there is no key. The Base64 tab on this page or the command base64 -d decodes the string. Text under a password is encrypted with AES-256 on the "Text encryption" page.
- Is it safe to paste a JWT into an online decoder?
- Until its exp time passes, a token gives access to the account, so paste it only where it doesn't go out over the network. Here the token is parsed in the browser, and the page makes no requests. The signature is not verified: that needs the secret or the public key.
- How do I make a Wi-Fi QR code so the password doesn't go to someone else's server?
- On the "QR code" tab choose Wi-Fi, and enter the network name and password. The string WIFI:T:WPA;S:name;P:password;; and the code itself are built in the browser, and the password is not sent to the server. For a WPA3-only network the field R:1 is added, for a hidden one H:true.
You might also need
Hash and checksum
MD5, SHA-1, SHA-256, SHA-512 of text and files, checksum comparison
Wi-Fi QR code
QR code for a network or a link, PNG and SVG, the password stays in the browser
Text encryption
encrypt with a password or hide it inside an image
Passwords
generator and leak check without sending the password anywhere