Encode and decode Base64 strings instantly
QRSwift's Base64 Converter lets you encode any plain text string into Base64 format, or decode a Base64 string back into human-readable text — all in one click. It's a go-to utility for developers working with APIs, authentication tokens, email attachments, or data URIs that require text-safe encoding. Full Unicode support means accented characters, emoji, and non-Latin scripts all encode and decode correctly. Like all QRSwift tools, everything runs locally in your browser with nothing ever sent to a server.
Paste your input
Type or paste either plain text (to encode) or a Base64 string (to decode) into the left panel.
Choose your direction
Click Encode → Base64 to convert text into a Base64 string, or Decode Base64 → Text to reverse the process.
Read the output
The result appears instantly in the right panel. If decoding fails (e.g. the input isn't valid Base64), an error message will tell you what went wrong.
Copy or clear
Select all text in the output panel and copy it, or hit Clear All to reset both panels and start fresh.
Base64 encodes binary or text data into a string made up of only 64 printable ASCII characters, making it safe to transmit in contexts that can't handle raw binary — such as JSON payloads, HTTP headers, email bodies (MIME), and data URIs for embedding images in HTML or CSS. It's also commonly used to store credentials in Basic Auth headers and to pass structured data through URLs without encoding issues.
No — Base64 is an encoding scheme, not an encryption algorithm. Anyone with a Base64 decoder (including this tool) can instantly recover the original text. Never rely on Base64 to protect sensitive information. If you need to secure data, use proper encryption such as AES before encoding. Base64 is purely about making data transport-safe, not secret.
The = characters are padding. Base64 works in groups of 3 bytes at a time; if the input length isn't a multiple of 3, one or two = characters are appended to make the output length a multiple of 4. This is completely normal and expected — the decoder knows to strip the padding when reversing the process. Some implementations (like URL-safe Base64) omit the padding; if a string without = fails to decode, try adding the missing padding first.