Check an integration value
Decode a Basic Authorization test value or a data field while troubleshooting an integration.
All developer toolsRuns locally in your browser
FREE BROWSER TOOL
Base64
Encode plain Unicode text to Base64 or decode Base64 safely in your browser. Useful for debugging transport and data URI values.
Use Base64 encoder now.
Encode or decode Unicode text locally. Your result updates in the current tab as you work.
Base64
Encode or decode Unicode text locally. Nothing you enter here is uploaded or stored.
Output
U292cmFuQ29kZSBtYWtlcyBwcmFjdGljZSBjb25jcmV0ZS4= --- Transport details --- Alphabet: standard Base64 Input UTF-8 bytes: 35 Result UTF-8 bytes: 48 Expansion: 137%
WHAT IT DOES
Useful when a small detail is blocking the next step.
Base64 represents bytes with printable ASCII characters. It is commonly used in transport formats that only accept text, but it is not encryption, hashing, or access control. This tool encodes Unicode text correctly before turning it into Base64 and decodes valid Base64 back to text.
Create a text fixture
Encode a small Unicode string for a test, URL-safe transport layer, or documentation example.
Understand data URIs
Inspect the encoded portion of a small text-oriented data URI before deciding whether it belongs in production.
WORKED EXAMPLES
See the exact decision the tool can help you make.
These examples are specific to Base64 encoder. Replace their values with your own, then use the result as a clue—not as a substitute for application validation.
Decode a test header safely
A documentation example contains dXNlcjpwYXNz and you want to understand the transport value.
INPUT
dXNlcjpwYXNz
RESULT
user:pass
The decoded value shows why Basic authentication must still be protected by HTTPS: Base64 is representation, not protection.
Keep Unicode text intact
You need a fixture containing the phrase café ☕.
INPUT
café ☕
RESULT
Y2Fmw6kg4piV
Unicode is encoded to UTF-8 bytes before Base64 conversion, avoiding the broken output produced by older ASCII-only browser helpers.
HOW TO USE IT
Three deliberate steps.
Use the result to make a decision in your code or content, not merely to produce another value to copy.
- 01
Choose the direction
Use Encode for readable text and Decode for an existing Base64 value.
- 02
Paste only the value
For a data URI, remove the leading media-type and comma first; this tool works with the Base64 content.
- 03
Check the result type
A successful decode is text. Binary files need a file-aware workflow rather than a text field.
Base64 is reversible
Anyone who can read a Base64 string can decode it. Never treat it as a way to conceal credentials, tokens, personally identifiable information, or application secrets.
JWTs and URL-safe tokens commonly replace + with - and / with _, often omitting padding. That makes them easier to transport in URLs, but it does not make them encrypted or signed by itself.
standard: a+b/c==
base64url: a-b_c
// A JWT has three Base64URL sections separated by dots.COMMON PITFALLS
Use the result without creating the next bug.
Each tool is deliberately narrow. These are the mistakes most likely to appear when its output is copied into a real product without checking the surrounding constraint.
Sending a whole data URI to a Base64 decoder.
Why it matters: The media type prefix is not part of the encoded payload.
Better approach: Split after the first comma, then decode only the value after it.
Using regular Base64 inside a URL path or query without encoding it.
Why it matters: Characters such as +, /, and = may be interpreted by URL processing.
Better approach: Use a documented Base64URL variant or percent-encode an ordinary Base64 value.
FAQ
Questions worth answering before you rely on the result.
These tools help with bounded client-side work. Production decisions still need the validation, review, and authorization appropriate to your application.
01Can Base64 encrypt a password?
No. Base64 only changes representation and is immediately reversible. Store passwords with a purpose-built password hash on a server.
02Why does decoding fail?
The value may contain a non-Base64 character, be truncated, use a URL-safe variant, or represent binary content that cannot be decoded as text.
03Does encoding make data smaller?
Usually it makes the data larger. Base64 expands binary data by roughly one third before transport compression.
KEEP BUILDINGMore small tools,