Privacy

The short version

• No file you queue is sent anywhere. The queue runs on your machine. Nothing leaves it.
• There is no account, no sign-in and nothing to create.
• Nothing about your pictures is stored between visits. Saved recipes hold rules and nothing else.
• On resizly.com itself, a cookieless page-view counter (Cloudflare Web Analytics) records visits in aggregate. It never sees your files. Resizly shows no advertising.

What happens to a file you queue

When you drop a folder, the browser reads the first sixty-four kilobytes of each file to find out its format, its dimensions, its orientation and whether it is animated. When you start a run, each file is decoded into memory inside this tab, drawn at the sizes your rules asked for, encoded, and appended to an archive that also lives in this tab. Then it is handed to your browser’s download machinery.

At no point is a picture, a filename, a dimension or a byte count transmitted. There is no server behind this site: it is a set of static files, and the part that does the work is JavaScript running on your own processor. Closing the tab discards everything, immediately and without a copy.

You can check this rather than take our word for it. Open your browser’s developer tools, keep the network panel open, and run a job. What you will see is this page, its stylesheet, its fonts and its icons, plus one small request to Cloudflare’s analytics beacon when the page loads on resizly.com. During the run itself no request carries a picture, a name or a size. The only requests a run can make are the optional downloads below, and they fetch files; they send nothing of yours.

Optional downloads

Three options fetch a file the first time you use them. Each is a download of code or a model to your device, never an upload:

• AVIF output loads an AVIF encoder (about 3.4 MB) from resizly.com itself, the first time a rule writes AVIF.
• AI detail (enlarging) and Keep faces in (crops) load a small model from our model file server, and the runtime that executes it (about 14 MB) from resizly.com. The detail model is 4.9 MB; the face finder is 0.2 MB. Each is checked against a recorded checksum before it runs.

The model file server receives an ordinary request for the file, which tells it the file was wanted and, as any server sees, your IP address. It does not receive the picture, the face boxes or anything the model produced: the model runs in this tab. If you never use these options, nothing is fetched.

What is kept on your device

Three things, and only these. First, saved recipes. A recipe is a named set of rules — targets, fits, formats, quality values and filename templates — stored in this browser’s local storage on this device. It holds no filenames, no dimensions of anything you processed and no record that a run ever happened. It never leaves the device and it is not readable by us. Deleting a recipe on the page removes it; clearing site data in your browser removes them all.

You can also export a recipe as a small .resizly.json file and import it elsewhere. That file is written by your browser straight to your disk and read back from it; it holds the same rules and nothing else, and it is never sent to us.

Second, while a run is going, a resume record: the relative path and byte size of each file already finished, and a fingerprint of the rules, so that if the tab is closed half-way the same folder dropped again can continue from where it stopped. It holds no picture, no dimension and no output. It is deleted when a run finishes, and by the button below. Comparing a folder with last run’s manifest reads that file in the tab and keeps nothing.

Third, if you used an AI option, its model file, kept in this browser’s cache storage so it does not download again. A recipe link (Copy as a link) keeps nothing either: the rules are inside the link, after the #, a part of an address browsers never send to a server.

Analytics

Resizly counts visits with Cloudflare Web Analytics, on a property that belongs to this domain alone. It sets no cookie, uses no device identifier and builds no profile of you. The beacon script loads only when the page is served from resizly.com or www.resizly.com; a copy of the site opened anywhere else, including a local preview, makes no analytics request at all.

What the beacon receives is what any page-view counter receives: the address of the page, the page that sent you here, and coarse facts about your browser, device type and country, together with page-load timings. Cloudflare sees your IP address as part of delivering the request, as any server would. What it never receives is anything from the working surface: not how many files were queued, not one of their names, not a single dimension, not your rules, and not whether a run was ever started. The page sends no custom events.

Advertising

Resizly shows no advertising. No ad code is loaded on any page, and no advertising network receives anything about your visit.

The contact form

The contact page is the one place on this site that sends anything. When you press its Send button, the name, email address and message you typed, together with the name of this site, are posted to a Google Form that the people behind Resizly read. Nothing goes while you type, and the page loads no Google script, font or frame beforehand. No other page here talks to Google, and no file from your queue can travel with a message.

Children

Resizly is a general-purpose utility and is not directed at children. Using it asks nobody of any age for a name, an address, a birthday or an email, and it keeps no account to attach such a thing to. Beyond the aggregate page-view counter above, the only thing that ever receives anything about a visitor is the contact form, and only what that visitor chose to type into it.

Changes, and how to ask

If this policy changes, the change will be on this page. We cannot send an announcement, because the site keeps no subscriber list of any kind. Questions about the site can be sent from the contact page.