For a week of continuous local recordings, multiply the saved file’s total bitrate by 604,800 seconds, then divide by eight to convert bits to bytes. Convert that byte count to GB or TB and leave room for overhead and other files; it is an estimate, not an exact disk requirement.
The key detail is to use the bitrate of the recording you will keep, not simply the stream’s resolution or the rendition a viewer happens to watch. If your recorder saves a re-encoded file, use that file’s bitrate. If it stores the incoming stream, use the incoming video and audio rates together.
The weekly storage formula
The basic calculation is:
Estimated bytes = total recording bitrate in bits per second × recording duration in seconds ÷ 8
The bitrate is expressed in bits per second, while file sizes are expressed in bytes. Since one byte contains eight bits, dividing by eight converts the result. For seven uninterrupted days, use 604,800 seconds: seven days multiplied by 24 hours per day, 60 minutes per hour, and 60 seconds per minute.
For example, suppose the saved recording has a sustained total bitrate of 5 Mbps. Convert that to 5,000,000 bits per second, multiply by 604,800 seconds, and divide by eight. The result is 378,000,000,000 bytes, or 378 GB using decimal units. This is the calculated media size under those inputs, before allowing for file-system use, other content, or differences in actual recording duration and bitrate.
Keep the units consistent. A bitrate written as 5 Mbps means five million bits per second in this decimal calculation. If you have a rate in Kbps, convert it to Mbps or to bits per second before combining it with other rates. Do not divide a number already expressed in bytes per second by eight again.
The formula scales directly with both bitrate and time. Double the sustained bitrate for the same duration and the calculated bytes double. Keep the bitrate and record for twice as long, and the result also doubles. That makes it useful both for selecting an archive drive and deciding how many days or weeks of recordings to retain.
Start with the saved file’s total bitrate
The saved file is the basis for storage planning. A live encoder may send one bitrate to YouTube, while local recording settings may save at a different bitrate. Some recording workflows preserve the incoming stream; others encode a separate local file. In the latter case, the saved file’s rate can differ from the live ingest setting, so the encoder’s stream target is not automatically the right input for the storage formula.
If video and audio rates are shown separately, add them first. For instance, 10 Mbps of video plus 128 Kbps of stereo audio is 10.128 Mbps total, because 128 Kbps is 0.128 Mbps. That is the total rate to use if those are the rates in the local recording. With the week-long multiplier, it works out to about 765 GB decimal before overhead.
The example is a calculation from its stated inputs, not a promise that every file with those settings will have exactly that size. A variable-bitrate recording can average below or above its target. A container, metadata, and recording interruptions can also affect the final file or the amount of content saved. Check an existing local recording’s properties or the recording software’s output settings, rather than inferring the rate from a title, resolution label, or playback quality.
YouTube’s live recommendations can help when the local recording uses the same settings as the stream. Its live encoder settings and bitrate guidance provides recommended ingest video rates by resolution, frame rate, and codec, as well as an audio recommendation. Use the matching row only as an input when it genuinely describes the saved recording. YouTube separately documents recommended upload encoding settings; upload guidance is not a substitute for checking the local file’s actual bitrate.
This distinction matters because YouTube says it automatically transcodes a live stream into different output formats for viewers. A viewer’s playback rendition is therefore not a sound basis for estimating the size of your local archive. Size the file you are keeping, not a version YouTube prepares for playback.
Calculate seven days of recording
For a sustained total rate of 1 Mbps, the calculation is 1,000,000 bits per second × 604,800 seconds ÷ 8. That gives 75,600,000,000 bytes in a full week. Repeat the same multiplication using your actual total recording bitrate in bits per second for a personalised estimate.
Here are a few worked inputs. These examples show calculated media sizes in decimal units, before practical allowances. The YouTube bitrate figures are live ingest recommendations, not measurements of local files; apply them to a local archive only if those settings describe what you record.
| Example input | Total bitrate used | Seven-day estimate |
|---|---|---|
| 1 Mbps sustained recording | 1 Mbps | 75.6 GB |
| 5 Mbps sustained recording | 5 Mbps | 378 GB |
| 10 Mbps video plus 128 Kbps audio | 10.128 Mbps | About 765 GB |
| 14 Mbps video plus 128 Kbps audio | 14.128 Mbps | About 1.067 TB |
The last two examples add the stereo audio rate to the video rate before applying the formula. Their video inputs correspond to settings in YouTube Help’s live guidance; they do not describe what every encoder, local recorder, or channel will produce. For a 24/7 music channel, for example, the recorded video might be a static visual loop while the audio is continuous. The storage calculation still depends on the rate of the saved file, not on the type of channel.
The duration also needs to match your real recording plan. Seven days without a gap is 604,800 seconds. If the recorder is stopped for maintenance or a file is only retained for the hours it is needed, use the actual recording duration instead. Conversely, a file that contains an extended slate, standby picture, or other material still consumes storage for as long as it is recorded.
Convert bytes to GB or TB
For decimal capacity, divide bytes by 1,000,000,000 to obtain GB, or by 1,000,000,000,000 to obtain TB. The 5 Mbps example produces 378,000,000,000 bytes: 378 decimal GB, or 0.378 decimal TB. The 14.128 Mbps example produces about 1,067,000,000,000 bytes: about 1,067 GB, or about 1.067 TB.
Drive packaging and some operating systems may label or display capacity using different unit conventions. A value in binary units is not numerically identical to the same label in decimal units, so check what units your calculator and drive display are using before comparing a calculated byte count with the advertised capacity. This is a unit-conversion issue, not a change in how much recorded data exists.
It is also easy to mix up bits and bytes. A rate in Mbps is megabits per second; a file size in GB is gigabytes. The divide-by-eight step converts bits to bytes, while the later division by a billion converts decimal bytes to decimal GB. Those are separate steps. Skipping either one, or applying one twice, can make the estimate wrong by a large factor.
For a spreadsheet, keep one clearly labelled input cell for total bitrate in Mbps, calculate bytes as bitrate × 1,000,000 × 604,800 ÷ 8, then divide by one billion for decimal GB. Add a separate input for duration if you plan to model shorter recordings or retention periods. Label the output as an estimate and record whether it is a media-only figure or includes your chosen headroom.
Quick estimate per 1 Mbps
For exactly seven days, each 1 Mbps of sustained total recording bitrate works out to 75.6 GB decimal. This shortcut comes directly from the formula above; it is not a published YouTube statistic. Multiply 75.6 by the total rate in Mbps to get the unpadded weekly estimate in decimal GB.
| Sustained total recording rate | Decimal estimate for one week |
|---|---|
| 2 Mbps | 151.2 GB |
| 5 Mbps | 378 GB |
| 8 Mbps | 604.8 GB |
| 12 Mbps | 907.2 GB |
| 20 Mbps | 1,512 GB, or 1.512 TB |
This is useful for comparing likely recording settings before running a test. It is not a guarantee that a variable-bitrate or separately encoded file will match the result. If the reported video rate is 8 Mbps and the audio rate is 128 Kbps, use 8.128 Mbps, not 8 Mbps, for the combined-rate estimate.
You can also reverse the shortcut when you have a fixed amount of space and want a rough sense of what fits. Divide the available decimal GB by 75.6 to estimate the Mbps you could sustain for a week, then leave a margin for non-recording files and operational needs. This reverse calculation is only a planning check: usable space may be less than a drive’s nominal capacity, and the stream may not run or record continuously at the assumed rate.
If you are adjusting encoder settings to reduce storage, remember that bitrate is only one part of the decision. Resolution, frame rate, codec, image motion, audio quality, and the purpose of the archive all matter. The practical guide to live-stream bitrate, latency, and stability can help you weigh a lower target against the stability and picture quality you need, rather than treating smaller files as the only goal.
Allow for overhead and headroom
The calculation estimates the bytes of recorded media implied by a bitrate and duration. It does not tell you the exact disk capacity to buy. Leave additional usable capacity for container overhead, filesystem use, logs or other files, and recording headroom. No single allowance suits every workflow, so base it on the software and the drive’s other jobs rather than applying an unexplained universal percentage.
A practical way to choose a margin is to record a representative sample using your actual settings, inspect its size and duration, and compare the observed rate with the estimate. Then consider what else will share the drive and whether recording must continue while files are being copied, checked, or deleted. A drive filled to its limit leaves little room for a new file to start or for normal housekeeping.
Plan retention as well as capacity. If you keep two weeks rather than one, the media-only estimate doubles at the same sustained rate. If each week is archived to another device and removed from the recording drive, the active drive may need space for a different part of the workflow. Write down whether the capacity is for one working week, several retained weeks, or both an active and a backup copy.
For a local archive, compare the recorder’s output mode, expected bitrate, audio rate, file-splitting behaviour, and retention period. A playlist that repeats continuously on YouTube Live may run as one long broadcast, but that does not dictate whether you save one continuous local file or separate segments. Those recording choices affect how you organise and manage storage, even when the total recorded duration is the same.
If local files are not needed after the live broadcast, you may not need a week-long local archive at all. If they are needed for editing, recovery, or later review, choose a retention period deliberately and test the full process before relying on it. A static-image 24/7 nature-sounds stream is one example where the live visual may look simple, but the saved audio and video file still needs to be sized from its actual recorded rate.
When your storage concern is specifically the computer needing to remain on for the broadcast, StreamNeo removes that particular burden by running an uploaded video as a YouTube live stream while your computer is off. That addresses broadcast operation, not a guarantee about how much local archive capacity you should retain; storage estimates still follow the file and retention plan you choose.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Is one week always 604,800 seconds?
It is 604,800 seconds for seven uninterrupted 24-hour days. If your recording has planned gaps or a shorter daily schedule, multiply the bitrate by the actual total recording seconds instead. Use continuous duration when the recorder is expected to capture the stream without breaks.
Should I use the YouTube stream bitrate or the file bitrate?
Use the bitrate of the file you are saving. If the local recording preserves the incoming stream, the ingest bitrate may be an appropriate input; if the recorder re-encodes it, use that output file’s rate. Add video and audio rates when they are listed separately.
Is the result an exact disk requirement?
No. It is a calculation from the assumed bitrate and recording duration, and actual file size can differ. The estimate also excludes practical allowances for overhead, filesystem use, other files, and headroom, so choose capacity above the calculated media size.
How much space should I plan for several weeks?
Calculate one week from the saved file’s total bitrate, then multiply by the number of weeks you intend to keep at that same duration and rate. Add room for overhead and other drive use, and account for any working copy and backup copy you plan to retain.