Browser-First by Design

Privacy Policy

This page states exactly what happens to your files on FileConvert.tech, when processing stays in your browser, when a server is involved, and what we collect. No vague promises.

1. When files are processed locally in your browser

Most conversions on FileConvert.tech run entirely inside your browser: image conversions and filters (JPG, PNG, WebP, AVIF, and more), PDF merge, page extraction and rotation, images-to-PDF, ZIP packing, and structured data transforms (JSON, CSV, YAML, Base64, hashing). For these tools your file is read into browser memory, converted, and handed back to you, it is not transmitted to any server. Each converter page states which processing model applies to it.

2. When server processing occurs, and what happens to the file

Some conversions cannot run in the browser, for example when your browser cannot decode the source format, or when the conversion engine (image pipeline, PDF engine, data parser) only exists server-side. In that case your file is sent over an encrypted HTTPS connection to our conversion endpoint and processed entirely in memory. Uploaded files are never written to disk or object storage: the file exists in server memory only for the duration of the request and is gone when the response is returned. We do not inspect, mine, or analyze file contents, and files are never used to train machine-learning models. Server-side uploads are limited to 100 MB per file.

3. Retention and deletion

  • Browser-processed files live only in your browser's memory. Closing the tab, removing an item from the conversion queue, or clearing the queue discards them immediately.
  • Server-processed files are held in volatile memory for the length of the conversion request only, there is no temporary file store, no background job queue, and nothing to purge later.
  • Download links are generated in your browser from the converted result; we never host converted files at a URL.

4. Analytics

We run first-party, privacy-conscious analytics to understand which tools are used and which fail. We record anonymous event counters only, tool viewed, file selected, conversion started, conversion succeeded, conversion failed, download completed, together with the tool identifier. We do not collect file contents, file names, or personal identifiers, and analytics events are aggregated in server memory without persistent per-user profiles.

5. Cookies

FileConvert.tech sets no tracking cookies and uses no third-party analytics or advertising scripts. Your interface preference (light or dark theme) is stored in your browser's local storage on your own device and is never transmitted to us.

6. Third-party services

This site loads no external analytics, advertising, or tracking services. All conversion engines and fonts are served from our own origin. Standard infrastructure providers (hosting and CDN) process requests only to deliver the site and its conversion API over HTTPS.

7. Your controls

  • Remove individual files from the queue at any time before or after converting.
  • Clear the entire queue with one action, in-memory files are discarded.
  • Block our analytics endpoint with content blockers without affecting any conversion feature.

Our commitments:

  • No file inspection: we never read, view, parse for profiling, or mine the contents of your files.
  • No AI training: your files are never used to train machine-learning or generative AI systems.
  • No accounts required: conversion works without sign-up, so we hold no profile data about you.
  • Honest tool pages: every converter page states whether it runs locally or via server processing.

Questions about this policy? See the contact page, last updated August 2026.