Base64 Encoder / Decoder

Base64 encodes binary data as ASCII text. It's commonly used for embedding images in HTML/CSS (data URIs), sending binary data in JSON APIs, encoding credentials in HTTP Basic Auth, and storing binary in text-only formats.

This tool handles text content. For binary files like images, use a file-to-Base64 converter. You can paste Base64-encoded data URIs to decode them back to text though.

Base64 is encoding, not encryption. Encoding transforms data into a different format that can be easily reversed — anyone can decode Base64 back to the original. Encryption uses a secret key to scramble data so only authorized parties can read it. Base64 provides zero security.

Base64 uses 64 characters (A-Z, a-z, 0-9, +, /) — that's 6 bits per character. Since each byte is 8 bits, 3 bytes (24 bits) become 4 Base64 characters. The 4/3 ratio means encoded data is about 33% larger than the original.

Base64 is more compact (33% overhead vs 100% for hex) and is preferred for data URIs, email attachments (MIME), and JSON binary data. Hex encoding is more human-readable for debugging and is commonly used for hashes, color codes, and memory addresses.

Yes. Base64 can encode any binary data including images, audio, PDFs, and executables. This tool handles text input; for binary files, you'll need a tool that reads the raw bytes. Data URIs (e.g., data:image/png;base64,...) are a common use case in HTML/CSS.

No - Base64 is a reversible encoding. Encoding converts text to a Base64 string, and decoding converts it back perfectly. It's not encryption, just a different representation.