Free · Fast · Privacy-first

Convert HEIC to JPG Online Free

HEIC is the default photo format on every iPhone running iOS 11 or later, and while the format quietly slashes the storage footprint of a typical camera roll by roughly half, that efficiency comes at a real cost the moment a HEIC photo leaves the Apple ecosystem. Windows refuses to open it without a paid codec, most Android galleries treat it as a broken file, and countless websites, content management systems, photo printers, and email clients reject HEIC uploads outright with a generic format error. FixTools solves this in seconds: a free, browser-based HEIC to JPG converter that needs no sign-up, no software install, no Microsoft Store purchase, and no email address, and that processes your photos entirely on your own device so they never touch a third-party server.

⚡ Use Tool Now How it works

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

⚡

Free with no sign-up required

🔒

Browser-based, files stay private

✨

Supports batch conversion

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

Why Browsers Cannot Display HEIC Files Natively

HEIC files are encoded using the HEVC standard, also known as H.265, the same compression technology that streams 4K Netflix and Apple TV content into your living room. HEVC was engineered for moving images and only later adapted for stills inside the HEIF container, which means that the moment a HEIC arrives at a non-Apple browser, the browser needs an H.265 decoder somewhere on the system to render even a single frame. Chrome, Firefox, and Edge deliberately ship without an HEVC decoder built in because the codec is encumbered by patent royalties owed to MPEG LA, Via LA, and several other patent pool administrators, and embedding a free decoder into the browser would expose the browser vendor to per-install licensing costs. The practical result is that a HEIC dropped into a standard browser image tag renders as the broken-image glyph, and that this is a licensing problem rather than a programming oversight.

Safari on Apple hardware is the well-known exception, and the reasons are structural. Apple writes the kernel, the WebKit rendering engine, the ImageIO framework, and the firmware that drives the silicon HEVC decoder, so every layer of the stack on an iPhone, iPad, or Mac already has paid HEVC licensing baked into the price of the device. Safari simply hands the bytes to ImageIO and receives a fully decoded bitmap back. Every other browser on every other platform treats HEIC as an unknown binary blob, which is why HEIC photos consistently fail when attached to a webmail compose window, dragged into a Slack channel, posted to LinkedIn, or selected from a file picker on a corporate intranet running on Windows. The user almost always blames the website, the messaging app, or their own phone, when in reality the failure point is the missing codec at the receiving end.

The most reliable fix is format conversion at the point of export rather than at the point of consumption. Converting HEIC to JPG inside the browser using the HTML5 Canvas API sidesteps the codec problem entirely because the conversion happens once, on the sender or owner of the file, while a working decoder is still available. The browser decodes the HEIC through whatever native ImageIO equivalent it has access to, paints the resulting pixels into an off-screen canvas, and then re-encodes the canvas as a baseline JPEG using the universally-supported libjpeg encoder that every browser ships with. On Windows or Android devices where there is no native HEIC decoder available at all, FixTools transparently swaps in a WebAssembly build of libheif that performs the decode in pure portable JavaScript-targeted code, and the output is byte-for-byte indistinguishable from what a Mac would produce, just slightly slower per file.

The strategic consequence for anyone working across platforms is straightforward: produce HEIC where the storage savings are real, namely on the iPhone itself and in iCloud Photos, but always convert to JPG before the photo crosses into a system you do not control. This rule of thumb avoids the entire codec-licensing minefield and means you never have to explain to a recipient why their computer cannot open the photo you just sent. Bookmark a browser-based converter, run a single batch each time you transfer files off the phone, and treat the JPG copies as the canonical sharable assets. The HEIC originals remain on the phone or in iCloud as the high-efficiency archive, and the converted JPGs become the universal currency for everything else.

HEVC licensing and browser support (MDN)HEIF standard ISO/IEC 23008-12 Apple HEIF developer documentation

How to use this tool

💡

Upload your HEIC files and convert them to JPG instantly. Download the converted files individually or as a ZIP.

How It Works

Step-by-step guide to convert heic to jpg online free:

1
Upload your HEIC file
Click the large Open HEIC to JPG Converter button and either pick files through the standard system dialog or drag a folder of .heic or .heif images directly onto the upload area. The interface accepts one file or hundreds at a time, holds them in your browser memory, and shows a small thumbnail preview as soon as the decoder reads each header so you can confirm visually that you queued the right photos before starting the actual conversion run.
2
Confirm the conversion settings
The default preset is JPG output at 85 percent quality, which is the sweet spot for most camera-roll photos and produces results that are visually identical to the HEIC original on any normal screen. If you are preparing files for print, slide the quality up to 92 percent; if you need the smallest possible files for email or messaging, drop it to 78 percent. No other settings require attention for a standard run.
3
Convert to JPG
Click Convert and the browser decodes each HEIC file using either the operating system native HEVC support or a bundled WebAssembly decoder, draws the resulting pixels onto an off-screen HTML5 canvas, and encodes that canvas as a baseline JPEG using your chosen quality target. A small progress bar shows the percentage complete per file, and on a modern multi-core laptop a typical iPhone photo converts in under two seconds.
4
Download your JPG files
When the run finishes you can grab individual JPG files by clicking the per-file download button, or hit Download All as ZIP to pull every converted image down in a single archive. The ZIP preserves the original HEIC base filenames so an album named IMG_4521 through IMG_4540 emerges with exactly those names, just with the .jpg extension swapped in for clean library re-import.

Real-world examples

Common situations where this approach makes a real difference:

Sharing iPhone photos with Windows colleagues

A marketing coordinator at a mid-sized retailer takes new season product photos on her personal iPhone 14 because the company camera is booked, and needs to email a tight selection to a Windows-based design agency by the end of the day. The agency reports back that every attachment shows as a generic file icon. She opens FixTools in Safari on the same iPhone, uploads eight HEIC photos, slides the quality to 90 percent for catalog use, and within thirty seconds has eight clean JPGs that she re-attaches and resends. No codec purchase on the agency side, no IT ticket on her side.

Uploading to a website with JPEG-only upload

A neighborhood restaurant owner photographs six new seasonal dishes on her iPhone before service and tries to drop them into the menu module of her WordPress site so the changes go live before the dinner rush. The CMS rejects each upload with a vague unsupported file type error and the kitchen is already plating. She loads FixTools on her laptop, drags all six HEIC files in at once, downloads the ZIP, extracts to Desktop, and uploads to WordPress on the second attempt. The detour adds maybe two minutes and avoids waiting for her web developer.

Preparing iPhone photos for a school project

A sixth-form student photographs reference material on his iPhone over the weekend for a Monday history presentation built in PowerPoint on a shared school computer that runs Windows 10. The presentation template needs JPEG because the school PCs have no HEVC codec installed and IT does not approve Microsoft Store purchases. He opens Chrome on the shared machine, navigates to FixTools, converts four HEIC photos without ever signing into anything, drops the JPGs into the slide deck, then logs out so nothing personal stays behind on the shared profile.

Converting a single HEIC photo attachment

A freelance writer working on a profile piece receives a single HEIC headshot by email from her iPhone-using interview subject, intended as the lead image for the published article. The magazine production system rejects HEIC outright and the editor needs the file within the hour. She drops the one attachment into FixTools, converts at quality 88 for a web display target around 1200 pixels wide, downloads the JPG, and submits it through the magazine portal under fifteen seconds after opening the tool, with no visible quality degradation at the publication size.

Pro tips

Get better results with these expert suggestions:

Use Chrome on Android for on-device conversion

Chrome on Android ships a mature WebAssembly runtime that can host the libheif decoder FixTools uses, which means the conversion runs entirely on the Android device with no network round trip. Save the HEIC attachment from Gmail or WhatsApp into the Downloads folder, open Chrome, drag the file into the upload area, and let the converter finish before saving the JPG straight back to your gallery for sharing or editing.

Set quality to 85 percent for the best size-to-quality ratio

JPEG quality settings above 85 percent produce files that are visually identical to the HEIC original but with file sizes that climb steeply for every extra point. At quality 85 a typical 3 MB iPhone HEIC converts to roughly a 4 to 5 MB JPG with no perceptible difference on a phone screen, a laptop monitor, or a standard A4 print. Push to 92 only for print deliverables; drop to 78 for fast email attachments.

Convert before uploading to social platforms

Facebook, Instagram, X, and LinkedIn all accept JPEG and apply their own aggressive recompression pass to whatever you upload. If you let them auto-convert a HEIC server-side, you stack two lossy compression steps on top of each other and the resulting feed image looks noticeably softer than it should. Convert to JPG at quality 90 in FixTools first so the platform reencode starts from a clean, high-quality baseline you actually controlled.

Batch download as ZIP to preserve filenames

When converting more than three or four HEIC files, always use the Download All as ZIP button rather than clicking each individual download arrow. Some browsers rewrite repeated downloads with generic names such as image (1).jpg, image (2).jpg, which destroys the chronological order of an album. The ZIP route keeps every original HEIC base name intact, just with the extension swapped, so your library re-import lands the photos back in the right sequence.

FAQ

Frequently asked questions

HEIC, short for High Efficiency Image Container, is the photo file format that iPhones and iPads have used by default since iOS 11 shipped in September 2017, and that several recent Android handsets including the Samsung Galaxy S21 family also support. Under the hood it is an instance of the HEIF container standard defined as ISO/IEC 23008-12, with the actual pixel data compressed using the HEVC video codec, also known as H.265. The combination delivers picture quality roughly equivalent to JPEG while using 40 to 50 percent less disk space, which is why Apple was willing to absorb the compatibility friction. The tradeoff is that HEIC requires a licensed HEVC decoder to open, and that decoder is missing or paywalled on most non-Apple platforms.

HEIC files use HEVC compression, and HEVC is encumbered by a thicket of patent royalties owed to MPEG LA, Via LA, and a number of individual rights holders. Microsoft chose not to bundle a free HEVC decoder into Windows because doing so would expose them to per-install licensing costs across every PC that ships with Windows. Instead, Windows users are pointed to the HEVC Video Extensions in the Microsoft Store, a paid add-on that costs around one US dollar. Without that extension installed, Windows Photos, the File Explorer thumbnail engine, and most native Windows applications cannot decode HEIC and show either an error message or a generic placeholder. On a Mac, the story is different: macOS High Sierra and later ship with HEVC support already paid for at the device level, so Preview, Photos, and Quick Look all handle HEIC natively without any user action.

JPEG is a lossy compression format by definition, so on paper any conversion from HEIC to JPG discards some information. In practice, at quality settings of 85 percent and above, the discarded information sits entirely below the threshold of human perception under normal viewing conditions, including on high-pixel-density laptop screens and in glossy photo prints up to A3 size. Decades of psychovisual research backs this up: the eye cannot reliably distinguish a quality-85 JPEG from the source pixels in any double-blind comparison of natural photographs. If you need mathematically lossless output, for example when the image will be reopened and resaved several times in an editor, convert to PNG instead and accept the larger file size in exchange for guaranteed pixel preservation through future edit cycles.

Yes, without qualification. FixTools is free for personal and commercial use with no usage tiers, no watermarks on the output, no attribution requirement, and no clause that limits redistribution or resale of the converted images. The converted JPG files belong entirely to you and inherit whatever rights you held in the original HEIC. There is no commercial license to purchase, no enterprise plan to sign, and no per-image fee for high-volume runs. The service is funded by display advertising on the conversion page, which keeps the tool economically sustainable without any direct charge to users regardless of how the resulting JPGs are eventually used.

No. Every step of the conversion runs locally inside your browser, using a combination of the HTML5 Canvas API, the platform native HEIC decoder where available, and a WebAssembly fallback decoder where it is not. Your photos never leave your device. You can verify this directly by opening browser developer tools, switching to the Network tab, and watching that no upload requests fire while a conversion is running. Two practical consequences follow: first, the converter keeps working even on a slow or intermittent connection once the initial page has finished loading, and second, your photos remain private at the level of the device they originated on, which matters for medical images, legal evidence, identification documents, and anything else you would not voluntarily upload to an unknown third party.

Yes. Batch mode is built into the converter and there is no artificial cap on the number of files you can queue. Drop a folder onto the upload area or shift-select inside the file picker and every selected HEIC will be added to the run. On a modern laptop with eight CPU cores, the conversion runs files in parallel through Web Worker threads, so a batch of forty mid-size iPhone photos typically completes in well under two minutes. When the run finishes, hit Download All as ZIP to retrieve every JPG in one archive that preserves the original HEIC base filenames. The only real ceiling is device memory, which determines how many files can be held in flight at once.

HEIF, short for High Efficiency Image File Format, is the container standard defined in ISO/IEC 23008-12, ratified by the Moving Picture Experts Group. The container itself is codec-agnostic, meaning the image bytes inside it can theoretically be compressed using any of several different codecs. HEIC is the specific filename extension Apple uses for HEIF containers whose payload is compressed with HEVC. AVIF is another HEIF variant whose payload is compressed with the patent-free AV1 codec and uses the .avif extension instead. Some Android cameras save HEIF files with the .heif extension. For practical conversion purposes, FixTools treats both .heic and .heif as interchangeable, since the decoder logic is identical and the container parsing is the same.

Apple transitioned iPhone and iPad cameras from JPEG to HEIC as the default capture format in iOS 11, released to the public in September 2017. The primary motivation was storage efficiency at scale. Across hundreds of millions of iPhones worldwide, halving the average photo file size translates into enormous savings in device storage, iCloud backup bandwidth, and Apple data center capacity. A typical iPhone HEIC weighs in around 2 to 3 MB; the equivalent JPEG would land closer to 4 to 6 MB at the same perceptual quality. You can opt out of HEIC capture on any iPhone by opening Settings, tapping Camera, choosing Formats, and selecting Most Compatible. From that point on every new photo is saved as JPEG instead, but existing HEIC photos in your library remain HEIC until you convert them.

Yes, FixTools writes the EXIF block from the source HEIC into the output JPG using the standard EXIF 2.3 encoding that every JPEG-aware tool understands. That means GPS coordinates from where the photo was taken, the timestamp, the iPhone model, the focal length, aperture, shutter speed, ISO setting, and white balance information all carry across to the converted file. This matters for several practical workflows: photo library managers like Lightroom and Apple Photos rely on EXIF timestamps to sort imports, real estate platforms read GPS data to auto-tag listings, and forensic workflows depend on intact metadata for chain of custody. Note that several social platforms strip EXIF on upload for user privacy, which is a server-side behavior and not a property of the FixTools output itself.

Yes, after the first successful page load. The converter is a static page bundled with its JavaScript and WebAssembly decoder, all of which the browser caches aggressively under standard HTTP cache headers. Once the page has loaded once with an active connection, you can disconnect from Wi-Fi, switch to airplane mode, or move to a location with no signal, and the converter will still process files using the cached assets. This is genuinely useful on long flights, in basements with no cellular service, in environments with regulatory restrictions on outbound network traffic, or anywhere else where you want guaranteed local processing without depending on the network being available at conversion time.