“Backup” in casual speech means “I can still see it in the grid.” Optimize iPhone Storage lives on that confusion: the mosaic remains, opening a photo waits on a download, and offline is a blur. If your search is iPhone optimize storage keep originals, you are trying to keep the files you would have copied off a camera while still shrinking Settings → iPhone Storage. Those are two different copies. Mix them up and you only have iCloud.

Azalea’s export is the PhotoKit / MediaStore asset. A Live Photo is a still plus a motion clip, so bytes run higher than a thumbnail count. The lab totals already include the pair. The app does not offer a “storage saver” encode. Originals go to your S3 bucket, USB folder, or Samba share. They never pass through an Azalea server. Bundle net.duguying.photos.

Compare, briefly: Azalea keeps the file you would have copied off a camera. iCloud Optimize keeps a cloud original and a local placeholder. Google’s saver tier often re-encodes. Only one of those three can be claimed on a Pixel from a USB disk.

Do not treat “upload complete” as a quality check. Open a 4K clip on the destination and read width. If it is 1080, you used the wrong product.

What Optimize actually changes

Settings → Photos → Optimize iPhone Storage tells iOS it may evict originals once they exist in iCloud Photos. The Photos line in Settings falls. The grid does not. That is the point of the feature, and also why it is a poor stand-in for a portable backup. If the 200 GB plan is full, Optimize stalls because originals cannot upload. That was the 14 Mar 2026 iPhone 15: 241.3 GB used, Photos 88.1 GB, iCloud Photos on, plan full, upload errors looping. Optimize was off, so the phone still held originals. We wrote them to USB first.

A week after that run, with Optimize then enabled, Photos was 41.6 GB. The disk library stayed 86.41 GB (92,778,479,616 bytes). That offload is iOS, not an Azalea toggle. There is no button in Cloud Album that means “delete locally, keep in our cloud,” because there is no our-cloud.

HEIC was 71% of the iPhone lab library (17,891 stills, about 3.12 MB each). A Windows box will need a codec, or you claim the disk on another iPhone. That is not Azalea converting badly. It is the file you asked to keep. Videos: 541 clips, mostly 4K30, about 56.5 MB each. Grid count will lie if you only look at stills.

Steps if you want both: a real copy, then Optimize

Install Azalea. Grant Allow Full Access. Limited Library makes Optimize and backup disagree about what “the library” even is.
Cloud Album → Backup Storage → add S3 or USB Device. English S3 tests used us-west-2. For USB, pick the folder in Files; iOS has no volume list. Tap Test Connection on a bucket profile.
Let automatic backup run until Pending is 0. Keep USB jobs in the foreground. Reopen after a lock screen; tap Resume Backup if needed.
Spot-check: one HEIC, one Live Photo pair, one 4K clip, opened from the disk or downloaded from the bucket. Read file size. If iCloud had already replaced a local with a placeholder, PhotoKit may stall; diagnostics can show iCloud original download stalled for over N seconds.
Only then open Settings → Photos → Optimize iPhone Storage. Write down the Photos line before and after. The destination library must not shrink. If it does, you pointed Optimize and the export at the same misunderstanding.

The Pixel 8 → iPhone 16 claim on 2 Apr 2026 is the other half of “keep originals.” 11,614 items, 81.95 GB on S3 us-west-2. After claim, the iPhone camera roll stayed empty until a few manual downloads. Favorites did not travel. Android cannot reuse iOS local_identifier. The originals were in the backed-up library, not in Recents.

One failure: a green bar on the wrong product

A green iCloud progress bar means iCloud accepted bytes. It does not mean you have a file you can plug into a Pixel. Apple’s export flattens the timeline and mishandles Live Photos. A Finder DCIM copy has no incremental index. If your plan is to keep originals and also free space, the order that has not burned the lab is: Azalea export → open files → then Optimize or delete only verified videos.

Do not combine Google Photos “delete device copies,” iCloud Optimize, and Azalea against the same local files. Three janitors, one roll.

Wrong-region S3 fails on the first list (signature error or 301). That is not a quality problem; it is a profile problem. Fix Region before you trust Pending. Picking a folder inside iCloud Drive for a USB profile is not an external original; the confirm exists because that would put the “backup” back in Apple’s account.

FAQ

If I turn on Optimize iPhone Storage, does Azalea still see originals?

Only if they are still on the device or if iOS can download them in time. If Optimize has already evicted a clip and iCloud Photos is broken or full, export stalls. Backup first, Optimize second. The March USB numbers exist because we did it in that order.

Does Azalea re-encode HEIC to JPEG to “keep originals”?

No. HEIC stays HEIC. DNG stays DNG. 4K stays 4K. Windows may need a codec. That is the format Apple wrote, not a conversion Azalea invented.

Yes. iCloud Photos and an Azalea USB or S3 profile can coexist. Do not let both sides delete locals until you have opened the second copy. Shared Photo Library invites are an Apple ID feature; they are not the same as two phones claiming one disk.

Why did Photos drop to 41.6 GB while the disk stayed 86.41 GB?

Because Optimize evicted locals after iCloud had the originals, and the disk already held an independent copy. The disk is the copy you can take to Android. iCloud is the copy that stays behind one Apple ID. Details are in the iPhone 15 case and the free space after backup note.

Where is the download?

/en/download. Object-storage setup is on the S3/COS/OSS page. USB picker limits are on the USB page.

Original quality versus Optimize iPhone Storage