Runs locally: why your files are never uploaded
All tooloora tools process your files locally in your browser — they are never uploaded. There is no upload server, no queue and no retention period: whatever you select stays on your device as a file and is processed by JavaScript and WebAssembly right in your browser. This page shows you how to verify that yourself.
Your file never leaves your device — all processing happens right in your browser.
How can I prove that nothing is uploaded? The airplane mode test
The simplest proof needs no technical skills: cut the internet connection before you process a file. An upload service would fail immediately — tooloora tools keep working.
Open a file tool, for example the PDF compressor, and let the page load completely.
Disconnect from the internet: turn on airplane mode or switch off Wi-Fi.
Select your file and process it as usual.
Save the result. Everything works without a connection, because nothing is uploaded.
What does the network tab show while a file is processed?
If you prefer hard evidence over a thought experiment, watch the traffic in your browser's developer tools:
- Press F12 (or right-click → Inspect) and open the “Network” tab.
- Process a file and watch the list of requests.
- No upload request appears: there is no POST or PUT request carrying your file to a server.
What you do see: the one-time delivery of the page itself and, for some tools, a processing engine being fetched — both are downloads to you, never uploads from you.
What data does tooloora transfer at all?
Honesty is part of the promise: “local” does not mean zero network traffic. These transfers happen — none of them carries your files:
- The page itself: HTML, CSS, JavaScript and fonts are delivered when you open tooloora.com, like on any website. This produces the usual server logs (see the privacy policy).
- Currency rates: the currency converter fetches daily rates from our own server (/api/rates). The rates come to you — what you convert is not sent anywhere.
- Processing engines (WASM): some tools fetch their engine once from our own server — a download to you, not an upload from you.
- Ads in the future: tooloora is meant to be funded by ads. Even then, ads load content — your files are never sent.
One principle behind all of this: tool resources are served from our own origin, not from third-party CDNs. Future ads would be the only third-party source — and they have nothing to do with your files.
How is this different from upload services?
Classic online converters work server-side: your file is uploaded, processed on someone else's machines and kept there for a retention period. That is not a scandal, it is the standard model — but it means a copy of your file leaves your device and you have to trust the provider's deletion policy.
Two examples from the providers' own privacy policies (as of July 2026): iLovePDF states that processed files are stored for up to 2 hours, Convertio for up to 24 hours. With local processing this question never comes up — there is no server copy to delete.
The honest flip side: local means your device does the work. For very large files a powerful server can be faster than an older phone, and browser memory sets a limit. In return you get something no upload service can offer: your file was never gone.
Frequently asked questions
Are my files really not uploaded?
No. Processing runs on JavaScript and WebAssembly directly in your browser; there is no upload endpoint for files. You can verify it yourself: disconnect from the internet and process a file (airplane mode test), or watch the network tab in your browser's developer tools.
What does local processing mean for privacy and the GDPR?
Your file contents never leave your device — no server copy is created, there is no retention period and neither we nor third parties can access them. The only transfer is what every website does: delivering the page itself (see the privacy policy).
Do the tools work offline?
Once the page is loaded, yes — processing needs no connection. You do need internet to open the page (and the first time a processing engine loads). tooloora is not an installable offline app yet.
Which exceptions are there to “local”?
Four, and all of them are downloads to you: the delivery of the page itself, currency rates from our own server, processing engines (WASM) from our own server, and ad banners in the future. None of them transfers your files.
Where are the limits of local processing?
Your device does the computing. Very large files take longer on weak hardware, and the browser's memory sets a hard limit — a data center can out-muscle a phone. For everyday file sizes the difference is barely noticeable.