A screen recording captures your entire screen, every frame, often at a higher resolution than a normal camera video — which makes it one of the densest, heaviest file types on any phone, and also one of the least likely to ever be watched again.

Why they're so much bigger than they seem

A few minutes of screen recording can consume hundreds of megabytes, and a long tutorial or support capture can grow much larger. The exact size depends on the device, display, frame rate, and what changes on screen. Sort by file size instead of estimating from duration, then trim waiting and repeated attempts before deleting the useful section.

How they end up forgotten

Many screen recordings are made for a single purpose: showing a bug, teaching a task, or catching something fleeting. Once the recipient confirms they have it, the long raw recording may no longer be useful. Preserve meaningful calls, evidence, or tutorials deliberately, and remove the routine captures whose job is clearly finished.

Where to find them

On iPhone, they live in your regular Photos library, mixed in with everything else — but you can isolate them via Albums → Media Types → Screen Recordings, which Photos generates automatically. On Android, check your Gallery app's video filter, or look in DCIM/Screenshots or a similarly named folder depending on your device.

A quick audit

Open the Screen Recordings album and sort by date. Anything older than a month has almost certainly already served its purpose — the bug got fixed, the message got read, the moment passed. It's one of the safest bulk-delete categories on the entire phone, right alongside old screenshots.

Want the big files handled gently? Arc finds oversized videos and lets you compress or review them before deleting a thing.
Get Arc free

Review screen recordings by purpose

Screen recordings are usually made to show one bug, save one live moment, or teach one task. Once that purpose is complete, the long raw capture rarely needs to stay.

  1. Sort by duration or size. Open the longest recordings first and scrub the timeline. Look for waiting, setup, repeated attempts, and the recording continuing after success.
  2. Trim before deleting. Keep the 20 seconds that demonstrate the issue or instruction and remove the idle minutes around it.
  3. Confirm the handoff. For a support ticket, make sure the recipient received and can open the clip before removing your copy.
  4. Save knowledge properly. Move useful tutorials into a named album or notes system with a short description, rather than leaving them in the camera roll.
  5. Stop future over-recording. Plan the steps first, enable Do Not Disturb, and stop immediately after the useful moment.

A useful decision rule

Keep the evidence or instruction, not the entire process of getting there. Trimming is often the highest-confidence storage win.

Before you finish

  • Sensitive notifications are not visible.
  • Required audio remains.
  • Shared or support clips reached their destination.

A calmer next step

Watch the first few seconds. If you cannot remember why you recorded it, that is usually your answer.