Free Base64 Encoder & Decoder

Encode text for a data URI, a JSON payload or a Basic Auth header — or decode a token segment back to readable text. UTF-8 correct, so accents and emoji survive the round trip.

Privacy Level 1 — 100% local: your files never leave your browser
Free plan: unlimited conversions, no signup. Base64 is encoding, not encryption: anyone can decode it, so never use it to protect a secret. Encoding runs entirely in your browser, which matters when the input is a token fragment, an API payload or a config value.

Options

Something not working?

Tell us what went wrong — it helps us fix the tool. Only what you type below is sent.

Need more power? Meet Base64 Encoder Pro

One-time payment. Yours forever. No subscription.

$29
single payment · lifetime updates included
FeatureFreePro
Text encode/decode, UTF-8 correctYesYes
URL-safe alphabet and line wrappingYesYes
Single-file encodingYesYes
Batch file encoding with a manifest—Yes
Ads—Yes

Frequently asked questions

Is Base64 encryption?

No. It is a reversible encoding: anyone with the output can decode it. Use it to move binary or special-character data through text-only channels (JSON, headers, data URIs), never to hide a secret.

Why do my accents or emoji break in other tools?

The classic browser functions btoa and atob only handle Latin-1. This tool encodes UTF-8 bytes first, so accented characters and emoji survive the round trip.

What is the URL-safe variant?

Standard Base64 uses + and /, which have special meanings in URLs. The URL-safe variant swaps them for - and _ and usually drops the trailing = padding. It is the form JWTs use — if a token decodes in one tool but not another, a standard-vs-URL-safe mismatch is the usual cause.

Is my input uploaded?

No. Encoding and decoding run in your browser, including file encoding. Close the tab and the input is gone.