Convert text to standard Base64 using UTF-8, or decode Base64 back to UTF-8 text. Encoding preserves spaces and line breaks in your text; decoding checks both the Base64 representation and the resulting UTF-8 bytes.
Runs locally in your browserPaste directly into the text field. Conversions run in your browser; there is no file upload, remote URL fetching or file download.
The text 你好 😀 encodes to 5L2g5aW9IPCfmIA=. Output uses A-Z, a-z, 0-9, + and /, adds = padding when needed, and has no line wrapping. Leading and trailing text whitespace stays intact. Unpaired UTF-16 surrogates are rejected; empty input is a valid empty conversion.
Decoding ignores only ASCII space, tab, CR, LF and form feed. If no = is present, missing padding is restored when possible: SGVsbG8 decodes to Hello. Incorrect, incomplete or excess padding, a remaining length of 4n+1, and trailing junk such as SGVsbG8=!!! are rejected.
Padding bits must be zero: Zg== decodes to f, while Zh== is rejected. A is also invalid.
/w== has valid Base64 syntax but does not decode to valid UTF-8 text. An error clears the previous result and disables copying. A UTF-8 BOM is retained as the actual U+FEFF character.
Explicit Base64URL characters - and _ are rejected, as is a data:text/plain;base64, prefix. Paste only the payload if it represents UTF-8 text. There is no Base64URL mode; standard Base64 is not URL percent encoding.
It returns UTF-8 text, not binary files. Valid Base64 alone does not make an image or archive supported input.
No. It is reversible encoding without a key, not encryption, and provides no confidentiality.