Loading...
Loading...
Encode and decode text or files to Base64 — instantly in your browser.
Use the Base64 converter to encode UTF-8 text into Base64 or decode Base64 back into readable text. Base64 is a transport encoding, not encryption, so it is best for small payloads, headers, and examples. Watch for padding, whitespace, and binary data that cannot be displayed safely as text.
Remove spaces and line breaks, then check that the Base64 string uses valid characters and correct padding.
The bytes may be binary or use a different character encoding, so do not assume every Base64 value is UTF-8 text.
Remember that Base64 can be reversed easily; use proper encryption or secret storage for sensitive data.
Check whether the API expects padded Base64, URL-safe Base64, or a specific prefix around the encoded text.
Base64 encoding and decoding happens in the browser tab, so the text you enter is not intentionally uploaded to a remote converter. Avoid real passwords, private keys, session cookies, and access tokens because Base64 is reversible and browser history or screen sharing can still expose values.
Decide whether you are turning UTF-8 text into Base64 or converting a Base64 string back to text.
Paste the exact text or encoded string, trimming unrelated whitespace from copied logs or headers.
Check equals-sign padding, readable UTF-8 characters, and any error message before using the result.
Use fake credentials or sanitized payloads in docs, tickets, and screenshots.
Input: hello. Output: aGVsbG8=. The equals sign is padding and may be required by strict decoders.
Input: ZGVtbzpwYXNz. Output: demo:pass. This demonstrates the format but should not be used with real credentials.
You can encode UTF-8 text into Base64 or decode Base64 back into readable text when the decoded bytes represent text. It is useful for headers, small config values, and test payloads.
No. Base64 is an encoding that makes bytes safe for text-only transport. Anyone can decode it, so never treat Base64 output as a secret or password protection.
The input may not be valid Base64, may be missing padding, or may represent binary bytes instead of UTF-8 text. Check the source and add required equals-sign padding when appropriate.
Padding uses one or two equals signs at the end so the encoded length aligns to four-character groups. Some systems omit padding, but other decoders require it.
Yes for small test values. Encoding username:password as Base64 can help inspect an Authorization header, but do not paste real credentials into shared devices or screenshots.
Base64 encoding (RFC 4648) converts binary data into a text representation using 64 ASCII characters. It was originally designed for email (MIME, RFC 2045) to safely transmit binary attachments through text-only protocols. Today it is used extensively in web development for data URIs (embedding images in HTML/CSS), JWT tokens, API authentication headers (HTTP Basic Auth), and transmitting binary data in JSON payloads. The encoding process takes 3 bytes of input and produces 4 Base64 characters, resulting in approximately 33% size overhead.
This tool is particularly useful when: