About Toolifine

The idea

Most online file tools work the same way: you upload your document to a server you know nothing about, a program there changes it, and you download the result. It works. It also means a contract, a passport scan, a medical letter or an unreleased set of accounts has been copied onto somebody else's machine, and you are taking their word for what happened next.

Browsers stopped needing that arrangement some years ago. They can read and write files, decode images, run compiled code at close to native speed, and use several processor cores. So the tools here load the code instead of the file: the page arrives, and then your own computer does the work. Nothing is uploaded, which means there is nothing to retain, leak or be asked to hand over.

What that actually buys you

• Privacy that is structural, not promised. Open your browser's Network tab and watch. There is no request carrying your file, because there is no server waiting for it.
• No queue. Nothing is uploaded, so nothing waits to upload. Large files are usually faster this way, not slower.
• It works offline. Once a tool page has loaded, disconnect. It keeps working.
• No account, no watermark, no upsell on the result.

And what it costs

This is the part most sites leave out. Doing the work locally means it is bounded by your device, not by a server farm. A 500-page PDF on a five-year-old phone can run out of memory where a server would not have blinked. Some formats have no usable open implementation at all, so those tools do not exist here rather than existing badly.

A few conversions genuinely need software a browser cannot provide — Office documents converted with real layout fidelity, for instance. Those run on our server, they say so on the page, and the file is deleted immediately afterwards. We would rather label the exception clearly than pretend it away. The privacy policy names every one of them.

How the tools are built

Every format is handled by a real implementation of that format — the same libraries used by desktop software — rather than by guessing. Where a tool cannot do something correctly, it says so instead of returning a damaged file quietly. The CSS minifier, for example, refuses stylesheets that use CSS nesting, because the minifier underneath it deletes nested rules without reporting an error. A tool that silently breaks your file is worse than one that declines.

Who this is for

Anyone who needs to change a file and would rather not hand it over: people working with client documents, anything under an NDA, medical or legal paperwork, or simply anyone who finds uploading a private document to a stranger's server an odd thing to be asked to do.

Found something broken, or a file that did not convert properly? Tell us — it is the fastest way for the site to get better.