Your files stay in your browser: here is how to check

The free LoopGIF tools open, edit and encode your file inside your browser tab. While a file is being processed, no request carries its bytes to a server. This page explains how that works, lists what does leave your browser, and shows how to check it yourself in about a minute.

By ·

How the free tools process a file

When you add a GIF, a video, a picture or some typed text to a free tool, your browser reads it straight from your device. The page turns it into frames. A decoder that ships with the page reads GIFs, and the browser's own image and video decoding handles pictures and video. Each frame is drawn on a canvas inside the page, where the crop, the text, the colour change or the resize is applied.

The final encoding runs in a Web Worker, a background thread of the same tab. The worker's script is a file served by this site, and the free tools load no code from any other site while they work. The finished file is kept as a blob in your browser's memory, and the download button points at that blob instead of a web address. Nothing about the file is stored on our servers for these tools, because nothing is sent.

We also read the code of every free tool for network calls: fetch, XMLHttpRequest, beacons and workers. The only fetches in the tool code load our own sample pictures and templates when you choose one of them. The only worker is the encoder script described above.

What does leave your browser

A free tool does not send your file anywhere, but a visit to any website involves some requests. This is everything we know of, so you can look for each one yourself.

  • Loading the page. Your browser asks this site for the page, its scripts, fonts and sample pictures, as with any website. These requests carry no file from your device.
  • A sign-in check. Each page asks the server whether you are signed in, with a GET request to /api/auth/get-session. If you are signed in, the page also asks for your credit balance. Neither request carries a file.
  • An analytics event. When an export finishes, the free tools call a helper that sends an event named tool_convert with three fields: tool, ok, ms. The first is the short name of the tool, for example compress. The second is true or false, whether the export finished. The third is how many milliseconds it took. It never includes a file name, file content or text you typed. The event goes out only when a Google Analytics tag is installed on the page, and when we checked on 18 November 2026 the page loaded none.
  • Microsoft Clarity. A banner asks whether to allow analytics. The Clarity script loads only after you choose Accept analytics, and Decline keeps it from loading. Our privacy policy says text and media are masked in Clarity recordings, and that Microsoft handles this information under its own privacy terms.
  • The AI tabs and AI pages. These upload by design. The AI tab on pages that have one, and the Animate Photo and AI sticker generator pages, send the picture or prompt you give them to our server and on to an AI provider, so that a model can make your clip. They need an account and cost credits. The privacy policy says what is stored and for how long. Everything on this page about files staying local is about the free tools, not these.

Check it yourself with the Network panel

You do not have to take our word for any of this. We wrote these steps in a Chromium-based browser such as Chrome or Edge on a computer. Other desktop browsers have a similar Network panel, though some names differ.

  1. Open a free tool, such as the GIF compressor. Open the browser's developer tools: press F12, or Ctrl+Shift+I (Cmd+Option+I on a Mac).
  2. Click the Network tab, then click the clear button (the circle with a line through it) so the list starts empty.
  3. Choose the Fetch/XHR filter (some browsers call it XHR). A page script that uploads a file shows up here.
  4. Add a file, then press the tool's button, for example Compress GIF. Watch the list while it works.
  5. An upload would appear as a POST or PUT request whose size is about the size of your file. With a free tool, the Fetch/XHR list stays empty while the file is processed.
  6. Now switch the filter to All. You may see a GET for a script file from this site the first time you use a tool (the encoder worker is about 13 KB), and rows that start with blob:. A blob: row is the page reading your file's data from its own memory. Neither is an upload.
  7. Compare sizes. The file you added is larger than every request in the list.

What we saw when we checked

We repeated those steps on 18 November 2026 in a Chromium-based browser, on a production build of this site's code, with the Network panel recording. We processed one file on each of the five tools below. Between pressing the button and the download link appearing, the only requests were GETs for this site's own script files. There was no POST, PUT, beacon or XHR. The largest request was 13,308 bytes, and the files we added were between 176,805 and 597,669 bytes.

Requests seen while one file was processed
ToolFile addedResultRequests while processing
Discord emoji makerGIF, 509,804 bytes70,058 bytes1 GET for our own script (13,308 bytes)
GIF CompressorGIF, 597,669 bytes451,174 bytes2 GETs for our own scripts (3,820, 13,308 bytes)
Video to GIFMP4, 176,805 bytes1,754,097 bytes1 GET for our own script (13,308 bytes)
Transparent GIF makerGIF, 509,804 bytes361,839 bytes1 GET for our own script (13,308 bytes)
GIF to WebPGIF, 509,804 bytes126,002 bytes4 GETs for our own scripts (1,366, 11,254, 3,104, 2,933 bytes)

The result is made on your device. A GIF made from a video can be larger than the video, as the video to GIF row shows.

What this does not cover

This describes what our code does, which is why the steps above let you see it for yourself. It cannot cover things outside the site. A browser extension can read a page, and a screen recorder can see your screen. On a shared or managed computer, ask whoever runs it. If our code changes, the same check shows you the difference.

For account, payment and AI data, read the privacy policy. For the tools themselves, start from the tools list.