How HEIC to PIC Works
Your photos are decoded and re-encoded inside your browser tab. Here is each step, and how to check that nothing is uploaded.
Last updated
The short version
When you open HEIC to PIC, your browser downloads a web page and a handful of code libraries. From then on, the conversion is done by that code running on your own computer or phone. Your photos are read from your device, turned into the format you picked, and handed back as downloads. They are never sent to a server, which is also why there is no queue, no account and no upload progress bar.
Step 1: the page loads its tools
The site itself is a set of static files served by a hosting provider. A static site has no application server waiting to receive photos; it can only hand out the same files to everyone who asks. The libraries that do the real work come from two public code delivery networks, jsDelivr and esm.sh:
- heic2any, which bundles libheif, the open-source HEIF decoder, compiled to WebAssembly.
- JSZip, for packing many output files into one ZIP.
- jsPDF, for building PDF documents.
- UTIF, for writing TIFF files.
- A WebAssembly AVIF encoder, fetched only the first time you choose AVIF.
WebAssembly is a compact binary format that browsers run at close to native speed. It lets a decoder originally written in C++ run inside a tab, under the same security sandbox as any other web page.
Step 2: decoding the HEIC
When you pick files or drop them on the page, the browser lets the page read just those files and nothing else on your disk. The bytes are loaded into memory and passed to libheif. It reads the HEIF container, finds the image or images stored inside, and decodes the HEVC-compressed data into ordinary pixels. A burst or image sequence holds several images, and each one is decoded in turn.
This is the slow and memory-hungry part. A 12 megapixel photo expands to tens of megabytes of raw pixels while it is being worked on, which is why very large batches on a phone go better in smaller groups.
Step 3: encoding the output
The decoded pixels are drawn onto a canvas, the browser's built-in drawing surface. If you chose a resize preset, the image is scaled down at this point. Then a format-specific encoder writes the new file:
- JPG, PNG and WebP use the encoders built into the browser. That is why WebP depends on the browser: Chrome, Edge and Firefox can write it, while Safari may not.
- PDF is assembled by jsPDF, which places each image on an A4 page.
- TIFF is written by UTIF as uncompressed RGBA.
- AVIF goes through the WebAssembly AVIF encoder, which is thorough but noticeably slower than the rest.
- BMP and ICO are simple enough to be written by the converter's own small routines: a 24-bit BMP, and a 256 by 256 icon with the photo fitted inside a transparent square.
- GIF is produced through heic2any, which can turn a multi-image HEIC into an animation.
Step 4: saving the file
Each finished file exists only in your browser's memory at first. The page creates a temporary local link to it, and clicking Download saves it through your browser's normal download system, into your Downloads folder or wherever your browser is set to save files. Downloading everything at once has JSZip assemble the ZIP in memory first. Close or reload the tab and those in-memory copies are discarded.
Check for yourself that nothing is uploaded
You do not have to take this page's word for it. Two quick tests settle the question.
Watch the Network tab
- Open the converter, then open the browser's developer tools: press F12 or Ctrl+Shift+I on Windows and Linux, or Cmd+Option+I on a Mac. In Safari, turn on the developer features in Safari's settings first (the name of that setting varies by version).
- Select the Network tab and clear the list.
- Convert a photo.
- Look at the new entries. You may see a library file being fetched, or entries beginning with
blob:, which are local links inside your own browser. You will not see a request carrying your photo to any server.
Convert with the internet switched off
- Load the converter and let the page finish loading.
- Turn off Wi-Fi or unplug the network cable.
- Add a HEIC photo and convert it to JPG. It works, because everything needed is already on your device.
One exception: the AVIF encoder downloads the first time you choose AVIF, so pick AVIF once while you are online if you want to repeat the offline test with that format.
What this design means for you
Local processing has trade-offs as well as benefits. Speed depends on your device rather than a server farm, so an older phone takes longer than a desktop, and memory sets the real ceiling on batch size. The full list of specs and edge cases is on the limits and specs page, the reasoning behind the default settings is on the methodology page, and the data the site does and does not handle is set out in the privacy policy. To try it, open the HEIC to JPG converter.
Frequently asked questions
Do I need an internet connection to convert HEIC files?
Only to load the page. Once it has loaded, conversion to JPG and the other built-in formats works offline; AVIF needs its encoder downloaded once first.
Can jsDelivr or esm.sh see the photos I convert?
No. They deliver the code libraries to your browser and, like any server, see the request for those files, but your photos are processed locally and never sent to them.
Why does the first AVIF conversion take longer to start?
The AVIF encoder is a separate WebAssembly module that downloads the first time you choose AVIF. AVIF encoding is also more demanding than the other formats, so it stays slower after that.
Why is converting slower on my phone than on my laptop?
All the work happens on your own device, so speed follows its processor and memory. Phones with less RAM do better with smaller batches.