Sample Header Ad - 728x90

No photos on phone, but Photos supposedly taking up gigabytes of space

0 votes
1 answer
85 views
I have an iPhone 13 (MNGD3LL/A) with iOS 18.5 (22F76), which is the latest general release available to me at time of writing. There are no photos in the **Photos** app on this device (except screenshots taken for this SE question). screenshot of an iOS device showing that there are only two photos, screenshots, in the Photos app There are no photos in the **Recently Deleted** album on this device. screenshot of an iOS device showing that there are no Recently Deleted photos for the Photos app Despite having only a few screenshots on this device the system shows that **Photos** are using ~26 GB of storage space. Almost 20% of the phone's disk is occupied by data for photos, according to the iOS **iPhone Storage** top-level settings. screenshot of an iOS settings menu displaying storage use for the photos app The individual **Photos** entry under **iPhone Storage** agrees that it's using ~26 GB of storage space. screenshot of an iOS settings menu displaying storage use for the device I deleted every photo and video from this iPhone a couple weeks and this space has not been reclaimed. I capture some multimedia every now and then, but delete it almost immediately, and then purge it from **Recently Deleted**. I've seen relatively old questions similar to mine reference "phantom" photos, and the idea that [manually changing the clock on my device](https://apple.stackexchange.com/questions/263732/photos-taking-up-storage-on-iphone-when-i-have-no-photos) might help reveal hidden photos that are stealing this space. I've found [that advice](https://apple.stackexchange.com/a/202692/130404) is not relevant to me. It seems like a functional and/or UX bug on Apple's part that the system can't explain this discrepancy between the reported quantity of photos on the phone and the reported storage usage by the **Photos** library on the phone. [Resetting my device to factory settings](https://apple.stackexchange.com/a/166803/130404) would likely fix the issue, but that seems heavy handed, and I was hoping a more elegant fix might exist here in the year 2025. Is there another way to resolve this issue?
Asked by Will Haley (186 rep)
Jun 25, 2025, 04:24 AM
Last activity: Jul 26, 2025, 12:02 AM