File privacy

The journey of a file

1. You pick or drop a file. The browser gives the page a reference to it; nothing is sent over the network.
2. The page creates a temporary local URL (blob:) and the browser decodes the image into memory.
3. The tool draws the pixels onto an HTML canvas and transforms them — scaling, cropping, flattening, analysing colours.
4. The canvas is encoded into a new file with canvas.toBlob, entirely inside your browser.
5. When you click download, that new file is saved from memory to your disk. Temporary URLs are released afterwards.

PixelKit has no upload endpoint, no file storage and no server-side image processing. You can verify this: open your browser's developer tools, switch to the Network tab and use any tool — no request carries your image. After the page has loaded you can even disconnect from the internet and the tools keep working.

Metadata: what is removed and why

Photos from phones and cameras usually contain EXIF metadata alongside the pixels: camera make and model, lens, exposure settings, date and time, sometimes the device's serial number and, very often, the GPS coordinates where the photo was taken.

A canvas holds only pixel colours. When the compressor, resizer, cropper, converter or favicon generator encodes a new file from the canvas, there is no EXIF block to copy, so the exported file does not contain that metadata. This is a genuine privacy benefit when you publish a photo taken at home: the location is not embedded in the file you share.

Some precise caveats:

• Orientation is applied to the pixels before export, so photos stay upright even though the orientation tag itself is gone.
• Embedded colour profiles are not copied either; images are exported as sRGB. Wide-gamut photos can look slightly less saturated.
• The Base64 tool encodes the original bytes unless you tick “Re-encode first to remove metadata”, so by default its output still includes any EXIF data.
• Removing metadata does not remove information visible in the image itself — street signs, house numbers, reflections or faces.
• Copyright and author fields are dropped too. If you need them, add them back with a metadata editor.

What we can see

Nothing about your files. The hosting provider sees ordinary web requests for the site's pages and scripts. If you accept cookies on a site where ads or analytics are enabled, those services see page visits as described in the privacy policy — still never your images.