Your photos never leave your device.

When you drop a HEIC photo into HEICPix, it stays inside your browser tab. The conversion uses libheif compiled to WebAssembly — that's just a fast version of regular browser code. Your photo is decoded and re-encoded entirely on your device.

We have no servers that touch your photos. We can't see them. We don't keep them. We don't even know that you converted them.

Don't take our word for it. Open Developer Tools in your browser (right-click → Inspect → Network tab) and watch what happens when you convert a photo. You'll see:

• The page loads (HTML, CSS, the JavaScript that runs the converter)
• The WebAssembly module loads once (about 1.5MB, cached after first visit)
• Zero requests when you drop a photo
• Zero requests when conversion happens
• Zero requests when you save the converted file

You can disable your internet entirely after the page loads and conversion will still work. That's the definition of client-side.

We use Google Analytics 4 to count anonymous page visits. This tells us things like:

• How many people visited HEICPix today
• Roughly which country (city-level at most)
• Which page they landed on (e.g. the FAQ)
• What browser they used

We've configured Analytics to anonymize IP addresses. We never set advertising cookies, never share data with third parties for marketing, and never see anything about the files you convert.

If you don't want analytics, use an ad blocker like uBlock Origin — it blocks Google Analytics by default. HEICPix works identically with or without analytics enabled.

HEICPix stores two small things in your browser's localStorage:

• Your theme choice (dark or light) — under the key heicpix:theme
• Your preferred output format (JPG or PNG) — under the key heicpix:format

That's it. No photos, no usage history, no account data. Clear your browser data to wipe these any time.

If you install HEICPix as a Progressive Web App (Add to Home Screen), you can share HEIC files directly from your OS share sheet straight into HEICPix. When this happens:

• The OS hands the file to our service worker (running in your browser)
• The file is stored briefly in IndexedDB (still in your browser)
• The converter reads it, converts, and clears the IndexedDB entry

The file never leaves your device during this flow either.