Overview
Base64 turns bytes into ASCII characters so text can pass through systems that expect character-safe data. It is often used when preparing Authorization values, encoding small request fragments, storing sample content in fixtures, or matching what another service returns. This tool is for text input, so it is best suited to small and medium strings rather than files or binary blobs. The output is reversible: Base64 does not protect secrets, and anyone who receives the encoded string can decode it back to the original text.
Use cases
- Authorization header prepEncode a user:password or client:secret pair before placing it in a Basic Authorization header for a request test.
- Webhook payload samplesRepresent small text fragments in Base64 when a receiving system expects encoded values inside a payload.
- Fixture values for testsCreate stable encoded strings for snapshots, mocks, sample responses, and integration test fixtures.
- Release notes and support casesShare an encoded example in internal documentation when you need a reproducible text value without manual formatting.
How it works
- 1
Enter the exact text you want to encode.
- 2
The browser converts the text’s UTF-8 bytes into a Base64 string.
- 3
Copy the result into your API client, header, documentation, or test case.
Examples
Readable phrase
Input: hello world
Output: aGVsbG8gd29ybGQ=
A straightforward text sample that makes the encoding pattern easy to verify.
Credential-style pair
Input: api:test-key
Output: YXBpOnRlc3Qta2V5
Shows the Base64 form of a colon-separated value commonly prepared before Basic Auth testing.
Mini JSON payload
Input: {"user":"ana","role":"admin"}
Output: eyJ1c2VyIjoiYW5hIiwicm9sZSI6ImFkbWluIn0=
Useful when a compact JSON fragment must be embedded as encoded text in a test or note.
Unicode text
Input: Café déjà vu
Output: Q2Fmw6kgZMOpasOgIHZ1
Demonstrates that accented characters are encoded from their UTF-8 bytes, not stripped or normalized.
FAQ
Does Base64 hide the content of my text?
No. Base64 is only an encoding format. It can be reversed immediately, so it should never be treated as secret storage.
Can I encode characters like accents, emojis, or non-Latin text?
Yes. The tool encodes the text as UTF-8 bytes, which preserves Unicode input such as ñ, ü, 漢字, and emoji.
Why does my output end with one or two equals signs?
Padding is part of standard Base64 for many inputs. It helps align the encoded output to the expected block size.
Can I paste the result directly into an HTTP header?
Yes, if the server expects Base64. For Basic Auth, the encoded value is usually written after the Basic prefix.
What mistakes cause bad output?
Changing the input text, adding extra spaces, or encoding already-encoded text are the most common issues. If the receiving system expects raw bytes instead of text, the result will also be wrong.
Is this tool suitable for large files?
No. It is designed for text conversion. Large files and binary data are better handled with file-oriented tools built for that purpose.