← All tools · Data Tools

Base64 Encode and Decode — Locally, Without Uploading

Encode a file (image, PDF, anything) to base64, or paste a base64 string and decode it back into a downloadable file. Useful for embedding images in HTML/CSS/email, debugging API payloads, or sharing a quick attachment via a text channel. All conversion is local — important because base64 strings can contain credentials, certificates, or signed tokens that you should never paste into a stranger's webpage.

No signup No file size limit Works offline Open source

Base64 ↔ File

Encode files to base64 or decode back. Browse all 13 converters →

Images → PDF

Combine JPG/PNG into one PDF document.

Local

Drop files here or browse

Up to any size. Multiple files OK.

🔒 stays on your device
Drop a file to enable

ForgeMyFile vs typical online converters

A side-by-side. We're not picking on a specific competitor — these are the patterns common across the category.

ForgeMyFileTypical online converter
Files uploaded to a serverNeverYes, every conversion
Files stored after conversionImpossible — nothing to storeOften retained 1–24 hours
Account / email requiredNoOften, especially for larger files
File size limitsYour device's RAMTypically 5–100 MB free tier
Works offline (after first load)YesNo
Source of conversion engineOpen-source libraries, view-source-ableProprietary server-side, opaque
SpeedLimited by your CPULimited by upload speed + queue
Page itself shows adsYes, plainly labeledYes, often disguised

Privacy, in plain language

We're going to be specific instead of saying things like "100% anonymous." That phrase is a lie on any page that loads ads — and we load ads. Here's what's actually true.

What runs entirely on your device

  • Reading your file from disk into the browser
  • The conversion itself — every one of the 13 tools
  • Saving the converted file to your downloads folder
  • The "preview" of converted text, JSON, or HTML

What does not run on your device

  • Ad scripts (when enabled by the operator) and their analytics
  • Page-view analytics, when enabled
  • The first-load fetch of Google Fonts CSS (libraries themselves are self-hosted)
  • After first load, the page works fully offline; ads do not

What we (the site operators) literally cannot see

  • Your file names
  • The contents of any file you convert
  • Which converter you used, or how often
  • Your conversion history

What ad networks may see

  • Your IP address and approximate location
  • Your user agent (browser + OS string)
  • The page you visited (URL)
  • Standard ad-serving cookies, where allowed by your browser

If you want to neutralize the ad networks too, run an ad blocker. The conversion tools themselves work either way — the privacy we offer for your files is independent of whether you block our ads.

How to use base64 ↔ file

  1. Drop a file (to encode) or paste base64 (to decode)Direction auto-detected.
  2. ConvertEncoded result appears in preview.
  3. Copy or downloadLocally.

Frequently asked questions

Will my file or data be uploaded?

No. Encoding/decoding uses the browser's FileReader and atob.

What about data: URI prefix?

Decode handles strings with or without the prefix.

Encoding format?

Standard base64. Not URL-safe — let us know if you need that variant.

Is there a size limit?

Browser memory only. Multi-megabyte files work; very large files may slow encoding visibly.

Related private tools