Checking storage space before a long recording
“How big will this recording be” is a question most people only ask after running out of space mid-recording. Here’s a practical planning reference instead.
Rough numbers by setting, per minute of recording
These are directional estimates using common H.264 compression at reasonable quality settings — actual results vary by content (fast motion compresses worse than static screens) and your specific software’s encoding settings, but they’re close enough to plan storage around:
| Resolution | Frame rate | Approx. size per minute |
|---|---|---|
| 720p | 30fps | ~15-25 MB |
| 1080p | 30fps | ~25-40 MB |
| 1080p | 60fps | ~40-70 MB |
| 4K | 30fps | ~100-160 MB |
| 4K | 60fps | ~160-280 MB |
What actually changes these numbers
Content matters more than most people expect. A mostly static screen (a document, a slide-based presentation) compresses far more efficiently than fast motion (gameplay, rapid scrolling, video playback within the recording) — the same resolution and frame rate can produce meaningfully different file sizes depending purely on how much is visually changing frame to frame.
Bitrate settings, if your tool exposes them, matter more than resolution alone. Two recordings at identical resolution and frame rate can differ significantly in size if one uses a higher bitrate setting — this is the actual dial to adjust if you need to trade file size against visual quality, rather than dropping resolution as the first lever.
A practical planning example
A one-hour tutorial recording at 1080p/30fps, mostly static content (slides, occasional cursor movement): reasonably estimate 1.5-2.5 GB. The same hour of fast-motion gameplay footage at the same settings could run meaningfully higher — 3-4 GB isn’t unusual — purely because of how much more the frame-to-frame content is changing.
Before a long or important recording
Check available storage against a generous estimate (round up from the table above, not down) before starting anything you can’t easily re-record. Running out of space mid-recording doesn’t just stop cleanly — depending on your recorder, it can corrupt the file entirely rather than simply ending it early.
If storage is a genuine constraint
Recording at 1080p/30fps instead of 4K/60fps for content that doesn’t need the higher fidelity (most tutorial and documentation recording genuinely doesn’t) is the most impactful single change — the jump from 1080p to 4K alone roughly triples to quadruples file size for the same length of recording.
Frequently asked questions
How much storage does a one-hour screen recording use?
At 1080p/30fps with typical content, roughly 1.5-2.5 GB is a reasonable planning estimate — more for fast-motion content like gameplay, less for mostly static content like slides.
Does 4K recording really take that much more space than 1080p?
Yes — expect roughly 3-4x the file size of equivalent 1080p footage at the same frame rate and length, which is worth weighing against whether you actually need 4K for the content in question.
What’s the fastest way to reduce screen recording file size without dropping resolution?
Adjust the bitrate setting directly if your recorder exposes it — this often preserves more visual quality per megabyte saved than simply lowering resolution.
Related reading: How to trim a screen recording without losing quality · Effortless MOV to MP4 conversion on Mac · How to record your screen without lag