Encode & Hash
Base64 Encode
Base64 is how binary pretends to be text. It is not encryption, it is not compression, and it is not a way to hide an API key from anyone who can scroll. This encoder is UTF-8 aware and local, which is what you want when the string is a password reset token you should not have pasted anyway — but especially when it is just an image data URL.
Drop a file on the left. Drafts stay in this browser. Shortcut: Ctrl or Cmd + Enter to run.
How this base64 encode works
- Paste or drop a .txt file into the input on the left.
- Flip options if you see them (comments, indent, case). Defaults are the safe ones.
- Hit Run, or Ctrl / Cmd + Enter. Leave “Process on server” off unless you mean it.
- Read the status line, then copy, download, or jump to a related tool.
Use Base64 when the pipe is text
JSON, XML, HTML attributes, and email still want ASCII-safe payloads. Base64 is the boring answer. Decode on the other side with the matching alphabet. Data URLs for images belong on the Image to Base64 tool so you do not guess the mime type.
If the job is secrecy, stop. Use TLS and a real secret store. If the job is integrity, use SHA-256. If the job is a JWT, decode the claims on the JWT page and still verify signatures on a server.
Frequently asked questions
What is Base64 for?
Turning bytes into ASCII so they can live in JSON, HTML, or email. WebBeautify encodes to V2ViQmVhdXRpZnk=. Anyone can decode it. That is the point — transport, not secrecy.
Is Base64 encryption?
No. It is the same idea as writing a number in hex. If a tutorial “hides” an API key in Base64, they hid it from their own eyes only. Use TLS and a secret store for secrets.
Why does Base64 make files bigger?
Fun fact: you pay about 33% extra (3 bytes become 4 characters), plus = padding. Encode a 3 KB icon and you get ~4 KB of ASCII. That is still a win for a tiny inline image vs another HTTP request — not a win vs gzip of the original binary.
Example of padding?
Man encodes to TWFu (no padding). Shorter inputs pick up =. If a decoder yells, you probably lost the padding or used Base64URL (- _) in a standard Base64 field.
Data URLs vs raw Base64?
Images in CSS/HTML want data:image/png;base64,.... — the mime type matters. Raw Base64 is just the characters. The Image to Base64 tool adds the prefix. Do not paste PNG bytes into JSON without agreeing on the format.
UTF-8 text vs binary?
Text should be encoded as UTF-8 bytes first. é is not one ASCII byte. A decoder that assumes Latin-1 will mojibake. If a string looks fine until one emoji, you found that bug.
Base64 vs hex vs hashing?
Hex is another ASCII costume (twice as long as the bytes). Hashing (SHA-256) is one-way. You cannot decode a hash back to the logo. Different jobs on the same toolbox drawer.
When should I not Base64?
Large videos, big photos, anything that belongs in object storage. Also passwords. Also “encryption.” Also when the API already accepts multipart uploads.