The Complete Guide to Converting iPhone Photos for Any Platform

Everything you need to know about converting iPhone HEIC photos to JPG, PNG, and WebP. Covers HEIC compatibility issues, format selection, EXIF and location data, Live Photos, ProRAW, and batch conversion strategies for large photo libraries.

Published April 6, 2026 · Updated April 6, 2026

If you have ever tried to share an iPhone photo with someone using a Windows PC, an older Android device, or a web platform that predates 2020, you have probably encountered the HEIC problem. The photo looks fine on your phone. It looks fine in iCloud. But when you email it, upload it, or transfer it via USB, the recipient sees an unrecognizable file extension and cannot open it.

This is not a bug. It is a consequence of Apple making a genuinely good technical decision — adopting a superior image format — without the rest of the ecosystem catching up at the same pace. HEIC is a better format than JPEG in almost every measurable way. But "better" does not mean "compatible," and compatibility is what matters when you need to share files across platforms.

This guide covers everything you need to know about iPhone photo formats, when and how to convert them, and how to handle the edge cases that most guides skip — Live Photos, ProRAW files, EXIF metadata, and batch workflows for large libraries.

Why iPhones Use HEIC

Apple adopted HEIC (High Efficiency Image Container) as the default photo format starting with iOS 11 in September 2017. The format is based on the HEIF (High Efficiency Image File Format) standard, which uses the HEVC (H.265) codec for compression.

The practical benefit is substantial: HEIC files are typically 40-50% smaller than equivalent JPEG files at the same visual quality. On a 256 GB iPhone, that difference translates to thousands of additional photos before you run out of storage. For Apple, whose business model involves selling devices at fixed storage tiers, making photos smaller without sacrificing quality was an obvious win.

HEIC also supports features that JPEG cannot match:

  • 16-bit color depth instead of JPEG's 8-bit, enabling smoother gradients and more accurate color reproduction
  • Transparency (alpha channel), which JPEG does not support at all
  • Multiple images in a single file, which is how Live Photos store both the still frame and the video clip
  • Non-destructive editing — iOS can store edit instructions within the HEIC container without modifying the original pixel data
  • Depth maps from Portrait Mode, stored alongside the main image

The problem is that HEIC adoption outside the Apple ecosystem has been slow and uneven, largely because HEVC — the underlying codec — is encumbered by a complex web of patent licensing requirements.

Where HEIC Compatibility Breaks Down

As of 2026, HEIC support has improved significantly, but gaps remain in places that affect everyday workflows.

Windows

Windows 10 and 11 can display HEIC images, but only after installing two extensions from the Microsoft Store: HEIF Image Extensions (free) and HEVC Video Extensions (sometimes $0.99, sometimes free depending on your device manufacturer). Many users do not know these extensions exist, and the experience of encountering an unopenable photo file is confusing and frustrating.

Android

Android added native HEIC support in Android 9 (2018), and most modern Android phones can open HEIC files. However, older devices running Android 8 or earlier cannot, and some third-party Android apps still do not handle HEIC correctly.

Web Platforms

Browser support for HEIC is inconsistent. Safari has supported it since 2017 (naturally, since Apple controls both). Chrome added HEIC support in version 118 (late 2023). Firefox added partial support more recently. But many web applications — email clients, CMS platforms, social media upload forms, e-commerce product photo uploaders — still reject HEIC files or fail to process them correctly.

Older Software

Desktop applications that have not been updated in several years typically cannot open HEIC files. This includes older versions of Photoshop (before CC 2020), GIMP (before 2.10.2 with a plugin), and many enterprise document management systems.

Choosing the Right Output Format

When you convert an iPhone photo, you need to pick a target format. The right choice depends on what you are doing with the image.

HEIC to JPG: The Universal Choice

JPG (JPEG) is the right choice for the vast majority of photo sharing and upload scenarios. Every device, browser, application, and platform on earth supports JPEG. The files are compact, the quality is excellent at settings of 85-95%, and there are zero compatibility concerns.

Use JPG when: emailing photos, uploading to social media, sharing with Windows or Android users, uploading to web platforms, printing photos, or any situation where universal compatibility matters more than cutting-edge efficiency.

Quality setting recommendation: 90% for a good balance of quality and file size. 95% if file size is not a concern and you want near-lossless results. 85% for web uploads where smaller files are beneficial.

HEIC to PNG: When You Need Perfection

PNG is a lossless format, meaning the conversion preserves every pixel exactly as it exists in the decoded HEIC image. PNG files are significantly larger than JPEG — typically 3-5x larger for photographs — but they never introduce compression artifacts.

Use PNG when: you need pixel-perfect accuracy (medical imaging, legal documents, technical diagrams), you need transparency (the alpha channel), you are working with screenshots or graphics rather than photographs, or you plan to do extensive editing and want to avoid generation loss from repeated re-saving.

HEIC to WebP: The Modern Middle Ground

WebP offers compression efficiency between JPEG and HEIC, supports both lossy and lossless modes, and includes transparency support. Browser support is now universal across Chrome, Firefox, Safari, and Edge.

Use WebP when: you are preparing images for web delivery and want smaller files than JPEG, you need transparency with better compression than PNG, or your workflow is entirely within modern browsers and platforms.

Handling EXIF and Location Data

Every iPhone photo contains EXIF metadata — a block of structured data embedded in the file that records information about when and how the photo was taken. This typically includes:

  • GPS coordinates (latitude and longitude of where the photo was taken)
  • Date and time (both the capture timestamp and the timezone)
  • Camera settings (aperture, shutter speed, ISO, focal length)
  • Device information (iPhone model, iOS version, lens identifier)
  • Software (which app took the photo, any editing software used)
  • Orientation (which way the phone was held)

When you convert HEIC to another format, you have an important decision to make: preserve or strip this metadata.

When to Preserve Metadata

Keep EXIF data when you are organizing your own photo library, transferring photos between your own devices, or sharing with trusted recipients who need the context (photographers sharing RAW+HEIC files with editors, for example). The orientation tag is particularly important — without it, some applications will display the photo rotated incorrectly.

When to Strip Metadata

Remove EXIF data when sharing photos publicly or with strangers. The GPS coordinates alone can reveal your home address, workplace, children's school, or other sensitive locations. Many people do not realize that every photo they post online potentially contains their precise location.

Social media platforms like Instagram, Facebook, and Twitter automatically strip EXIF data from uploaded photos. But email, messaging apps (sometimes), cloud storage sharing links, forums, and many websites do not. If you are sharing a photo through any channel that might preserve the original file, strip the metadata first.

When converting with a tool like Fileza.io, the conversion process gives you the opportunity to handle metadata according to your needs — and since the processing happens locally in your browser, your metadata never touches a remote server regardless of your choice.

Live Photos: The Dual-File Challenge

Live Photos are one of Apple's more interesting features and one of the most confusing to deal with outside the Apple ecosystem. A Live Photo consists of two components:

  1. A still HEIC image — the primary photo you see in your camera roll
  2. A short MOV video clip — typically 1.5-3 seconds of video captured around the moment you pressed the shutter

On an iPhone or Mac, these two files are linked and behave as a single unit. When you long-press a Live Photo, it plays the video. When you share via AirDrop, both components transfer together.

When you transfer Live Photos to a non-Apple platform, the pairing breaks. You get separate .heic and .mov files (or sometimes just the HEIC image, with the video stripped). To convert the photo portion, treat it like any other HEIC file. The video portion can be converted separately using a video conversion tool.

If you want to create an animated GIF or short video clip from a Live Photo, you will need to work with the MOV file directly using video tools.

ProRAW and DNG Files

iPhone Pro models (iPhone 12 Pro and later) support Apple ProRAW, which saves photos in the DNG (Digital Negative) format. ProRAW files are dramatically different from HEIC:

  • File sizes of 25-50 MB per photo (compared to 1-3 MB for HEIC)
  • 12-bit color depth with wide color gamut
  • Full sensor data with minimal processing
  • Extensive editing latitude — you can recover highlights and shadows far beyond what HEIC allows

ProRAW/DNG files are intended for photographers who want maximum editing flexibility. If you shoot ProRAW, you probably want to edit in Lightroom, Capture One, or similar software before converting to a delivery format.

For converting DNG files to JPG, PNG, or WebP for sharing, the same principles apply as with HEIC — but be aware that the conversion will bake in whatever the current processing state is. If you have not adjusted the RAW processing settings, the default Apple processing pipeline will be applied, which is generally excellent but not customizable during a simple format conversion.

Batch Conversion for Large Libraries

If you have been using an iPhone for years, you may have thousands or tens of thousands of HEIC photos. Converting them one at a time is not practical. Here are effective approaches:

Browser-Based Batch Conversion

Tools like Fileza.io support selecting multiple files at once. You can select dozens or hundreds of HEIC files from a folder, choose your output format and quality settings, and convert them all in a single batch. Since the processing happens locally in your browser, your photos remain private even during bulk operations.

For very large libraries (10,000+ photos), break the job into batches of a few hundred files to avoid overwhelming your browser's memory. Modern browsers handle several hundred files well, but attempting to convert 10,000 photos simultaneously will likely exhaust available RAM.

iPhone Settings: Automatic Transfer Compatibility

Apple provides a built-in partial solution. Go to Settings > Photos (or Settings > Camera on older iOS versions) and look for the Transfer to Mac or PC setting. Set it to Automatic rather than "Keep Originals." With this setting, your iPhone will automatically convert HEIC to JPEG when transferring photos via USB to a Windows PC or non-Apple device.

The limitation is that this only works for USB transfers, not for AirDrop, email, cloud sync, or any other sharing method.

Changing the Default Capture Format

You can also switch your iPhone to capture JPEG instead of HEIC. Go to Settings > Camera > Formats and select Most Compatible. This uses JPEG for photos and H.264 for video.

The tradeoff is real: your photos will take roughly twice as much storage space, and you lose the advanced features of HEIC (16-bit color, depth maps in the same container, non-destructive edits). For most users, converting on an as-needed basis is a better approach than permanently switching to JPEG capture.

A Practical Workflow

Here is a streamlined workflow for handling iPhone photos across platforms:

  1. Keep shooting in HEIC. The storage savings and quality benefits are worth it.
  2. Use AirDrop for Apple-to-Apple sharing. No conversion needed — HEIC works natively.
  3. Convert to JPG before sharing cross-platform. Use a local tool like Fileza.io to convert — your photos stay on your device.
  4. Strip EXIF data before sharing publicly. Remove GPS coordinates and personal metadata for any photo going to a public audience.
  5. Use WebP for web delivery. If you are uploading to a website or platform that supports WebP, take advantage of the smaller file sizes.
  6. Keep HEIC originals. Always retain your original HEIC files as archives. They are the highest quality version and take the least space.

The iPhone photo ecosystem is slightly fragmented, but the friction is manageable once you understand the formats involved and have a reliable conversion tool in your workflow. The key principle is simple: shoot in the best format your device supports (HEIC), and convert to the most compatible format your recipient needs (usually JPG).

Sources

  1. Apple Developer Documentation: HEIF and HEVC — Apple's technical documentation on HEIC/HEIF format support across iOS and macOS.
  2. Microsoft Support: HEIF and HEVC media extensions — Microsoft's guide to installing HEIC support on Windows 10 and 11.
  3. MPEG HEIF Standard (ISO/IEC 23008-12) — The formal specification for the High Efficiency Image File Format container.
  4. ExifTool Documentation — Comprehensive reference for EXIF metadata fields and their presence across image formats.
  5. Adobe DNG Specification — Adobe's documentation on the Digital Negative format used by iPhone ProRAW.