Screen recordings are everywhere now: software tutorials, gameplay clips, online-class lectures, and quick bug reports for a support team. Yet the file that lands on your disk can be a pleasant surprise or a nasty one. A one-hour tutorial captured at 1080p can weigh less than 500 MB or more than 5 GB, and the difference comes down entirely to three recording settings most people never touch. This guide explains exactly how those settings shape file size, shows a comparison table of typical recording sizes, and shows you how to estimate any recording before you press the record button.
Why screen recordings vary so much in size
Unlike a camera that records whatever the lens sees, screen recording software re-encodes pixels as it captures them. The encoder decides how much visual information to keep and how much to throw away. Aggressive settings produce tiny files but blurry text; generous settings keep every pixel crisp but fill your drive fast. Because software like OBS Studio, QuickTime, and the built-in Windows Game Bar use different default encoders and bitrates, two people recording the same screen can end up with files that differ in size by a factor of ten.
The most important thing to understand is that file size is not a property of your screen. It is a property of your encoder settings. The same 1920×1080 display can produce a 2 GB recording or a 400 MB recording of the identical one-hour session.
The three settings that control file size
Every recording encoder answers to three masters. Change any one of them and the file size moves.
- Resolution. The number of pixels captured per frame. Recording at 4K (3840×2160) captures four times the pixels of 1080p, so it needs roughly four times the bitrate to keep the same quality.
- Frame rate. The number of frames captured per second. A 60 fps recording captures twice as many frames as a 30 fps one. For slide presentations the difference barely matters; for gameplay it matters a lot.
- Codec and bitrate. The codec (H.264, H.265/HEVC, AV1) decides how efficiently frames are compressed, and the bitrate decides how much data the encoder is allowed to spend per second. Bitrate is the single biggest lever on file size.
Typical screen recording sizes, compared
The table below shows what a one-hour recording usually weighs at common settings, using typical H.264 bitrates from popular recording software. Your exact file will vary with how much movement is on screen — a static slide deck compresses far better than a fast-paced game.
| Setting | Bitrate | 1 hour ≈ | Best for |
|---|---|---|---|
| 720p, 30 fps | 3 Mbps | 1.35 GB | Quick tutorials, low storage |
| 1080p, 30 fps | 6 Mbps | 2.7 GB | General tutorials, classes |
| 1080p, 60 fps | 10 Mbps | 4.5 GB | Gameplay, software demos |
| 1440p, 60 fps | 18 Mbps | 8.1 GB | High-detail screencasts |
| 4K, 30 fps | 25 Mbps | 11.25 GB | Professional production |
| 4K, 60 fps | 45 Mbps | 20.25 GB | Maximum quality archives |
Switching to the H.265 (HEVC) codec cuts these numbers by roughly 30–50% at similar visual quality, because the newer codec compresses each frame more efficiently.
The simple formula behind every estimate
File size is simply bitrate multiplied by time. Once you know the bitrate your software uses, you can predict any recording length with one calculation.
File size (MB) = bitrate (Mbps) × time (seconds) ÷ 8. Example: a 30-minute recording at 8 Mbps weighs 8 × 1800 ÷ 8 = 1,800 MB, or about 1.8 GB.
The Screen Recording Size Estimator tool applies this formula for you — enter your resolution, frame rate, codec, and planned recording length, and it tells you the expected file size instantly, no manual math required.
How to estimate before you record
- Check your software's bitrate. In OBS Studio, open Settings → Output and read the bitrate next to the encoder. QuickTime and Game Bar use fixed internal bitrates, typically 6–8 Mbps at 1080p.
- Multiply by your planned length. A 45-minute lecture at 6 Mbps becomes 6 × 2700 ÷ 8 ≈ 2,025 MB.
- Add headroom. Movement-heavy screens can push variable-bitrate encoders 20–30% above the average. Keep at least double the estimate free on your drive.
- Or use the estimator. https://veltrixnews.online/tools/screen-recording-size-estimator handles resolution, frame rate, and codec in one step and is faster than doing the math by hand.
Seven tips to keep screen recordings small
- Record at 1080p, not 4K, unless your audience needs pixel-perfect detail. 4K quadruples the file for a sharpness gain most viewers will never notice.
- Drop to 30 fps for static content. Slide decks, code walkthroughs, and webinars look identical at 30 fps and use far less data.
- Use H.265 when your audience's devices support it. It delivers the same quality at roughly half the bitrate of H.264.
- Lower the bitrate before lowering resolution. A 1080p video at a moderate bitrate looks sharper than 720p at a high one.
- Close unnecessary windows. Animations, notifications, and busy wallpapers make the encoder work harder and the file bigger.
- Re-encode after recording. Running a finished video through HandBrake with H.265 can shrink it 40–60% with no visible quality loss.
- Record in shorter segments. Splitting a two-hour session into four 30-minute parts makes files easier to upload, back up, and recover if one corrupts.
Frequently asked questions
How big is a one-hour 1080p screen recording?
Typically between 2 GB and 5 GB with H.264 at 30–60 fps, depending on the bitrate your software uses. At a modest 4 Mbps setting it can be as small as 1.8 GB, while high-quality gameplay captures can exceed 5 GB. Switching to H.265 cuts those figures by roughly a third.
Does a higher frame rate double the file size?
Not automatically. File size follows the bitrate, not the frame rate directly. If you raise fps from 30 to 60 but keep the same bitrate, the file stays the same size — each frame just gets fewer bits and may look slightly softer. In practice, encoders raise bitrate with fps to hold quality, which is why 60 fps recordings are usually 50–80% larger.
Which codec gives the smallest screen recordings?
AV1 produces the smallest files at a given quality, followed by H.265 (HEVC), then H.264. The trade-off is encoding speed and compatibility: H.264 plays everywhere and encodes fast, H.265 needs about twice the CPU, and AV1 is still slow to encode in real time on most hardware. For most people, H.264 or H.265 is the practical choice.