Tools that stay
on your device.
Tool Pantry is a collection of 184 free browser tools for everyday files. Everything runs locally — no uploads, no accounts, no watermarks. Here's who makes it and how it's tested.
Tool Pantry in one line: a small independent team building free file tools that run entirely in your browser — PDF, images, video, audio, and text — funded by simple ad slots, with every tool tested on real files before release.
Why everything runs locally
Most "free online tools" work by uploading your file to a server, processing it there, and sending it back. That model has three costs people rarely think about: your private files sit on someone else's computer, the upload/download round trip wastes time, and the server bill eventually shows up as watermarks, file-size limits, or paid tiers. We built Tool Pantry on the opposite model. Modern browsers can compress images, edit PDFs, trim video, and convert audio entirely on the device — so there is no server, no upload, and nothing to monetize beyond the occasional ad slot.
What we believe
- Privacy by architecture, not by promise. Files never leave your device because there is nowhere for them to go. You can verify it in your network panel — or by turning off the internet and watching the tool still work.
- No accounts, ever. Nothing here needs a sign-up, and nothing here can lose your password.
- Honest numbers. When our guides claim a compression result, it's a number we measured on a real file — and our benchmarks and speed tests pages publish the raw results, including the unflattering ones (like HEIC-to-JPEG conversions sometimes growing files).
- Free means free. No watermarks, no artificial size limits, no "pro" gate hiding the actual export button.
How the tools are tested
Every tool runs through automated end-to-end tests on real files before it ships — the same tests that produce the measured numbers in our guides. For example, the video tools are verified with frame-level checks (a muted video's bitstream is confirmed MD5-identical to its source; a rotated video's output is compared pixel-by-pixel against a reference rotation). Guides follow the standards described on our editorial page: real test files, published measurements, dated updates.
Built for people — and for agents
Besides the human-facing site, everything here is readable by machines: every page has a Markdown version, the site publishes llms.txt and a machine-readable catalog at tools.json, stateless helper endpoints live under /api, and there is an installable Agent Skill so coding assistants can route file tasks here. All free, no keys.
Contact
We are reachable through our GitHub profile: github.com/wu736139669. For press and directory listings, the press page has boilerplate copy, logos, and facts. For corrections to any guide or benchmark, see the editorial page — we fix errors and note the change.
Who runs Tool Pantry?
A small independent team that builds and tests every tool in-house. There is no company account to sign up for and no sales team — the public presence is the site itself and the GitHub profile at github.com/wu736139669, which is also the way to reach us.
How does Tool Pantry make money if everything is free?
Some pages show advertising slots. That is the entire business model: no accounts, no paid tiers, no upsells, no selling of data — because no data ever reaches us. Files are processed in your browser and never uploaded.
How can I verify my files are never uploaded?
Open your browser's network panel while using any tool — you will see no upload requests for your file. Stronger check: load a tool, disconnect from the internet, and it still works, because the processing code already runs on your device.
How are the tools and guides tested?
Every tool goes through automated end-to-end tests on real files before release, and the guides publish the actual measured numbers — like the HEIC and video compression figures on our benchmarks pages. When something fails a test, it does not ship.
Is there an API or agent layer?
Yes. Every page has a Markdown version, the site publishes llms.txt and a machine-readable catalog at tools.json, stateless endpoints live under /api, and there is an installable Agent Skill for coding assistants. All free and key-less.