File Privacy and Browser Processing
Understand local file processing, supporting asset downloads, analytics and external content requests.
Updated August 27, 2026EveryFileTool's current file-processing tools process selected files in your browser. Those selected files are not uploaded to or stored by EveryFileTool for processing. That does not mean every network request stops after a page loads.
User file processing and transfer
For local file tools, the browser reads the selected file and creates the result on your device. The source file is not sent to EveryFileTool's server as an upload.
Supporting downloads
Some tools need to download code, a media runtime, language data, or a machine-learning model. For example, video tools can load a WebAssembly runtime, OCR can load language data, and background removal can load a model. These resources run locally after loading; the selected user file is not included in the asset request.
External content
A tool that retrieves public content can contact its provider. For example, the YouTube Thumbnail Downloader sends a public video identifier to YouTube's image service to retrieve the thumbnail. This is different from uploading a user-selected file.
Analytics and other site requests
In production, analytics may receive page and privacy-safe interaction information. Help search analytics never includes the raw Help query. Advertising or other enabled site services can also make network requests.
Read the Privacy Policy for the authoritative description of files, analytics, cookies, advertising, Contact data and user choices.