We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Convert text to and from Base64 strings. Supports standard and URL-safe encoding, and is compatible with UTF-8 and multiple character sets.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Base64 represents bytes with printable characters so data can be carried in text-oriented contexts. It is an encoding scheme, not encryption: the output can be decoded by anyone who has it. This page converts text in either direction and offers a URL-safe option. It does not accept arbitrary files or act as a file-to-Base64 converter.
Text must first become bytes. For ordinary Unicode text, this tool encodes the input as UTF-8 before Base64 conversion, so accented characters, Chinese text, and emoji can round-trip when decoded with the same text interpretation. Standard Base64 uses + and /; the URL-safe alphabet substitutes - and _. In URL-safe encoding, trailing = padding is removed. The option therefore affects both the alphabet and padding behavior.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Select encoding when the input is readable text, or decoding when the input is a Base64 string.
Leave URL-safe off for standard Base64. Turn it on when the receiving format expects - and _ in place of + and /.
Paste or type a value. For example, the text Hello World encodes as SGVsbG8gV29ybGQ= in standard Base64. Review the output and copy it into the system that needs it.
When decoding, use the matching mode for the alphabet. A malformed string or bytes that do not form valid UTF-8 text may produce an invalid-input error rather than readable text.
Use cases
See how the tool fits into real work and everyday tasks.
Decode a known Base64 text field from a development log to read its UTF-8 contents. Avoid treating the decoded string as trusted instructions or data.
Encode text using the URL-safe setting when a receiving specification calls for the alternate alphabet. Confirm that the target also accepts omitted padding.
Compare a short input before and after encoding to see how bytes are represented with Base64 characters. Decode the result to confirm it returns the original text.
Q&A
Find concise answers to common questions and confusing cases.
No. Base64 is reversible encoding, not encryption, access control, or a password-hashing method. Do not use it to conceal credentials or private information.
The standard alphabet’s + and / become - and _, and encoded output omits trailing padding. Use the mode required by the receiving format.
This page is for text. It does not convert arbitrary binary bytes into a downloadable file, so binary payloads may fail to decode as UTF-8.
Check that the input is valid Base64 and that you selected the correct alphabet. Even valid Base64 can represent bytes that are not UTF-8 text.
Notes
Review scope, result limitations, and important precautions before use.
Base64 changes representation only. It provides no confidentiality and does not validate what decoded text means.
Related
Discover related tools, collections, and available API capabilities.