The Biggest Storage Wins Are Almost Always a Few Huge Files
When a phone warns that storage is running out, the natural reaction is to start deleting photos at random — old screenshots first, then bursts, then anything that looks duplicative. That is honest work, but it rarely moves the needle where it matters. The truth about storage pressure is simpler and a little uncomfortable: most of it sits in a small number of unusually large files.
Most libraries are heavy at the top
Sort your library by file size and look at the top 20 items. In a typical phone, those 20 items are heavier than the bottom 5,000 combined. A 4K video, a Live Photo pair, a high-resolution document scan, a downloaded meme saved into the library — heavyweight items do not arrive one at a time, but they accumulate quietly over years.
Why the long tail does not help
It feels productive to delete a hundred 2 MB images and free 200 MB. The math rarely works out: the next photo in line is also around 2 MB, and there are thousands of them. The time spent reviewing a hundred small items is comparable to the time spent reviewing two big ones, but the storage impact is an order of magnitude apart.
The items that quietly eat the most
Some heavyweight items are easy to forget because you do not see them every day: a 4K video shot once for a one-off event, an exported video edited on the phone, a Live Photo pair that includes both the still and the movie. They are large, you may have watched them once, and they do not surface in "all photos" lists in any way that flags their size.
Start at the top, work down
The fastest path to freeing meaningful space is to start at the top of a size-sorted list and work down. Every decision at the top is high impact: a single tap can free hundreds of megabytes or several gigabytes. By the time you reach items under 50 MB, you are back to the small-photo cleanup that started this whole exercise.
Size first, then memory
A useful rule of thumb: if a file is heavy and you cannot remember why it matters, it can usually go. If it is heavy and you know exactly when you will rewatch it, it stays. The decision framework is binary and quick, which is why a size-sorted list finishes in a fraction of the time an undifferentiated one does.
Local review, system deletion
The size list is built from your library's local metadata. Reviewing it does not upload anything. Every deletion still goes through the system photo library with your explicit confirmation, so the protected deletion prompts you already trust remain in charge.