Explainer ·
Why Utilio keeps files on your device
Utilio is built so common file tasks can finish inside your browser. For local tools, the file is opened by the page on your device, processed there, and the result is created there.
Short version
Local file tools do not send the file content to Utilio servers.
Your browser still needs enough memory and format support to process the file safely.
Network lookup tools are different: they disclose what is sent before you run them.
What happens
When you choose a file in a local Utilio tool, the browser gives that page temporary access to the selected file. The tool reads it in the browser tab, performs the task, and shows or exports the result from the same device.
This model fits viewers, PDF utilities, image tools, text tools, and generators where the work can be handled by browser APIs or code already loaded with the page.
- A PDF compression tool can prepare a smaller copy without sending the source PDF to Utilio.
- An image tool can resize, convert, or clean metadata from a local image in the browser.
- A viewer can open a document for inspection without creating an account or server storage.
What does not happen
For local tools, Utilio does not receive the file body, pasted text, generated values, or result content. Utilio also does not use tool content for advertising or AI training.
The page may still load the application code, styles, icons, and privacy-safe analytics configuration. Those requests are separate from the content you process in the tool.
- No Utilio account is created for the file.
- No server file-processing queue is used by local tools.
- No raw file names, document text, passwords, tokens, or generated values are allowed in analytics events.
What you should still watch out for
Browser-local processing reduces what Utilio can receive, but it does not make every file safe. A file can still contain sensitive metadata, hidden document data, or malicious content that your browser or another app may handle later.
Use a trusted device, avoid shared browser profiles for sensitive work, review the result before sending it elsewhere, and be careful with browser extensions that can read page content.
Network tools are separate
A small number of tools cannot work only from your device. DNS Lookup, for example, needs an external DNS-over-HTTPS lookup and explains that before it runs.
Utilio separates local browser tools, network lookup tools, static reference pages, generators, and any future tools with server processing so the processing model stays visible.
Questions people ask before using private browser tools
Are online file tools safe for private documents?
It depends on how the tool works. Utilio labels local tools before the input area so you can see when a file stays in the browser instead of being sent to a server.
Can I edit or compress a PDF without uploading it?
For supported local PDF tools, yes. The browser opens the file on your device and creates the result there. Very large or unsupported files may fail because the browser still has memory and format limits.
Does Utilio store my files after I use a local tool?
No. Local tools do not send file content to Utilio servers, so Utilio has no server file copy to store after the task.