The person behind Tool Lab
Tool Lab is a one-person project, not a company. This page explains who maintains it, how the tools are built, and how the site stays free — so you can decide whether to trust it with your files.
Tool Lab started with a small annoyance that kept repeating. Every time I needed to compress a PDF or convert an image, the first three search results wanted the same things: create an account, accept a file size cap, wait in an upload queue, then find a watermark on the result.
What bothered me most was not the friction. It was that a contract, a scanned ID or an internal report had to be uploaded to a server I could not inspect, run by a company whose retention policy was a paragraph I had to take on faith.
So I built the toolkit the other way around. Every tool on this site reads your file with the JavaScript File API and processes it in the memory of your own browser tab. There is no upload endpoint in the code, which means there is nothing to leak, nothing to retain and nothing to sell. You do not have to believe that — open your browser’s network tab while you use any tool and watch for yourself.
That single constraint shapes everything else. No account, because there is no server-side session to create. No file size limit, because there is no storage quota to enforce. No paid tier, because running no file servers means each additional user costs close to nothing.
The trade-off is honest and worth stating: processing happens on your device, so a very large file will be limited by your own memory rather than by a data centre. On a modern desktop that ceiling is several gigabytes — higher than the free tier of most upload-based tools.
How this stays free: the site is funded by non-intrusive display advertising. There are no sponsored tool placements, no affiliate links inside the tools and no data brokering — there is no user data to broker in the first place. If that ever changes, this paragraph changes with it.
Six rules this site is built on
These are engineering constraints rather than marketing lines. Each one is visible in how the tools actually behave.
Privacy by architecture
Files are read locally with the JavaScript File API. No upload endpoint exists in the codebase, so there is no server copy to secure, retain or lose.
Speed without a queue
Nothing is transmitted, so nothing waits in line. Processing time depends on your own hardware, not on how busy a shared server happens to be.
Free with no asterisk
No account, no trial, no locked export, no watermark. Every tool is complete on first use, and there is no upgrade page to find.
Works on the device you have
Responsive from the first line of CSS. The same tool runs in a desktop browser, a tablet and a phone without a separate mobile build.
Verifiable, not just claimed
Because processing is client-side, you can audit it. Open DevTools, watch the network tab, and confirm that no request carries your file.
Simple enough to skip the manual
Drop a file, adjust one setting if you want, download the result. Every tool follows the same shape so the second one needs no learning.
Nine tools, honestly counted
This is the complete list as of today — not a roadmap presented as a product. Anything still being built is labelled as such on the tools page.
New tools are prioritised by what visitors actually ask for.
What this site does and does not do
Stated plainly, so there is nothing to discover later in a settings page or a policy update.
What it does Committed
- ✓ Processes every file inside your browser tab
- ✓ Releases that memory the moment you close the tab
- ✓ Works without an account, an email or a cookie wall
- ✓ Returns output with no watermark and no export cap
- ✓ Discloses its funding model on this page
What it never does Ruled out
- × Upload, copy or store your files on a server
- × Sell, share or broker user data to third parties
- × Hide working features behind a paid tier
- × Accept payment for placement in tool listings
- × Require an account to unlock a full-quality result
Try it before you trust it
Open any tool, then open your browser’s network tab. The absence of an upload request is the whole argument.