LESS DISK MATH. MORE RECORDING.

Know what your
recording will take.

Estimate file size. Keep a disk reserve. See how much recording time fits — using your numbers, not a guess about your game.

Only in your browserNo uploads. No accounts. No tracking scripts.

01 / YOUR INPUTS

Make a recording plan

Start with
Measured recording
min

Use file size and playback duration from the same recording, with similar content and settings to your next session. Nothing is uploaded.

Your next session

hours

1.5 hours = 1 h 30 min.

%

Extra budget, not a guaranteed limit.

Your disk budget

Enter current free space, not total drive capacity. Windows often labels binary GiB as “GB”; choose GiB for that number. Other apps can consume space while you record.

Use a decimal point or comma; no thousands separators.

02 / THE ESTIMATE

Room for your recording

EXAMPLE ESTIMATE

Session budget

—

Recording rate—
Time until your reserve—
Sessions that fit—
Usable disk space—
This session / usable space

An estimate, not disk monitoring. It does not prevent a full disk or change recorder settings. Time is rounded down to whole minutes.

A PLAN, NOT A PROMISE

Three numbers. Fewer surprises.

01

Measure a real session

Open a finished recording's file properties and check its playback duration. File size divided by duration gives an observed average that includes its audio and container. Use the same game and settings for a useful comparison.

02

Leave room on the drive

The reserve stays outside your recording budget. The planning buffer increases the estimated recording rate, so the reported time to reserve is more conservative. The example's 25% is a starting assumption, not a validated safety margin.

03

Recheck before recording

CQP, CRF, ICQ and VBR can produce different sizes with different content. A sample average is not a maximum. Check free space again, leave room for other apps, and use a representative sample rather than an idle menu screen.

THE DETAILS THAT MATTER

Recording storage,
without the guesswork.

Read the method and limitations →
Why not estimate from resolution or a CQP number?

Resolution, frame rate, scene complexity and encoder settings affect how much data is needed. There is no universal CQP-to-file-size conversion. This tool uses your observed file size or an entered bitrate rather than inventing one. See OBS's recording settings guide.

What is the difference between GB and GiB?

1 GB is 1,000,000,000 bytes. 1 GiB is 1,073,741,824 bytes. Windows frequently shows a binary count with a “GB” label. For an exact size from Properties, divide its bytes by 1,073,741,824 and select GiB, or by 1,000,000,000 and select GB. Don't mix the two.

How does bitrate turn into file size?

Add video bits/second and all audio bits/second, divide by 8, and multiply by the recording's duration in seconds. For example, 8 Mbps of video with no audio for one hour is 3.6 GB before container overhead or a planning buffer. Audio tracks each contribute their own rate. See OBS's bitrate calculation example.

Is this only for OBS?

No. The arithmetic works for any recorder when you know the file size and duration, or the total audio/video rates. It does not inspect OBS, capture your screen, select a drive, or recommend a codec. Other recorders may use different rate-control behavior.

Is my recording or disk information sent anywhere?

No file is read and entered numbers stay in this page. There are no ads, analytics or tracking scripts in this version. A public web host still receives ordinary page requests; external links have their own privacy practices. Copying an estimate writes only the summary you requested to your clipboard. Read the privacy disclosure.