About FineDocs

The idea

Almost every free file tool on the web works the same way: you upload a document, a server processes it, you download the result. That design made sense when browsers could not do much. It has not made sense for years, and it comes with costs that have nothing to do with the actual work — you wait through two transfers, you hand a copy of your document to a company you know nothing about, and you accept a file-size cap that exists to control someone’s bandwidth bill.

Modern browsers can decode a JPEG, restructure a PDF and run a compression codec directly. So that is where the work happens here. The site is a set of static files, and the only server-side code behind it accepts one short message: the name of a tool that has just finished, which is how the count in the footer is kept. It has no way to receive a document, even in principle.

What that buys you

No upload wait, so a 100 MB file is processed as fast as a small one. No account and no email address. No watermark. No queue and no daily limit, because there is no shared resource to ration. The size ceiling is your own device’s memory rather than a business decision. And the tools keep working if your connection drops mid-session, since nothing needs the network once the page has loaded.

What it costs you

Being straight about the trade-offs, since most sites are not.

Processing is bounded by your device. A very large PDF on an older phone can run out of memory where a server with plenty of RAM would not. Each tool states the file size it has actually been tested up to rather than an aspirational number.

Some operations are genuinely unavailable. Real PDF compression — the kind that resamples embedded images and subsets fonts — requires software licensed under the AGPL. Rather than ship a copyleft dependency or a misleading half-measure, that tool is simply absent for now, and pages say so instead of pretending otherwise.

A few formats need capabilities that not every browser has. Where that is the case, the tool says what your browser is missing rather than silently producing nothing.

How the tools are built

Wherever the browser can already do the job, it does, with no download at all: image decoding and encoding use the same pipeline that draws pictures on every site you visit, and hashing uses the built-in cryptography API.

Where a real library is needed, it loads only when you choose a file, never on page view — which is why these pages open instantly despite some tools depending on multi-hundred-kilobyte WebAssembly modules. PDF work uses @cantoo/pdf-lib, JPEG compression uses Mozilla’s MozJPEG compiled to WebAssembly, and everything is licensed permissively.

All the heavy work runs in a Web Worker, on a thread separate from the page, so the interface stays responsive even while a large file is being processed.

The numbers on each page are real

Every tool page has a measured results table. Those figures are not estimates or marketing: a script runs each tool over the same fixed set of sample files on every build and records the actual byte counts, including the cases where a tool makes a file larger. Where a page claims a tool beats some alternative, the comparison was run and the result is what is printed.

Money

The site is free with no watermarks and no paid tier. Static hosting costs essentially nothing at this scale, which is what makes that sustainable. There is no advertising at the moment; if it is ever added it will be limited and kept away from the tools themselves, because an ad next to a download button is both hostile and a good way to get banned by ad networks.

Your files are not the business model and never will be — there is no mechanism by which they could be, given they never leave your machine.

Contact

Bug reports and requests for specific tools are genuinely useful. Reach us at hello@finedocs.online.