Privacy by architecture

Your files never leave your browser

Most file tools upload your documents to process them. Filecraft doesn't. Everything runs locally in your browser — we never see your files.

You can verify this yourself in under 30 seconds.

See how it works Or verify it yourself →

File stays in your browser

Your device → Browser memory → Your download

Other tools upload your files. Filecraft does not.

This is not a feature difference. This is an architectural difference.

Upload-based tools

Your file is sent to their server over the internet
Their server processes your file on their infrastructure
A copy of your file exists on systems you don't control
You trust their promise to delete it afterward
If their server is breached, your file is exposed

The Filecraft way

LocalInstantPrivate

Your file stays in your browser — it is never sent anywhere
JavaScript in your browser tab does all the processing
No copy of your file exists outside your device
There is nothing to delete because we never had it
A breach of our servers cannot expose what we never received

What happens to your file

Follow your file from selection to download. It never leaves your device.

1
You select a file
Your browser reads the file from disk into its own memory — one place only.
File location: Your browser
2
Processing runs locally
Web Workers handle PDFs. Canvas API handles images. JavaScript handles data. All inside your browser tab. No network calls.
File location: Still your browser
3
You download the result
The processed file goes directly from browser memory to your disk.
File location: Your device
4
You close the tab
Memory is released. No copy exists anywhere else — not on our servers, not in transit, not cached.
File location: Nowhere

Prove it to yourself

You can confirm everything above in 30 seconds. No special tools — just your browser.

1
Open Developer Tools → Network tab
Press F12 (Windows/Linux) or Cmd + Option + I (Mac). Click the Network tab and clear the log.
2
Use any Filecraft tool
Drop a file, process it, download the result.
3
Read the network log
You will see page assets and analytics beacons. You will not see your file.

GET main.js

GET styles.css

GET vendor.js

✕ No file upload

✕ No POST request

Common questions

Can Filecraft see my files?

No. Your files are read into your browser's memory and processed there. Filecraft's servers receive a page visit — they never receive file content, metadata, or filenames.

What if I lose internet while processing?

Once the tool page has loaded, processing does not require an internet connection. You can disconnect from Wi-Fi and your file will still process. You need a connection only to load the page initially.

How is this different from tools that say they delete files after processing?

Those tools upload your file, process it on their server, then promise to delete it. You are trusting their deletion policy. With Filecraft, there is nothing to delete because nothing was uploaded in the first place.

Does local processing work on mobile?

Yes. Modern mobile browsers support the same JavaScript and Web Worker APIs. Processing happens on your phone's processor, just like on a desktop.

Are there any exceptions where files are uploaded?

In normal use, never. Enterprise accounts have an optional server-assisted mode for very large files, but it requires explicit consent and is clearly labeled. It is never the default.

What about the OneDrive/SharePoint integration?

When you open a file from OneDrive or SharePoint, your browser downloads it directly from Microsoft's servers. It is then processed locally in your browser. Filecraft's servers handle only the authentication metadata — never the file bytes.

Try it now

Try it. Open your Network tab and see it for yourself.

All tools →Security architecture →Pricing →