How to Batch Convert HEIC Photos for Email and the Web
iPhone HEIC files still bounce off Windows inboxes and CMS uploads. Here is when to convert once, how to balance quality vs file size, and how to keep originals while you send the copies.
You tap Share, attach a few iPhone shots, and the reply comes back blank - or worse, a Windows PC shows a broken icon. HEIC is efficient on Apple devices, but email clients, older Windows builds, and many website uploaders still expect JPG or PNG. Batch converting once beats fighting each recipient - if you keep the originals and send the compatible copies.
Where HEIC still breaks sharing
HEIC (High Efficiency Image Container) is what modern iPhones save by default. It is smaller than JPEG at similar quality, which is great for your library. The friction shows up the moment the file leaves your Apple bubble:
- Email - some corporate Outlook setups and webmail clients refuse HEIC attachments or strip the preview so the recipient sees nothing useful.
- Windows - without the HEIF extensions (or an older OS), Explorer cannot thumbnail or open the file. "HEIC compatibility Windows" is still a real support ticket, not a myth.
- Websites and CMSs - form uploads, WordPress media libraries, and many design tools reject HEIC outright or convert poorly server-side.
- Print and client handoff - labs and freelancers often ask for JPG because their pipelines never added HEIC.
If you already weighed formats in HEIC vs JPG, this is the practical follow-through: when sharing is the goal, convert for the channel - do not assume everyone can open what your Photos app shows fine.
Convert once vs per recipient
Converting one photo every time someone asks wastes time and produces inconsistent quality. A better habit is a short batch before you share:
- Select the set you actually need (vacation album, product shots, school forms) - not the whole library.
- Pick one output for that job: JPG for email and most websites, PNG when you need a lossless still or transparency, PDF when a contact wants a single document (see convert HEIC to PDF on iPhone), WebP when the destination is a modern site that accepts it.
- Save the converted copies to a folder or album you can find again - "Email JPG" or "Web ready" - so the next reply reuses the same files.
One batch for the trip beats twenty one-off exports from Mail. Recipients get files that open; you stop redoing the same taps.
Quality vs file size settings
JPG and WebP let you trade clarity for size. Email attachments and CMS limits care about megabytes; a hero image on your site cares about sharpness. Practical defaults:
- Email and messaging - mid-high quality (around 70-85%) keeps faces and text readable without bouncing size limits.
- Website galleries - similar range, or WebP if the site accepts it, so pages load faster on mobile.
- Print or archival handoff - higher quality or PNG; do not squeeze these to save a few hundred KB.
Zoom a converted sample on-device before you upload a whole set. If skin tones look blotchy or fine text softens, bump quality a notch. If Mail refuses the attachment, drop quality slightly or send fewer photos per message - batch conversion makes that experiment cheap.
Keep originals and send the copies
Never overwrite the HEIC master with a lossy JPG. Keep the original in Photos (or Files), convert to a new file with a clear suffix, and share only the copy. That way you can re-export at a different quality later, strip metadata for a public post in a separate step, or go back to HEIC for Apple-to-Apple AirDrop.
HEIC Snap is built for that workflow: pick up to 100 photos, choose JPG, PNG, WebP, or PDF, set quality when it matters, and convert on-device so nothing uploads to a server. Originals stay untouched; you send the compatible copies to email, Windows PCs, and the web. Batch once, keep the masters, and stop explaining why the attachment will not open.