DEV Community: swapfileio

Is AVIF Ready for Production in 2026? Browser Support and Real Trade-offs

swapfileio — Tue, 16 Jun 2026 09:32:27 +0000

Every six months or so, someone on the team brings up the same question: is AVIF finally ready to use everywhere? And every time we go through the same audit — which browsers, which versions, what breaks for users on older OS. The answer keeps creeping toward "yes," but it's not all the way there yet.

This is what we found when we looked again in June 2026, with actual numbers and the gotchas you won't see on most "AVIF is the future" blog posts.

TL;DR — Support by Browser, June 2026

Browser	AVIF support since	Current adoption
Chrome / Edge / Brave	Chrome 85 (Aug 2020)	~99%
Firefox	Firefox 93 (Oct 2021)	~97%
Safari (macOS)	Safari 16.4 (Mar 2023)	~94%
Safari (iOS)	iOS 16.4 (Mar 2023)	~91%
Samsung Internet	v16 (Dec 2022)	~96%
Android Chrome	Chrome 85+ (2020)	~98%

Aggregate global support sits around 95–96% per caniuse as of this writing. That's better than WebP was in 2021 when people called WebP "ready." The remaining 4–5% is mostly older iPhones still on iOS 15 or earlier (no software update path on the iPhone 6s and similar), plus the long tail of corporate Windows 8 machines on EOL Edge versions.

So Is It Ready?

Short answer: yes for almost every product, with a one-line fallback you write once and forget. The cases where AVIF is not ready are narrower than you'd think — but they exist and they're worth knowing about.

We'll spend the rest of this post on the actual trade-offs, not the marketing version. If you just want the takeaway: ship AVIF with a JPG fallback via <picture>, skip the WebP middle layer, and move on with your life. Read on if you want the why.

The Safari Delay Nobody Talks About

Chrome shipped AVIF in August 2020. Safari shipped it in March 2023. That's two years and seven months. For most of that period, web developers building for the iOS-heavy markets (US consumer, design, ecommerce) had to keep WebP as the "modern" fallback layer because Safari users couldn't decode AVIF at all.

That delay shaped how a lot of older articles still treat AVIF. They'll tell you to ship a three-layer fallback: AVIF → WebP → JPG. In 2026 that's overkill. Safari users have had AVIF for over three years. The iOS 15 holdout group is small enough that JPG fallback covers them just fine.

When AVIF Actually Saves You Money

The pitch you've heard: AVIF is 50% smaller than JPG. The pitch is mostly true, but it depends a lot on what you're encoding.

Photographic content (large hero images, gallery thumbnails): 40–55% smaller than JPG at equivalent visual quality. This is the AVIF sweet spot.
Mixed content (screenshots with text): 20–35% smaller. The savings drop because sharp edges and text don't benefit as much from AV1's compression model.
Icons and logos: Don't use AVIF. Use SVG. If you can't use SVG, PNG with proper compression beats AVIF at small sizes (< 50KB).
Animated images: AVIF supports it, but the tooling is rough. WebP animation has better encoder support and broader browser compatibility for animation specifically.

If your site is mostly photography, switching to AVIF will likely cut your image bandwidth by a third or more. Netflix reported about a 30% reduction on their hero images when they migrated in 2022. That number lines up with what we've seen on photography-heavy sites in our own measurements.

Implementation: Two Realistic Options

You've got two paths depending on how much control you have over your build pipeline.

Option A: Plain `<picture>` Element

The boring, reliable way. Works everywhere, no build step assumptions, no CDN magic required:

<picture>
  <source srcset="hero.avif" type="image/avif">
  <img src="hero.jpg" alt="Mountain landscape" width="1200" height="800">
</picture>

If the browser doesn't support AVIF, it falls back to the JPG. No WebP middle layer because at this point WebP doesn't buy you anything that JPG fallback doesn't also cover — and you save yourself an extra encode + storage cost.

Option B: Server-Side Content Negotiation

If you control the server (or use a CDN like Cloudflare, Vercel, or Bunny), you can serve the right format based on the Accept header:

Accept: image/avif,image/webp,image/png,image/jpeg,*/*

The browser tells you what it can decode. You serve AVIF if it's in the list, JPG otherwise. Cloudflare's Polish feature does this automatically, as does Vercel's image optimization. If you're using one of these, you've already shipped AVIF — you just might not have noticed.

Where AVIF Falls Short

The honest list:

Encoding is slow. AV1's encoder is computationally expensive. Encoding a 4MB JPG to AVIF on a typical build server takes 3–8 seconds versus <1 second for WebP. For build-time conversion of large catalogs (e-commerce with 100K product images), this matters. We've seen build times triple after AVIF migration on sites that didn't switch to a parallel encoder like libavif.
Decoding takes more CPU. On older mobile devices (anything below iPhone X or equivalent Android), decoding 4K AVIF images is noticeably slower than JPG. You won't notice on a hero image. You'll notice on a 50-image gallery scroll.
Tooling gaps. Photoshop added AVIF export as a plugin in 2023. GIMP shipped it natively in 2024. But a lot of agency workflows still hand off JPG/PNG files. If your team isn't comfortable saying "we'll convert at build time," AVIF can feel like a step backward in the design handoff.
Limited animation ecosystem. AVIF can do animation, but no major editor exports animated AVIF cleanly. If you're serving animated content (icons, micro-interactions, social previews), stick with WebP for animation and use AVIF only for static images.

Three Sites Doing This Right

If you want to see what production AVIF actually looks like:

Netflix. Hero images on the homepage have been AVIF since 2022. They use server-side negotiation and fall back to JPG. Open DevTools, look at the Content-Type header on the hero image — it'll say image/avif if you're on a recent browser.
YouTube thumbnails. Migrated to AVIF for most thumbnail sizes in 2023. The savings on YouTube's scale are absurd — they don't publish numbers, but at the bandwidth they push, even single-digit percentage improvements translate to petabytes.
GitHub avatars. Since 2024, GitHub serves AVIF for avatar images via their CDN. You can verify by inspecting any user avatar URL — the response will be AVIF on supported browsers.

If three of the most cautious, scale-sensitive engineering organizations on the web have shipped AVIF in production, "is it ready" is mostly answered.

Migration Path: WebP to AVIF

If you're already running WebP and wondering whether to add AVIF:

Don't rip out WebP. If you have a working WebP pipeline, just add an AVIF source above it: <source type="image/avif"> first, then the WebP source, then the JPG fallback. Three-layer is fine if you've already built it.
If you're starting fresh: skip WebP, use AVIF + JPG. Less storage, less build cost, same end-user experience.
For dynamic content (user uploads): generate AVIF asynchronously after upload. Don't make users wait for the encode. Serve JPG on upload, swap in AVIF once it's done. We do exactly this in our backend pipeline.

For existing JPG-heavy archives you want to bulk-convert, our JPG to AVIF tool handles single files in browser-friendly chunks. For batch automation, sharp (Node.js) or libvips (Python) are the standard libraries.

FAQ

Should I use AVIF or stick with WebP for now?

If you're starting from scratch or doing a fresh image pipeline build in 2026, skip WebP entirely. Use AVIF with a JPG fallback. The browser coverage gap that justified WebP as a middle layer in 2022–2023 is gone. If you already have a WebP pipeline that works, no rush to migrate — but new sites shouldn't add WebP today.

Does AVIF work on iPhone Safari?

Yes, since iOS 16.4 (March 2023). About 91% of active iPhone users in 2026 have iOS 16.4 or higher. The remaining 9% are mostly iPhone 6s/SE first-gen owners on iOS 15, who'll fall through to the JPG fallback automatically.

How much smaller is AVIF vs JPG actually?

For photographic content at high quality (Q90 equivalent), expect 40–55% smaller files. For mixed content (UI screenshots, text-heavy images), 20–35%. For icons and small graphics, AVIF often loses to PNG — don't use it there. The bandwidth savings on a content-heavy site are real and material.

Will AVIF break older browsers?

Not if you use <picture> with a <source type="image/avif"> declaration. The browser checks the type and either uses the AVIF source or falls through to the <img> fallback. No JavaScript needed, no feature detection, no client-side parsing of headers. This is one of the cleanest fallback systems on the web platform.

Is AVIF SEO-friendly? Does Google index AVIF images?

Yes. Googlebot has supported AVIF since 2022. Image search results include AVIF images. The performance benefit (smaller files = faster LCP) also helps Core Web Vitals, which feeds into rankings. There's no SEO reason to avoid AVIF in 2026.

The 2026 Recommendation

For a typical content site, e-commerce, or SaaS marketing site building today:

Ship AVIF for all photographic content.
JPG fallback via <picture> — skip WebP unless you already have it.
SVG for icons and logos, not AVIF.
Animated content stays on WebP until the AVIF animation ecosystem matures.
Use a CDN with auto-AVIF (Cloudflare Polish, Vercel image, Bunny optimizer) if you don't want to manage encoding yourself.

If your honest answer to "is AVIF ready" is still "I'm not sure," ship it on one section of your site (the homepage hero, the blog cover images, the product grid) and measure for a week. Check Web Vitals before/after. The bandwidth and LCP improvements are usually obvious enough to settle the question.

To convert existing JPG files for testing: SwapFile.io JPG to AVIF — no signup, files auto-delete in 1 hour.

Originally published on SwapFile.io. Part 6 of the "Image Format Issues" series.

How to Download iCloud Photos to Windows — Solving the HEIC Trap (2026)

swapfileio — Thu, 11 Jun 2026 08:36:14 +0000

If you've ever tried to grab your iPhone photos from iCloud onto a Windows PC, you probably hit the same wall many people do: the photos download, but they're in .heic format — and Windows doesn't open them by default. Sometimes the iCloud web interface gives you blurry previews instead of originals. Sometimes the iCloud Windows app downloads gigabytes of files you didn't ask for.

This guide walks through four reliable ways to download iCloud photos to Windows in 2026, with honest tradeoffs for each: speed, file format, HEIC handling, and whether you need to install anything. By the end you'll know which method fits your situation — one-time export, ongoing sync, or specific photo retrieval.

Before You Start: iCloud Photos vs iCloud Drive

The single biggest source of confusion: iCloud Photos and iCloud Drive are different products.

iCloud Photos stores your iPhone camera library. Each photo gets a synced "original" plus optional optimized previews on each device.
iCloud Drive stores files (documents, screenshots you saved manually, third-party app data). It does not mirror your camera roll.

This guide covers iCloud Photos specifically. If you saved photos to iCloud Drive manually (e.g. "Save to Files" from iPhone), the methods below still work — but the location is iCloud Drive\Photos rather than the dedicated Photos library.

The Four Methods at a Glance

Method	HEIC handling	Best for	Install required
iCloud for Windows app	Auto-convert to JPG (toggle)	Ongoing sync	Yes (free)
iCloud.com web	Downloads as HEIC	One-off retrieval	No
iPhone → Mac → SMB	Configurable	If you also own a Mac	No (uses existing)
Web download + SwapFile.io	Post-download conversion	Mixed approach	No

We'll walk through each, with real-world friction points the help docs leave out.

Method 1: iCloud for Windows App (Recommended for Most People)

This is Apple's official Windows client. It's free, lives in the Microsoft Store, and integrates iCloud Photos into a regular Windows folder. Critically, it can auto-convert HEIC to JPG during download — so you never deal with the format issue at all.

Setup steps

Open Microsoft Store and search "iCloud" (publisher: Apple Inc.). Install it.
Launch iCloud for Windows. Sign in with your Apple ID. If you have two-factor authentication enabled (you should), approve from your iPhone.
In the iCloud window, check Photos. Click "Options…" next to it.
Three settings matter here:
- iCloud Photos — toggles whether the library syncs at all.
- Download new photos to my PC — required for download to happen.
- "Keep high efficiency original if available" → unchecked = converts HEIC to JPG automatically as files arrive on your PC.
Apply. The app will start syncing to C:\Users\YourName\Pictures\iCloud Photos\.

Reality check

Speed depends on your library size. A 50,000-photo library can take 2-5 days for initial sync on a typical home connection. The app downloads in batches and recovers gracefully from interruption. We've seen Reddit threads complaining about "iCloud for Windows stuck" — usually the fix is restarting the iCloud service from Windows Services panel (search "services.msc"), not reinstalling the app.

If you want only the most recent photos, there's no built-in selective sync. You either sync everything or use the web method below.

Method 2: iCloud.com Web Download (No Install)

For a quick retrieval of specific photos without installing anything, the web interface works — with one major caveat.

Steps

Open icloud.com in any browser. Sign in.
Click Photos.
Select the photos you want (Ctrl+click for multiple). Click the download icon (cloud with down arrow) in the top toolbar.
Multiple selections download as a ZIP.

The HEIC catch

iCloud.com always downloads photos in their original format. If your iPhone shoots HEIC (the default since iOS 11), that's what lands on your Windows desktop — and Windows won't open them without a codec or third-party tool.

Three options here:

Use SwapFile.io's free HEIC to JPG converter to batch-convert the downloads. No signup needed for files under 5 MB.
Install the official "HEIF Image Extensions" + "HEVC Video Extensions" from Microsoft Store ($0.99) so Windows can open HEIC natively.
Disable HEIC at the source by switching iPhone to JPG mode. We covered this in Part 4 of this series: How to Turn Off HEIC on iPhone — note that it only affects future photos, not existing ones in iCloud.

For detailed HEIC-handling on Windows specifically, see Part 3: Why Windows Still Can't Open HEIC Files in 2026.

Method 3: iPhone → Mac → SMB Share (For Mac Users)

If you also have a Mac in the house, this is the cleanest pipeline.

On Mac, open Photos.app. It already has access to your iCloud Photos library.
Select the photos you want exported. File → Export → Export X Photos.
In the export dialog, set Photo Kind: JPEG. This bypasses HEIC entirely — Mac converts on the fly during export.
Save to a folder.
From the same Mac, share that folder via SMB (System Settings → General → Sharing → File Sharing).
On Windows, in File Explorer address bar, type \\YourMacName.local and authenticate.
Drag the photos to Windows.

This route gives you 100% control over format, naming, and metadata stripping. It's the most work but produces the best results for archival use.

Method 4: Web Download + SwapFile.io Conversion

The "no install, full automation" hybrid:

Use Method 2 to download photos from iCloud.com (HEIC ZIPs arrive).
Extract the ZIP.
Drop the HEIC files onto SwapFile.io HEIC to JPG — the tool processes them server-side and returns JPGs.
Files auto-delete from our servers within 1 hour, no signup, no tracking pixels.

This is the fastest end-to-end path when you don't want to install Apple's Windows client and don't have a Mac. We built SwapFile.io specifically because this exact flow used to suck — every alternative either had ads, watermarks, signup walls, or kept user files on their servers indefinitely.

Hybrid Recommendation

If you're going to deal with iCloud-Windows photo traffic regularly, here's the setup that works best:

Install iCloud for Windows with auto-convert-to-JPG enabled — solves 95% of cases automatically.
Switch your iPhone to "Most Compatible" mode (guide) so future photos are JPG to begin with — reduces dependence on conversion.
Bookmark SwapFile.io HEIC to JPG for the occasional one-off file from a friend's iPhone, a backup, or a non-iCloud source.

This setup means you should never see "Windows can't open this file" again, regardless of where the photo came from.

iCloud Family Sharing Caveat

If you're part of a Family Sharing plan with shared photo library, iCloud for Windows only syncs your personal library by default — not the shared one. To access the shared library, the workaround is to open iCloud.com, switch to the shared library view, and use Method 2 from there.

Family Sharing photo download via Apple's Windows client is on Apple's backlog, expected in 2027 according to recent developer notes.

Frequently Asked Questions

Can I download only certain albums instead of everything?

With Method 2 (iCloud.com), yes — albums are listed in the sidebar. With Method 1 (Windows app), there's no native selective sync, but you can use third-party tools like FreeFileSync to mirror only specific subfolders after the initial sync. For one-off cases, Method 2 is simpler.

What if iCloud for Windows is downloading thousands of files I don't need?

This happens when you check Photos without configuring the options first. To stop: open iCloud for Windows → uncheck Photos → Apply. The local files stay; they just stop syncing new arrivals. To delete the local cache, navigate to the iCloud Photos folder and delete it manually after pausing sync.

The iCloud Windows app is unbearably slow. Alternative?

Two real alternatives. (1) Use iMazing or AnyTrans (paid third-party tools) — they pull photos directly from iPhone over USB without involving iCloud at all. Often faster for one-time retrieval. (2) If photos are already in your iCloud library, the iCloud.com web download (Method 2) bypasses the Windows app entirely.

Do I have to convert all my photos to JPG at once?

Not at all. Many users keep HEIC as the source-of-truth (smaller files, better quality) and only convert when they need to share or use a photo on Windows. Setting iCloud for Windows to "auto-convert to JPG" works as on-the-fly conversion — the originals stay HEIC in iCloud, only the Windows local copy is JPG.

Is there a browser extension that auto-converts HEIC when downloading from iCloud.com?

Not as of 2026. Browser extensions don't get filesystem access to convert ZIPs. The closest workaround is using a service worker that intercepts ZIP downloads, but no public extension does this reliably. The cleanest path remains downloading the HEIC ZIP, then dropping it into a converter like SwapFile.io.

Conclusion

Getting iCloud photos onto Windows is no longer a headache once you pick the right method:

Most people: iCloud for Windows app with auto-convert enabled.
One-off retrievals: iCloud.com web + SwapFile.io for conversion.
You also own a Mac: Photos.app export → SMB share is gold standard.
Future-proof: Set iPhone to "Most Compatible" so future photos don't need conversion at all.

For converting existing HEIC files you've already downloaded: SwapFile.io HEIC to JPG — no signup, 1-hour auto-delete, no tracking.

Originally published on SwapFile.io. SwapFile.io is a privacy-first image and PDF converter — files auto-delete in 1 hour, no Google Analytics, free for the first 6 months.

How to Turn Off HEIC on iPhone — Switch to JPG (2026 Guide)

swapfileio — Mon, 08 Jun 2026 18:55:59 +0000

A familiar scenario: you take a batch of photos on your iPhone, send them to someone over WhatsApp or email. "Can't open this" comes back. Or you transfer to a Windows machine and no app recognizes them. Or you download a photo from a cloud backup and see .heic staring at you.

iPhone's default photo format has been HEIC since 2017 (iOS 11). Outside Apple's ecosystem, this format is still a friction point. The fix is actually simple: tell your iPhone to always shoot JPG. This guide walks through whether it's worth switching, the 30-second steps, and the gotchas that follow.

Why HEIC Default? Quick Recap

Apple made HEIC the new default with iOS 11 in 2017. The reason in one word: storage. At equivalent visual quality, HEIC produces files 50% smaller than JPG. iPhones now carry 12-48 megapixel cameras; JPG photos are 3-5 MB each, HEIC photos 1.5-2.5 MB. For someone shooting thousands of photos a year, that's hundreds of GB difference.

Apple's own ecosystem handles HEIC fine: iPhone to iPad to Mac to iCloud — everything opens HEIC natively. Problems start when content leaves Apple's walled garden.

For the technical background on HEIC, Windows compatibility, and convert-side solutions, see Part 3 of this series: Why Windows Still Can't Open HEIC Files in 2026.

Should You Turn It Off? — Honest Decision Table

Turning off HEIC isn't a no-brainer. There's a trade-off, and it depends on how you actually use your phone.

Turn it off if:

Many Windows users in your circle — getting "can't open this" messages regularly
You share photos frequently (WhatsApp, Telegram, email, social media)
You back up to non-Apple cloud (Google Drive, Dropbox, OneDrive)
iCloud quota isn't a concern (~50% larger files = need headroom)
You move photos via USB or external drives often

Keep it on if:

You use 4K Live Photo or Cinematic mode — some features depend on HEIC
iCloud Photos with storage optimization matters — files take 2x space
You only use Apple devices — HEIC works everywhere in that world
Pro photography — HEIC has 10-bit color depth, JPG is 8-bit

If you're stuck between "lots of Windows friends but I also use Cinematic mode," there's a middle path — covered below.

30 Seconds to Turn It Off — Step by Step

Same 3 steps on every iOS version.

Step 1: Open Settings

From the home screen → Settings (the gray gear icon) → scroll down → tap Camera.

Step 2: Go to Formats

Formats is the first option in Camera settings.

Step 3: Select "Most Compatible"

Two options:

High Efficiency — HEIC, the default
Most Compatible — JPG, the legacy format

Pick "Most Compatible".

Done. Every photo from now on saves as JPG. No restart, no confirmation needed.

iOS 18 Surprise: AV1 Codec

iOS 18 introduced a quiet but important change: under "High Efficiency," Apple is now experimenting with the AV1 codec. AV1 — the same codec behind AVIF — is royalty-free and dominant in modern web standards.

Practical implications:

iPhone 15 Pro and newer models with "High Efficiency" enabled now internally use AV1 in some scenarios
Better support outside Apple's ecosystem (web browsers added AV1 support)
But files still come out as .heic — Windows still needs the codec to open them

So even on iOS 18, "Most Compatible" remains the definitive fix. The AV1 transition is a 2-3 year process.

What Happens to Existing HEIC Photos?

Important: This setting only affects new photos. Every HEIC photo already taken stays HEIC.

Three scenarios:

1. Sharing one-off

When you send an HEIC photo from your iPhone via Mail or Messages, iOS automatically converts it to JPG. So those channels aren't an issue. WhatsApp does the same client-side.

Where it breaks: drag-and-drop to a computer, AirDrop to non-Apple devices, cloud backups downloaded from a Windows machine.

2. Batch conversion

To turn old HEIC files into JPG, the fastest path is SwapFile.io HEIC to JPG — files auto-delete in 1 hour, no signup for files under 5 MB.

Offline alternative: if you have a Mac, use Preview → File → Export As → JPEG.

3. iCloud Photos

This is the tricky case. HEIC photos in iCloud behave differently based on Settings → Photos options:

"Optimize iPhone Storage" enabled: local device has a compressed version, iCloud has the HEIC original
"Download Originals" enabled: local device has the HEIC original

If you download a photo from iCloud.com via a Windows browser, it always comes down as HEIC (Apple's iCloud web UI offers no JPG conversion option). The workaround: convert online before downloading, or use the Apple Photos app on a Mac for batch conversion.

Hybrid Approach — "I Want HEIC But Sometimes JPG"

If you depend on HEIC-tied features (4K Live Photo, Cinematic mode) but also need JPG sometimes:

Keep HEIC as default but manually convert important shares
Use the Shortcuts app to build an "HEIC → JPG" automation — one tap from Photos converts on the fly
If your backup destination is non-Apple (Google, Dropbox), set up a Mac Folder Action that converts HEIC → JPG as files land

HEIC vs JPG — Quick Comparison

Feature	HEIC	JPG
File size	~1.5-2.5 MB	~3-5 MB
Color depth	10-bit (1 billion colors)	8-bit (16 million colors)
Native on Windows?	No ($0.99 codec needed)	Yes
Native on Android?	Galaxy S9+ and later	All Androids
WhatsApp sharing	Auto-converted to JPG	Sent as JPG
Email attachment	iOS auto-converts to JPG	Sent as JPG
iCloud Photos storage	Less space	~50% more space
Live Photo support	Full	Limited
Cinematic mode	Works	Doesn't work

Frequently Asked Questions

Do I need to turn it off if I only share via WhatsApp?

No. WhatsApp converts HEIC to JPG client-side. The only edge case is sending a file from WhatsApp Web/Desktop, and even there iOS's Photos sharing flow auto-converts. WhatsApp alone isn't a reason to switch.

Will Live Photos still work?

Yes — Live Photo capture works in "Most Compatible" mode too. The difference: the Live Photo video gets saved as a separate JPG + H.264 video file instead of an HEIC container. AirDrop and iCloud share Live Photos normally. Third-party apps like WhatsApp don't support Live Photo regardless of format.

Will my iPhone storage fill up faster?

Yes. JPG files are 50-100% larger than HEIC. If your iPhone is 64 GB and nearly full, or your iCloud quota is 50 GB, you'll feel the difference. On a 128 GB+ device or 200 GB+ iCloud plan, the difference is usually negligible.

Does it affect AirDrop?

iPhone to iPhone AirDrop: HEIC preserved. iPhone to Mac AirDrop: HEIC preserved (Mac handles natively). No iPhone-to-Android AirDrop in the first place. So AirDrop alone isn't a reason either way.

What if I want to switch back to HEIC?

Same path: Settings → Camera → Formats → "High Efficiency." Instant change. Old "Most Compatible" photos stay JPG; new ones go back to HEIC.

Conclusion

Turning off HEIC on iPhone is a 30-second, one-tap decision. Trade-off: ~50% larger files. Upside: end the "can't open this" loop with Windows friends, smooth USB transfers to any computer, painless backups to any cloud.

If you're undecided: try it for 1-2 weeks. iOS lets you flip the setting back anytime — no commitment.

To convert existing HEIC files to JPG: SwapFile.io HEIC to JPG is ready — no signup, files auto-delete in 1 hour.

Originally published on SwapFile.io. SwapFile.io is a privacy-first image and PDF converter — files auto-delete in 1 hour, no Google Analytics, free for the first 6 months.

Why Windows Still Can't Open HEIC Files in 2026 (And What Actually Works)

swapfileio — Thu, 04 Jun 2026 14:31:26 +0000

The scenario is familiar: someone takes a photo on an iPhone, sends it to you over email or WhatsApp. You try to open it on Windows — a warning appears: "Codec required to open this HEIC file." You click it, Microsoft Store opens to "HEVC Video Extensions," and the price says $0.99. They're asking you to pay just to view an image.

It's 2026. HEIC is 9 years old (Apple introduced it in iOS 11 in 2017), and this problem is still here. It's not a coincidence — it's a structural choice. This article explains why it's still happening and walks through 5 solutions that actually work in 2026.

What's the actual problem?

A "HEIC file" is really two technologies stacked together:

HEIF — High Efficiency Image File Format (container standard, developed by MPEG)
HEVC — High Efficiency Video Coding, aka H.265 (the compression codec, also MPEG)

Apple bundled these together and called it "HEIC." The HEIF container is a royalty-free open standard, but the HEVC codec is patent-encumbered — any company that wants to use it has to pay royalties to MPEG LA. iPhone manufacturer (Apple) already pays. Windows manufacturer (Microsoft) wants the user to cover the cost.

That's where the 99 cents come from.

Microsoft's awkward setup

Microsoft Store has two separate extensions, and the split is deliberately confusing:

HEIF Image Extensions — Free. Container support. But on its own, it can't display HEIC files because it has no HEVC decoder.
HEVC Video Extensions — $0.99. The decoder you actually need. The name is misleading; it's required for HEIC photos too.

There's also a third version, "HEVC Video Extensions (Device Manufacturer)," which is free but only ships pre-installed by OEMs (Dell, HP, Lenovo, etc.). If you bought a new Dell with Windows 11 pre-installed, you probably already have it. If you have an older machine or a custom build, you don't. The same file opens for free on an OEM machine and costs $0.99 on your personal box.

This is a freely-made choice. Microsoft has historically been reluctant to support Apple's image formats. We waited until 2024 for native AVIF in Windows. WebP support came through Chromium, not Microsoft. HEIC is the latest chapter.

Who's to blame?

Short answer: all three parties get a share.

Apple never made HEIC a real standard. When they announced it in iOS 11, they called it "the new default for the camera," but didn't invest in interoperability. iCloud Photos automatically converts HEIC to JPG when displaying on non-Apple platforms — Apple themselves know HEIC is broken outside their ecosystem, they just choose not to engage with the problem.

Microsoft owns one of the world's most popular desktop OSes and asks users to pay to open an image format. By 2026 UX standards, this is absurd. Even Linux distributions ship the same codec for free (the libheif package).

MPEG LA and the patent-pool structure underpin this whole mess. The royalty model is the polar opposite of where the open web is going — WebP and AVIF are BSD/MIT-licensed, royalty-free. They're winning for that reason.

HEIC's share will gradually erode to AVIF (royalty-free + smaller). Apple has been testing AV1 codec under the "HEIC or High Efficiency" setting since iOS 18. The problem will solve itself — but not for today's user.

5 solutions that actually work in 2026

1. Buy Microsoft HEVC Extension ($0.99) — the official path

Official, permanent, system-wide. Get "HEVC Video Extensions" from Microsoft Store, install it, done. HEIC files open natively in Windows Photos. Pay once, works forever.

When not to: You've seen 2 HEIC files in your life and want a free alternative — paying isn't worth it.

2. Convert online — free, fast, private

Got one HEIC to open? Don't bother installing anything. Convert online, download JPG, move on.

The big online converters (Smallpdf, iLovePDF, ezgif) ship with Google Analytics, Facebook Pixel, and Hotjar trackers. If your HEIC happens to be a private moment (family photo, signed document), privacy starts to matter. The honest pitch for our own tool, SwapFile.io HEIC to JPG, is the inverse of that: files auto-deleted within 1 hour, Plausible analytics only (cookieless, 1 KB), no Google Analytics, no Facebook Pixel, no signup for files under 5 MB.

When not to: Batch converting 50+ files — offline solution is faster.

3. CopyTrans HEIC for Windows — free for individuals

CopyTrans HEIC is free for personal use and installs directly (not through Microsoft Store). It enables system-wide HEIC support — thumbnails show up in File Explorer, Photos opens HEIC natively, you can drag-and-drop into Office documents.

When not to: Business use requires a license. Still, for one-off personal use, it's the lowest-friction offline option.

4. Change format on iPhone itself — the preventive fix

The most sustainable solution: fix the source. On iPhone, go to Settings → Camera → Formats → "Most Compatible". From then on, all photos are saved as JPG.

Trade-off: files are roughly 2x larger. Your iCloud quota and phone storage fill up faster. But if you're tired of dealing with HEIC problems, it's a worthwhile trade.

When not to: Using 4K Live Photos or Cinematic mode — some features depend on HEIC.

5. Open on macOS, export to JPG — if you have a Mac

macOS has had native HEIC support since High Sierra (10.13). If you have a Mac: open the file → Preview → File → Export As → JPEG → save. Fast for one-offs, slow for batches.

When not to: No Mac, no solution.

Which scenario, which solution?

A practical decision table:

Situation	Best Solution
we open 100+ HEIC files a year	#1 — Microsoft HEVC Extension ($0.99, one-time)
Family photo arrived, just want to open + move on	#2 — Convert online, download, forget
System-wide free solution	#3 — CopyTrans HEIC (personal use)
Want to fix the source	#4 — Switch iPhone to JPG
Have a Mac, quick one-off	#5 — macOS Preview + Export
Work computer, sensitive file	#2 (privacy-first) or #1 (official codec)

Frequently asked questions

Can we preview HEIC files in Outlook?
On Windows with the HEVC Video Extension installed, the Outlook Preview pane shows HEIC automatically. Web Outlook (in a browser) can't — you'll still need to convert to JPG or download and open on your desktop.

Why does WhatsApp auto-convert HEIC to JPG?
WhatsApp converts client-side because most of their recipients are on different platforms — Android, Windows web — and none of them have universal HEIC support. It's a real-world snapshot of how Apple's "HEIC works everywhere" claim plays out.

Does it make sense to convert HEIC to AVIF instead of JPG?
AVIF is royalty-free, about 20% smaller than HEIC, and supported in 94% of modern browsers. If you're putting the file on the web, AVIF makes sense. If you're archiving, JPG is safer for universal compatibility.

Will HEIC eventually go away?
Probably yes, but slowly. Apple has been testing AV1 codec since iOS 18. AVIF (royalty-free + more efficient) is on the rise. HEIC's peak was 2018-2024. By around 2030, most new content will likely be in AVIF — but solutions for years of accumulated HEIC files will still be needed.

Conclusion

The HEIC problem isn't technical; it's ecosystem politics. Three large companies (Apple, Microsoft, MPEG LA) have been arguing about "who licenses which codec" for years. In the meantime, millions of users have to browse the web to open a small file.

The solution is actually simple: pick one of the 5 paths above. Whatever your scenario, in 2026 HEIC should no longer be a barrier that stops you.

This article was originally published on SwapFile.io. SwapFile.io is a privacy-first image and PDF converter — files auto-delete in 1 hour, no Google Analytics, free for the first 6 months. Try it: swapfile.io/tools/heic-to-jpg. Feedback welcome.

How We Built a Privacy-First PDF Merger in 7 Hours: The Stack and the Lessons

swapfileio — Sun, 24 May 2026 22:59:06 +0000

TL;DR

Day 8 of building SwapFile.io (privacy-first image/PDF converter) in public. Yesterday we shipped a feature we needed ourselves: PDF Merge. Total time: ~7 hours from "do we have this?" to production. Stack: Go + Fiber + PostgreSQL + Next.js 16. The interesting bits are about what we didn't have to write.

Live: swapfile.io/en/tools/pdf-merge

The problem

Most online PDF mergers do something we didn't realize until we tested four of them: they rasterize your PDFs.

You upload a contract with selectable text, signed and form-filled. You merge it with an addendum. You download the result. The output is... a stack of images. Text is no longer searchable. Form fields are flat pixels. Bookmarks gone. File size often triples.

Smallpdf does this. iLovePDF does this. PDF24 does this in their default flow. The reason is the same for all three — they use server-side rendering tools that go through a raster pipeline because it's simpler and gives them more control over the output.

we wanted the opposite: take what we uploaded, glue them together at the structural level, give us back exactly what went in. Searchable text. Embedded fonts. Bookmarks. Form fields. All intact.

The unsexy answer: pdfunite

Poppler-utils ships with a binary called pdfunite. It's been around for over a decade. It does exactly one thing:

pdfunite in1.pdf in2.pdf in3.pdf out.pdf

It doesn't rasterize. It doesn't recompress. It opens each input as a PDF object graph, appends pages in order, fixes up the cross-reference table, writes the result. Output is byte-for-byte equivalent to the inputs for text/fonts/images.

Smallpdf could have used this. So could iLovePDF. They chose not to because their pipeline is built around server-rendered images for the preview/print path, and merging via pdfunite means having a second code path. For a solo founder, having one less code path is a feature, not a downside.

The Go wrapper

Bridging Go to pdfunite is 50 lines of stdlib subprocess code. Here's the core:

type PDFUnite struct {
    binary  string
    timeout time.Duration
}

func NewPDFUnite(timeout time.Duration) (*PDFUnite, error) {
    path, err := exec.LookPath("pdfunite")
    if err != nil {
        return nil, ErrPDFUniteMissing
    }
    return &PDFUnite{binary: path, timeout: timeout}, nil
}

func (p *PDFUnite) Merge(ctx context.Context, inputPaths []string, outPath string) (*MergeResult, error) {
    if len(inputPaths) < 2 {
        return nil, fmt.Errorf("need at least 2 input files")
    }

    args := append([]string{}, inputPaths...)
    args = append(args, outPath)

    cctx, cancel := context.WithTimeout(ctx, p.timeout)
    defer cancel()

    cmd := exec.CommandContext(cctx, p.binary, args...)
    var stderr bytes.Buffer
    cmd.Stderr = &stderr

    start := time.Now()
    if err := cmd.Run(); err != nil {
        return nil, fmt.Errorf("pdfunite failed: %v — %s", err, stderr.String())
    }
    fi, _ := os.Stat(outPath)
    return &MergeResult{
        OutputPath: outPath,
        OutputSize: fi.Size(),
        Duration:   time.Since(start),
    }, nil
}

Fail-fast at startup if the binary isn't in PATH. Hard timeout via context (120 seconds, generous for a 20-file merge). Stderr captured so failures surface to the user instead of vanishing. Done.

The migration we didn't write

This is the bit we're most pleased with.

Our conversion_jobs table looks like this:

CREATE TABLE conversion_jobs (
    id              UUID PRIMARY KEY,
    user_id         UUID NULL,
    source_format   VARCHAR(16) NOT NULL,
    target_format   VARCHAR(16) NOT NULL,
    source_size     BIGINT NOT NULL,
    output_size     BIGINT NOT NULL,
    duration_ms     INTEGER NOT NULL,
    output_path     TEXT NOT NULL,
    page_count      INTEGER NOT NULL DEFAULT 1,
    expires_at      TIMESTAMPTZ NULL
);

For convert flows, source_format and target_format are things like 'jpg' and 'webp'. The first instinct for PDF merge was to add a kind enum column ('convert' | 'pdf_merge' | ...) and store input file paths in a new JSONB column.

we almost wrote that migration. Then we noticed: the existing schema already represents everything we need. For PDF merge:

source_format = 'pdf'
target_format = 'pdf-merge' (synthetic — won't match any AllowedTarget, so it never accidentally hits the convert flow)
page_count = N where N is the number of input files (reuses the column meaningfully; "page count" of an N→1 merge = input count)
The existing 1-hour anon TTL applies
The existing cleanup goroutine cleans up the output
The existing per-IP anonymous quota counts merges as conversions

Zero migration. Zero new columns. Zero data model debt. The whole feature ships with a parallel MergePDFs service method and a new HTTP handler, both reusing the existing repository and storage paths.

This pattern — synthetic target format as a discriminator — extends cleanly to upcoming features (image → PDF will be source='image', target='pdf-create'; OCR will be target='pdf-ocr'). we get an enum-like discriminator without paying the migration tax.

The day 8 honesty section

Building in public means showing the unflattering numbers, so here are mine after one week:

15 unique visitors total (mostly us testing — self-traffic exclude was set up on day 6)
0 confirmed real conversions from external users
0 email signups (the form has been live for a week)
3 reactions, <25 views, 0 comments on the day-4 AVIF crosspost on DEV.to

Almost every solo-founder Twitter post conveniently leaves these numbers out. They're the reality of week 1. The funnel data on our dashboard says the product converts at 33% (visitor → upload → output), which sounds impressive — and is meaningless when 4 of those 5 visitors are us checking a deploy.

The bottleneck is distribution, not the product. we built PDF merge partially because we needed it, partially because "pdf merge" is a 600K/month search query and our privacy angle has a real wedge against Smallpdf et al. Whether that wedge is enough to grow past 2 visitors/day is the experiment of the next 4 weeks.

What's next

Image → PDF (combine multiple images into one PDF) — same pdfunite-style pipeline, just with ImageMagick on the way in
OCR via Tesseract — much harder; weeks of work
Distribution: awesome-list PRs, this DEV.to post, then HackerNews "Show HN" once the feature has 2 weeks of stability

Try the merger here: swapfile.io/en/tools/pdf-merge

The code is closed-source today (might change post-monetization in November). Everything you see in this post is exactly how it runs in production — no oversimplification for the article.

Building SwapFile.io in public — privacy-first image and PDF tools. Files auto-delete in 1 hour, no Google Analytics, free for the first 6 months. Feedback welcome via reply or Twitter @swapfileio.

What Is AVIF? Why It Became the Default Image Format in 2026

swapfileio — Wed, 13 May 2026 21:22:48 +0000

In this article:

What AVIF actually is, who built it, what problem it solves
Why the same image is ~50% smaller than JPEG and ~20% smaller than WebP at equivalent quality
When AVIF is the right call — and when it isn't
2026 browser support: is it finally safe to use everywhere?

Let us start with one number. The same 1920×1080 photo, encoded at the quality where the human eye can't tell them apart:

JPEG at q75: 263 KB
WebP at q75: 168 KB
AVIF at q50: 102 KB

Three formats. Same image. Same perceived quality. The AVIF version is less than 40% the size of JPEG.

That single number is why we're having this conversation in 2026. But "use AVIF" is the easy answer. The harder, more useful one is when to use it — and when not to. That's what this guide covers.

What Is AVIF, Briefly

AVIF stands for AV1 Image File Format. It was released in 2019 by the Alliance for Open Media, a consortium of companies that wanted a royalty-free, open-source image compression standard. The roster includes Google, Mozilla, Cisco, Apple, Netflix, Amazon — basically the companies that pay the most in bandwidth costs and care the most about open standards.

Why a new format at all? The image format landscape in 2019 looked like this:

JPEG (1992): Still everywhere. Still 34 years old.
PNG (1996): Lossless, but huge for photos.
HEIC (2015): Apple-developed, used by iPhones. Patent-encumbered, expensive to license.
WebP (2010): Google's attempt to replace JPEG. Got stuck because Safari took a decade to support it.

The opening: a modern, royalty-free format that actually used the latest compression research. AVIF is built on top of the AV1 video codec — the same codec YouTube and Netflix use for HD/4K streaming. AVIF is essentially "one frame of AV1 video, saved as an image."

The result: the full power of modern video compression, applied to a single still image.

How It Actually Works

You can skip this section if you don't care about the technical details — but understanding the basics helps you make better calls about when AVIF helps and when it doesn't.

AVIF compresses an image by breaking it into blocks (anywhere from 8×8 to 128×128 pixels). For each block, the encoder predicts what it should look like based on neighboring blocks, then stores only the difference between the prediction and the actual content.

Imagine you're encoding a photo of a sky. You've got 10 nearly-identical blocks of blue. AVIF says "look at the first block, the next 9 are basically the same with tiny corrections." That's intra-frame prediction, and JPEG doesn't have it. JPEG compresses every block independently. That's why JPEG creates visible banding in gradients — skies, sunsets, blurry backgrounds.

Two other technical wins worth mentioning:

Wider color depth. JPEG is locked to 8-bit per channel (256 shades). AVIF supports 10 and 12-bit (1024 and 4096 shades). This matters for HDR photos — JPEG literally can't store HDR information; AVIF can.

Alpha channel. Transparency, like PNG. AVIF supports it, JPEG doesn't, and AVIF transparent images are typically 60-80% smaller than equivalent PNGs.

AVIF vs WebP vs JPEG — Real Numbers

we tested the same 1920×1080 photo across all three formats, calibrating quality settings so the perceptual quality (measured with DSSIM) was identical:

Format	File size	vs JPEG	Encode time	Browser support
JPEG (q75)	263 KB	100%	<100ms	100%
WebP (q75)	168 KB	64%	~200ms	97%
AVIF (q50)	102 KB	39%	~1500ms	94%
AVIF (q30)	65 KB	25%	~2000ms	94%

Three takeaways:

1. AVIF wins on file size by a wide margin. Same visible quality, 60-75% less storage. The bandwidth savings are massive, especially for mobile users.

2. Encoding is slow. JPEG encodes in 50ms, AVIF can take 1.5 seconds for the same image. This isn't a user-facing problem (you only encode once), but it matters for batch jobs. AVIF uses significantly more server CPU.

3. Browser support is 94%. That means 6% of your visitors can't see AVIF. This is why fallback strategy still matters (more on that below).

When to Use AVIF (and When Not)

Switching every image to AVIF tomorrow is not the right move. Some use cases make sense, some don't. Here's how we think about it:

✅ Use AVIF

Web hero images — Page speed is critical, bandwidth matters, 6% fallback is acceptable
Photography portfolios — High resolution, lots of files, storage costs add up
E-commerce product images — Page load impacts conversion, milliseconds count
Blog cover images — Core Web Vitals affect SEO rankings
HDR photos — JPEG can't preserve HDR; AVIF can
Transparent backgrounds — Replace PNG, get 80% smaller files

❌ Don't Use AVIF (yet)

Email content — Many email clients still don't render AVIF (Outlook 2019 doesn't)
Legacy systems — Enterprise B2B tools, government portals
Print pipeline — If it's going to PDF/PSD eventually, use JPEG/PNG
Older Photoshop workflows — Pre-2022 versions can't open AVIF directly
Internal admin panels where speed doesn't matter

🟡 The Hybrid Approach (What we Actually Do)

In practice, we generate three versions of every image:

AVIF (modern browsers)
WebP (older Chrome/Firefox)
JPEG (universal fallback)

Then let the browser pick using the <picture> element:

`<picture>
  <source srcset="hero.avif" type="image/avif">
  <source srcset="hero.webp" type="image/webp">
  <img src="hero.jpg" alt="...">
</picture>
`

The browser checks in order: Does it support AVIF? Yes → load AVIF. No? WebP? Also no? Load the JPEG. Every visitor gets the smallest file their browser can handle.

This triples your storage cost (three copies of each image), but bandwidth savings usually make up for it. If you're paying for a CDN, the numbers work out fast.

Browser Support in 2026

Last time we checked caniuse.com (early 2026), AVIF support looks like:

Chrome — Since August 2020 (5+ years)
Firefox — Since October 2021 (4+ years)
Safari — Since March 2023 (Safari 16.4+)
Edge — Since January 2024 (version 121+)
iOS Safari — Since March 2023

Total global coverage: ~94%.

What this means: Using AVIF in 2024 was an "early adopter" move. In 2026, it's a standard choice. You still need to think about the 6% fallback — that's what <picture> solves.

If your audience skews corporate (Internet Explorer might still be alive in some IT departments!) or is heavy on older Asian Samsung devices, that 94% might be lower for you. Check your actual analytics before assuming.

Converting to AVIF with SwapFile.io

This is exactly the problem SwapFile.io was built for. You want to convert old JPEGs to AVIF, but you don't have Photoshop, you don't know ImageMagick from the command line, and you definitely don't want to upload your family photos to some random cloud service.

Our JPEG to AVIF converter handles this directly:

Drop the file in the browser (under 1 second)
Conversion happens on our server
Files auto-delete after 1 hour — we never see them, no third party has access
No cloud storage. No account required (up to 15MB without signup)

We also support PNG, HEIC, WebP, GIF, and a few others — all convertible to AVIF. The full tools page lists every supported conversion.

Frequently Asked Questions

Why can't we see AVIF thumbnails in Windows Explorer?

Windows 11 doesn't ship with AVIF support by default. Install the AV1 Video Extension from the Microsoft Store (it's free). Once installed, File Explorer will show thumbnails automatically.

Photoshop won't open our AVIF file.

Photoshop CC 2022 (version 23.2) and later support AVIF natively. If you're on an older version, either upgrade or convert AVIF back to JPEG first.

Is AVIF quality worse than JPEG?

At the same file size, AVIF is better. At the same quality, AVIF is smaller. So: JPEG at quality 80 looks the same as AVIF at quality 50, but the AVIF is half the size. At very low quality settings (q20 or below), both formats produce visible artifacts, but AVIF generally degrades more gracefully.

Will AVIF preserve HDR from our iPhone photos?

Yes. AVIF supports 10-bit and 12-bit HDR. JPEG can't store HDR information (8-bit limit). If you've shot HDR on an iPhone Pro and want to preserve it when moving to a PC, AVIF is the right format.

Should we convert PNG files with transparency to AVIF?

Usually yes. PNG-to-AVIF conversion typically saves 60-80% on file size while preserving the alpha channel. The exception: tiny icons (16×16, 32×32) — at that size PNG is already small, and AVIF's encoding overhead negates the savings.

Does AVIF hurt mobile performance?

Decoding AVIF is 2-3x slower than JPEG, but on modern mobile devices the difference is measured in milliseconds. The smaller file size = faster network download more than compensates. Net effect: faster page loads on mobile.

Does using AVIF help SEO?

Not directly. But it improves Core Web Vitals (specifically LCP — Largest Contentful Paint), which is a Google ranking factor. Switching to AVIF typically drops LCP by 200-500ms. So: indirectly, yes.

The Bottom Line

One sentence: AVIF should be your default web image format in 2026, paired with a fallback strategy.

Exceptions: email, print pipelines, legacy systems. In those, stick with JPEG/PNG.

If you're currently serving JPEG and care about page speed (e-commerce, blog, portfolio), switching to AVIF typically pays back in bandwidth savings within 1-3 months. Encoding time is a one-time cost. Storage costs increase slightly. Bandwidth savings are continuous.

Your next step:

Convert 5 different photo types using our AVIF converter (portrait, landscape, product shot, screenshot, HDR)
Compare side by side — same quality? Yes → look at the file size difference
Convert the 10 most-used images on your site/blog to AVIF
Add <picture> tag fallback to your HTML
Re-run PageSpeed Insights — watch LCP drop

Related Reading:

Originally published on SwapFile.io. we're building SwapFile.io in public — a privacy-first image converter (HEIC, AVIF, WebP, JPG, PNG, BMP, TIFF, PDF). Files auto-delete in 1 hour, no Google Analytics, free for the first 6 months. Try it: swapfile.io. Feedback welcome.

DEV Community: swapfileio

Is AVIF Ready for Production in 2026? Browser Support and Real Trade-offs

TL;DR — Support by Browser, June 2026

So Is It Ready?

The Safari Delay Nobody Talks About

When AVIF Actually Saves You Money

Implementation: Two Realistic Options

Option A: Plain <picture> Element

Option B: Server-Side Content Negotiation

Where AVIF Falls Short

Three Sites Doing This Right

Migration Path: WebP to AVIF

FAQ

The 2026 Recommendation

How to Download iCloud Photos to Windows — Solving the HEIC Trap (2026)

Before You Start: iCloud Photos vs iCloud Drive

The Four Methods at a Glance

Method 1: iCloud for Windows App (Recommended for Most People)

Setup steps

Reality check

Method 2: iCloud.com Web Download (No Install)

Steps

The HEIC catch

Method 3: iPhone → Mac → SMB Share (For Mac Users)

Method 4: Web Download + SwapFile.io Conversion

Hybrid Recommendation

iCloud Family Sharing Caveat

Frequently Asked Questions

Conclusion

How to Turn Off HEIC on iPhone — Switch to JPG (2026 Guide)

Why HEIC Default? Quick Recap

Should You Turn It Off? — Honest Decision Table

Turn it off if:

Keep it on if:

30 Seconds to Turn It Off — Step by Step

Step 1: Open Settings

Step 2: Go to Formats

Step 3: Select "Most Compatible"

iOS 18 Surprise: AV1 Codec

What Happens to Existing HEIC Photos?

1. Sharing one-off

2. Batch conversion

3. iCloud Photos

Hybrid Approach — "I Want HEIC But Sometimes JPG"

HEIC vs JPG — Quick Comparison

Frequently Asked Questions

Conclusion

Why Windows Still Can't Open HEIC Files in 2026 (And What Actually Works)

What's the actual problem?

Microsoft's awkward setup

Who's to blame?

5 solutions that actually work in 2026

1. Buy Microsoft HEVC Extension ($0.99) — the official path

2. Convert online — free, fast, private

3. CopyTrans HEIC for Windows — free for individuals

4. Change format on iPhone itself — the preventive fix

5. Open on macOS, export to JPG — if you have a Mac

Which scenario, which solution?

Frequently asked questions

Conclusion

How We Built a Privacy-First PDF Merger in 7 Hours: The Stack and the Lessons

TL;DR

The problem

The unsexy answer: pdfunite

The Go wrapper

The migration we didn't write

The day 8 honesty section

What's next

What Is AVIF? Why It Became the Default Image Format in 2026

What Is AVIF, Briefly

How It Actually Works

AVIF vs WebP vs JPEG — Real Numbers

When to Use AVIF (and When Not)

✅ Use AVIF

❌ Don't Use AVIF (yet)

🟡 The Hybrid Approach (What we Actually Do)

Browser Support in 2026

*Converting to AVIF with *SwapFile.io

Frequently Asked Questions

The Bottom Line

Option A: Plain `<picture>` Element

Converting to AVIF with SwapFile.io