7 Hidden Photo Formats Secretly Eating Your iPhone Storage: AAE, FullSizeRender, and More

Open your iPhone's storage settings. It says Photos is using 24 GB. You count your photos — maybe 8,000 images at an average of 1.5 MB each. That's only 12 GB. Where is the other 12 GB hiding?

The answer lies in hidden companion files that iOS creates silently alongside your visible photos. These invisible formats serve legitimate technical purposes — non-destructive editing, thumbnail caching, depth mapping — but they accumulate into a massive storage shadow that no standard photo gallery app reveals.

The 7 Hidden Photo Formats on iPhone

1. AAE Files — Apple's Non-Destructive Edit Sidecars

Every time you crop, rotate, apply a filter, or adjust brightness in the Photos app, iOS does not modify the original image. Instead, it creates an .AAE file (Apple Adjustment Extension) — a small XML/plist document that records your edit instructions. The original image stays untouched, and the AAE file is applied as an overlay during rendering.

Individual AAE files are tiny (1–5 KB). But if you've edited 3,000 photos over the years, that's 3,000 orphaned AAE files that persist even if you revert the edits. They also transfer during backups and migrations, creating file system clutter.

2. FullSizeRender — The Instagram/VSCO Export Shadow

When you edit a photo in Instagram, VSCO, Snapseed, or any third-party app and save it back to your camera roll, the app doesn't overwrite the original. Instead, it creates a brand-new full-resolution JPEG named FullSizeRender (or a variant like IMG_E1234). Now you have two copies: the original HEIC and the exported JPEG — often 3× larger because JPEG compression is less efficient than HEIC.

Users who regularly edit and re-save photos in third-party apps can accumulate thousands of these shadow copies without realizing it. A camera roll with 10,000 visible photos may contain 2,000–4,000 FullSizeRender duplicates consuming 6–12 GB of invisible storage.

3. PVTC Thumbnails — The Preview Cache

iOS maintains a multi-resolution thumbnail database at PhotoData/Thumbnails/. For every photo in your library, the system pre-renders three thumbnail sizes: a tiny grid icon (88×88), a medium preview (256×256), and a large preview (1024×1024). This cache enables the Photos app to scroll smoothly through tens of thousands of images without loading full-resolution files.

On a 15,000-photo library, the thumbnail cache typically consumes 1.5–3 GB. It regenerates automatically if deleted (via a restore or reset), but it cannot be manually purged without affecting Photos app performance.

4. Live Photo MOV Companions

Each Live Photo consists of two files: the HEIC still image and a QuickTime .MOV video clip (H.265 encoded, 1.5 sec before + 1.5 sec after the shutter). When you convert a Live Photo to a standard still (long press → turn off Live), the MOV file is not always immediately deleted. Orphaned MOV companions from converted Live Photos can linger indefinitely.

5. Depth Map and Segmentation Mask Files

Portrait Mode photos bundle a TrueDepth or LiDAR depth map and a person segmentation mask alongside the primary image. These auxiliary data files enable the adjustable bokeh effect and Lighting modes. Each depth map adds 1–3 MB per Portrait photo. On devices with thousands of Portrait shots, this overhead reaches 3–8 GB.

6. PhotoData Caches and Analysis Data

iOS runs continuous on-device machine learning analysis on your photo library: face recognition, object detection, scene classification, pet identification. The results are stored in PhotoData/ SQLite databases and feature vector caches. On large libraries (20,000+ photos), this analysis data grows to 2–5 GB. It's the primary reason the "System Data" category in Settings → iPhone Storage can balloon unexpectedly.

7. TRIM Artifacts from Edited Live Photos

When you trim a Live Photo (choosing a different key frame or shortening the clip), iOS preserves the original full-length MOV and creates a .TRIM metadata file pointing to the new in/out points. The untrimmed video data stays on disk, adding 2–4 MB per trimmed Live Photo — invisible storage overhead for an edit that feels like it should reduce size.

How Much Hidden Storage Are You Wasting?

How to Reclaim the Invisible Storage

1. Delete the parent photo: When you delete a photo, iOS also removes its associated AAE, depth maps, MOV companion, and TRIM artifacts. The most effective cleanup strategy is removing unwanted photos — the hidden files follow automatically.
2. Avoid re-saving edited photos: Instead of exporting from Instagram/VSCO back to your camera roll (creating FullSizeRender copies), share directly from the editing app.
3. Convert Live Photos before deleting originals: If you only want the still image, use the Photos app's built-in "Save as Still Photo" function (iOS 17+) which properly removes the MOV companion.
4. Reduce PhotoData analysis pressure: A smaller, cleaner library means less ML analysis data. Deleting 5,000 unnecessary photos can shrink the analysis database by 1–2 GB.

Surface the Hidden Clutter Automatically

Swipe Photo Cleaner (Wipe AI) identifies the most common sources of invisible storage waste: duplicate FullSizeRender exports, orphaned burst sequences, and outdated screenshots. By removing the parent photos through fast card-swipe decisions, all associated hidden companion files are automatically purged — no file system spelunking required.