Key takeaway
Base64 encodes binary data as ASCII text so it can travel in places that prefer text — email attachments historically, data URLs, some tokens.
It is encoding, not encryption — anyone can decode it.
What it means
Bytes map to an alphabet of A–Z a–z 0–9 + / with = padding.
Size grows ~33%.
UTF-8 text should be encoded as bytes first.
When you would use it
Data URLs, debugging payloads, working with APIs that expect Base64 fields.
Never as a secrecy mechanism.
How to use the tool
Use the matching TCB Tools page and work top to bottom:
- Open Base64 Encoder/Decoder.
- Paste text or use the mode you need.
- Encode or decode.
- Verify round-trip on a sample.
No account is required. Results update as you type.
How encoding works + example
Example text “Hi” encodes to a short Base64 string (try it live).
If decode fails, check missing padding or URL-safe variants (-_ vs +/).
How to read the result
Readable Base64 still exposes data.
URL-safe alphabets differ.
Local tool — still do not paste production secrets casually into shared machines.
Common mistakes
- Calling it encryption. It is not.
- Wrong alphabet variant. Match the spec.
- Line breaks unexpected. Some systems wrap.
- Double encoding. Encode once.
Related ideas
JSON and URL encoding tools for neighboring jobs.
Data URLs for tiny icons are fine; huge Base64 images bloat HTML.
Document which variant your API expects.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit Base64 weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure Base64; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about Base64, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions Base64.
If leadership wants only a headline, still keep working notes for Base64 in your own folder.
Seasonality and promotions change Base64; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for Base64.
Revisit assumptions about Base64 after tool, tracking or pricing changes.
A short checklist for Base64 beats relying on memory during busy weeks.
Data URLs for tiny icons are fine; huge Base64 images bloat HTML.
Document which variant your API expects.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit Base64 weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure Base64; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about Base64, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions Base64.
If leadership wants only a headline, still keep working notes for Base64 in your own folder.
Seasonality and promotions change Base64; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for Base64.
Revisit assumptions about Base64 after tool, tracking or pricing changes.
A short checklist for Base64 beats relying on memory during busy weeks.
Data URLs for tiny icons are fine; huge Base64 images bloat HTML.
Document which variant your API expects.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit Base64 weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure Base64; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about Base64, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions Base64.
If leadership wants only a headline, still keep working notes for Base64 in your own folder.
Seasonality and promotions change Base64; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for Base64.
Revisit assumptions about Base64 after tool, tracking or pricing changes.
A short checklist for Base64 beats relying on memory during busy weeks.
Data URLs for tiny icons are fine; huge Base64 images bloat HTML.
Document which variant your API expects.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Try the tools
Use the Base64 Encoder & Decoder.
