Skip to main content
ToolForForever LogoToolForForever

About ToolForForever

ToolForForever is a small collection of 26 free tools for everyday file work: combining and shrinking PDFs, compressing and converting images, building ZIP archives, reading text out of a photo, and running the sums people actually need. Every one of them runs inside your browser.

Creators

ToolForForever was created by Sameer Rout and Sampangi Sony. Built with a focus on speed, accessibility, and privacy, the platform provides everyday online utilities designed to process files locally in your browser without uploading your documents to remote servers. Practical processing limits depend on your device memory and file size.

Why this site exists

Searching for something as ordinary as “merge two PDFs” returns a wall of sites that all work the same way: you upload your file to their server, wait, download the result, and hope that the copy they kept is deleted on the schedule their privacy policy claims. For a restaurant menu that is fine. For a rental contract, a passport scan, a medical letter or a client’s accounts, it is a bad trade, and it is a trade most people never consciously agreed to.

The uncomfortable part is that the upload is usually unnecessary. Browsers have been able to manipulate files locally for years: canvas for images, WebAssembly for serious computation, Web Workers for keeping the interface responsive, and mature libraries for PDF and archive formats. Once those pieces exist, the server stops being a technical requirement and becomes a business decision - a way to meter usage, build an email list, or train a model on other people’s documents.

ToolForForever is the version where that decision goes the other way. There is no upload endpoint anywhere in the application, because there is nothing on the server to receive a file. The site is a set of static pages, and the work happens on your machine.

How it works, concretely

You load a page. Your browser downloads the HTML, a stylesheet, and a small amount of JavaScript. When you open a specific tool, that tool’s code is fetched - and only that tool’s code, which is why opening the word counter does not download a PDF engine. When you choose a file, your browser reads it from disk on your instruction. The conversion runs in the tab, or in a Web Worker that the tab creates so the page stays responsive.

The actual computation is done by four ordinary web technologies depending on the task: the canvas API for anything image-related, PDF-LIB and pdf.js for documents, fflate for ZIP archives, and WebAssembly for OCR and background removal. None of them is capable of transmitting your file, because transmitting requires a network request and none is made.

Two tools do download something the first time you use them: the background remover fetches roughly 40 MB of machine-learning weights, and OCR fetches the language data for the language you pick. Those are downloads of model data to your browser, and they are cached afterwards. Your photograph or scan is still read locally and still never leaves your device. We would rather state that plainly than claim “nothing is ever downloaded”, which would not be true.

How the site is paid for

Hosting a static site is inexpensive, which is deliberate: it means the site does not need to monetise your documents to survive. Running costs are covered by advertising through Google AdSense, shown on content pages to visitors who consent to it.

Ads are never shown while a tool is processing or on a result screen, where a misplaced click would be likely. They are always labelled as advertising, never styled to look like a button or a download link, and there are never more than three on a page. Advertising has no influence on the tools, and there is no “premium” tier that produces better output - everybody gets the same result.

Principles we hold to

These are not aspirations; they are constraints the code is written against, and they are checked before anything ships.

What we are not

We are not affiliated with Google, Adobe, Microsoft, Apple or any other company whose product names appear on this site. Those names are used only to describe compatibility, because that is how people search for what they need. We are not a document management service, we do not offer cloud storage, and we cannot recover a file you have lost.

We are also not infallible. Conversion and compression are produced by your browser, and different browsers vary slightly in how they encode images. If an output matters - a document you are filing, a photo for an official application - check it before you rely on it. Every relevant page says so, and the Disclaimer sets out the limits in full.

Getting in touch

Bug reports are genuinely welcome, especially when a specific file produces a wrong result. Because we never see your files, a description of the file and what went wrong is far more useful than the file itself, and we would rather you did not send us anything confidential.

For questions, corrections to a guide, or anything else, use the contact page. We read everything and answer most inquiries within a couple of days.

Start with something useful

If you came here to get something done rather than to read about us, these are the tools people use most.