Base64 Encoder & Decoder
Encode and decode UTF-8 text using standard Base64 or the URL-safe alphabet locally.
Text and encoding
Processed locally in your browser. No uploads or external requests. Up to 200,000 input characters. UTF-8 text only; decoding arbitrary binary data is not supported. Base64 is not encryption.
Converted output
Understand your results
For developers inspecting text payloads and URL-safe encoded values.
Encoding converts text to UTF-8 bytes and then the Base64 alphabet. Decoding validates the chosen alphabet and reconstructs UTF-8 text. For example, café and an emoji can round-trip without the Latin-1 limitations of calling btoa directly on Unicode text. Base64URL substitutes - and _ for + and / and omits padding on output.
How to use this tool
- Choose standard Base64 or Base64URL and the correct conversion direction.
- Paste the text or encoded value and run Convert.
- Review the output, then copy or download the text result.
What the observations mean
Standard and URL-safe Base64 encode the same bytes using different alphabets. Successful decoding establishes text validity, not trust or safety.
Worked example
Encode a short UTF-8 text value and decode it again.
Text: Hello
Standard Base64: SGVsbG8=Encoding Hello produces SGVsbG8=. Decoding that standard Base64 restores Hello. Base64URL mode uses its own alphabet/padding convention for contexts that need it.
Limits and processing
Up to 200,000 input characters, locally processed as UTF-8 text. Invalid alphabets, padding bits or malformed UTF-8 fail instead of silently corrupting data. Base64 is encoding, not encryption; arbitrary binary files are outside this text tool.
Common problems and practical fixes
- Wrong alphabet
- Select Base64URL for -/_ input and standard Base64 for +/ input.
- Padding rejected
- Check copied text for missing characters, misplaced = signs or noncanonical trailing bits.
- Binary output
- Use a binary-aware decoder if the payload is not UTF-8 text.
Best practices
Keep secrets out of shared examples; encoding does not make sensitive data safe to publish.
Practical tips
- Base64 is reversible encoding, not encryption, compression or access control.
- Choose the alphabet your consumer expects. Whitespace in encoded input is ignored; malformed padding and trailing bits are rejected.
- Only UTF-8 text decoding is supported. Images, archives or arbitrary binary data require a binary-aware workflow.
Frequently asked questions
Practical answers for using the Base64 Encoder & Decoder.
Can I encode emoji and non-English text?
Yes. TextEncoder and a fatal UTF-8 TextDecoder preserve supported Unicode text; malformed surrogate input is rejected.
Why does decoded data fail as UTF-8?
A syntactically valid Base64 value can represent binary bytes rather than text. This tool reports that distinction rather than replacing invalid bytes silently.
Is there an input limit?
Yes. Each operation accepts up to 200,000 input characters. No file is uploaded or read into memory by this tool.