Filewhisk is a small collection of file tools that run entirely inside your web browser. Nothing you open here is uploaded, queued, stored or processed on a remote machine.
Who makes Filewhisk
Filewhisk is built and maintained by the Filewhisk team, a small independent team that launched the site in September 2026. We are not part of a larger software company, there are no investors, and there is no premium plan waiting behind the free tools.
The site started from a simple frustration: compressing a passport photo or merging two PDFs should not mean handing personal documents to a server you know nothing about. So every tool is written to run on your device and to keep working after the page has loaded, even with the network switched off. After launch we keep improving tools based on bug reports, feature requests and the searches that bring people to each page.
You can reach the team directly at hello@filewhisk.com — a person reads every message.
How a tool gets built here
Every tool goes through the same four steps before it appears on the site, and they are worth describing because they are the reason some obvious tools are missing and others took longer than they look:
- Research first. Before anything is written we read what the existing tools for that job actually do, where they stop, and what people are really trying to finish. If we cannot find something to do better than what exists, we do not build it.
- Built to be tested. The tool is written so a script can drive it like a person would — choosing files, clicking buttons, reading the result.
- Tested with real files in a real browser. Not a mock: an actual browser opens the actual page, drops in prepared files (rotated PDFs, transparent PNGs, unbalanced photos of signatures, encrypted documents) and the output is measured. A page-numbering tool is checked by reading the numbers back out of the finished PDF and measuring where they landed; a signature tool by re-rendering the signed page and looking at the ink.
- Checked live. The same tests run again against the published site, and screenshots are taken with a file loaded, because a tool that works locally can still break on the real thing.
Those tests have caught real bugs before anyone else met them — page ranges that were silently ignored, a watermark that drew the page content twice, a preview that lagged one stroke behind. We would rather tell you that than pretend the first version is always right.
What we will not do
- Upload your files. Not as an option, not “for faster processing”. If a tool cannot run in your browser, it does not ship.
- Put a tool behind an account. No sign-up, no email wall, no “free trial” that turns into a subscription at the download step.
- Add a watermark to your output and sell its removal.
- Invent numbers. Where a page quotes a file size, a rule or a measurement, it comes from a test we ran or a source we link. When something is a rule of thumb, it says so.
- Take payment for a recommendation. When a page says another tool is better for a job, that is because it is.
Why local processing
Almost every free file tool on the web works the same way: you upload your file, a server converts it, and you download the result. That model has three problems. Your file sits on someone else's disk. The operator has to pay for bandwidth and compute, so they impose file size caps, daily limits and sign-up walls. And you wait in a queue.
Modern browsers can do this work themselves. The Canvas API, WebCodecs and WebAssembly are fast enough to compress an image, convert a format or strip hidden EXIF data on your own hardware. Building the tools this way removes all three problems at once: there is no upload, so there is nothing to cap, nothing to store, and nothing to wait for.
How to verify the claim
You do not have to take our word for it. Open a tool, then disconnect from the internet before you drop a file in. The tool still works — the page was already downloaded, and the processing happens locally. You can also watch the network tab in your browser's developer tools and confirm that no request carries your file.
How this site is funded
Filewhisk is free and supported by advertising. We do not sell data, and because your files never reach us, there is no file data that could be sold. Ads are placed around the content, never inside the tool itself, and never in a way that interrupts a task in progress.
Contact
Found a bug, or want a tool that does not exist yet? The contact page explains how to reach us.