The result differs from another encoder
confirm both tools use UTF-8 and compare normalization, BOM and line endings.
Convert UTF-8 text to Base64
Encode UTF-8 text as standard or URL-safe Base64 while preserving the source representation. Review, copy or download the result.
Base64 utility · Fast, exact Base64 conversion
What this tool does
This page encodes UTF-8 text into Base64 without applying format-specific validation or transformation. Use Standard or URL-safe output according to the receiving protocol, then copy or download the value.
Convert now
1
Enter or upload
Paste text or choose a file
2
Choose an action
Encode, decode or inspect
3
View results
Review output and byte details
1. Input
0 characters
2. Action
3. Output
0 characters
4. Quick actions
5. Base64 information
DescriptionBase64 represents bytes as text; it is not encryption.
AlphabetA-Z, a-z, 0-9, +, /, =
Input size0 characters / 0 bytes
Output size0 characters / 0 bytes
PaddingUses = to complete a four-character group.
StatusReady
How it works
Input bytes
101010 111100 110101 ...
Split into 6-bit groups
101010 111100 110101 ...
Convert to indexes
42 60 53 ...
Base64 characters
q 8 1 ...
How to convert UTF-8 text to Base64
Paste the UTF-8 text source exactly as it should be encoded.
Keep Encode selected and choose the output option shown by the tool.
Review the output and byte information, then copy or download the result.
Output and format behavior
Text is converted to UTF-8 bytes and then Base64-encoded. Unicode characters can occupy several bytes, so character count and byte count are not the same.
Use Standard Base64 for the normal RFC 4648 alphabet. Use URL-safe only when the receiving system expects Base64URL; padding rules can differ by protocol.
Expert tip
Compare byte count rather than character count when checking Base64 size; emoji and many non-Latin characters use multiple UTF-8 bytes.
When this is useful
Typical workflows include:
- Encode or recover multilingual UTF-8 text without treating visible characters as single bytes.
- Prepare an exact payload for an API request, webhook fixture or integration test that expects Base64 text.
- Place a value in a configuration field that accepts text but not arbitrary bytes or line breaks.
Limitations and safety
Important constraints:
- Base64 normally adds about one third to the byte payload, before any data-URL prefix or surrounding markup.
- Base64 is reversible encoding, not encryption. Anyone who receives the string can decode the original bytes.
- Text is converted through UTF-8 bytes. Character count and byte count can differ, especially for emoji and non-Latin scripts.
Troubleshooting
Emoji or accented text looks wrong after decoding
the receiving side may be interpreting UTF-8 bytes with another character set.
Frequently asked questions
What exactly is preserved?
Text is converted to UTF-8 bytes and then Base64-encoded. Unicode characters can occupy several bytes, so character count and byte count are not the same.
How are Unicode characters handled?
Text is represented as UTF-8 bytes. A visible character may use multiple bytes, which is expected and affects the Base64 length.
What is the difference between standard Base64 and Base64URL?
Standard Base64 uses + and /. Base64URL uses - and _ and may omit padding; choose the form required by the receiving system.
Why do emoji or non-Latin text produce longer Base64?
They often use multiple UTF-8 bytes per visible character. Base64 length follows byte count, not the number of characters on screen.
Related Base64 tools
Continue with the localized page that matches the next operation:
Convert Base64 to UTF-8 textBase64 Encoder and DecoderConvert JSON to Base64Convert decimal ASCII byte codes to Base64
Paste your input above, run the conversion, and copy or download the result.