Archive HEIC to AVIF — the open-codec upgrade for iPhone libraries
Same container, open codec. Swap Apple's HEVC for AV1 — keep the compression, drop the licensing dependency. Every core encodes at once, metadata rides along, the archive never leaves your machine.
A real archival re-encode, running on your machine
This is the slower page on purpose. Your archive is worth the extra minutes — you encode once, read forever. Budget 3–8 seconds per 12 MP photo. Metadata, GPS and color profile all survive.
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.
Same container generation, open codec underneath
HEIC and AVIF share plumbing. The difference is the codec underneath — and which industry group maintains it. For anything you intend to keep, that's the bet that matters.
Your photos shouldn't need Apple to survive the decade
HEIC is what your iPhone hands you. It's patent-pool gated, and nine years after it launched the rest of the world still argues about decoding it. Pick up a Windows laptop in 2036 and ask it to open a 2019 camera roll — the answer depends on whether a codec license is still being honored. An open format doesn't have that conversation. Your memories don't need Apple's permission to load.
Same box, different codec politics
HEIC and AVIF sit in the same container family. The structure is familiar — thumbnails, metadata boxes, tile layout. The difference is what's inside. AVIF uses AV1, the open video codec built by the Alliance for Open Media — Google, Amazon, Netflix, Microsoft, Mozilla and others — precisely to sidestep royalty pools. For an archive you plan to keep for a decade, the codec you pick is a bet on which ecosystem will still be readable.
Comparable compression, fundamentally different reach
File size lands within a few percent of the HEIC original at the same perceptual bar — AV1 closed the gap to HEVC years ago. What's different is reach. AVIF opens natively in every modern browser, every desktop OS, and on Android without a device-specific Gallery app. HEIC still depends on Apple shipping the decoder, or on a Windows user buying a Store extension that was pulled in some regions. An AVIF archive is one you can hand to your future self without a codec asterisk.
Under the hood
The decode uses the same HEVC decoder your Mac does. The encode uses AV1 — the open video codec under AVIF — with libaom-powered tile-parallel encoding across every core you have. An adaptive quality loop targets PSNR ≥ 44.5 dB and SSIM ≥ 0.95 per image. EXIF, GPS and the Display P3 ICC profile are written straight into the AVIF container. No sidecars, no lost capture dates.
HEIC vs AVIF as an archival format
| Criterion | HEIC | WebP |
|---|---|---|
| Container family | HEIF | HEIF — same family |
| Codec underneath | HEVC — patent-pool licensed | AV1 — royalty-free, open |
| Governance | HEVC patent pools | Alliance for Open Media |
| Compression at equal quality | Baseline | Within a few % of HEVC |
| Native browser support | Safari only | Chrome, Firefox, Safari 16.4+, Edge |
| Expected 10-year readability | Depends on Apple | Open spec, multiple decoders |
| Typical encode cost (12 MP) | Encoded on-device | 3–8 s on 8-core, parallel |
How to migrate an iPhone archive to AVIF
A deliberate, once-per-archive job. Set it running and come back.
- 1
Pull the HEIC archive out of iCloud, iPhone or a Time Machine backup
Use iCloud Photos' Download Originals, the macOS Photos library export, or the DCIM folder from an iPhone backup. AVIF is worth the encode cost on originals — don't waste it on the already-compressed Shared Album versions.
- 2
Plan the batch around encode time
Budget 3–8 seconds per 12 MP photo on a modern laptop; a thousand-photo archive is roughly an hour on eight cores. Split very large libraries into chunks of ~500–1000 so your browser's memory stays bounded.
- 3
Let AV1 run on every core
Each image gets decoded, quality-searched, then split into tiles and encoded across your cores at once. Metadata — the full EXIF block, the Display P3 ICC profile — is embedded directly into the AVIF container before emit.
- 4
Archive the ZIP alongside the original HEIC until you trust the migration
When the batch finishes you get a ZIP of .avif files. For a real archival migration, keep the HEIC originals on a separate drive for a release or two before deleting. AVIF is what you're moving to, not a replacement you delete the source behind on faith.
AVIF Results
AVIF matches WebP quality (SSIM Δ < 0.005) while shipping ~45% smaller files on the same Excellent preset.
Typical AVIF savings
Measured on 24 diverse photos at matched perceived quality (SSIM ≥ 0.95)
HEIC to AVIF — archival questions
For long-term storage, is AVIF actually a better bet than keeping HEIC?
For anyone outside the Apple ecosystem, yes. HEIC depends on Apple maintaining — and non-Apple platforms licensing — HEVC. AV1 has an open specification, multiple independent decoders, and hardware decoders already shipping in modern phones, TVs and GPUs. Nine years in, HEIC still requires special handling outside Apple; AV1 already ships as a first-class format in every major browser.
Will my library actually get smaller after the re-encode?
Probably not — expect file sizes within about ±5–10% of the HEIC originals. HEVC and AV1 are the same compression generation, and the quality target here is deliberately transparent, not aggressive. You're migrating for portability and open-format provenance, not for bytes saved. Think of it as swapping the lock, not shrinking the house.
How long will a real migration take?
AVIF encode is 5–20× slower than WebP per image, because AV1 does much more work per block. A 12 MP iPhone photo runs 3–8 seconds on an 8-core laptop with parallel encoding; a 200-photo batch is roughly 5–15 minutes. A full 10,000-photo library is half a day. Plan to kick it off and come back to it.
Does AVIF preserve my Display P3 color profile from the iPhone?
Yes. The ICC profile is embedded directly into the AVIF container, so when a color-managed viewer opens the file it applies the same gamut transform the iPhone expected. EXIF (including GPS and capture timestamp) and XMP ride along the same way. If you strip the ICC manually the colors will look flat in a browser — so don't.
Can my browser really encode AV1?
Yes. The AV1 encoder is libaom compiled to WebAssembly with pthreads, and this page already serves the cross-origin isolation headers that let worker threads spawn. Tile-parallel encoding splits each image across your cores — that's why the wall-clock is actually competitive.
What about the Live Photo motion track?
A Live Photo is a still HEIC plus an MOV sidecar. SciZone re-encodes the still to AVIF and leaves the MOV alone. AVIF supports image sequences in theory, but turning Live Photo motion into an AVIF sequence isn't an archival operation — store the original MOVs separately if the motion matters to you.
Why not just keep the HEIC originals and convert later if I need to?
You absolutely can. The argument for converting now is format risk — HEIC's non-Apple support has only gradually improved over nine years, and a codec you can't open in a decade is a lost archive. AVIF today already has broader browser and OS support than HEIC ever achieved. If your threat model is 'I want these readable on whatever device I'm holding in 2036', encoding now to an open format hedges that risk.
Should I delete the HEIC originals after the conversion?
Not immediately. Keep them on a separate drive for at least one full backup cycle — verify a sample of the AVIF files open cleanly in your target apps, check that the metadata survived, and only then reclaim the space. Lossy re-encoding is a one-way operation; give yourself a rollback window.
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. 🎯