Free · Fast · Privacy-first

Convert HEIC to JPEG

JPEG and JPG are the same file format, just written two different ways. JPEG is the full acronym standing for Joint Photographic Experts Group, the standards committee that designed the format back in 1992, and JPG is the three-letter file extension that arose from the eight-dot-three filename limit on early Microsoft operating systems. The two are interchangeable and any application that opens one opens the other without distinction. FixTools converts your HEIC files to JPEG output, written with the conventional .jpg extension, instantly inside your browser tab. The result is a file that opens on every operating system, every web platform, every email client, every messaging app, and every photo printer in existence, with no codec installation, no Microsoft Store purchase, and no software download required at any point in the workflow.

⚡ Use Tool Now How it works

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

⚡

JPEG and JPG are identical formats

🔒

Instant in-browser conversion

✨

No software or sign-up needed

Image Tool

HEIC to JPG Converter

All processing happens in your browser — your files are never uploaded to any server.

🚀Open HEIC to JPG Converter

100% Free · No account · Works on any device

HEIF Container vs. HEVC Codec: The Two-Layer Structure of HEIC

Understanding why HEIC files end up so much smaller than equivalent JPEGs requires separating the container from the codec, which are two distinct ideas that the casual reader often conflates. The HEIF container, formally specified in ISO/IEC 23008-12, is the outer wrapper that holds image data along with its associated metadata, color profiles, thumbnails, depth information, and optionally multiple images or image sequences inside a single file structure. The HEVC codec, also known as H.265, is what actually compresses the pixel data living inside that container. JPEG by contrast is both a container and a codec rolled together, using a DCT-based compression algorithm that was standardized in the early 1990s and which has only seen incremental improvements since. HEVC compression is roughly twice as efficient as DCT for photographic content, which is the single biggest reason HEIC files come in at 40 to 50 percent the size of equivalent-quality JPEGs.

The efficiency difference translates into measurable, real-world consequences that you can feel on a device storage indicator. A typical iPhone 14 photo in HEIC weighs around 3 to 4 MB at the default camera quality. The same photo saved as JPEG at equivalent perceptual quality would land at 6 to 8 MB. Multiply that delta across a camera roll of ten thousand photos, which is a normal accumulation for a two-year-old iPhone, and you have a difference of 20 to 40 gigabytes of stored data. Now multiply that delta across hundreds of millions of active iPhones worldwide and the aggregate is staggering: petabytes of storage saved across Apple's iCloud backend, billions of dollars saved in user-facing storage upgrades, and a meaningful reduction in the carbon footprint of Apple's data centers. The HEIF standard also supports storing multiple images in one file for HDR, Live Photos, and burst shot scenarios, none of which JPEG can do natively without external sidecar files.

When you convert from HEIC to JPEG you are deliberately trading compression efficiency for compatibility, and it is worth understanding precisely what happens at the bit level so the trade is informed. The HEVC-compressed pixel data inside the HEIC container is decoded into raw pixel values held in browser memory as an RGB or YCbCr buffer. Those pixel values are then handed to a JPEG encoder which applies the DCT transform, quantization, and entropy coding to produce a new JPEG bitstream at whatever quality factor you chose. No additional quality is lost beyond what the JPEG quality setting implies because the pixel data going into the JPEG encoder is exactly the data that came out of the HEIC decoder. The only quality loss is introduced by the JPEG encoding step itself, which at 85 to 90 percent quality is visually imperceptible in any photograph under any normal viewing condition.

A subtle but important point that often confuses people is the difference between the .jpg and .jpeg file extensions. These are two ways of writing the same extension and represent the same exact file format. The three-letter .jpg form arose because early Microsoft DOS and Windows file systems used the FAT eight-dot-three filename convention which limited extensions to three characters maximum. The four-letter .jpeg form is the natural shortening of the full Joint Photographic Experts Group name and is more common on Unix systems where extension length never had a hard limit. Modern systems accept both interchangeably and every image viewer, editor, and uploader treats a file ending in .jpg identically to one ending in .jpeg. FixTools writes output with the .jpg extension as the more universal convention, but you can safely rename the file to .jpeg if a specific intake system insists on the longer form.

HEIF standard ISO/IEC 23008-12 overview HEVC compression efficiency research (IEEE)JPEG format specification overview (Wikipedia)

How to use this tool

💡

Upload HEIC files. FixTools outputs standard .jpg files (JPEG format). Use these wherever JPEG compatibility is required.

How It Works

Step-by-step guide to convert heic to jpeg:

1
Upload your HEIC file
Click the Open HEIC to JPG Converter button and use the system file picker or the drag-and-drop area to load one or more .heic or .heif files into the browser. Multiple selections are supported in a single upload action, and the upload area accepts folder drops in browsers that support that gesture. Each file you queue appears as a small thumbnail with its size and dimensions while waiting in the conversion queue.
2
Conversion is automatic
The tool defaults to JPEG output and immediately begins processing every queued file using the platform-native HEIC decoder on Apple devices or the bundled WebAssembly libheif decoder everywhere else. No format selection step is needed because JPEG is the assumed target. A quality slider sits near the convert button if you want to override the default 85 percent encoding quality for either smaller files or higher fidelity, but standard operation needs no settings changes.
3
Download the JPEG
When conversion completes, the result panel lists every output file with its final size and a download arrow. Each file is a standard JPEG image written with the conventional .jpg extension, which is identical in every functional respect to a file written with the .jpeg extension. Open the downloaded file in Windows Photos, macOS Preview, the Android Gallery, iOS Photos, any web browser, any email client, or any image editor without any compatibility concerns.

Real-world examples

Common situations where this approach makes a real difference:

User confused by HEIC vs JPEG terminology

A Windows 10 user receives a HEIC file from an iPhone-using friend and searches Google for a HEIC to JPEG converter, genuinely uncertain whether JPEG is the same thing as JPG or some subtly different format that the file picker on the receiving end might specifically want. FixTools converts the file to a standard .jpg output and clarifies the terminology question along the way: JPEG and JPG are simply two ways of writing the same extension. The user opens the resulting file in Windows Photos within ten seconds of the conversion finishing, with no codec purchase or account creation required at any step.

Web developer uploading images to a CMS

A freelance web developer building a small business client site receives thirty HEIC product photos that the client took on an iPhone 13 over a weekend. The headless CMS the developer uses for the build only accepts JPEG and enforces a 5 MB per image upload limit. The developer batch-converts all thirty HEIC images in FixTools at quality 88, which lands the output JPEGs at around 4.2 MB on average, comfortably under the limit while preserving plenty of sharpness for product display. The full conversion runs in a single three-minute browser session without ever leaving the build environment.

Print shop receiving orders from iPhone users

A neighborhood photo print shop receives a steady trickle of print orders by email from customers who attach HEIC files exported directly from their iPhones. The shop's legacy RIP software only accepts JPEG and PDF input, so the staff have a recurring conversion task every shift. An employee opens FixTools in Chrome at the start of each shift and runs the day's incoming HEIC orders through batch conversion at quality 92 for print sharpness. The typical daily batch of fifteen to twenty-five files converts in under five minutes with no additional software install on the shop computers.

Preparing photos for a portfolio website

An emerging photographer builds a personal portfolio site on Squarespace and shoots a new series of urban architecture photos on an iPhone 14 Pro as a deliberate constraint exercise. Squarespace's image upload dialog accepts JPEG but not HEIC, so the eight portfolio photos cannot upload directly. The photographer converts each HEIC in FixTools at quality 90 to ensure architectural detail in the deep shadows of the building facades survives into the JPG output. The resulting JPEGs average 6.8 MB each at full resolution and upload into Squarespace without complaint.

Pro tips

Get better results with these expert suggestions:

HEIC and HEIF files are interchangeable in FixTools

A handful of cameras and Android devices save HEIF images with the .heif extension rather than the more common .heic that iPhones use. Both extensions represent the same underlying HEIF container format with an HEVC-encoded payload, and FixTools routes them through identical decoder pipelines. There is no need to rename a .heif file to .heic before uploading. If a file manager on your system refuses to recognize a .heif file at all because the OS lacks a registered handler, renaming is a harmless cosmetic operation that does not modify the underlying file bytes.

Understand the 40-50 percent size increase before batch converting

When planning a bulk HEIC to JPEG conversion across a substantial photo library, budget realistically for the resulting storage growth before you even begin the run. A 20 GB iCloud photo library stored as HEIC will land somewhere between 35 and 40 GB once converted to JPEG at quality 85, and substantially more if you push quality higher for print or archival use. Verify that the destination drive, external SSD, or cloud storage account has at least double the source library size in free space available before you launch a large batch.

Use 90 percent quality for print, 80 percent for web delivery

Photographers converting HEIC for delivery to a print lab should set the quality slider to 90 to 95 percent to retain fine detail in shadow regions and the subtle gradations in highlights that JPEG compression at lower quality factors tends to flatten in ways that survive into the final printed output. For web publication where total page weight and load speed dominate the user experience, 75 to 80 percent quality produces files comfortably under one megabyte for typical 12-megapixel smartphone captures while remaining visibly sharp at normal web display sizes.

Verify color space conversion for wide-gamut content

Every iPhone camera since the iPhone 7 captures photos in the Display P3 color space, also known as DCI-P3, which contains a wider gamut of saturated reds, oranges, and greens than the sRGB standard most web browsers and social platforms assume. When converting to JPEG for the web, FixTools maps the gamut down to sRGB to ensure colors display consistently in browsers and on social platforms. Unmanaged conversions in lower-quality tools can produce slightly desaturated colors, particularly in vivid reds and greens that fall outside the sRGB triangle.

FAQ

Frequently asked questions

There is no functional difference between the two; they are simply two ways of writing the same file extension. JPEG is the full acronym standing for Joint Photographic Experts Group, the standards committee that defined the format in 1992. JPG is the three-character extension form that originated because early Microsoft DOS and Windows operating systems enforced an eight-dot-three filename convention under the FAT filesystem, which limited extensions to three characters. Both extensions identify the same image format with the same bitstream structure, and every application that opens .jpeg will open .jpg, and vice versa. FixTools writes its output with the more universally compatible .jpg extension, but you can rename to .jpeg without modifying the file.

At equal file sizes, yes, HEIC contains visibly more detail than JPEG because the HEVC compression algorithm at the heart of HEIC is roughly twice as efficient as the DCT algorithm JPEG relies on. A 3 MB HEIC and a 3 MB JPEG of the same scene shot under the same conditions will not look the same: the HEIC will preserve subtle gradations and fine detail that the JPEG sacrifices to its less efficient compression. At equal perceptual quality, HEIC files come in 40 to 50 percent smaller. However, JPEG's universal compatibility means that for any sharing scenario outside the Apple ecosystem, the practical advantage swings back to JPEG despite its compression deficit. Both formats have their right contexts.

At 85 percent conversion quality and above, the JPG will be visually identical to the HEIC original under any normal viewing condition. This includes high-density displays like a MacBook Pro Retina screen at native resolution, standard photo prints up to A3 size, and projection in conference room presentations. Pixel-level mathematical differences absolutely exist between the HEIC source and the JPG output, and they would show up under careful per-pixel diff inspection, but those differences sit below the threshold of human visual perception. Decades of psychovisual JPEG research consistently shows that quality 85 is the boundary where compression artifacts become invisible to unaided vision in photographic content.

Windows 10 and Windows 11 can both open HEIC files, but only after installing the HEVC Video Extensions from the Microsoft Store, which is a paid add-on costing around one US dollar. Some Windows PCs sold with the operating system pre-installed receive a free OEM variant called HEVC Video Extensions from Device Manufacturer, which is functionally identical to the paid version but bundled with the device license. Without either of these codec packages installed, Windows Photos shows an error when opening HEIC files, File Explorer cannot generate HEIC thumbnails, and most native Windows applications including Microsoft Office cannot place HEIC images. Browser-based conversion in FixTools sidesteps the codec requirement entirely.

Converting at 85 to 90 percent JPEG quality produces output that is visually indistinguishable from the HEIC original to the human eye under any normal viewing condition. The conversion process fully decodes the HEIC into a raw pixel buffer first and then re-encodes that buffer as JPEG, so no compression artifacts compound on top of each other; the only quality reduction is whatever the JPEG encoding step introduces at the chosen quality factor. At 90 percent, that reduction is mathematically real but visually invisible. For workflows that genuinely cannot tolerate any loss whatsoever, including some forensic or scientific imaging contexts, convert to PNG instead, which is genuinely lossless at the cost of a much larger file size.

FixTools writes output files using the .jpg extension because three-character extensions remain the more universal convention across legacy systems and intake forms. Functionally, .jpg and .jpeg are identical and any application that opens one opens the other without distinction. If a specific intake system, online form, content management system, or printing service insists on the .jpeg form specifically, you can rename the downloaded file by appending an additional "e" to the extension or by using your operating system's rename function. The internal bitstream is exactly the same JPEG data regardless of which extension the file ends in.

This size increase is fully expected and is not a flaw in the conversion process. HEVC compression, which is what produces the small HEIC file in the first place, is roughly twice as efficient as the JPEG DCT compression algorithm for photographic content. The HEIC was already aggressively compressed using a modern algorithm specifically designed for efficiency. Converting to JPEG necessarily requires re-encoding the pixel data with the older, less efficient JPEG codec, and that codec needs more bytes to represent the same visual information at the same perceptual quality. The 40 to 50 percent size increase from HEIC to JPEG at equivalent quality is a fundamental property of the two formats, not a converter limitation.

Yes, the workflow on iPad is identical to the one on iPhone with the bonus of a larger screen for managing files. Open Safari on your iPad, navigate to fixtools.io, and tap through to the HEIC to JPG Converter. Tap Upload and select HEIC files from your Files app, the Photos library, or an iCloud Drive folder. Safari on iPadOS fully supports the Canvas API and uses the iPad hardware HEVC decoder so the conversion runs entirely on-device at speeds comparable to a Mac. Tap Download and the JPEG saves into the Files app Downloads folder, from where you can drag it into Photos, iCloud Drive, or any third-party cloud storage app installed on the iPad.

Yes, FixTools handles the full 48-megapixel ProRAW HEIC files that the iPhone 15 Pro and Pro Max produce when shooting in the high-resolution mode, though the conversion takes slightly longer per file than for standard 12-megapixel HEICs because there is simply more pixel data to decode and re-encode. A typical 48-megapixel ProRAW HEIC of around 25 MB converts to a JPEG of around 18 to 22 MB at quality 90, depending on the scene complexity. The hardware HEVC decoder on the iPhone 15 Pro handles these files in roughly two to three seconds; on a desktop browser without hardware acceleration the same file takes around five to eight seconds through the WebAssembly decoder.