FilechangesHow File Processing Works
Filechanges mixes browser-based tools with a smaller number of server-assisted tools. This page explains which workflows stay on your device, which ones can reach the server, and where to read the matching security and deletion details.
Tools that stay in your browser
Core PDF tools and image tools run directly in your browser during normal use. For those workflows, your file does not need to be uploaded to or stored on Filechanges servers.
What exists temporarily during local processing
When you use a local tool, the file is loaded into browser memory so the tool can read, transform, and export it. The generated result is also kept temporarily in your current session so you can download it.
That temporary working copy is cleared when you reset the tool, refresh the page, or close the tab. For browser-only workflows, Filechanges does not need to store those working files on its servers.
Server-assisted tools
Some tools, including AI-assisted workflows, OCR, real office conversion, and PDF password operations, use server-side request handling. Those tools can send file contents or rendered page images to a Filechanges server route in order to generate a result.
In the current app code, those requests are processed for the active response and should delete temporary working files after completion. If you require a strictly browser-only workflow, use the local tools instead of the server-assisted conversion, OCR, password, or AI tools.
Security and deletion details
Browser-only tools give you the strongest privacy because the file stays on your device. If you use a server-assisted workflow, review the matching security and deletion pages before using it for sensitive material.
What users should expect
- No account is required for the main local PDF tools.
- Browser-only files are limited to the tool and tab you open; they are not shared between users.
- For browser-based tools, processing speed depends on your own device and browser.
- If you are handling highly sensitive documents, prefer the tools that explicitly say they run in your browser.
- If you use AI-assisted tools, assume the content leaves your device for the request and use only what you are comfortable sending to the server environment.