How we protect your files
FileConvert.tech is designed so that the safest possible thing (keeping your file on your own device) happens by default. This page explains our security architecture in plain language.
Browser-first processing
Whenever a conversion can technically run in your browser, it does. The file is processed locally in memory and never transmitted to us. Each converter page states exactly which model applies to it.
Isolated server workers
Conversions that genuinely require server processing run in isolated workers. Files are transmitted over TLS, held only in memory during the conversion, and deleted immediately after the output is produced.
HTTPS everywhere
All traffic, including pages, uploads, and downloads, is served over HTTPS. We do not offer or support unencrypted access to the product.
Strict upload validation
Uploaded files are validated by content type and size before processing. We do not execute uploaded files; conversions parse and re-encode data using sandboxed runtimes and established open-source libraries.
No secrets in your browser
There are no API keys, admin interfaces, or credentials embedded in client code. The public site talks only to documented public endpoints.
Minimal, honest analytics
We collect anonymous event counts (for example, that a conversion succeeded) to decide which tools to build next. We never collect file contents, filenames, or personal identifiers.
Found a security issue?
Please report it responsibly to security@fileconvert.tech. We take every report seriously and will not pursue legal action against good-faith research.