Privacy and browser guide
What “processed in your browser” means
A local file tool reads and transforms the selected file in the browser instead of uploading it to a conversion server. That reduces where the file needs to travel, but it does not mean the website makes no network requests.
What stays on your device
For KeepFile's browser-based tools, the selected file is read into the page's memory and the operation runs in JavaScript in your tab. The generated result is handed back to the browser for download. The site does not need to receive the file contents to perform that operation.
What still uses the network
Your browser must first request the page and its code. KeepFile is hosted by Cloudflare, loads typefaces from Google Fonts, and includes Cloudflare Web Analytics and Google AdSense code. Those requests can expose ordinary connection information to the relevant providers. Advertising and analytics are separate from the file conversion code. See the Privacy policy for more detail.
How to check a workflow
- Open the tool page before selecting a file.
- Open your browser's developer tools and choose the Network panel.
- Clear the request list, select a test file, and run the operation.
- Look for requests initiated after selection. A local workflow should not send the document itself to a file-processing endpoint. Network panels can be difficult to interpret, so this check is useful evidence, not a formal security audit.
Local does not remove every risk
Anyone with access to your device or browser profile may still see local files or downloads. Malicious extensions, compromised devices, and insecure copies of downloaded results are outside the tool's protection. Large files can also consume substantial memory. For sensitive work, use a trusted device and review the code and the downloaded result to the level your situation requires.