HEIC to JPG Converter

What is the HEIC format?

HEIC stands for High Efficiency Image Container, and it is the file format your iPhone, iPad and Mac most likely use to save photos today. The name describes exactly what it is: a container — a wrapper that can hold one or more images along with their metadata, thumbnails and auxiliary data. The underlying technology is HEIF, the High Efficiency Image File Format, which is an industry standard defined by the Moving Picture Experts Group (MPEG). When Apple writes a photo to a .heic file, it stores the actual picture inside that container using HEVC (High Efficiency Video Coding, also known as H.265), the same advanced compression codec used for 4K video. In other words, every HEIC photo is essentially a single, beautifully compressed frame of HEVC video wrapped in a HEIF box. That pairing of a flexible container with a modern codec is the whole reason HEIC files are so small and so capable.

The headline advantage of HEIC is efficiency. Because HEVC compression is dramatically more sophisticated than the decades-old algorithm inside a JPG, a HEIC photo typically occupies roughly half the storage of an equivalent-quality JPEG. A photo that would be four megabytes as a JPG can land at around two megabytes as a HEIC with no visible loss of detail — and across a library of thousands of photos, that saving is enormous. For Apple, which ships devices with fixed, non-expandable storage, halving the size of every photo a customer takes is a meaningful product decision. For you, it means more photos fit on your phone, iCloud backups are faster, and AirDrop transfers complete in less time.

But HEIC is not only about saving space. The container format is genuinely more capable than JPG in ways that matter for modern photography. It can store 10-bit and even 12-bit colour depth instead of JPG’s 8 bits, which means far smoother gradients and a much wider tonal range — essential for high dynamic range (HDR) images. It supports wide colour gamuts such as Display P3, so the vivid reds and greens captured by recent iPhone cameras survive in the file. It can hold transparency through an alpha channel, multiple images in a single file (the basis of Live Photos, bursts and image sequences), depth maps for Portrait mode, and even non-destructive edits. A JPG can do none of these things; a single HEIC file can do all of them at once.

The catch — and the reason a converter exists — is compatibility. HEIC is a young format by the standards of the web. It debuted on consumer devices in 2017, and while Apple’s ecosystem embraced it immediately, the wider world of Windows PCs, Android phones, older software, email clients, content management systems and web browsers has been slower to catch up. Many programs simply cannot open a .heic file, and almost no web browser can decode one natively. JPG, by contrast, opens absolutely everywhere. So when you need to share an Apple photo with someone on a different platform, upload it to a website that rejects HEIC, or edit it in software that does not recognise the format, converting that HEIC to JPG is the simplest and most reliable solution — and that is exactly what this tool does.

HEIC vs JPG: a detailed comparison

HEIC and JPG are both image formats, but they were designed in different eras for different priorities, and understanding the trade-offs makes it clear when each one is the right choice. JPG — properly JPEG, after the Joint Photographic Experts Group that created it — dates from 1992. It is the most universal image format in history: there is essentially no camera, phone, computer, browser, printer or app made in the last thirty years that cannot open a JPG. That ubiquity is its single greatest strength. Its weaknesses are a product of its age: it is limited to 8 bits per colour channel, it cannot store transparency, it has no support for HDR or animation, and its lossy compression, while good, is far less efficient than modern codecs.

HEIC, arriving twenty-five years later in 2015 as a specification and 2017 on Apple devices, was built to fix exactly those limitations. Its HEVC-based compression produces files around half the size of a comparable JPG, so it is the more space-efficient format by a wide margin. It supports 10-bit and 12-bit colour for smoother gradients and true HDR, wide colour gamuts such as Display P3, an alpha channel for transparency, depth and disparity maps, and multiple frames in one file for Live Photos and bursts. On paper, HEIC beats JPG on nearly every technical axis except one — and that one exception, compatibility, is decisive for a great many real-world tasks.

The practical difference comes down to where a photo needs to go. If a picture is going to live inside Apple’s ecosystem — viewed on your iPhone, synced to iCloud, edited in Photos on a Mac, shared by AirDrop to another Apple device — HEIC is the better choice, because everything in that world understands it and you keep the smaller files and richer colour. The moment that photo needs to leave the ecosystem, the calculus flips. Uploading to a job application portal, emailing to a relative on an Android phone, embedding in a website, importing into older Photoshop or Lightroom versions, attaching to a printing service, or posting somewhere that only accepts JPEG — in all of these cases, a HEIC will be rejected or refuse to open, and a JPG will just work.

There is also a subtle quality consideration. Converting HEIC to JPG is a one-way trade: you gain universal compatibility but you lose HEIC’s extra capabilities. The 10-bit HDR collapses to 8-bit standard dynamic range, wide P3 colour is mapped into the narrower sRGB space used by JPG, any transparency is flattened onto a background, and depth maps and Live Photo motion are discarded — JPG keeps only the still frame. None of this means the resulting photo looks bad; a well-converted JPG is visually excellent and indistinguishable from the original to most eyes. It simply means the conversion is best understood as creating a portable, shareable copy of an Apple photo, while you keep the original HEIC as your high-fidelity master. That is the workflow this tool is designed to support — convert for sharing, archive the original.

Why do iPhones save photos as HEIC?

Apple switched its devices to HEIC by default in 2017 with the release of iOS 11, alongside the iPhone 8 and iPhone X, and the decision was driven primarily by storage economics. iPhones ship with a fixed amount of internal storage that cannot be expanded with a memory card, so every megabyte a photo consumes is a megabyte the customer cannot use for apps, music or more photos. By moving from JPEG to HEIC, Apple roughly halved the size of every photo taken on the camera without sacrificing visible quality. For a user shooting thousands of pictures a year, that is the difference between filling a phone and never thinking about storage at all — and it makes the lower-capacity, cheaper models far more practical to own.

Storage was only part of the motivation, though. By 2017 the iPhone camera had outgrown what JPEG could represent. The hardware was capturing scenes with extreme contrast — bright skies and deep shadows in the same frame — that demand high dynamic range, and JPEG’s 8-bit depth simply cannot store that range smoothly. HEIC’s 10-bit colour and HDR support let the camera preserve detail in both highlights and shadows, producing the rich, lifelike photos that became a selling point for the iPhone. The format also natively supports the wide Display P3 colour gamut of Apple’s screens, so the vivid colours you see on the display are the colours actually stored in the file rather than a washed-out approximation.

HEIC also unlocked features that have become signatures of the iPhone experience. Because a single HEIC container can hold multiple images and auxiliary data, it is the natural home for Live Photos, where a short burst of frames and audio accompany the still; for Portrait mode, where a depth map stored alongside the image lets you adjust the background blur after the fact; and for burst sequences. None of these would fit cleanly into a flat JPEG. The efficiency of HEVC compression made it feasible to capture and keep all this extra data without the file sizes ballooning, so the format and the features grew up together.

Crucially, Apple was careful to make the transition mostly invisible. iOS includes automatic, on-the-fly conversion: when you share a HEIC photo with an app or service that cannot handle it, or transfer photos to a Windows or older computer, the system can deliver a JPEG copy instead. That is why many iPhone users never realise their photos are HEIC until they try to move the raw files manually — for example by plugging the phone into a PC, copying from iCloud, or pulling files off an SD card from a camera. In those situations the automatic conversion does not happen, you end up with .heic files that your other software refuses to open, and a converter like this one becomes the bridge that turns those Apple photos back into universally readable JPGs.

The benefits of converting to JPG

The single most compelling reason to convert HEIC to JPG is universal compatibility. JPG is the lingua franca of digital images: every operating system, every web browser, every email client, every social network, every printing service and virtually every piece of photo software made in the past three decades reads it without question. When you convert an Apple photo to JPG you remove every barrier between that image and the people, websites and programs you want to share it with. There is no plugin to install, no extension to enable, no “this file type is not supported” error — the photo simply opens. For anything destined to leave the Apple ecosystem, that reliability is worth more than the storage savings HEIC offers.

Compatibility is especially important for the everyday tasks where HEIC quietly causes friction. Uploading a profile picture or document scan to a website that only accepts JPEG or PNG; attaching photos to a job or visa application; sending pictures to a relative whose Android phone or Windows PC cannot preview HEIC; embedding images in a Word document, PowerPoint deck or PDF; importing shots into an older version of Photoshop, Lightroom, GIMP or a video editor; printing photos at a kiosk or online print service — every one of these is a place where a HEIC stops you and a JPG keeps you moving. Converting in advance means you never have to discover the incompatibility at the worst possible moment.

JPG is also the safer choice for long-term accessibility and archiving in mixed environments. Because the format is so deeply entrenched and so widely implemented, a JPG you create today will still open effortlessly on whatever devices and software exist far into the future. HEIC, being newer and tied more closely to Apple’s ecosystem, carries a small but real risk that a particular recipient, platform or legacy system simply will not be able to read it. If you are sending photos to many different people, posting publicly, or storing images somewhere they must be readable by anyone, JPG removes that uncertainty entirely. It is the dependable common denominator.

Finally, converting to JPG is the practical foundation for almost any further work you want to do with an Apple photo. Web optimisation tools, automated image pipelines, content management systems, e-commerce platforms and design applications overwhelmingly expect JPG or PNG input. Once your iPhone photos are JPGs, you can resize, crop, compress, watermark, run them through a background remover, or batch-process them with any of the standard tools in this suite — none of which would touch a raw HEIC. Think of JPG conversion as the gateway step: it turns a closed, Apple-specific file into an open, editable, shareable image that the rest of the world is ready to work with.

How HEIC to JPG conversion works (in your browser)

Converting a HEIC file to a JPG involves two distinct stages: decoding the original, and encoding the result. Decoding is the hard part. Inside every HEIC is an image compressed with HEVC, and turning that compressed data back into a grid of visible pixels requires an HEVC decoder — a substantial, specialised piece of software. The problem is that web browsers, with the sole exception of Safari on Apple devices, do not include an HEVC image decoder. If you simply hand a .heic file to Chrome, Firefox or Edge, the browser has no idea what to do with it. This is precisely why a HEIC photo refuses to display on a web page or open in most online tools, and it is the technical obstacle this converter has to overcome.

The solution is to bring the decoder to the browser ourselves. This tool ships with libheif — the open-source, industry-standard library for reading HEIF and HEIC files — compiled to WebAssembly (WASM). WebAssembly is a portable, low-level format that lets code originally written in languages like C and C++ run inside any modern browser at near-native speed. So when you add a HEIC photo, the libheif WASM module parses the HEIF container, locates the primary image, decodes the HEVC-compressed data into raw pixels, applies the correct orientation and colour information, and hands the finished image to the page. It is a real, complete HEIC decoder running locally on your machine — not a thumbnail trick or a server call, but the genuine article executing in your browser tab.

Once the photo has been decoded into pixels, the second stage is straightforward and fast. The decoded image is drawn onto an HTML canvas, where your chosen adjustments — orientation, resizing, quality — are applied, and then the browser’s built-in encoder writes it out in the format you selected. For JPG, WebP and AVIF this uses the same hardware-accelerated codecs the browser uses for every image it saves, so encoding is quick and high quality. For formats the browser does not natively produce, such as PDF or TIFF, the tool encodes them itself. Throughout, the conversion runs through a managed queue so that a batch of dozens or hundreds of photos is processed smoothly without freezing the page, with progress shown for each file.

The defining characteristic of this whole process is that nothing leaves your device. There is no upload step, no server, no cloud account. Your HEIC files are read directly from your machine into the browser’s memory, decoded and re-encoded there, and the finished JPGs are handed straight back to you for download. Because the work happens locally, conversion is fast, it works offline once the page has loaded, and — most importantly — your photos remain completely private. The locations, faces, timestamps and camera details embedded in your Apple photos never travel across the internet to a stranger’s server, because the entire pipeline, decoder and all, lives inside your own browser tab.

Apple photo compatibility guide (iPhone, iPad, Mac)

Within Apple’s own ecosystem, HEIC works flawlessly and invisibly, which is exactly why so many people are surprised to learn their photos are even in that format. Any iPhone running iOS 11 or later (from the iPhone 7 onward), any iPad on iPadOS 11 or later, and any Mac on macOS High Sierra (10.13) or later can capture, display and edit HEIC natively. The Photos app, Quick Look preview, Messages, Mail, AirDrop and iCloud Photos all handle the format seamlessly. If you only ever view and share your pictures between Apple devices, you may never need to convert anything — the system simply shows you your photos and quietly manages the file format behind the scenes.

The friction appears at the boundary of that ecosystem. Windows is the most common place people hit it: a fresh Windows installation cannot open .heic files in Photos or File Explorer’s preview, showing a black thumbnail or an error instead. Microsoft offers HEVC and HEIF extensions through the Microsoft Store that add support, but the HEVC video extension typically carries a small charge and many users either do not know it exists or would rather not install it. Android is similarly mixed: newer phones and Google Photos can often display HEIC, but plenty of apps, older devices and third-party tools cannot. Across both platforms, the safest assumption is that a HEIC you send may not open — which is why converting to JPG before you share removes all doubt.

Software compatibility is its own consideration. Recent versions of Adobe Photoshop and Lightroom, Affinity Photo, and many modern editors can import HEIC, but older releases cannot, and a great deal of business and web software — content management systems, e-commerce back-ends, document tools, automated upload forms — expects JPG or PNG and will reject a HEIC outright. Web browsers are the starkest case: only Safari decodes HEIC, so any image you want to display on a website, or run through a browser-based tool, generally needs to be a JPG, PNG or WebP first. Understanding where these walls are helps you decide when conversion is necessary versus when Apple’s automatic handling will cover you.

It is worth knowing how Apple’s own automatic conversion behaves so you can predict when you will end up with stubborn .heic files. When you share through iOS’s share sheet, AirDrop to a non-Apple target, or transfer photos in a way the system mediates, iOS will frequently hand over a JPEG copy automatically, sparing you any trouble. You can even set this as the default behaviour: under Settings, going to Photos and choosing “Automatic” for the “Transfer to Mac or PC” option tells the phone to convert to a compatible format when offloading to a computer. The cases where you are left with raw HEIC are typically manual ones — copying files directly off the device’s storage, downloading originals from iCloud.com, or receiving HEIC files someone else exported. Those are precisely the situations this converter is built to resolve, turning Apple-native photos into files the rest of your devices and apps accept.

HEIC metadata and privacy (EXIF, GPS, camera data)

Every photo your iPhone takes carries far more than the visible image. Embedded inside the HEIC file is a rich layer of metadata, most of it stored in the EXIF (Exchangeable Image File Format) standard. This includes the exact date and time the photo was taken down to the second, the make and model of the device, the specific lens used, and detailed camera settings such as aperture, shutter speed, ISO and focal length. For photographers and archivists this information is genuinely valuable — it lets you sort, search and understand a library, and it preserves the technical record of how each shot was made. But the same metadata can reveal a great deal more about you than you might intend.

The most sensitive piece of embedded data is location. If location services are enabled for the camera, every photo is stamped with the precise GPS coordinates — latitude, longitude and often altitude — of where it was taken. That means a single holiday snap, a picture of an item you are selling, or a photo of your children can silently broadcast your home address, your travel patterns or your daily routine to anyone who receives the file and knows how to read it. Because this data is invisible in normal viewing, people routinely share photos online without realising they are also sharing exactly where they were standing. Stripping GPS data before publishing is one of the simplest and most effective privacy steps you can take.

This tool treats metadata as something you should be able to see and control, not something that just happens to you. Before converting, you can inspect the EXIF, GPS and camera information held inside each HEIC, so you know exactly what the file contains. Then you decide what travels into the converted JPG. You can preserve everything — useful when you are converting your own photos for a personal archive and want to keep the capture details and dates intact. You can strip everything for maximum privacy. Or you can take a more nuanced approach and remove only the sensitive categories, such as deleting GPS location while keeping the harmless camera settings and timestamp. The choice is yours, and it is made explicitly rather than by accident.

Because the entire conversion runs inside your browser, your metadata is never exposed to anyone during the process either. With a server-based converter, you upload your original photo — GPS coordinates and all — to a company’s computers, and you have to trust how they handle, log and delete it. Here there is no such exposure: the file is read locally, the metadata is parsed locally, and whatever you choose to keep or remove is written into the output locally, all without a single byte being transmitted. This makes the tool a sound choice precisely for the photos where privacy matters most — pictures that reveal a location, a face or a moment you would rather not hand to a third party just to change a file format. If you want a dedicated pass over metadata, the companion Remove EXIF Metadata tool gives you even finer per-field control.

HEIC for photographers: HDR, wide colour and depth

For serious photographers, HEIC is more interesting than its reputation as “the format that won’t open” suggests. Its biggest technical advantage over JPG is bit depth. JPG stores 8 bits per colour channel, which gives 256 levels per channel and around 16.7 million colours — plenty for ordinary images, but prone to visible banding in smooth gradients like skies and studio backdrops. HEIC stores 10 bits per channel as standard, lifting that to 1,024 levels per channel and over a billion colours. The result is dramatically smoother tonal transitions and the headroom needed to represent high dynamic range scenes faithfully. When an iPhone captures a sunset with a bright sky and shadowed foreground, that extra bit depth is what lets the file hold detail in both extremes at once.

Wide colour gamut is the second photographic strength. Modern iPhone cameras and displays work in the Display P3 colour space, which covers a noticeably larger range of saturated reds, greens and oranges than the older sRGB space that JPG effectively assumes. HEIC can carry that full P3 gamut, so the intense, lifelike colours captured by the sensor are preserved in the file exactly as the screen shows them. Convert carelessly to a standard sRGB JPG and those out-of-gamut colours have to be remapped, which can slightly mute the most vivid hues. A good converter handles this colour mapping deliberately and intelligently, so the JPG looks as close as possible to the original — and this tool applies a proper colour-managed conversion rather than a naïve one.

HEIC’s container also stores data that goes beyond the visible picture, and this is where it gets genuinely clever. Portrait mode photos include a depth map — a secondary grey-scale image encoding how far each part of the scene is from the camera — which is what allows the background blur to be adjusted or removed entirely after the shot is taken. Live Photos bundle a short video clip and audio alongside the still. Burst captures store multiple frames in one file. The format can even hold an alpha transparency channel and non-destructive edit instructions. All of this richness is part of why Apple chose HEIC; it is a format designed for computational photography, not just storage.

The important thing to understand when converting is what survives and what does not. A standard JPG is a single, flat, 8-bit sRGB still image, so converting from HEIC necessarily flattens the richer data: the 10-bit HDR is tone-mapped down to 8-bit, the P3 colour is mapped into sRGB, the depth map and Live Photo motion are dropped, and only the primary still frame is kept. For sharing and compatibility this is exactly what you want — a clean, universal photo. But for your own master archive, it is wise to keep the original HEIC files, because they hold capabilities a JPG can never recover. If you need to preserve maximum quality and editability while gaining a more standard format, exporting to a high-quality format such as TIFF or a top-quality WebP, rather than a heavily compressed JPG, will retain more of the original’s fidelity.

Best export settings for quality and file size

Choosing the right export settings is about matching the output to its purpose, and the first decision is the format itself. For maximum compatibility — sharing with anyone, uploading to any website, sending to any device — JPG is the right answer, and you should set its quality somewhere between 80 and 90 for everyday photos. That range looks visually identical to the original to almost any viewer while keeping the file comfortably small. Push quality to 92 or higher only for images where fine detail is critical, such as prints or professional delivery, since the file size climbs steeply for diminishing visible gains above that point. Below about 70, compression artefacts start to become noticeable in smooth areas and around edges.

If your destination supports modern formats, WebP and AVIF are worth considering instead of JPG. WebP typically produces files 25 to 35 percent smaller than a JPG at the same visual quality, supports transparency, and is now read by every major browser — making it an excellent choice for websites and apps you control. AVIF, based on the AV1 codec, goes further still, often halving the size of a JPG while also supporting HDR and wide colour, which means it can preserve more of the original HEIC’s richness than a JPG can. The trade-off is that AVIF encoding is more demanding and its support, while good, is not quite universal. As a rule of thumb: JPG when it must open anywhere, WebP for the modern web, AVIF when you want the smallest files and the best colour fidelity and control the audience.

Resolution is the lever people most often overlook, and it usually matters more than format. An iPhone photo can be 4,000 pixels or more across, which is far larger than almost any screen will ever display. If your converted photo is going onto a website, into a document, or being emailed, resizing the longest edge down to something like 1,920 or 2,560 pixels can cut the file size by half or more with no visible difference at normal viewing sizes, because file size grows with the square of the dimensions. Reserve the full native resolution for cases that genuinely need it — large prints, cropping latitude, or archival masters. This tool lets you set a maximum dimension as you convert, so right-sizing the whole batch is a single setting.

Finally, weigh up colour and metadata as part of your export profile. For photos with HDR or vivid P3 colour, allowing the tool’s colour-managed conversion to map the image into sRGB carefully will give the most natural-looking JPG; if you are exporting for the web specifically, WebP or AVIF at a high quality will hold onto more of that colour than JPG. On metadata, decide based on destination: keep EXIF and capture details for your personal archive, but strip GPS and other sensitive fields for anything you publish or send to people you do not fully trust. A sensible default profile for general sharing is JPG at quality 85, resized to a 2,560-pixel longest edge, with GPS removed — small, sharp, universally readable and privacy-safe. Save your own preferred settings once and apply them across every conversion.

A professional Apple-photo conversion workflow

A reliable workflow for handling Apple photos at scale starts with a clear principle: keep your originals and convert copies. Your HEIC files are your high-fidelity masters — they hold the full 10-bit colour, HDR, depth data and the smallest file sizes — so you never want to overwrite or delete them in the course of making a shareable version. Treat conversion as an export step that produces a portable duplicate, leaving the source untouched. This non-destructive approach means you can always re-export later at a different size, format or quality without compounding any loss, and your archive remains as good as the day the photo was taken.

The second step is to standardise your output for each destination. Rather than deciding settings photo by photo, define a small number of export profiles that match how you actually use images: perhaps a “web” profile of WebP at quality 82 resized to 1,920 pixels with GPS stripped; a “share” profile of JPG at quality 88 at full or near-full resolution with metadata kept; and a “document” profile that merges photos straight into a PDF. With profiles in mind, converting a fresh batch of iPhone photos becomes a matter of picking the right one and clicking convert. Consistency like this matters enormously when the photos sit side by side — in a gallery, a product catalogue, a report or a portfolio — where mismatched sizes and quality would look unprofessional.

For larger jobs, lean on the batch features rather than working one file at a time. Add an entire folder of HEIC photos at once, let the managed queue process them with per-file progress, and use retry to clean up any individual file that fails rather than restarting the whole set. When the run finishes, download everything as a single ZIP so the export arrives tidy and organised, or merge the photos into one multi-page PDF when you need a document — a set of receipts, an ID and supporting paperwork, or a contact sheet of proofs. Because everything happens locally, even a camera roll of several hundred photos converts without uploading a single byte or waiting on a network.

Finally, build privacy and downstream editing into the routine. Before converting photos you intend to publish or send beyond your circle, inspect the metadata and strip GPS and other sensitive fields so you are not unknowingly sharing your location. After conversion, the resulting JPGs, PNGs or WebPs are ordinary, universally editable images, ready for any further step you need — resizing, cropping, compressing, watermarking, background removal or assembly into a PDF — using the other tools in this suite that simply cannot touch a raw HEIC. Put together, this workflow turns a phone full of closed, Apple-specific files into clean, private, consistent, shareable images, while preserving your originals as the master copies you can always return to. That is the professional way to live with HEIC: embrace it on your devices, and convert deliberately whenever a photo needs to face the wider world.

100% private — your photos never leave your device