To estimate storage for a 30-day library of pre-recorded YouTube streams, multiply the local recording’s combined bitrate by the seconds you will record, then divide by eight. The result is an estimate of the media data represented by those inputs, not a universal file size or a complete drive-capacity recommendation.
For a continuous 1080p30 example using YouTube’s recommended H.264 video bitrate and stereo audio bitrate, the calculation comes to about 3.28 decimal TB, or 2.98 TiB, before headroom and other files. Your own total will change with the recording settings, daily hours, retention period and copies you keep.
Define what you are estimating
Start by separating the local library from the stream viewers watch. This calculation estimates the size of the recorded source files on your own storage, using their bitrate and recorded duration. It does not estimate every version YouTube may make for playback, nor does it automatically include project files, logs, backups or spare drive capacity.
That distinction matters because YouTube processes a completed broadcast into a video and may make it available after processing. The Google for Developers LiveStreams documentation describes the relationship between a broadcast and its resulting video; it does not give a local-library capacity figure. If you need an archive you control, calculate the capacity for your own recordings separately from what appears on the channel.
A 30-day library can mean two different things. It might mean a recording that runs continuously for 30 days, or files covering some shorter number of hours on each of 30 days. Use the hours you actually intend to retain rather than treating “30 days” as a fixed file size. A devotional channel recording around the clock, a study channel recording only its evening sessions, and a business replaying a short loop have different totals even if each keeps a month of material.
The estimate is useful for choosing a capacity range and comparing storage options. It is not a guarantee that a drive with that headline capacity will have that much free space after formatting or that your encoder will hold one exact data rate throughout every recording. Keep those decisions separate: calculate the media estimate first, then allow for the way you operate and preserve the library.
Use bitrate multiplied by recorded time
The reproducible formula is:
Storage in bytes = total bitrate in bits per second × recording duration in seconds ÷ 8
Bitrate is a rate of data; duration is the time for which that rate is recorded. Their product gives bits, and dividing by eight converts bits to bytes. If a recording uses a configured or measured average bitrate, use that figure for the estimate. If you only know a target bitrate, recognise that it is an input to an estimate, not proof that every saved file will land on the calculated size.
For continuous recording, work out the time explicitly. Thirty days × 24 hours per day × 60 minutes per hour × 60 seconds per minute equals 2,592,000 seconds. If you record fewer hours, multiply the number of recording hours per day by the number of days and by 3,600 seconds per hour. For example, eight hours per day over 30 days is one-third of the continuous duration, so with the same bitrate its estimated media data is one-third as much.
Use consistent units before multiplying. A bitrate of 10 Mbps means 10,000,000 bits per second when using decimal megabits. Do not type “10” into a formula that expects bits per second: that would be off by the conversion from megabits. A spreadsheet can keep the inputs visible, for example with one cell for bits per second, one for seconds, and a result cell that divides their product by eight.
For a variable-bitrate recording, the target or maximum setting may not match the average across the entire file. A quiet, static ambience scene and fast-moving footage can produce different data rates under some encoder settings. If you have a completed sample recorded with the same settings and material, its file size over its duration can give a more relevant average for your planning; test a representative period, not only a brief opening scene.
Convert bytes to TB or TiB explicitly
After calculating bytes, state the unit system. Decimal units use powers of 1,000: divide bytes by 1,000,000,000 for GB and by 1,000,000,000,000 for TB. Binary units use powers of 1,024: divide by 1,073,741,824 for GiB and by 1,099,511,627,776 for TiB. TB and TiB are not interchangeable labels for the same quantity.
The storage industry commonly labels drive capacities in decimal TB, while some operating systems display a related capacity using binary-sized units or less familiar labels. That is one reason a new drive can appear to have less capacity in a computer’s storage view than its box suggests. Formatting and filesystem structures also use space. Those details are not part of the bitrate formula, so do not quietly fold them into the estimate.
For clarity, report both where it helps: “about 3.28 TB decimal (about 2.98 TiB binary)”. This lets someone compare your arithmetic with a drive sold in TB while also understanding a binary readout. If you use a different conversion convention, name it rather than leaving readers to guess.
Do not round intermediate values too early. Keep the bitrate and duration inputs intact through the multiplication, convert the final byte total, then round the displayed result to a sensible number of decimal places. A planning estimate is not made more reliable by displaying extra digits that the original bitrate assumptions do not justify.
Add audio and video rates correctly
If the video and audio settings are supplied separately, add their rates before multiplying by the duration. For example, 10 Mbps video plus 128 kbps audio is 10,000,000 + 128,000 = 10,128,000 bits per second. Converting both values into bits per second avoids mixing Mbps and kbps directly without a unit conversion.
YouTube Help’s encoder settings guidance lists recommended H.264 settings that include 10 Mbps video for 1080p30 and 128 kbps for stereo audio. The rates are useful inputs for an illustrative estimate, not a statement about the file size of every 1080p stream. Resolution alone does not specify the encoded bitrate, and another encoder setting or local recording profile can produce a different result.
Some software presents an overall rate, while other configurations list video and audio separately. If the displayed total already includes audio, do not add the audio rate again. If you record separate audio tracks or multiple audio languages, check whether their bitrates are additional streams in the saved file and count them only when they add data to the recording you retain.
The same approach works for other settings. YouTube’s guidance lists 6 Mbps video for H.264 720p60, alongside the 128 kbps stereo audio recommendation. The combined rate is 6.128 Mbps. That can be used in the formula for a separate estimate; it should not be treated as a promise that all 720p60 files will have a particular size.
Work through the 30-day example
For a continuous 1080p30 illustration, use the two YouTube Help recommendations above: 10 Mbps H.264 video and 128 kbps stereo audio. Add them to get 10.128 Mbps, or 10,128,000 bits per second. For 30 days without pauses, use 2,592,000 seconds.
The arithmetic is:
10,128,000 bits/second × 2,592,000 seconds ÷ 8 = 3,281,472,000,000 bytes
That is approximately 3.28 TB decimal, or 2.98 TiB binary. Dividing the same rate by 8 and multiplying by 3,600 seconds gives about 4.56 GB decimal for one hour. These figures are direct calculations from the stated bitrate and time. They are not measured recordings, a universal 1080p size rule, or a drive recommendation that includes spare capacity.
If the channel records eight hours each day for 30 days at the same combined rate, use 864,000 seconds rather than 2,592,000. That gives about 1.09 TB decimal of estimated media data before headroom. The shorter recording schedule changes the duration input; it does not change the bitrate assumption.
| Recording pattern and settings | Duration used | Estimated media data |
|---|---|---|
| 1080p30, 10 Mbps video + 128 kbps audio, continuous for 30 days | 2,592,000 seconds | About 3.28 TB decimal / 2.98 TiB binary |
| Same settings, eight hours per day for 30 days | 864,000 seconds | About 1.09 TB decimal |
| 720p60, 6 Mbps video + 128 kbps audio, continuous for 30 days | 2,592,000 seconds | About 1.99 TB decimal |
The table is a comparison of arithmetic inputs, not of measured files. For your planning sheet, replace the example’s bitrate with the combined rate for your own local recording and replace its duration with the real schedule. If a stream stops overnight or takes scheduled breaks, count only recorded seconds. If the file continues recording through a slate or standby image, those seconds remain part of its duration even if they contain little visual change.
Check the estimate against actual files
Once you have a representative recording, compare its size with the estimate. Record how long the sample ran, note the local encoding settings, and divide its byte size by its duration to derive an observed average rate. Convert bytes consistently if you want to compare that average with the bitrate used in the spreadsheet. A sample from the same type of content and the same recording configuration is more informative than a different channel’s file.
A single sample is a check, not a guarantee of future size. Content changes, variable-bitrate behaviour, audio configuration and interruptions can change the average. For a lofi station, one hour of still artwork and steady music may not behave like a local news loop with changing video; the only safe inference is about the tested material and settings. If file sizes vary, use the higher plausible sustained average for capacity planning rather than relying on the smallest sample.
Confirm that you are measuring the file you plan to keep. A remuxed copy, proxy, separately saved audio track or second quality version may add another file, while deleting a temporary intermediate may reduce retained space. Check a complete recording in the folder where your archive will live, not just a progress indicator while recording is underway.
For a broader always-on channel workflow, the article on using cloud video playout for an always-on YouTube channel covers the distinction between keeping a playback schedule running and preserving source files. If your question is about making a sequence repeat in a particular format, looping a playlist of Minecraft VODs is a separate operational problem from capacity arithmetic. Neither changes the need to calculate retained local files from their bitrate and duration.
Account for everything outside the formula
The formula covers only data represented by the bitrate and duration you supply. It does not include filesystem overhead, room for recordings to vary, a separate backup, duplicate quality versions, other channel assets or files you have not counted. Add these as separate planning items so that the estimate remains auditable. If the arithmetic says 3.28 TB, avoid describing that as “the drive you need” without first considering those extras and the usable capacity after formatting.
Choose headroom based on your own uncertainty and workflow. A channel with stable settings and a tested sample may choose a modest buffer; one whose settings or daily schedule change often may want more room. There is no YouTube-prescribed reserve percentage in the bitrate guidance. Write down the buffer as your decision, not as part of the formula or an official rule.
Backups also need separate arithmetic. If you keep a second complete copy, the media capacity for that copy is approximately another copy of the retained files, before each drive’s own formatting and overhead. A second drive in the same room can help if one drive fails, but it does not address every risk, such as theft, fire or mistakes copied to both locations. Decide what failure you are trying to recover from and keep the backup arrangement independent enough to serve that purpose.
YouTube Help’s archive guidance recommends recording a local archive as a backup and warns that a live stream longer than 12 hours may not be captured as an automatic archive. Treat that as an archive caveat, not a file-size limit or a guarantee about what will be available. If reliable retention matters, keep your own local recording and verify that it completed before deleting source material.
For one local library, compare an external drive by usable capacity after formatting, connection type, sustained transfer needs, portability and warranty. A second drive is relevant if you choose to keep an additional copy. A NAS may suit a shared archive or a collection you expect to expand, but it is not required to perform the calculation. You can also see how equipment choices for YouTube creators fit into a broader setup; storage capacity is still best chosen from your own recordings and retention schedule.
If the more pressing issue is that your computer must remain on to keep a playlist broadcasting, that is a different constraint from local archive capacity. StreamNeo can remove the need to leave your own computer running for the broadcast, while the storage estimate for files you retain still depends on your bitrate, duration and copies. Keep those two decisions separate when planning the channel.
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
How much storage do I need for 30 days of YouTube streams?
There is no single size without knowing the local recording bitrate and how many hours you record. At the example rate of 10.128 Mbps, continuous recording for 30 days works out to about 3.28 TB decimal before headroom, backups or other files; multiply by your actual recorded time and substitute your own rate.
How many GB is one hour of 1080p streaming?
It depends on the bitrate, not resolution alone. At the example combined rate of 10.128 Mbps, one hour is about 4.56 GB decimal by the formula; a different encoder setting, audio rate or average bitrate changes that estimate.
Does YouTube save the live stream automatically?
YouTube may archive a completed live stream, but its Help page says streams longer than 12 hours may not be captured as an automatic archive. If you need a dependable local copy, make and check your own recording rather than treating the channel archive as your only copy.
Do I need to count YouTube’s different playback resolutions?
No. The estimate here is for your local source recording, so do not multiply it by the number of viewer playback renditions YouTube creates. Count extra copies only if you also save those copies locally and plan to retain them.