PixHeic
Convert HEIC to PNG for GitHub README Images
GitHub renders your README in a browser, and browsers cannot decode HEIC. Convert to PNG and the image appears for everyone.
100% Local — Files Never Leave Your Browser
Convert HEIC to PNG now
Drop your .heic files into the converter and download lossless PNGs with any transparency intact. Decoding runs on your device via WebAssembly, so nothing is uploaded to a server.
Open the PNG converter Free, no sign-up, no watermark. Alpha channels are preserved.Zero uploads
The decoder runs in your browser via WebAssembly. Your files never touch a server, so there is nothing to retain, leak or subpoena.
Transparency preserved
If your source carries an alpha channel, it survives the conversion intact. PNG is the only common photo format that keeps it.
Lossless output
PNG stores every pixel exactly. Re-saving a sticker ten times leaves it identical to the first save, unlike JPEG.
Why the image does not render
A .heic committed to a repository and referenced from a README shows as a broken image, because GitHub is rendering markdown into HTML and the browser cannot decode the file. The asset is in the repo; it simply cannot be displayed.
PNG is the right format for the things READMEs contain: screenshots, architecture diagrams, logos and badges are all flat-colour, hard-edged content where PNG is both lossless and smaller than a JPEG would be at equivalent clarity.
Light mode, dark mode and transparency
GitHub serves both themes, and a logo with a baked-in white background looks broken in dark mode. A transparent PNG works on both — or use GitHub's #gh-dark-mode-only and #gh-light-mode-only suffixes to serve two variants.
Screenshots taken on a phone are far larger than any README needs. Use the web presets in the Output size control to scale them down as you convert — a 4000-pixel screenshot in a repository is a permanent cost to everyone who clones it.
Converting preserves transparency — it does not create it
PNG supports an alpha channel, and this converter carries one across if your source already has one. A normal photo taken on a camera has no transparency, and converting it to PNG will not cut the subject out — you will get the same picture with the same background, in a larger file.
To get a transparent subject, remove the background first. On an iPhone, press and hold the subject in Photos to lift it out, then share it as an image; on a desktop, use the background removal in your editor of choice. Convert afterwards and the transparency comes through.
Frequently asked questions
Will my transparent background survive the conversion?
Yes, if the source has one. HEIC supports an alpha channel and PNG preserves it, so a lifted subject or an edited cut-out comes through with its transparency intact. What conversion cannot do is add transparency to a photo that never had it.
Should I use PNG or JPG for this?
PNG for anything with transparency, flat colour, hard edges or text — stickers, emoji, logos and icons all qualify, and PNG is lossless so repeated edits do not degrade it. JPG for photographs you are simply sharing, where PNG would spend three to five times the file size preserving detail nobody can see.
Does this tool resize images to the required dimensions?
Yes. The converter has an Output size control with presets for the common targets — Discord and Slack emoji at 128 px, Twitch emotes at 112 px, stickers and avatars at 512 px — each of which centre-crops to a square and scales the longest edge down as it converts.
Large reductions are done in halving steps rather than one draw, which is what keeps a 128 px emoji from looking crunchy. Images are never enlarged: ask for 512 px from a 300 px source and you get 300 px.
Is anything uploaded to a server?
No. PixHeic decodes your file with a WebAssembly build of libheif that runs inside your own browser tab, so the image is read from your device into memory and converted there. You can confirm it in your browser's Network tab, or disconnect from the internet after the page loads and convert anyway.