Privacy

Bytes are read from disk by this page, rewritten in a worker and handed straight back to your download folder; no origin, no queue and no log ever sees them, and nothing survives the tab closing.

The short version

Pick a file, and the picture is decoded and re-encoded by code running on your own machine. There is no server behind this site — it is a static export, there are no API routes, and no endpoint exists here that could accept a file even if something tried to send one. Close the tab and nothing about your picture remains.

What happens to a file you open, precisely

• The browser hands this page a reference to the file you chose. The first megabyte is read to identify the format and to measure the metadata blocks; the rest is read to decode the pixels.
• The pixels live in memory as an ImageBitmap. They are not written to local storage, session storage or IndexedDB — a build-time audit fails this site if any of those appear in code that can reach an image buffer.
• Re-encoding happens in a Web Worker on the same machine. The result is a blob in memory, which the download control hands to the browser as a file.
• Nothing about the file — not its name, not its size, not its dimensions, not its contents — is transmitted anywhere by this page.
• Reloading or closing the tab discards all of it. There is no history, no recent-files list and nothing to clear.

What the analytics see

Nothing at all today. No measurement property has been registered for this domain, so the pages ship without a beacon: view the source of any of them and there is no measurement tag in it, no request goes out to a measurement host, and no visit, referrer or country figure is written down anywhere. Shipping a beacon against an unconfigured property would add a third-party request to every page load and record nothing from it, which on a page whose whole argument is that it sends nothing would be a poor trade.

If one is ever registered it will be Cloudflare Web Analytics, picked because it sets no cookie and assigns no identifier that follows a reader between visits, on a property belonging to this domain alone rather than one shared with other sites. What it would then see is a URL, a referrer, and coarse browser and country figures. What it could not see, before or after, is anything about a picture you opened — that never leaves the tab. This section is rewritten on the same day such a script first ships, not afterwards.

What the advertising sees

This site is built to carry Google AdSense, and carries no advert yet. The domain has not been approved for an account, the switch that renders a unit is off in the source, and nothing is drawn where a unit would go — so if you are reading this to find out what is watching you from an ad slot on this page, the answer today is that there is no ad slot on this page. The placements are already decided in code: one band below the working surface on a tool route, three inside a guide, and none of them above the tool or inside the comparison view.

Once a unit does render, serving it hands Google the request information any web request carries — your IP address, your user agent, and the page the unit sits on — and Google may use cookies or similar technology in accordance with its own policies, which you can review and adjust in its ads settings. What an advert will not have, then or now, is the picture: an advert is markup in the page, the picture is pixels in a worker, and no path exists between the two.

What is not here

• No accounts, no sign-in and no email address is ever asked for.
• No file storage, no processing queue, no logs of your work.
• No cross-site identifier shared with any other site.
• No tracking parameters added to the one outbound link in the footer.

Contacting us and changes to this page

If something on this page turns out to be inaccurate, it is a bug and worth reporting. Any change to how this site handles files will be described here before it ships, and a change that introduced a server-side step would be a different product rather than an update to this one.