Security

The claim

Your photos are converted on your computer and never sent anywhere. Everything below is how that is done, in enough detail that you can verify it rather than believe it.

What happens when you convert a file

The page reads your file from disk using the browser's own File API — the same mechanism that lets you attach something to an email, and one that gives the page the bytes without moving them anywhere.

Those bytes are handed to a Web Worker: a background thread inside your browser. The worker runs libheif, the reference HEIC decoder, compiled to WebAssembly and served as a file from this site. It decodes the photo into raw pixels.

The pixels come back to the page and are drawn onto a canvas, and the browser's own built-in JPEG encoder writes the result. That encoder is part of your browser, not something we supply.

The finished JPG is held in your browser's memory until you download it or close the tab.

How to verify it

Open developer tools, go to the network tab, and convert a photo. You will see the page's own files load — HTML, styles, the decoder — and no request carrying your image, because there is none.

Everything this site serves is static and readable. Nothing is minified beyond recognition and the decoder is shipped exactly as its authors published it.

What this does not protect against

Being honest about the boundaries: this protects your photo from us and from the network. It does not protect you from your own device. If your computer is compromised, a page running in your browser cannot fix that.

It also does not encrypt anything, because there is nothing in transit to encrypt.

Reporting a problem

If you find something that contradicts any of the above, tell us — hello@myconverterpro.com. A claim this specific is worth correcting quickly if it is ever wrong.