Skip to content
FITFILE

How it works

Your files never leave your device.

FITFILE is built as a static website with no backend. The work happens in your browser, using your device's own processor and memory. Not uploading is not a policy we promise to follow — it is an architecture: there is nothing on the other end to upload to.

What happens to a file

  1. A file opens in your browser

    When you choose a file, it opens directly into your browser's memory — the same way a photo opens in a local app. Nothing is transmitted anywhere.

  2. Your device does the work

    Processing runs as code on your own processor and memory, inside the browser's sandbox. FITFILE's job is to bring the code to your file — never the other way around.

  3. The result is saved from memory

    The output is assembled in your browser and downloaded straight to your disk. Your original file is never modified, and neither file ever crosses the network.

Bytes received by FITFILE servers

This counter can never move. FITFILE is published as plain static files — there is no server behind this site capable of receiving a file, a filename, or anything you do here.

Don't trust us — check

  • Watch the network. Open your browser's developer tools on the Network tab while FITFILE works on a file. You will see the page load its own code — and nothing carrying your file ever leaving.
  • Go offline. Once a page has loaded, disconnect from the internet. Local processing keeps working, because the network was never part of it.
  • Read the policy. This site ships a Content-Security-Policy header with connect-src 'self' — the browser itself forbids this page from talking to any other server.

What FITFILE ships

FITFILE only publishes tools that already work. What you see on this site is what it can do — no previews, no betas, no coming-soon pages.

Built with React and React Router · Type set in Archivo & IBM Plex Mono · Served as prerendered static HTML on Cloudflare Pages