About
This site exists because decoding Base64 is usually the last step of a frustrating afternoon: the string is truncated, the padding is gone, the prefix is still attached, and you have no idea what the file was supposed to be. The point here is to make that step trivial.
Why build it
Most Base64 tools assume a clean input and a user who already knows the answer. Real inputs are messier: a value pasted out of an API response, an email attachment wrapped in awkward places, a token with the URL-safe alphabet, a file with no name. This tool assumes the input is messy and says plainly what it found.
Principles
- Local by default — nothing is uploaded, and it works offline once loaded
- Say what happened — repairs are reported rather than applied silently; failures name the exact position
- No account, no wall — no sign-up, no quota, no upsell
- Honest about limits — truncated data cannot be recovered, and the tool tells you so instead of guessing
How it is built
A static site: plain HTML, CSS and TypeScript, no framework, no backend. Every page is generated at build time with its own title, description and structured data, and the conversion logic is covered by an automated test suite. Because there is no server work, there is nothing to queue behind and nothing to leak.
Feedback
Bug reports, awkward inputs the tool handles badly and feature ideas are all welcome at greedy2899@gmail.com. A real example that failed is worth more than a general suggestion.
Frequently asked questions
Will it stay free?
Yes. There is no server cost to pass on and no paywall planned. If advertising is introduced later it will not affect what the tool does.
Who maintains it?
A small independent project. The aim is a tool that does one job properly rather than a suite of half-finished converters.
Are feature suggestions welcome?
Yes, especially when they come with the input that failed. Requests that fit the browser-only, no-upload design are the easiest to say yes to.