How Much Disk Space Does Screen Recording Use? A Storage Guide for Long Sessions

Where screen recording storage goes: what gets written to disk, how to estimate space before an hour-long session, and how to clean up safely.

You sit down to capture a 90-minute workshop, hit record, and forty minutes later your Mac starts complaining that the startup disk is almost full. Or you finish the session fine, open your home folder a week later, and discover that last month’s recordings are quietly occupying 60 GB.

Screen recording is one of the few everyday tasks that writes data continuously, at high speed, for as long as you let it run. Most storage surprises are not mysterious — they come from not knowing what gets written, where it lands, and how long it stays there. This guide covers all three, with the arithmetic you need to plan a long session before you start it.

What a Recording Actually Writes to Disk

A finished video is one file. A recording in progress is not.

While you record, Recorded writes each source as its own file inside a per-session folder: the screen capture as recording.mp4 (H.264), the webcam as a separate webcam.mp4 if the camera is on, and audio as uncompressed WAV — mic_audio.wav for the microphone and audio.wav for system sound. Small metadata files sit alongside them to keep the tracks in sync and store your cursor data.

Two consequences matter for storage planning:

Audio is not compressed during capture. WAV is raw 16-bit PCM. The math is fixed and easy: a stereo 48 kHz track is 192 KB per second, which is about 11.5 MB per minute, or roughly 690 MB per hour. A mono microphone track is half that. Record a one-hour session with both microphone and system audio and you have written over a gigabyte of audio alone — before counting a single video frame.

Webcam footage is additive. It is encoded separately rather than burned into the screen capture, which is what lets you move, resize, and restyle the camera later in the editor. It also means the camera is a second video file growing in parallel.

This design is deliberate: separate tracks are what make non-destructive editing possible. The trade-off is that the raw session folder is always larger than the video you eventually export.

Where Recorded Keeps Them

Recordings live under your user folder, not in a hidden application cache:

  • macOS: ~/Movies/Recorded/Recordings
  • Windows: %USERPROFILE%\Videos\Recorded\Recordings

Each session gets its own subfolder. You never have to go hunting manually, though — every card in the recordings library has an Open folder action that reveals the session in Finder or File Explorer, which is the fastest way to inspect what a recording is actually costing you.

The library is also where the sizes are visible. Each card shows the recording’s date, its duration, and its size on disk — and that size figure is the whole session folder, video plus webcam plus both audio tracks plus metadata, not just the screen file. If a number looks surprisingly large for a short clip, the extra is almost always uncompressed audio.

Estimating Before You Press Record

For the export side, the math is predictable. Recorded’s export panel targets a high-quality H.264 bitrate — about 10 Mbps for 1080p output, scaled by pixel count — and shows you an estimated file size and export time before you commit. Translate that into something you can plan around:

Export resolutionApproximate size per minuteOne hour
720p~33 MB~2 GB
1080p~75 MB~4.5 GB
1440p~133 MB~8 GB
4K~300 MB~18 GB

Those are ballpark figures from bitrate arithmetic, not guarantees — a static slide deck compresses far below the target, and continuous scrolling pushes against it. But they are accurate enough to answer the only question that matters before a long session: do I have room for this?

Raw capture is harder to predict precisely because it depends on what is on screen, so the practical rule is to assume the session folder will be larger than the export and keep headroom accordingly. For a one-hour 1080p recording with microphone and system audio, planning for 10–12 GB of free space — capture plus the export you will make afterward — leaves you comfortable. Running a disk down to its last gigabyte is where recordings fail.

The export panel’s resolution list runs from 480p through 1440p and 4K, plus Original and Retina. If you are tight on space, the single most effective lever is exporting at the resolution your audience will actually watch rather than the resolution you captured. A tutorial embedded in a documentation page at 800 pixels wide gains nothing from a 4K export and costs you four times the bytes. There is more on that trade-off in our guide to reducing screen recording file size.

GIFs Are a Special Case

GIF has no bitrate to turn down. Its size is a direct product of pixel count, frame rate, and duration, because every frame is stored as its own indexed-color image. That is why a fifteen-second GIF can easily outweigh a two-minute MP4, and why Recorded warns you before exporting a GIF longer than about thirty seconds.

If you need a GIF, keep it short, keep the dimensions small, and use the lower frame-rate option. If you need anything longer than half a minute, MP4 is both smaller and better looking. Export options cover MP4 (H.264) and GIF — there is no intermediate format to split the difference, so the decision is simply which of the two fits the destination.

Recording Long Sessions Without Running Out

Long sessions are where storage problems actually bite, because the write continues for an hour or more without any natural pause.

Check free space first, not when the warning appears. There is no pre-flight disk check that stops you from starting a recording you do not have room for. Thirty seconds of looking at your available space beforehand prevents the worst possible failure mode: losing a session you cannot re-stage.

Record to an internal drive. Capture writes continuously, and the drive has to keep up in real time. A network share, a cloud-synced folder, or a slow external disk can introduce stalls that show up as dropped frames rather than an obvious error. Keep captures on internal storage and move finished exports elsewhere afterward. If you are also chasing stutter, our performance optimization guide covers the other bottlenecks.

Pause the sync client. A folder watched by Dropbox, iCloud Drive, or OneDrive will try to upload a multi-gigabyte file that is still being written to. Since recordings default to ~/Movies or Videos, this usually is not an issue — but if you have relocated anything into a synced folder, disable syncing before a long capture.

Break the session into takes. A 90-minute single take is one enormous session folder, and a mistake at minute 80 puts all of it at risk. Recording in several shorter takes caps your exposure, makes each file manageable, and tends to produce better video anyway. We wrote about this approach in recording in takes.

If the Disk Fills Mid-Recording

When a recording cannot finish writing, it does not silently disappear. The session is marked as failed in the recordings library, with details about what went wrong, so you can tell a disk problem apart from a capture problem instead of guessing.

That is also a reason not to clear your library the moment something looks broken. Open the folder first and check whether the screen file is intact — a recording that stopped early is sometimes still usable for the part it did capture.

Cleaning Up Without Losing Work

The storage problem most people actually have is not a single huge recording. It is forty old sessions nobody ever revisited.

A simple routine keeps it under control:

  1. Sort by what you have already exported. Once a recording is exported and published, the session folder is raw material. Keep it if you expect to re-edit; delete it if the published video is the deliverable.
  2. Delete from the library, not the Finder. The library’s delete action removes the whole session folder, including the separate audio and webcam files. Deleting only the screen file by hand leaves orphaned tracks behind.
  3. Rename as you go. Recording 2026-10-24 tells you nothing in six weeks, which is how recordings survive cleanups they should not survive. The rename action exists for exactly this. Our guide to organizing your recording library goes further on naming schemes.
  4. Archive the raw takes you genuinely need. Move those session folders to an external drive rather than keeping them on your working disk.

The one thing worth resisting is deleting raw sessions on the same day you publish. Give it a week — re-edit requests arrive far more often than expected, and re-recording a session from scratch costs much more than a few gigabytes did.

A Quick Pre-Session Checklist

  • Free space checked, with room for the capture and the export
  • Recording to an internal drive, not a network or synced folder
  • Long content split into takes rather than one continuous file
  • Export resolution chosen for the destination, not the display
  • Last month’s published sessions reviewed and cleared

Storage planning is unglamorous, but it is the difference between an hour-long session that finishes and one that dies at minute forty with nothing to show. If you have not set up yet, you can download Recorded and check where your recordings will land before your first long capture.