Encode text to Base64 or decode Base64 back to text directly in your browser.
Your text is processed locally in the browser. Nothing is uploaded or stored.
The base64 and base64url alphabets follow RFC 4648. MIME's 76-column line wrap follows RFC 2045 §6.8.
Standard Base64 uses + and / in its alphabet; Base64URL replaces them with - and _ so the output is safe in URLs and filenames. It's the variant used in JWTs and OAuth tokens — toggle URL-safe to switch.
No — it's an encoding, not encryption. It provides no secrecy; anyone can decode it back to the original text.
It won't — if the decoded bytes aren't valid UTF-8 text (an image or binary file, for example), that's detected automatically and shown as a hex dump instead of garbled text. For a full file, use the Base64 File Encoder to download the original.
Padding brings the output to a multiple of 4 characters. Base64 with omitted trailing padding is still accepted when decoding.
Yes — turn on Line-by-line to treat every line as its own independent encode/decode operation instead of one continuous block.
No — encoding and decoding run entirely in your browser.