Base64 Encoder
Encode any text to Base64. Unicode-safe, supports URL-safe variant, runs in your browser.
EncodeURL-safeClient-sideFree to use
0 / 500,000
How to use
- Paste your text. Any UTF-8 text, emoji, special chars all work.
- Copy the Base64. Toggle URL-safe variant if needed.
Common use cases
- Encoding binary data for JSON APIs
- Embedding images as data URIs
- Stashing payloads in URL params
Frequently asked questions
- What is Base64 and why use it?
- Base64 is a binary-to-text encoding (RFC 4648) that represents 8-bit bytes using 64 printable ASCII characters. It is the standard way to embed binary data inside text-only formats like JSON, XML, email, and URLs.
- What is the difference between standard and URL-safe Base64?
- Standard Base64 uses + and / characters, which need escaping in URLs and filenames. URL-safe Base64 (also RFC 4648) replaces + with - and / with _, and usually drops the trailing = padding so the result fits cleanly into URLs and tokens.
- Does this encoder handle Unicode and emoji?
- Yes. The text is first UTF-8 encoded into bytes, then those bytes are Base64 encoded. Emoji, Chinese, accented characters, and other non-ASCII content all encode and decode round-trip correctly.
- Can I encode an image or other binary file?
- Yes. Use the Encode file button to choose any file (up to 10 MB) and get both the raw Base64 and a ready-to-paste data URI. For a fuller file-focused workflow, see the Base64 File Converter.
- How much larger does Base64 make my data?
- Base64 expands binary data by roughly 33% (every 3 bytes become 4 ASCII characters). That overhead is the cost of staying inside text-only formats.
Related tools
How to use
- Paste your text. Any UTF-8 text, emoji, special chars all work.
- Copy the Base64. Toggle URL-safe variant if needed.
Common use cases
- Encoding binary data for JSON APIs
- Embedding images as data URIs
- Stashing payloads in URL params
Frequently asked questions
- What is Base64 and why use it?
- Base64 is a binary-to-text encoding (RFC 4648) that represents 8-bit bytes using 64 printable ASCII characters. It is the standard way to embed binary data inside text-only formats like JSON, XML, email, and URLs.
- What is the difference between standard and URL-safe Base64?
- Standard Base64 uses + and / characters, which need escaping in URLs and filenames. URL-safe Base64 (also RFC 4648) replaces + with - and / with _, and usually drops the trailing = padding so the result fits cleanly into URLs and tokens.
- Does this encoder handle Unicode and emoji?
- Yes. The text is first UTF-8 encoded into bytes, then those bytes are Base64 encoded. Emoji, Chinese, accented characters, and other non-ASCII content all encode and decode round-trip correctly.
- Can I encode an image or other binary file?
- Yes. Use the Encode file button to choose any file (up to 10 MB) and get both the raw Base64 and a ready-to-paste data URI. For a fuller file-focused workflow, see the Base64 File Converter.
- How much larger does Base64 make my data?
- Base64 expands binary data by roughly 33% (every 3 bytes become 4 ASCII characters). That overhead is the cost of staying inside text-only formats.