How to Convert HEIC to JPG on Windows (2026 Guide)

You've copied photos from an iPhone to a Windows PC, opened File Explorer, and found blank thumbnails instead of memories you can use. Double-clicking the file may produce a “Photos can't open this file” message, even though the image looks perfectly normal on the phone. The practical answer depends on what you're holding: one HEIC photo, a folder of images, a privacy-sensitive collection, or a repeatable conversion pipeline.

This guide treats how to convert HEIC to JPG on Windows as a decision tree. You'll find the built-in Windows route first, then batch tools, browser-based options, and command-line workflows, with the trade-offs that matter when a conversion needs to be reliable.

Table of Contents#

• Why HEIC Files Trip Up Windows Users
  • Match the method to the job
• Converting HEIC to JPG Using Built-In Windows Tools
  • Install the decoding support
  • Save a copy from Photos
  • Use Paint as the fallback
• Batch Converting HEIC Libraries on Windows
  • Configure the first batch carefully
• Online and WebAssembly HEIC to JPG Converters
  • Comparison of common options
  • The under-a-minute test
• Command-Line and Automation Options
  • A simple PowerShell loop
  • Validate metadata separately
• Quality, Metadata, and Format Trade-Offs
  • Metadata deserves its own test
• Picking the Right Method and Quick FAQ
  • Quick answers to awkward edge cases

Why HEIC Files Trip Up Windows Users#

HEIC stands for High Efficiency Image Container, the file container commonly associated with Apple's implementation of HEIF. Apple introduced the format with iOS 11 and macOS High Sierra in 2017, after HEIF had been standardized in 2015. Windows support arrived later and developed in stages, which is why an iPhone photo can open instantly on Apple hardware but fail on a Windows machine. The format history is documented in the HEIF and HEIC format overview.

The problem usually appears at the decoder layer. File Explorer may not render a thumbnail, Photos may report that it can't open the file, and Paint may refuse to load it. Microsoft's HEIF Image Extension provides the required Windows support, while Microsoft also states that HEVC Video Extensions are needed for Windows to read or write .heic files through that extension. The Microsoft Store listing explains that HEIF support applies to both .heic and .heif files and depends on the matching HEVC component for HEIC handling, as described in the Microsoft HEIF Image Extension listing.

Windows version differences add another layer of confusion. Windows 10 version 1803 added HEIF support in the Photos app, while Windows 11 bundled HEIF Image Extension by default beginning with 22H2, according to the format timeline above. Older Windows 10 builds, particularly pre-1803 systems, may need extra codecs or an entirely separate conversion workflow.

Match the method to the job

Microsoft Store installation can also fail on managed, offline, or tightly restricted corporate computers. N and KN editions may require additional media components, and an organization's firewall or app policy can block Store access altogether. In those cases, repeatedly clicking Install usually won't solve the underlying problem.

Use this decision rule:

• One or two images: Install the codecs, then use Photos or Paint.
• A folder or library: Choose an offline batch converter with an explicit output folder and quality setting.
• Sensitive images: Keep the files local and avoid uploading them to a cloud service.
• Recurring transfers: Use ImageMagick, libheif, or a PowerShell workflow that can run without manual clicks.

If the converted JPGs are still too large for a website or email, a separate guide to making file sizes smaller can help after conversion.

Converting HEIC to JPG Using Built-In Windows Tools#

For a single image, Windows' own tools are usually the least complicated option once HEIC decoding works. The key point is that Photos and Paint can convert HEIC natively only after the required codec stack is installed. Microsoft-community guidance consistently points users toward HEIF Image Extensions, and in many cases the matching HEVC Video Extensions, before attempting the save operation. See the Windows codec and conversion guidance for the dependency details.

Install the decoding support

Open the Microsoft Store and search for HEIF Image Extensions. Install it, then install HEVC Video Extensions from Device Manufacturer if Windows still can't open the image. Microsoft offers a device-based HEVC option in some configurations, while other systems may display a manufacturer codec priced at $0.99, so check the exact listing and your organization's software policy before buying anything.

Restart Photos after installation. If the file still fails, restart Windows, then try opening the image directly from File Explorer rather than from a recent-files list.

Save a copy from Photos

1. Right-click the .heic file in File Explorer.
2. Choose Open with, then select Photos.
3. In Photos, select the three-dot menu.
4. Choose Save as or Save a copy.
5. Select JPEG (*.jpg) as the output type.
6. Choose a destination and set the quality control if Photos presents one. High is the sensible default for a normal photo.

The Windows Photos HEIC conversion walkthrough illustrates this menu path. The original HEIC remains unchanged, and Photos creates a separate JPEG copy.

Use Paint as the fallback

Paint is useful when Photos' save command is missing or behaves differently after an app update. Open the HEIC in Paint, select File, choose Save as, then select JPEG picture. Confirm the destination and quality prompt, then save the new file.

If Windows keeps opening the wrong application, right-click the HEIC file, choose Open with, select Photos, and enable the option to use that app as the default for the file type. Before changing file associations through registry instructions, create a backup. The relevant association area is HKLM\Software\Microsoft\Windows Photo Viewer\Capabilities\FileAssociations; editing the registry without a backup can create a new problem rather than fixing HEIC support.

For Store-blocked systems or N/KN editions, use an approved offline converter or ask the administrator to install the required media and image components. If you also need to resize or reformat the resulting images, Picjam photo resizing guide is a useful companion resource. For a browser-based alternative, see the HEIC to JPG conversion tool.

Batch Converting HEIC Libraries on Windows#

Photos and Paint are fine for a single file. They become a poor workflow when a folder contains dozens or hundreds of HEIC images because every file requires a separate open-and-save cycle. Microsoft-community answers recommend local converters or command-line workflows for bulk jobs because they can process folders, apply predictable naming, and expose quality controls. The recurring codec issues and batch recommendations are discussed in Microsoft's bulk conversion guidance.

Desktop tools worth evaluating include CopyTrans HEIC for Windows, iMazing HEIC Converter, and ImBatch. Their interfaces differ, but the practical workflow is similar: select the source files or folder, drag them into the application, choose an output directory, set JPEG quality, and start the job.

Configure the first batch carefully

Set the output destination outside the source folder whenever possible. That prevents the application from reading its own newly created JPGs and reduces the chance of overwriting or confusing source files. Decide whether the output should preserve the original filename or append a suffix such as _converted, especially if the source and destination might later be merged.

Quality controls aren't standardized. One program may use a Photoshop-style scale from 0 to 12, while another uses a 1 to 100 slider. Translate the setting by reading the application's description, not by assuming that the same number means the same compression. A high-quality setting around 90 to 95 is often used when preserving detail matters, but the right value depends on whether the JPG is for archiving, editing, or web delivery.

Check whether the tool can:

• Process subfolders: Enable recursive scanning if the library has year, event, or device folders.
• Preserve capture dates: Confirm that EXIF timestamps remain attached to the JPG.
• Use multiple cores: Parallel processing can shorten large local jobs, but it can also increase memory pressure.
• Avoid silent resizing: Some applications may downscale images above 4000px without making that behavior obvious. Disable resize options unless you specifically need them.
• Prevent collisions: Never let two source files with similar names write into a shared destination without a collision rule.

Before starting a large library, test a small mixed sample. Open the outputs, compare dimensions, inspect orientation, check capture dates, and confirm that the destination contains the expected number of files. Also test an image with unusual metadata or a wide-gamut source, because some tools produce a usable JPG while changing color or metadata.

Batch rule: Never begin a major conversion until one small test confirms filenames, dimensions, orientation, metadata, and destination behavior.

If the converted images need to be packaged for delivery, you can use a workflow for combining images into a PDF after verifying the JPG outputs.

Online and WebAssembly HEIC to JPG Converters#

Browser tools remove installation friction, but they aren't all doing the same thing. A conventional online converter uploads the HEIC file to a remote server, processes it there, and returns a JPG. A WebAssembly converter runs the conversion engine inside the browser, so the file can remain on the Windows device.

That distinction matters for private photos, client assets, medical imagery, and company folders. A browser interface alone doesn't prove local processing. If privacy is important, open the browser's developer tools, watch the Network panel during conversion, and confirm that the HEIC file isn't sent to an upload endpoint. A page that merely says “secure” hasn't given you enough technical evidence.

Comparison of common options

The table separates architecture from convenience. Server-side services can be easy for occasional, non-sensitive images, but you should check file handling, batch restrictions, account prompts, watermarks, and whether thumbnails remain on the provider's infrastructure. Free tiers may impose limits such as 10 to 50 files or 100 MB per batch, but those limits can change, so verify the current interface before planning a library migration.

PDFWix provides a browser HEIC-to-JPG workflow designed for Windows browsers, with local WebAssembly processing described for its web tools. Its broader privacy model is outlined in this guide to whether online PDF tools are safe.

The under-a-minute test

• Convert one harmless sample and inspect the browser's Network panel for unexpected file uploads.
• Open the JPG in File Explorer and check dimensions, orientation, and capture date before using the tool for private or irreplaceable images.

Command-Line and Automation Options#

A command-line workflow makes sense when HEIC files arrive in predictable folders, when a contractor handoff needs repeatable processing, or when nobody should have to click Save for every image. The usual Windows choices are ImageMagick with libheif support, standalone libheif tools such as heif-convert, and ExifTool for metadata checks or transfer.

Install ImageMagick from a trusted Windows distribution and confirm that its build includes the libheif delegate. Alternatively, install MSYS2 and obtain the relevant packages there. For a simpler decoder path, use the standalone libheif command-line utilities. ExifTool is separate, but it helps you inspect and manage EXIF and XMP after conversion.

A simple PowerShell loop

After confirming that ImageMagick can decode one test file, run this from PowerShell:

Get-ChildItem "C:\Photos\Incoming" -Filter *.heic -File | ForEach-Object { magick $_.FullName -quality 90 (Join-Path $_.DirectoryName ($_.BaseName + ".jpg")) }

The command walks one folder and writes JPG copies beside the originals. The -quality 90 value is an output setting, not a promise that every converter interprets quality identically. For a safer production job, write to a separate destination and add collision checks.

To mirror subfolders into another tree:

$src="C:\Photos\Incoming"; $dst="C:\Photos\Converted"; Get-ChildItem $src -Recurse -Filter *.heic -File | ForEach-Object { $relative=$_.FullName.Substring($src.Length).TrimStart('\'); $out=Join-Path $dst ([IO.Path]::ChangeExtension($relative,".jpg")); New-Item -ItemType Directory -Force -Path (Split-Path $out) | Out-Null; magick $_.FullName -quality 90 $out }

If ImageMagick reports “no decode delegate for this image format”, the executable cannot read HEIC. Install or select a build with libheif support, confirm the correct executable is on your PATH, and test with magick identify sample.heic. If the error persists, use heif-convert instead of forcing a broken ImageMagick installation.

Validate metadata separately

Conversion and metadata management are separate tasks. Use ExifTool to inspect the result:

exiftool -EXIF:DateTimeOriginal -EXIF:GPSLatitude -EXIF:GPSLongitude -XMP: all "C:\Photos\Converted\image.jpg"

For metadata passthrough, test a controlled copy first rather than applying a broad write operation to an entire library. Preserve the original HEIC files, compare the source and output reports, and be especially cautious with GPS data.

Task Scheduler can run the PowerShell script when an incoming backup folder is available. Create a task that starts PowerShell with the script path, set the working folders explicitly, and write a log containing successes and failures. Automation is only useful when the output can be audited.

Quality, Metadata, and Format Trade-Offs#

HEIC-to-JPG conversion trades compatibility for efficiency and feature depth. JPG opens in more Windows applications, websites, printers, and editing tools, but it may be larger and it can't retain every HEIC capability. Keep the original HEIC as the master when the image matters, then create JPG derivatives for sharing or systems that reject HEIC.

JPEG quality controls are not universal. Some applications label quality with a percentage-like scale, while others use a smaller numeric range. Settings around 75 to 82 are often used as a practical perceptual balance for ordinary phone photos, while settings below 60 can make blocking more visible and settings near 95 may increase file size without a corresponding visible improvement for everyday phone viewing. Treat those values as starting points, then inspect the actual output from your chosen encoder rather than assuming the slider behaves identically everywhere.

Metadata deserves its own test

Useful EXIF fields may include capture date, GPS coordinates, and camera model. Some converters carry these fields across, while others remove them or drop Apple-specific MakerNotes. Open the JPG's Properties > Details panel in File Explorer, or use ExifTool to compare the original and converted files.

Color can change too. Wide-gamut images, including sources using Apple's P3 profile, need careful handling. If the HEIF Image Extension isn't installed correctly, Windows Photos may not interpret or retain the source color information as expected. A JPG can look acceptable in one viewer and noticeably different in a color-managed editing application, so test a representative image before converting a full archive.

Archive practice: Keep the HEIC original, verify one converted file, and treat the JPG as a compatibility copy rather than a replacement master.

A flat JPG also can't preserve the complete behavior of a Live Photo, depth maps, or the paired motion component. If you need editing latitude or lossless intermediate files, consider retaining the original and exporting a PNG or TIFF where the project requires it. For document workflows involving images, the HEIC to PDF converter may be more appropriate than creating standalone JPGs, but inspect the resulting pages and metadata before delivery.

Picking the Right Method and Quick FAQ#

The fastest choice is usually obvious once you identify the job:

• One-off photo: Use Windows Photos or Paint after installing the codecs. A browser converter can be convenient for a non-sensitive file.
• Entire iPhone backup: Use CopyTrans HEIC for Windows or iMazing HEIC Converter, then verify a sample before processing the complete folder.
• Privacy-restricted folder: Use a local ImageMagick or libheif workflow, with separate source and destination directories.
• Scripted pipeline: Use libheif or ImageMagick through PowerShell and log failures for review.

Common failures include blank Explorer thumbnails, an iCloud export that has re-encoded files at a lower quality, and sideways JPGs caused by mixed-orientation EXIF flags. Don't delete the HEIC originals until you've checked dimensions, orientation, capture dates, and the number of converted files.

Quick answers to awkward edge cases

Can Windows 7 or Windows 8 convert HEIC without a codec pack? Not through the modern built-in Photos workflow. Use a compatible offline converter or a supported command-line decoder, and avoid installing random codec packs from unverified sites.

What happens to Live Photos? A JPG represents the still image only. The motion portion and associated Live Photo pairing aren't contained in a standalone JPEG.

Will GPS data survive? It may, but it depends on the converter. Check the output with File Explorer's Details panel or ExifTool before sharing location-sensitive images.

What about a folder larger than 50 GB? Use a local batch or command-line process, split the work into manageable source folders, write to a separate destination, and keep a conversion log. Browser memory and upload behavior make a large private library a poor fit for casual cloud conversion.

Is HEIC ever better than JPG? Yes, for storage efficiency and modern image features. JPG remains the safer delivery format when compatibility matters more than compact storage.

The mental checklist is short: How many files, how private are they, do you need metadata, and will this happen again? Answer those questions first, then choose the tool instead of forcing every job through the same recipe.

PDFWix provides a browser-based HEIC-to-JPG converter for Windows that can process files locally through WebAssembly, without installing desktop software or requiring an account for its web tools. For a quick, non-sensitive conversion or a privacy-conscious browser workflow, visit PDFWix and test one file before converting the rest.