Base64 to text converter
Read a Base64 message as text, or encode your words. Check the result, then copy it or save a TXT file.
Standard Base64 with UTF-8 text bytes. No account needed. Encoding is not encryption.
Up to 1,000 UTF-8 bytes and 4,000 Base64 input units including whitespace. No silent shortening.
Use case-sensitive standard Base64, with = padding where needed. Ordinary spaces, tabs and line breaks are ignored. Changing direction keeps your typed input.
Your decoded text
3 UTF-8 bytes. Standard Base64 alphabet.
UTF-8 text only, not arbitrary binary files or encryption. Copy and TXT contain this result, without labels or an added newline.
Actual copyable examples
- Text: Hi! (3 bytes)
- SGkh
- Text: café (5 bytes)
- Y2Fmw6k=
Paste either result into Base64 to decode. The accented letter uses two UTF-8 bytes, so the second example contains five bytes of text.
Check the alphabet and padding
Standard Base64 uses A-Z, a-z, 0-9, + and /. Case matters. Each group of four characters represents up to three bytes; = fills the final group when needed. Zg== decodes to f, while Zm8= decodes to fo.
Use complete groups and the appropriate final padding. Missing, misplaced or excess padding produces an error. Unused bits in the final group must be zero: Zh== is rejected rather than silently treated as Zg==. Encoding adds padding without inserting line breaks.
Ordinary spaces, tabs and line breaks in pasted Base64 are ignored as this tool's input convenience. Other characters are rejected. Whitespace in your original text is encoded as bytes and retained when decoded.
This is standard Base64, not Base64url with - and _. It does not parse JWT tokens, data URL prefixes or uploaded files. Base64 can represent any bytes, but this tool only accepts valid UTF-8 text; bytes from Latin-1 or another encoding can mean something else.
See RFC 4648, Base64 for the alphabet and padding, canonical unused bits for strict validation, and RFC 3629, UTF-8 for the text encoding.
Limits, exports and data handling
Encode or decode up to 1,000 UTF-8 bytes. Base64 input also has a 4,000-unit limit including whitespace. Accents and emoji can use several bytes. Incomplete Unicode, control characters other than tabs and line breaks, and bidirectional formatting controls are rejected without repair or partial output. Your input is never silently shortened.
Changing direction keeps your typed input. Copy and UTF-8 TXT contain only the current result, without labels or an added final newline. A literal leading U+FEFF is retained; browser text fields and receiving editors may adapt line endings. If copying fails, select the raw result or download TXT. Export before leaving; no draft is saved automatically.
Input stays in this page's memory, not links, saved settings or analytics events. Site resources and analytics still make requests; see data handling. Base64 does not protect a secret. Do not treat it as encryption.
Have hex bytes instead? Use Hex to text. For zeros and ones, use the binary translator. Check unusual decoded characters with the Unicode inspector.