This is a privacy-first local alternative to the upload-based tool sites that ask you to hand over your contract, your medical scan or your client drawing before they will do a five-second job. Every tool here runs 100% inside your browser: no login, no upload, no account, and no copy of your file kept anywhere but your own device.
The site is built and operated by Wen Xin, a developer who wants to make the web a little less annoying, one tool at a time.
Contact: wenxin202305@gmail.com
Most "free online tool" websites today bury a five-line utility under cookie walls, forced sign-ups, upload queues, and three pages of SEO filler before the actual button — and, quietly, they keep a copy of whatever you uploaded. Tool Station started as a reaction to that: instead of another upload box, we ship a privacy-first local alternative. Each tool is a single page that does its job in seconds, on your own CPU, with no account and no upload.
The utilities are plain HTML and JavaScript. Where heavy lifting is needed — PDF generation, DXF parsing, image segmentation — the browser's own APIs and WebAssembly modules do the work on your device. This is why the site needs no backend for tool logic, and why it stays fast.
New tools are added when a task annoying enough crosses our path. If a small utility would save you time, the contact page is open — the best suggestions come from people doing real work.
Tool Station is an independent, one-person project run by Wen Xin, a software developer. There is no company behind it, no venture funding and no growth team — just a developer who got tired of uploading a private document to a random website in order to change one number in it. Every tool on this site exists because that specific task was annoying enough to solve properly. If something is broken or missing, the same person reads the email: wenxin202305@gmail.com.
How this site is made. Every tool is built and tested in real browsers — Chrome, Edge, Firefox and Safari — before it goes live, and every guide on this site is written from actually using the tool it describes, on the same kinds of files you would use it on. When a claim published here turns out to be wrong, the fix is recorded in the corrections list below rather than being silently edited.
The tools are free and stay free. The site is kept online with money from display advertising (Google AdSense) shown on some pages. Advertising pays for hosting and domain costs; it does not buy influence over what the tools do. There is no affiliate padding, no "recommended" rankings, no sponsored tools and no paywalled features. Nothing you do inside a tool changes what ad you see — the ad networks never receive your file, your text or your results.
The tools target the current versions of Chrome, Edge, Firefox and Safari on desktop and mobile. A few of them — the ones that use WebAssembly, such as background removal and PDF rendering — need a reasonably modern browser and will say so instead of failing silently. Pages are written in semantic HTML, work with keyboard navigation and screen readers, respect your operating system's dark mode setting, and stay readable when you zoom in. Nothing is hidden behind hover-only interactions.
Each page is a single static HTML file with plain JavaScript — no build step, no framework, no bundle that needs a loading spinner. Where heavy lifting is required, the browser's own APIs do the work: the File API for reading files you pick, Canvas and WebAssembly for image segmentation, and well-known open-source libraries for PDF reading and writing. That is why the site needs no backend for tool logic, why it loads fast on a phone, and why it keeps working if you lose your connection after the page has loaded.
Suggestions are welcome and genuinely read. The most useful request names the task, the file types involved and what the current workaround is. Requests that need a server — anything involving other people's data, live prices scraped in the background, or user accounts — are out of scope, because staying local is the whole point of the site.
Privacy promises on the internet are cheap, so do not take this page's word for it. Load any tool once, switch off your network connection, and run a job on a throwaway file — a tool that finishes offline did not use a server. The full technical walkthrough, including what local processing does not protect you from, is in Why every tool here runs in your browser. The commercial logic behind the upload-based alternative is set out in What "free" online converters actually do with your file.
We would rather publish a correction than leave a misleading claim standing. A running log of changes affecting what the tools do or how they are described: