Base64 Encoder & Decoder
Encode and decode text to and from Base64. UTF-8 safe, supports URL-safe variant. Everything runs locally.
01Why this Base64 tool
Encode and decode, fast.
Four reasons API engineers, security folks, and frontend devs keep this tab pinned.
- 01
Encode and decode in one place
Switch between encode and decode with a tab. Paste, see the result, copy — no flag in a URL or hunting for the right CLI.
- 02
URL-safe variant when you need it
Standard Base64 uses +/= which break in URLs. Flip a toggle and get URL-safe (-_) output that drops into query strings cleanly.
- 03
Updates as you type
No 'click to encode' button. Type or paste in the left, the right updates in milliseconds with the encoded or decoded result.
- 04
Strings stay in your browser
Auth tokens, API keys, credentials — they're often what gets encoded. None of it leaves your machine, because it never travels to a server.
02How it works
Three quick moves.
- ModeEncodeDecode
Step 1Pick encode or decode
A tab toggle at the top. Encode for raw text → Base64. Decode for Base64 → original text.
- Input1user:hunter2
Step 2Paste your input
Drop in a string, a JSON blob, or whatever you need to encode. Multi-line is fine; the tool handles UTF-8 cleanly.
- CopiedEncodeddXNlcjpodW50ZXIyBase64 · ready
Step 3Copy the result
The output updates immediately. Click Copy and paste it wherever you need it — header, URL, config file.
03Use cases
Where Base64 shows up.
The format hides in surprisingly many corners of every engineer's day.
Basic auth headers
HTTP Basic Auth wants 'user:pass' Base64-encoded. Type, encode, paste into the Authorization header for a curl or Postman request.
user:pass → dXNlcjpwYXNzInline data URIs
Embedding a small image as a data: URI? Base64-encode it for the src attribute and skip an extra HTTP request.
image → data:image/png;base64,...Encode tokens in URLs
Need to pass a payload through a URL safely? URL-safe Base64 escapes the characters that would otherwise break.
Token → URL-safe Base64Decode email attachments
MIME attachments are Base64. Paste in the encoded blob from a raw email to read what's inside without saving the attachment.
MIME chunk → readable textInspect a webhook signature
Many webhook signatures encode the signed payload in Base64. Decode to verify the original bytes match what you expect.
Sig → raw bytesConfig values in YAML/env
Kubernetes secrets are Base64. Encode a config value to drop it into a Secret manifest without touching kubectl.
Password → k8s secret value
04Quick tips
Things to watch for.
Small details that bite if you ignore them.
- 01
Toggle URL-safe for query strings
Standard Base64 contains +/= which require URL encoding to ride in a query string. URL-safe mode skips the double encoding.
- 02
Watch the trailing = signs
Standard Base64 pads with = to make the length divisible by 4. The decoder handles missing padding, but most other tools don't — keep it if you'll paste elsewhere.
- 03
UTF-8 is handled cleanly
Multi-byte characters (emoji, accents, Chinese) encode and decode without corruption. The tool uses TextEncoder/TextDecoder under the hood.
- 04
Base64 is not encryption
Anyone can decode Base64 — it's encoding, not security. Don't use it to hide secrets; pair with proper encryption when secrecy matters.
05Loved by
API, security, and frontend engineers.
I encode auth headers a dozen times a day. This page is in my pinned tabs and beats the CLI for pasting straight into Postman.
Inlining favicons and tiny SVGs as data URIs — paste, encode, drop into CSS. Skips one HTTP request per asset.
Decoding suspicious webhook bodies during incident response. Fast, local, no risk of pasting payloads into a third-party tool.
06Questions
Base64, plainly answered.
What people check before their first encode. Anything missing? hello@wirelogs.com.
01What is Base64?
An encoding that represents arbitrary binary data using only 64 ASCII characters (A-Z, a-z, 0-9, +, /). It's commonly used to ship binary data through systems that only handle text — HTTP headers, JSON, URLs, email.
02Is Base64 encryption?
No. Base64 is encoding, not encryption — anyone can decode it. Use it to safely transport bytes through text-only channels, not to hide secrets.
03What's URL-safe Base64?
A variant that replaces + and / (which have meaning in URLs) with - and _, and drops the = padding. Useful when the encoded value lives inside a URL or filename.
04Does it handle non-English text?
Yes. Encoding and decoding use TextEncoder/TextDecoder, so emoji, accented characters, Chinese, Japanese, and other multi-byte UTF-8 strings round-trip cleanly.
05Is the tool free?
Yes. No usage cap, no watermark, no sign-up. Encode and decode as much as you need.
06Does my data leave the browser?
No. All encoding and decoding happen locally with built-in browser APIs. Wirelogs never sees what you paste — useful for tokens, passwords, and other sensitive inputs.
Ready when you are
Paste, convert, copy.
Drop your text or Base64 into the tool above and copy the result. Nothing leaves your machine.
- UTF-8safe
- Localprivate
- $0now and always