Frequently Asked Questions
What is Base64 encoding?
Base64 is a binary-to-text encoding scheme that represents binary data using 64 printable ASCII characters (A-Z, a-z, 0-9, +, /). It's commonly used to embed binary data in text-based formats like JSON, HTML, CSS, and email.
What is URL-safe Base64?
URL-safe Base64 replaces + with - and / with _, making the output safe for use in URLs and filenames without additional encoding. It's defined in RFC 4648.
Why does Base64 increase the size?
Base64 encodes 3 bytes of binary data into 4 ASCII characters, resulting in roughly 33% size increase. This is the trade-off for being able to represent binary data as text.
Is my data safe?
Yes. All encoding and decoding happens entirely in your browser. No data is ever sent to any server. You can verify this in the Network tab of your browser's developer tools.
What file types can I encode?
Any file type — images, PDFs, documents, binaries. The file tab supports files up to 10 MB. The result includes a Data URI option that you can use directly in HTML or CSS.
Is Base64 encryption?
No. Base64 is an encoding scheme, not encryption. It converts binary data to text for safe transport but provides zero security — anyone can decode it instantly. Never use Base64 to protect sensitive data.
Why is Base64 used in JWT tokens?
JWT tokens use Base64url encoding to safely represent JSON data in URLs and HTTP headers. The header and payload sections are Base64url-encoded, making them compact and URL-safe while remaining easily decodable.
What is the difference between Base64 and Base64url?
Standard Base64 uses + and / characters which are not safe in URLs. Base64url replaces them with - and _ and omits padding (=). Use Base64url for JWT tokens, URL parameters, and filenames.