About this base64 decoder
Decode standard Base64 back into UTF-8 text. Paste the encoded string, including any final equals signs, and run the decoder. Whitespace such as spaces or wrapped line breaks is ignored before validation. For example, YWJj decodes to abc, while aMOpbGxv decodes to héllo. Empty input represents an empty message and returns an empty result rather than an error.
The validator checks the standard alphabet, complete four-character groups and the permitted final padding patterns. After decoding the bytes, a strict UTF-8 decoder rejects byte sequences that cannot represent valid text. An error can therefore mean either malformed Base64 or a valid binary payload that is not textual UTF-8. This distinction matters for images, compressed files and executable data that are routinely carried inside Base64 strings.
This tool expects standard padded Base64, not a data URL and not the URL-safe alphabet used in JWTs. Remove the data URL header before decoding textual content. Decoding alone does not establish who created the data or whether its contents are trustworthy.
Which controls should I check first?
The Base64 Decoder form labels its controls as Input; Result. Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
How should I interpret this specific operation?
Whitespace is removed before the padded standard alphabet is validated. Passing that validation only establishes that bytes can be decoded. The subsequent strict UTF-8 step can reject a binary payload even when its Base64 is valid. If the value represents an image, use the image decoder instead of assuming that every successful Base64 byte sequence should produce readable prose.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| aMOpbGxv | héllo |
Is this a representation change or a content change?
An encoding expresses bytes or characters using a different alphabet or escape notation. It should not be confused with encryption, compression or permission to execute the result. Work out which layer the receiving field expects before converting. A URL component, a complete URL, an HTML text node and a JSON string need different escaping rules. Encoding for one context does not automatically make a value safe in another. Keep the unencoded source while editing and convert at the boundary where the destination requires it. Otherwise repeated conversions can encode existing escape markers rather than the original content.
How do I diagnose a malformed input?
Check the alphabet, prefix, separators and final padding against this tool's documented input format. A pasted quotation mark or trailing label can turn a valid payload into invalid text. For UTF-8 decoding, a byte sequence can be syntactically valid in its outer representation yet still fail to represent text. Binary images and compressed data are examples of payloads that should not be forced through a text decoder. Use the appropriate file or image workflow for them. Do not remove padding or percent signs at random to make an error disappear; first identify what those characters mean in the expected representation.
Why does decoding once matter?
A value can have more than one encoding layer. Decoding the outer layer yields another encoded string rather than necessarily reaching the final readable content. Repeating the operation is appropriate only when the source format specifies those layers. With URL components, decoding separator characters too early can change the structure of a query. With HTML entities, a decoded angle bracket is ordinary text until another application interprets it as markup. Inspect the result as text before placing it into an active context. Keep a record of which layer you decoded so that a later step does not accidentally repeat it.
How do non-ASCII characters affect the result?
A character such as é occupies more than one UTF-8 byte. An emoji can require several bytes even when it occupies one visible position. Encoders process those bytes according to their representation rules, so output length cannot be predicted from visible character count alone. A percent-encoded character can consist of several percent triplets, and Base64 groups bytes rather than visible letters. Compare the worked Unicode example with the result instead of assuming one output group per character. A strict text decoder helps expose damaged bytes that would otherwise be replaced by an ambiguous replacement character.
How should I check a round trip?
Encode a short representative source, decode it with the matching inverse convention, and compare the complete result with the original. Include spaces, punctuation and a non-ASCII character if those occur in your real data. Matching the visible text is useful, but an exact workflow may also need to compare line endings and Unicode normalization. Do not mix standard Base64 with URL-safe Base64 or form-style plus handling with ordinary URL component handling. A successful round trip proves agreement between those representation choices. It does not authenticate the source, validate a web destination, or establish that decoded markup is safe to render.
Can I paste wrapped lines?
Yes. Whitespace is removed before validation.
Why does valid Base64 sometimes fail?
Its decoded bytes may be binary rather than valid UTF-8 text.
Does it accept Base64url?
No. This decoder expects the standard plus/slash alphabet and padding.