Free the Tools
About

How it works

Every tool runs inside your browser. Here is what comes in, what stays on your device and what goes out, and how to check each one yourself.

Serverfreethetools.comSends the page and the tool's code
Page and tool code, once. Then it works offline.
Anonymous counts only: which tool, whether it worked
Your device
  1. Your fileOr the text you type
  2. The toolRuns in your browser
  3. The resultMade right here

Where the result goes

  • Downloads folderWhen you press Download
  • LibraryA copy, in this browser only
Any other serverBlockedBy the page's security policy
No connection allowed
Your file goes to the tool and becomes the result without leaving your device. The only things sent are anonymous counts, and only to freethetools.com.

What we send, exactly

Once per visit
The site that sent you, by name only (like google.com), and whether you're on a phone, tablet or desktop. Cloudflare adds the country.
When you use a tool
The tool's name, and that it was opened, used, worked (you downloaded, shared or copied a result) or couldn't finish. Nothing about your file.
When you add or remove a favourite
The tool's name, as a like.
When you press “I want this”
The name of the planned tool, as one vote.
When you send the suggestion form
Your message, as an email to the maintainers. Only when you press Send. See the privacy notice.
Never
Your files, anything you type into a tool, your IP address, cookies or an ID.

If your browser sends Global Privacy Control or Do Not Track, we send only the likes you press by adding a favourite and the votes you press with “I want this”. The totals are public on Usage stats, and the privacy notice has the details.

Check it yourself

You don't have to take our word for it. Each check takes a minute.

  1. Watch the network

    Open your browser's developer tools (F12, or Cmd+Option+I on a Mac) and choose Network. Then use any tool with a file of your own.

    You'll see requests only to freethetools.com: the page, the tool's code, and small requests to /api/stats/ such as {"tool":"pdf/compress","kind":"use"}. None of them carries your file.

  2. Go offline

    Open a tool, then turn off Wi-Fi or switch on flight mode. Use the tool, or even reload the page.

    It still works, because it runs on your device. A tool you have opened once is kept for offline use.

  3. Find where your files go

    A result goes to your Downloads folder when you press Download, like any download. The Library keeps a copy in this browser's own storage.

    In developer tools, open Application, then IndexedDB, then ftt-library. What this browser stores below shows the same, and clears it.

  4. Read the security policy

    View the page source (Ctrl+U, or Cmd+Option+U on a Mac) and search for Content-Security-Policy.

    It says connect-src 'self': the browser lets the page talk to freethetools.com and nowhere else, even if a tool had a bug. Our automated tests fail if a page tries.

  5. Read the code

    Every tool's code is public, in its own folder on GitHub. Anyone can check it, run it or improve it.

  6. Check that the site is that code

    Verify this site compares every file served here with the fingerprints published for the build.

    It shows a match, file by file, or names the files that differ.

What this browser stores

Everything Free the Tools keeps on this device, read live from this browser. None of it is sent to us.

    Suggest a tool

    Step 1 of 3 What should the tool do?

    For example: join two PDFs, or shrink a photo. At least 10 characters.