We're listening

Get in Touch

Bug report, feature idea, or just a question about Base64? We read every message and respond promptly.

🐛

Report a Bug

Something producing incorrect output or broken in your browser? Tell us exactly what happened OS, browser, and input if possible.

Use the form →
💡

Feature Requests

Missing a mode, encoding variant, or UX improvement? We prioritise features that real developers need. Share your idea.

Use the form →
📖

Documentation & FAQ

Many common questions are already answered in our FAQ section covering Unicode support, URL-safe Base64, padding, and more.

Browse the FAQ →
🔐

Security & Privacy

Concerns about data handling or security? All processing is client side. Read our privacy pledge or reach out directly.

Read our pledge →
✉️

Direct Email

Prefer to email us directly? Send your message to our support email address.

[email protected] →

Send a Message

Fill in the details below and we'll get back to you as soon as we can. Fields marked * are required.

Please enter your first name.
Please enter a valid email address.
Please enter a message.
✓

Message Sent!

Thanks for reaching out. We've received your message and will get back to you within 1–2 business days.

We Read Every Message

We're a small team of developers and we take feedback seriously. Bug reports, especially those with a clear description of what went wrong, usually get the fastest response. We also track feature requests the most commonly requested ones make it into the tool.

<24h
Typical Reply
100%
Read Rate
Free
Always
Before You Write

Common Questions Answered

Check if your question is already covered you'll get a faster answer.

📡 Is my data sent to a server?

No. Everything runs in your browser using native JS APIs. Nothing is transmitted not even anonymously. It works offline after the first page load. Read our privacy pledge.

🌐 Why does Unicode / emoji break?

It shouldn't we use TextEncoder for proper UTF-8 conversion before Base64 encoding. If you're seeing issues, tell us your browser and the input that's breaking.

🔗 What is URL-safe Base64?

It replaces + with - and / with _ per RFC 4648 §5, safe for JWTs and query strings. Use the URL-Safe tab in the tool. More in the FAQ.

📁 How do I encode a file?

Switch to the File tab on the main tool, then drag-and-drop or browse for your file (up to 10 MB). You'll get a Base64 string you can use as a data: URI directly. Open the tool.

🔒 Is Base64 encryption?

No. Base64 is an encoding scheme fully reversible with zero confidentiality. Anyone with the string can decode it instantly. Use AES or RSA for actual encryption. Full FAQ answer.

⚙️ Can I use this offline?

Yes. After the page has loaded once, it works without an internet connection because all processing is client-side JavaScript with no external API calls. Learn how it works.