Base64, URL & hash tool

Text is always converted to UTF-8 bytes before encoding, which is the standard on the web, so “Çağrı” becomes w4dhxJ9yxLE=. Some older tools use Latin-1 or Windows-1254 and give different output. Decoding also reads UTF-8; if the data is not text (an image, a PDF), you can download it as a file instead.

Component (encodeURIComponent) encodes everything except letters, digits and - _ . ! ~ * ' ( ), which is right for a single query value or path part. Full URL (encodeURI) keeps characters such as : / ? & = # so that a whole address stays usable. “Spaces as +” follows the form encoding used in query strings.

Not for security. Collisions can be created for both, so do not use them to protect data or to store passwords. They are still fine for checking that a file was copied correctly. For integrity use SHA-256 or SHA-512; for passwords a dedicated slow function such as Argon2, scrypt or bcrypt is needed, not a plain hash. To create strong passwords, use Password generator.

Hashes work for files up to about 2 GB. The file is read in 8 MB pieces in a background worker, so memory use stays low and you can cancel at any time; all four hashes are calculated in one pass. Base64 conversion of files is limited to 10 MB, because the result is about a third larger and has to fit in the page.

HMAC combines a secret key with a hash to sign a message. APIs and webhooks (for example payment providers) use HMAC-SHA256 to prove that a request really came from them. Enter the key and the message here to compare a signature. For links and file names, also see Slug generator.