Privacy policy

The short version

This page reads the file you pick, changes its pixel dimensions inside the tab you are looking at, and writes the result to your downloads folder; there is no server behind it to send anything to.

That is a description of the architecture rather than a promise about conduct: the site is static files, there is no endpoint that receives an image, and the resizing code runs only in your browser. You can check it — open your browser's network panel, resize something, and watch no picture leave.

What happens to a file you open

• The browser reads the file from your disk into memory in this tab. The first 128 kilobytes are examined to work out what the file really is and whether it carries an orientation tag.
• The pixels are decoded, rotated if the browser has not already done it, and held as a bitmap in memory.
• Resampling, encoding and any file-size search run in a worker thread in the same tab.
• The result is written to your downloads folder by your browser, from memory.
• Closing or reloading the tab discards the picture, its name and every size you typed. None of them is written to storage or sent anywhere.

Opening a HEIC makes the page fetch its decoder — a WebAssembly module — from this site, the same server the rest of the page came from. Code travels to you; nothing travels back. Your file is not attached to that request, is not named in it, and is decoded in the tab like every other format.

The AI enlarger on /upscale-image is the one page that downloads a model. When you press its button the first time, the page fetches the model file (about 4.6 MB) from our model file server and the ONNX Runtime engine (about 13.4 MB) from this site, checks the model against its recorded SHA-256, and runs it in your tab. Those requests carry no picture, no file name and nothing about what you are doing; the picture is enlarged in memory like every other job here. No other page downloads a model.

What this browser keeps

If you save your own preset under Presets, its name and settings — sizes, mode, format, quality, file-size limit — are kept in this browser's local storage so they are there next time. No picture, file name or image data is ever stored. If you turn on Remember my last target (homepage, Export panel), the current size, mode and output settings are kept the same way and restored on your next visit; turning it off deletes them. No picture, file name or image data is ever stored. Export lists what is kept, with Clear saved presets and Forget last target buttons. If you turn on Remember finished files in the batch panel, the batch rule and each finished file's name and byte size are kept so an interrupted batch can skip them next time — never a picture; it is cleared when a batch completes or you turn it off. The AI enlarger keeps the model file in this browser's cache so it is not downloaded twice; Clear downloaded models on that page removes it. Clearing this site's data in your browser settings removes all of it too. A recipe link you copy holds settings only, and goes wherever you paste it. Nothing else is written to your device.

What we count

On resizepicture.com itself, the page loads Cloudflare Web Analytics, a cookieless page-view counter on this site's own property. It records the page address, the referring page, a coarse country, the browser and the device type, plus page-load timing. It sets no cookie, uses no device identifier and builds no profile across sites.

It is told nothing about the picture you open, its name, the sizes you type or the file you save, and it does not run at all on any other address — a local copy or a preview of these files sends nothing.

No advertising

This site shows no advertising and loads no advertising code. If that ever changed, this page would say so first, with what an advertising provider could see, before any of it ran.

Hosting logs

The files are served from a content delivery network, and like every web server it records requests: an IP address, a timestamp, the file requested, a user-agent string. That is the ordinary operation of serving a web page and it happens whether or not you use the tool. Those records are the host's, kept to their retention schedule, and they contain requests for HTML, CSS, JavaScript and fonts — never a picture of yours, because a picture of yours is never requested from anywhere.

The contact page

The contact page holds the only form on this site. When you press its send button, it posts the name, email address and message you typed, plus the domain resizepicture.com, to a Google Form, and Google keeps that response under its own policies. Nothing is sent while you type or when the page opens, no picture or size setting goes with it, and no other page here sends anything to Google.

Children, accounts and contact

There are no accounts and no sign-in. Apart from a note you choose to send from the contact page, nothing personal is collected from anybody of any age. If a genuine privacy question about this site is not answered above, ask it there.

Changes

If this policy ever changes it will be because the site changed, and the change will be described here rather than summarised. In particular, if any part of this tool ever stopped running locally, that would be stated on the tool itself and not buried on this page.