How it works
From HEIC to JPG, in three steps
- 01
Decode
Your HEIC file is decoded to raw pixels locally, using a WebAssembly build of libheif.
- 02
Re-encode as JPG
Pixels are re-encoded as JPG at the quality level you choose, right in your browser.
- 03
Download
Your JPG downloads straight to your device. It never touched a server.
JPG has been the web's default photo format since 1992, and it earns that position through simplicity: every browser, phone, printer, photo-editing app, and print shop on the planet can open it without a second thought. No other image format comes close to that level of universal support. It compresses each 8×8 block of pixels using a discrete cosine transform (DCT) and Huffman coding, discarding the visual detail human eyes notice least in exchange for a much smaller file.
Because JPG is also a lossy format, like HEIC's underlying HEVC compression, converting HEIC to JPG usually shrinks the file rather than growing it, unlike the HEIC to PNG path, where a lossless destination format can't take advantage of the same compression tricks and often produces a larger file instead. This tool decodes your HEIC photo to raw pixels using a WebAssembly build of libheif in a background worker, then re-encodes those pixels as JPG right in your browser at the quality level you choose, all without a single byte ever leaving your device.
When you need this
Forms that accept JPG
Most websites, application forms, and online portals that reject HEIC uploads are perfectly happy with JPG and don't need lossless accuracy: job applications, e-commerce listings, forum posts, and general file uploads all fall into this bucket, and JPG is the safe default choice.
Sharing to an older device
Emailing or texting a photo to someone on an older phone, a work computer, or software that's never heard of HEIC calls for JPG specifically. It's the one format you can send without wondering whether it'll open on the other end.
Social media and messaging
Social media platforms, messaging apps, and photo-sharing sites are built around JPG (or quietly convert to it internally anyway), so uploading a JPG directly avoids any surprises in how the platform recompresses or displays your photo.
Everyday use
For ordinary day-to-day use (backing up photos, building a folder to browse later, attaching a picture to a document), PNG's larger file size buys you lossless accuracy you probably don't need, while JPG gives you a much smaller file at a quality difference most people will never notice.
Worked example
Say you've got a landscape photo from a hike, saved by your iPhone as a 3.1 MB HEIC file, and you want to upload it to a forum post that only accepts JPG.
Drop the file into the box above (JPG is already selected), leave quality at its default 85%, and click "Convert." In about a second, entirely on your device, you'll have a JPG in the neighborhood of 1.0 to 1.2 MB, something like 3.1 MB down to 1.1 MB is typical: roughly two-thirds smaller than the original HEIC, with no visible difference at normal viewing sizes.
Want it a bit sharper, at the cost of a slightly bigger file? Drag the quality slider up toward 95%. Want it smaller still, for a faster upload? Drag it down toward 60 to 70%. You'll trade a little detail for a noticeably smaller file. Either way, the conversion itself takes about a second, whether it's one photo or a whole batch.
Format explainer
JPEG has barely changed since it was standardized in 1992: it splits an image into 8×8 pixel blocks, runs each one through a discrete cosine transform, and discards the frequency information human vision notices least, before compressing what's left with Huffman coding. It's a simple, decades-old recipe, which is exactly why hardware and software everywhere have been built to decode it instantly, with zero compatibility concerns.
HEIC takes a fundamentally more modern approach: it typically stores a photo using HEVC (H.265), the same intra-frame video compression standard behind 4K streaming, which predicts each block from its neighbors using dozens of directional patterns before compressing whatever's left. That extra sophistication is why HEIC packs the same visual quality into roughly half the bytes JPEG needs, but it's also newer and far less universally supported. Converting to JPG trades away some of that raw efficiency in exchange for a format guaranteed to open absolutely everywhere, which is exactly the trade this page exists to make easy.
Frequently asked questions
For most purposes, yes. JPG is the most universally compatible image format (every device, browser, website, and printer accepts it without question), and converting from HEIC to JPG typically shrinks the file, since both are lossy formats. Choose PNG instead only if you specifically need lossless, pixel-perfect accuracy or transparency; otherwise JPG is the safer, smaller, more compatible default.
A small amount, yes. JPG is a lossy format, so some image detail is discarded during encoding. At the default 85% quality setting, that loss is generally invisible at normal viewing and printing sizes. If you need to guarantee zero quality loss, HEIC to PNG conversion is lossless, though the resulting file will usually be considerably larger.
85% (the default) is a solid balance of file size and sharpness for most photos. Push it toward 95 to 100% for images you plan to print large or edit further, where every bit of detail matters. Drag it down toward 60 to 70% for casual sharing or thumbnails, when upload speed and storage space matter more than maximum sharpness.
Yes. Drop as many .HEIC or .HEIF files as you like into the tool at once. There's no batch limit imposed by the tool itself, only your device's own memory and processing power. Each file converts and shows its own status individually, and you can download everything together afterward as a single .zip.
Yes. This tool decodes the HEIC to raw pixels and re-encodes those pixels as JPG, which doesn't carry over the original file's EXIF metadata (GPS location, camera model, shot settings, and so on). If you need that metadata intact, keep a copy of the original HEIC file alongside the converted JPG.
No. Decoding the HEIC and encoding the JPG both happen locally in your browser, using WebAssembly and a background worker thread. There's no server anywhere in that path. You can verify this yourself: open your browser's DevTools, watch the Network tab while converting a photo, and you'll see no request carrying your image data anywhere.
Drop the file into the box at the top of this page, leave the output on JPG, and click Convert. You'll have a JPG in about a second. Decoding and encoding both happen on your device, so there's no upload step to wait on.
The same way as on any other device: this runs in your browser, not through Windows' own HEIC support, so you don't need to install the HEIF/HEVC extensions from the Microsoft Store first (the usual fix, and one that's tripped a lot of people up). Drop the file in, download the JPG.
You might not need this tool at all: macOS Preview already opens HEIC natively, and File > Export lets you save a copy as JPEG. This page is still worth using if you'd rather not click through that dialog for every photo, or want a quality slider instead of Preview's fixed export.
For photos you already have, open this page in Safari and convert them the same way as on a computer. If you'd rather your camera just stop shooting HEIC going forward, that's a Settings change, not a conversion: Settings > Camera > Formats > Most Compatible.