Inspect encoded API values
Decode Base64 strings found in headers, payload examples, and config snippets.
Free browser tool
Base64 Encoder and Decoder
Use this Base64 encoder and decoder to convert text into Base64 or decode Base64 strings back into readable content. Base64 is common in API examples, small data URIs, authorization headers, config snippets, and transport formats that need binary-safe text.
The tool supports UTF-8 text, shows clear errors for invalid Base64 input, and runs in the browser without requiring login or server-side processing.
Base64 encoder/decoder
Encode text to Base64 or decode Base64 into UTF-8 text.
What this tool does
Base64 converts bytes into a text-safe alphabet that can travel through systems designed for plain text. Developers see it in authorization headers, small embedded assets, API examples, email formats, and configuration values. It is convenient because the output avoids control characters and most punctuation that can confuse transport layers.
This tool supports both encoding and decoding. Encode readable UTF-8 text when you need a Base64 value for a test or example. Decode Base64 when you need to inspect a value that appears in logs, headers, or documentation. Remember that Base64 is reversible and does not protect secrets.
Common use cases
Create test fixtures
Encode sample text into Base64 when a test or documentation example expects encoded input.
Debug Unicode handling
Check whether text survives Base64 encode and decode steps without character loss.
Example before and after
The encoded value is safe to place in text-oriented fields, but anyone can decode it back to the original text.
Plain text
hello OrlixioBase64 output
aGVsbG8gT3JsaXhpbw==How to use
- Paste text or a Base64 string into the input textarea.
- Choose Encode Base64 or Decode Base64.
- Review the output, then copy or clear it.
Common errors
Treating Base64 as encryption
Base64 does not hide information. Do not use it to protect passwords, tokens, or private data.
Invalid padding
Some Base64 strings include = padding. Missing or extra padding can cause decoders to reject input.
Confusing Base64URL
JWTs commonly use Base64URL, which swaps characters and often omits padding.
Why use this tool
Inspect Base64 snippets from APIs and configs.
Create safe encoded text for examples and tests.
Decode values without installing a command-line utility.
Best practices
Decode before trusting
Always inspect decoded content before assuming what an encoded value contains.
Avoid live secrets
Do not paste production credentials into browser tools unless the values are redacted.
Use the right variant
Use normal Base64 for general text and Base64URL-aware tools for JWT segments.
Related tools
Related guides
What is Base64 encoding
Base64 turns bytes into text-safe characters for transport, but it is reversible and should not be treated as security.
What is JWT and how to decode it
JWTs are common in authentication. Learn what the three sections mean and why decoding is not verification.
Best practices for working with API responses
API responses are easier to debug when you validate syntax, format payloads, inspect errors, and compare changes deliberately.
FAQ
Is Base64 encryption?
No. Base64 is encoding, not encryption. Anyone can decode it.
Does this support Unicode text?
Yes. The tool encodes and decodes UTF-8 text.
Is my text uploaded?
The tool runs in your browser and does not require login, a database, or server-side processing.
Why does decoding fail?
The input may not be valid Base64 or may represent bytes that are not valid UTF-8 text.