Base64 encode / decode
Plain text ↔ Base64 in both directions—extra spaces and line breaks in the coded text are ignored when decoding.
Encoding and decoding small payloads
Base64 is common in APIs, data URLs, emails, and configuration snippets where binary or special characters need a text-safe wrapper. This tool helps you switch between plain text and encoded output without leaving the browser.
Why size grows
Base64 usually makes data larger, not smaller, because it encodes information in a text-friendly alphabet. That tradeoff is normal and expected, so use it for transport compatibility rather than compression.
Common Base64 uses
Developers encode small binary blobs for JSON payloads, data URLs, or email attachments. Remember Base64 expands size by roughly one third.
Limits
Designed for snippets — enormous payloads may stress memory.
Debugging encoded payloads
API docs often show Base64-wrapped tokens or small binary blobs. Decoding here lets you inspect the inner JSON or text without writing a throwaway script, which speeds up integration work during development.
When to avoid Base64
Prefer direct binary upload endpoints for large files; Base64 is best for small snippets embedded in JSON or data URLs during prototyping.
Quick start
- Choose encode or decode — Switch mode depending on whether you have plain text or Base64.
- Paste input — Add the string to transform — keep snippets modest for browser memory.
- Copy output — Use the result in APIs, data URLs, or config files.