iPhone HEIC to WebP — make your photos upload anywhere
The fix for 'this file type is not supported'. Convert a whole camera roll in seconds so LinkedIn, Slack, Reddit, Discord, Gmail and every Windows preview will finally open it. No codec purchase, no upload, no account.
Drop iPhone HEIC here → get WebP back
No sign-in, no upload, no Apple ecosystem required. Drop a folder of iPhone photos, walk away with a ZIP you can attach anywhere, upload anywhere, share anywhere.
Supported input formats
- ✓ JPG / JPEG — Photos, portraits, web content
- ✓ PNG — Screenshots, icons, transparent images
- ✓ HEIC / HEIF — iPhone photos, Apple formats
- ✓ TIFF — Scans, prints, high-resolution archives
- ✓ GIF — Animations and static GIFs
- ✓ BMP, PSD & more — Anything ImageMagick can decode
How the conversion works
- 1. DropDrag files or a whole folder into the box below. Folder structure is preserved in the output ZIP.
- 2. AnalyzeEach image is analyzed for entropy and content type. The engine picks per-image quality settings targeting PSNR ≥ 44.5 and SSIM ≥ 0.95.
- 3. EncodeConversion runs on all of your CPU cores in parallel via Web Workers. EXIF, ICC color profiles and geolocation are copied onto the WebP or AVIF output.
- 4. DownloadWhen the batch is done, a ZIP containing every converted file downloads automatically. No re-upload, no waiting on a server.
Why HEIC keeps getting rejected — and why WebP fixes it today
This isn't a compression optimization story. It's an 'I need these photos to actually upload, right now' story. Here's what's getting in your way and what the swap actually changes.
Apple's format, on everyone else's terms
AirDrop a handful of .heic files onto a Windows laptop and watch every useful destination push back. LinkedIn's uploader rejects them silently. Reddit turns them into a broken thumbnail. Slack previews fail. Notion and Google Docs refuse to embed them. Discord shows a grey box. You didn't pick this format — your iPhone did — and now every single share takes three extra steps.
Microsoft charges 99 cents for a codec that still won't fix your LinkedIn upload
Windows 11 can open HEIC, but only once you install the paid HEIC Image Extensions from the Microsoft Store — and that listing has been pulled in some regions, leaving users with no native option at all. Even when it works, it only fixes Preview. Your browser upload is still broken. WebP is the format the rest of the internet already speaks — drop your photos in, walk away with a ZIP you can attach anywhere, upload anywhere, share anywhere. Nothing ever leaves your machine.
A camera roll in seconds, not minutes
Two hundred iPhone photos in roughly 30 seconds on an 8-core laptop. That's feed-it-and-switch-tabs territory, not watch-a-progress-bar territory. WebP is the quick format — if you need these photos in an email thread right now, this is the tool. The AVIF page next door is for the archival case, where size matters more than speed.
Your browser decodes HEIC like a Mac does
Under the hood it's the same HEVC decoder your Mac uses, compiled to run inside the tab. EXIF comes across — GPS to ten decimal places, sub-second capture timestamps — so Google Photos still sorts by date, your locations still cluster on the map, your Memories still group the way they did.
What changes when you switch HEIC to WebP
| Criterion | iPhone HEIC today | WebP |
|---|---|---|
| Opens in a Windows browser without plugins | No | Yes, everywhere |
| Uploads to LinkedIn / Reddit / Discord | Rejected or broken preview | Accepted |
| Embeds in Notion, Google Docs, Slack | Fails | Renders inline |
| Viewable on Android without Samsung Gallery | Often not | Always |
| Needs a Store codec install | Yes (paid, region-locked) | No |
| File size vs source | 100% | Roughly comparable (±10%) |
| GPS + capture time kept | Yes | Yes |
From rejected HEIC to accepted WebP in four steps
If you can drag a file onto a web page, you can do this.
- 1
Get the .heic files onto whatever machine you're on
AirDrop to a Mac, plug the iPhone into Windows and copy out of DCIM, or download a ZIP from iCloud.com — doesn't matter which. All you need is a folder of .heic / .heif files sitting somewhere.
- 2
Drop them onto this page
Drag the folder (or individual files) into the converter below. The first visit loads a small one-time engine; after that, every subsequent batch starts instantly — even offline.
- 3
Let the scheduler work the batch
Every core encodes in parallel. A hundred iPhone photos typically finishes while you're still looking at the progress bar, which is a satisfying number of photos per tab.
- 4
Paste into whatever was rejecting HEIC
Download the ZIP of .webp files with EXIF and GPS intact. Drag into Gmail, Slack, LinkedIn, Reddit, Discord, Notion, a WordPress uploader — pick your platform, it will accept them without comment.
WebP Results
See how WebP compresses real photos with our Excellent preset — the default when you click convert.
Typical WebP savings
Measured on 24 diverse photos at matched perceived quality (SSIM ≥ 0.95)
HEIC to WebP — the practical questions
I just need to email iPhone photos to someone on Windows — is this the tool?
Exactly the case it's built for. Drop the .heic attachments in, download the .webp ZIP a few seconds later, attach that instead. The recipient double-clicks and it opens in whatever image viewer their OS ships with — no codec purchases, no 'file type not supported' popup ruining your Tuesday.
Why does Slack / LinkedIn / Reddit reject my iPhone pictures in the first place?
They don't decode HEIC server-side. Apple's format is HEVC-compressed inside a HEIF container, and most upload pipelines don't ship an HEVC decoder because the codec carries patent royalties. WebP has no such licensing drama, so those same services accept it without complaint.
How fast is a real iPhone camera roll?
Around 30 seconds for 200 photos on an 8-core laptop, give or take depending on resolution and whether you have ProRAW mixed in. WebP is the quick format; the same batch as AVIF would take five to fifteen minutes, because AV1 encoding is much more expensive.
What happens to my Live Photos?
A Live Photo is two files: a still HEIC and an MOV video sidecar. SciZone converts the still (the frame you actually see and share) and leaves the MOV alone. If you need the motion clip too, pull it from the same iPhone export folder — same filename with a .MOV extension.
Does this work offline after I load the page once?
Yes. The image engine — under 5 MB, downloaded once — gets cached by the service worker on first load. After that you can disable your network and keep converting batches. The work happens inside the browser tab, not on a server.
Will GPS coordinates still be in the WebP files?
Yes, unless you specifically strip them. The full EXIF block rides along — capture time, GPS, camera make and model, lens, orientation. Google Photos will still sort by date and cluster pins on a map. If you're about to publish the photos publicly, strip the metadata with a separate privacy tool afterwards.
Can my whole iPhone library go through this in one sitting?
Technically yes. For very large libraries (thousands of files) it's easier to process in chunks of around 1,500 — not because the tool can't, but because chunking gives the tab room to breathe. Workers recycle every 32 jobs to keep memory bounded; the scheduler meters dispatch against available RAM.
Why WebP and not JPG?
JPG works too, but you'd throw away 25–35% of the iPhone's size advantage for no real compatibility gain — anywhere that accepts JPG now also accepts WebP. WebP is the one-to-one swap: same universal reach, file sizes comparable to the HEIC you started with.
Why Choose SciZone?
We're not just another optimizer. We engineered a fundamentally better solution.
| Feature | SciZone (You're here) | Other Optimizers |
|---|---|---|
| CPU Utilization
How processing power is used
| True Multi-Threading Intelligently uses all CPU cores without overloading your system | Single-Threaded Uses only one CPU core, wastes available power |
| AVIF Encode Speed
How fast AVIF actually runs in the browser
| Tile-Parallel Encoding Each AVIF image is split into tiles encoded across every core — ~6× faster than single-tile libaom on large photos | Single-Tile Default libaom's internal threading caps around 4 threads per encode, regardless of how many cores you have |
| Quality Settings
How compression is optimized
| Unique Per Image Algorithm analyzes each photo and picks optimal settings | One-Size-Fits-All Same settings for every photo, inconsistent quality |
|
Metadata & Color Profiles
Preservation of image data
| Fully Preserved EXIF, color profiles, geolocation. Everything stays intact | Often Stripped Color profiles lost, metadata incomplete |
|
Quality-Size Balance
Optimization results | Perfect Balance Maximum compression with imperceptible quality loss | Inconsistent Either too large or noticeable quality loss |
The Bottom Line
Every photo is unique. Our intelligent algorithm understands this and analyzes each image individually to find the perfect balance between file size and quality. We utilize your computer's full power without overloading it, preserving every detail of your metadata and color profiles. Your files are smaller, faster, and absolutely perfect. 🎯