Privacy & usage

This page describes exactly what Cody Image Converter does with your files and your device. It's short on purpose.

Your images stay on your device

Cody Image Converter has no server-side component and no upload endpoint. When you add an image, the browser reads it from your device, decodes it, resizes and re-encodes it using WebAssembly code running in a background worker, and offers the result back to you as a download — all inside the page you're looking at. The image bytes never travel over the network.

You can verify this yourself: open your browser's network inspector while converting a file. You'll see the page's own assets load once, and no request containing your image data.

No accounts, no analytics, no tracking

There's nothing to sign up for. This site does not use analytics, advertising pixels, or any third-party tracking scripts. It does not set tracking cookies. Your hosting provider's standard web server logs (the same basic access logs any website generates) are outside this application's control — check with whoever hosts the site for details on those.

What is stored locally

While a browser tab is open, converted images are held in memory (and briefly as temporary object URLs) so you can preview and download them. Nothing is written to persistent storage on your device, and everything is discarded when you close or reload the tab.

Offline use

Once the page and its WebAssembly codecs have loaded, conversion works without an internet connection, since none of the processing depends on a network call.

Third-party code

The conversion engine is built on open-source components adapted from Google's Squoosh project (MozJPEG, WebP, AVIF and OxiPNG encoders) plus the JSZip library for ZIP downloads. See open-source credits for the full list and license texts.

Questions

This page describes the application's behavior as built. If you're the site operator and have added your own contact details or terms elsewhere on this domain, those govern in addition to what's described here.