Encode and decode modes
Use one page to encode plain text into Base64 or decode Base64 text back into readable UTF-8 output for inspection.
Encode UTF-8 text, decode Base64 or Base64URL strings, remove padding when needed, and copy the converted text after review.
Encode UTF-8 text, decode Base64 strings, and switch Base64URL output.
Strip padding when a token, URL parameter, or filename requires it.
Use this flow when you need a quick Base64 encoder, Base64 decoder, Base64URL converter, or data URI text check.
Add the plain text you want to encode, or paste a Base64, Base64URL, or data URI string you need to decode. Keep only the value needed for this conversion.
Select Base64URL when the encoded result belongs in a URL, token, or filename. Turn off padding when the receiving system expects the final equals signs to be omitted.
Use Encode, Decode, or Swap to compare the two text areas. Confirm decoded text is readable and encoded text uses the expected alphabet before copying the result.

Use one page to encode plain text into Base64 or decode Base64 text back into readable UTF-8 output for inspection.
Switch to the URL-safe alphabet so plus and slash characters become dash and underscore, which is useful for tokens, links, and filenames.
Remove trailing equals signs when a protocol or library expects unpadded Base64URL, then keep padding enabled for systems that require standard Base64.
When decoding a data URI string, the tool removes the data prefix and decodes the Base64 payload, which helps inspect pasted image or file snippets.
Encoding uses UTF-8 bytes for text, and decoding turns bytes back into text. Binary data may appear unreadable when shown in a text area.
Swap input and output for quick round-trip checks, clear the input when finished, and copy the converted text after confirming it matches the target format.
Base64 explains how typed text, pasted Base64 strings, Base64URL options, padding choices, decoded output, swapping, and clipboard copy are handled during normal browser use.
Base64 encodes and decodes typed or pasted text inside the browser session, including Base64URL normalization and data URI prefix removal during decode.
Closing or refreshing Base64 clears the input, output, URL-safe option, and padding option unless the browser preserves page state.
Base64 can be used without sign-in, so text encoding and decoding checks can finish without creating a saved profile.
Review these notes before encoding tokens, headers, data URI snippets, API values, config strings, or anything private.
Base64 can expose the original text to anyone who decodes it. Do not treat encoded passwords, API keys, private tokens, or customer data as hidden.
Normal conversion runs in the browser without sign-in, but company policy should still decide whether secrets or client data may be pasted into a web tool.
Base64 is reversible encoding, not encryption. It helps represent bytes as text, but it does not protect confidentiality, integrity, or access control.
Decode a sample before relying on an encoded value. Small differences in URL-safe characters, padding, or whitespace can break strict receivers.
Standard Base64 uses plus, slash, and padding. Base64URL replaces plus and slash, and many token formats omit padding characters.
This page is designed for text. If you need to encode or decode binary files, use a file-aware tool and verify the bytes with the destination system.
Copy the result only after confirming whether the target expects standard Base64, Base64URL, padding, no padding, or a full data URI.
When decoded output looks garbled, the input may be binary data, use another character encoding, or contain a prefix that is not part of the Base64 payload.
Base64 runs in the active browser workspace for text input; very large strings may slow encoding, decoding, swapping, copying, or display.
Invalid Base64 strings can fail to decode. Remove unrelated labels, quotes, headers, or pasted explanation text before trying again.
Base64 represents bytes with printable characters. Developers often use it for headers, tokens, JSON fields, data URI snippets, and systems that need text-safe transport.
No. Base64 is reversible encoding and should not be used to hide secrets. Anyone with the encoded string can decode it unless real encryption or signing is applied separately.
Base64URL changes the alphabet so the output is safer inside URLs, filenames, and token segments. It replaces plus and slash characters with dash and underscore.
Some protocols and libraries use unpadded Base64URL, especially in token or URL contexts. Keep padding enabled when a receiver expects standard Base64 with trailing equals signs.
Yes. During decode, the tool can strip a data URI prefix before decoding the Base64 payload. Review the output carefully because binary content may not display as readable text.
4.3 (470 ratings)