About FilesProcess

FilesProcess is a set of 171 file tools – 62 for PDFs, 87 for images, 22 for audio – that do their work inside your browser. There is no upload endpoint, no account system and nowhere on a server for your documents to sit. It has been running since October 2026.

Why it works this way

The usual online PDF or image tool takes your file, sends it to a server, does the job there and deletes it some hours later. That is a reasonable engineering choice, and for most files it is fine. It stops being fine the moment the file is a payslip, a bank statement, a signed contract or a photo of an ID card – because now a copy of that document exists on a machine you do not control, for a period you have to take on trust.

Browsers can do this work themselves. PDF.js, pdf-lib, MozJPEG, libwebp, libheif, Tesseract and DeepFilterNet3 all compile to JavaScript and WebAssembly and run on your device at usable speed. So that is where FilesProcess runs them. The trade-off is real and worth stating: your phone or laptop does the work, so very large files are slower here than on a server, and some things – validated PDF/A output, for one – cannot be done in a browser at all, so they are not offered.

You do not have to take the claim on trust

“We never see your files” is the easiest sentence in the world to write and one of the harder ones to check. Three ways to verify it yourself, in rough order of effort:

• Watch the network. Open any tool, press F12 → Network, and run it. No request carries your file, at any file size. Step-by-step walkthrough.
• Pull the plug. Load a tool, switch on airplane mode, then run it on a new file. It still works, because nothing on the other end is needed.
• Read the measurements. We ran the same upload test against the popular online file tools and published what each one actually sends: what online file tools upload, measured.

How it is paid for

There is no paid tier, no subscription and no account to create. Because every tool runs on your device, the site itself is static files on a CDN – the hosting costs little more than the domain name, which is why there is no pressure to put a login or a file-size wall in front of the tools. If that ever changes, this page will say so before anything else does.

How the tools are tested

Every tool is run end to end in a real browser against the production build with sample files, and the output is checked rather than the fact that a download appeared: PDFs are re-opened and their page count, text and encryption verified; converted images are decoded again and their pixels and dimensions compared; audio is re-measured. The in-place PDF editor is additionally checked against PDF.js on a corpus of real documents, confirming the edited text is present, the old text is gone, and nothing outside the edit moved by a single pixel.

Tools that only partly work say so on their own page, in the status badge and in a limitations section – “PDF to Word keeps fonts and layout for most digitally created PDFs” is a more useful sentence than a claim of perfect conversion that falls over on your first scanned file. One tool, PDF/A conversion, is listed as unavailable rather than shipped badly.

Who makes it

FilesProcess is built and maintained by one developer. It is not a company, there is no team behind it and no investor money in it – which is worth knowing both ways: nobody is being paid to monetise your attention, and nobody is on call at 3am either. If a tool hands you a wrong file, the fastest route to a fix is mailing it in; that address reaches the person who wrote the code.

What we collect

Anonymous page views and the name of the tool used – never file names, file sizes or file contents, because those never leave your device to be collected. Visitors in the EEA, the UK and Switzerland are asked before any analytics cookie is set. The privacy page lists every third party involved and exactly what each one receives.