Update your browser or use a current version of Chrome, Edge, Firefox or Safari.
Base64 represents binary bytes with a limited text alphabet. It is useful when a system accepts text but needs to carry bytes. Because it is reversible and contains no key, Base64 is encoding—not encryption.
Unicode text is first converted to UTF-8 bytes with TextEncoder. Those bytes are then grouped into Base64 characters. Decoding reverses the process with a strict UTF-8 decoder, avoiding the Latin-1 limitation of calling btoa() directly on arbitrary text.
Uses + and /, normally with = padding. It is common in files, email formats, and data URLs.
Uses - and _ and often omits padding, making it convenient inside URLs and tokens such as JWTs.
Four Base64 characters represent three input bytes, producing roughly 33% overhead before surrounding formats or padding. It should not replace compression.
No. Valid UTF-8 is displayed as escaped text. Binary or invalid UTF-8 is identified without invented output.
Yes. This decoder restores valid missing padding when Base64URL mode is selected.