Back to Tools ๐Ÿ”’ 100% Browser-Based & Private
B64
Developer Utilities

Base64 & URL Encoder-Decoder

Instant Two-Way Conversion โ€ข Full UTF-8 Unicode Support โ€ข Zero Server Upload

Encode and decode plain text, tokens, API credentials, and web URLs. Runs 100% locally in your browser memory for maximum privacy and zero latency.

Zero Server Tracking UTF-8 & Emoji Safe Instant Real-Time
๐ŸŸข Successfully Encoded to Base64
220 bytes (220 chars)
Plain Text / Source Input
137 chars โ€ข 165 bytes
3 lines
Base64 Output
220 chars โ€ข 220 bytes
VG9vbFdhbGEgQUkg4oCUIFplcm8tVXBsb2FkIFByaXZhY3khIPCfmoAK4KSo4KSu4KS44KWN4KSk4KWHIOCkpuClgeCkqOCkv+Ckr+CkviAoSGVsbG8gV29ybGQgaW4gSGluZGkpCnsic2VydmljZSI6ICJCYXNlNjQgJiBVUkwgRW5jb2Rlci1EZWNvZGVyIiwgImluQnJvd3NlciI6IHRydWV9
1 line

Zero-Upload Privacy Architecture: All encoding and decoding operations run 100% locally inside your web browser sandbox using native browser APIs. No strings, tokens, passwords, or query parameters are ever transmitted to any remote server or stored in logs.

Developer Guide & Technical Reference

Understanding Base64 & URL Percent-Encoding

Everything developers need to know about binary-to-text encodings, URI safety, and RFC standards.

What is Base64 Encoding?

Base64 is a binary-to-text representation scheme designed to encode arbitrary binary data or text strings into an ASCII format. It divides binary sequences into 6-bit chunks, where each 6-bit integer maps to one of 64 printable characters: A-Z, a-z, 0-9, +, and /, with = used for byte padding.

Because legacy network protocols like SMTP (email) and HTTP headers were built to transport 7-bit ASCII text, raw binary bytes could be corrupted during transit. Base64 guarantees that data passes through any gateway intact without modification.

3 Raw Bytes (24 bits) โ†’ 4 Base64 Chars (33% size increase)
Common uses: Basic Auth headers, JWT payload inspection, inline data URIs in CSS/HTML, email MIME attachments.

What is URL Encoding (Percent-Encoding)?

URL Encoding (governed by RFC 3986) transforms characters that are not permitted or reserved in a Uniform Resource Identifier (URI) into a percent-sign followed by their two-character hexadecimal UTF-8 byte value.

For example, a space character becomes %20 (or + in form data), an ampersand & becomes %26, and non-ASCII Unicode characters (like emojis or Hindi letters) are converted into their multi-byte hexadecimal sequence (e.g. ๐Ÿš€ becomes %F0%9F%9A%80).

Space โ†’ %20 | & โ†’ %26 | ? โ†’ %3F | / โ†’ %2F
Common uses: Query parameter serialization, OAuth redirects, form submissions, webhook URLs.

How to Use the Base64 & URL Encoder-Decoder

1

Pick Mode

Choose between Base64 for binary data/tokens, or URL Encoding for web query parameters and links.

2

Select Direction

Select Encode to transform plain text into safe strings, or Decode to restore encoded strings to text.

3

Type or Upload

Paste raw text into the input panel, click Sample for a quick test, or click Upload to load a file.

4

Copy or Swap

Conversion updates live. Click Copy to copy output to clipboard, or click Swap to reverse immediately.

Frequently Asked Questions

Frequently Asked Questions