Base64 to File · File to Base64
Paste it in. Raw Base64, a full data: URL, or an entire JSON API response — the tool inspects the input first, repairs what it can, and tells you exactly where the data breaks. Images, PDFs and archives are all recognized. The result appears as you paste; there is no button to press.
- Runs entirely in your browser — nothing is uploaded
- File type read from the header, not the file name
- Missing padding and stray line breaks fixed for you
- Paste, drop a file, or Ctrl+V a screenshot
- Over 20 file types recognized from magic bytes
Processed as you paste — no button to press (Ctrl+Enter converts now / Esc clears)
Drop a file here, or — Ctrl+V a screenshot works too
Any file type · 100 MB maximum
Paste, drag and drop, or Ctrl+V a screenshot
How to use it: three steps
- Paste it in — paste, drop a file, or Ctrl+V a screenshot. Any format works
- Read the report — prefixes, line breaks and missing padding are repaired for you; broken data is named precisely
- Take the file — download the restored file, or copy the encoded result
How it works
There is no backend API — just static files. Everything you see is the whole app, and the conversion runs in your browser.
No network round trip and no spinner: the result is there the moment the input lands.
Not from the extension. A file starting with %PDF is a PDF even if it is named .exe. Over 20 formats are recognized out of the box.
Frequently asked questions
Which file types are supported?
Images (PNG, JPEG, GIF, WebP, SVG), PDF, Word, Excel and PowerPoint (Office Open XML), ZIP, MP3 and other audio, plus plain text. The type comes from the file header, so a wrong file name does not matter.
How large can the input be?
Up to 100 MB. Anything above a few megabytes is processed on a background thread, so the page stays responsive while it works.
Is Base64 encryption?
No. Base64 is an encoding that lets binary data travel through text channels — anyone can decode it in seconds. Never use it to protect passwords, keys or personal data.
What if decoding fails?
The report names the exact position of the bad character and the likely cause: invalid characters, missing padding, truncated data, or Base64URL mixed with the standard alphabet. Each fix is covered under common Base64 decode errors.