For a 24/7 recorded education stream, plan storage from the total average bitrate being saved and the length of time you need to keep recordings. As a starting estimate in decimal units, multiply total recorded bitrate in Mbps by hours and by 0.45 to get GB; then account for other feeds, copies and operating headroom.
A continuous recording at 1 Mbps uses about 10.8 GB per day before overhead. Resolution alone cannot tell you how much space you need: two 1080p recordings can have different bitrates, and audio, additional renditions and backups all add to the stored total.
What determines storage for a continuous recording
The basic inputs are the average bitrate written to storage and the duration of the recording. Bitrate is the amount of encoded data produced over time. At a constant bitrate, keeping the recording twice as long takes roughly twice the media space; doubling the bitrate has the same effect. In practice, variable-bitrate encoding and changes in scene complexity can make the average differ from a setting or target value.
For an education channel, the recorded material may include slides with small text, a teacher writing on a board, camera demonstrations, screen capture, or a quiet lecture with little movement. Those are different pictures for an encoder to represent. A resolution label does not capture all that, and it does not include how the audio is encoded or whether a separate recording is being made.
Start with the output of the recorder you will actually use, not a bitrate copied from an unrelated example. A live platform’s ingest recommendation can help you choose a starting point, but your local recording might use another encoder setting, codec or quality mode. If the recording tool reports an average bitrate or the resulting file size, that is more useful for storage planning than resolution alone.
A representative sample is worth making before you buy a drive or commit to an archive plan. Include the kinds of lessons you will actually stream: a slide with fine print, a writing demonstration, ordinary movement and the intended audio. If the size of that sample varies substantially from one lesson to another, use a cautious average for planning and leave room for unusually large files.
Once you know how the continuous source will be prepared, file choices matter too. The guide to preparing video files for a 24/7 YouTube stream covers practical preparation; here, the key is to measure the file or output your chosen workflow produces rather than infer storage from a video’s dimensions.
Use the bitrate-hours estimate
Use this estimate for media payload in decimal units:
GB ≈ total bitrate (Mbps) × hours × 0.45
The coefficient converts megabits per second over a number of hours into an approximate number of gigabytes. It is a planning shortcut, not a capacity guarantee or a claim about a particular recorder. At 24 hours, the estimate is about 10.8 decimal GB for each 1 Mbps of total recorded bitrate. Multiply that daily amount by the number of days you intend to retain the material.
For example, if the total recorded bitrate averages 4 Mbps, a day is approximately 4 × 24 × 0.45, or 43 GB. Thirty days is approximately 1.3 TB in decimal units, before extra feeds, copies and overhead. Those rounded figures make the scale easier to see; they are not exact capacity requirements. Use the same method with your own measured bitrate and retention period.
Keep the units consistent. Mbps means megabits per second, while file sizes are commonly shown in megabytes or gigabytes. Do not enter a figure in MB/s as if it were Mbps. For a bitrate that changes over time, calculate using a representative average over an ordinary recording, then use a higher planning assumption if your lessons sometimes produce larger files.
You can also reverse the calculation. If you have a known usable capacity and a desired retention period, divide the available decimal GB by 0.45 × total Mbps × hours per day to estimate how many days one stream could fit. Do not treat the result as a promise that the drive can be filled completely: the recorder, operating system and any parallel copies need space too. A sensible plan stops below the nominal limit.
If your recordings feed a repeating live playlist, storage needs may not match the amount of source material held at any one moment. Think separately about the archive you retain and the playlist files you keep available for broadcast. The guide to streaming a YouTube playlist continuously with OBS is relevant to the playback workflow, while the estimate here is for the bytes your recording process actually saves.
Count video and audio bitrate
Add video and audio before using the formula. If the video is 6 Mbps and the audio is 160 Kbps, convert 160 Kbps to 0.16 Mbps and use a total of 6.16 Mbps. Leaving out audio may not change the estimate as much as omitting a whole extra video feed, but it still understates what the recorder writes.
Check whether the displayed bitrate is video-only or a combined stream rate. Some interfaces show separate values, others report a total, and a recording container can include data beyond the encoded picture and sound. Avoid adding audio twice if the number you obtained already includes it. When the software provides no clear average, inspect a sample file’s properties or use the recorder’s own reporting tools, then record your assumptions alongside the calculation.
Audio can also vary. A lecture might have a microphone, music bed or other audio source; the final encoded audio rate depends on the configuration you use. The important thing is not to assume that a silent-looking slide stream has zero audio storage. Include the actual audio track even when it sounds quiet.
Use the settings as a quality decision as well as a storage decision. Lower bitrate generally means less space, but fine text, handwriting or movement may become harder to see. YouTube’s official live encoder settings guidance gives H.264 reference recommendations of 10 Mbps for 1080p30 and 12 Mbps for 1080p60. These are platform guidance, not a universal rule for local recording, and they do not tell you what your recorder will save.
YouTube also advises testing with audio and movement resembling the intended stream. That is a useful discipline for a classroom or study channel: a static title slide is not a representative test for a teacher writing equations or moving between a document camera and a screen. Make a sample, check legibility, and use the measured result to size storage.
Work through the 6.16 Mbps example
Suppose the recording uses 6 Mbps video plus 160 Kbps audio. The audio converts to 0.16 Mbps, making the combined rate 6.16 Mbps. Applying the formula gives these rounded planning estimates:
| Retention period | Calculation | Approximate media payload |
|---|---|---|
| 24 hours | 6.16 × 24 × 0.45 | 66 GB |
| 30 days | 6.16 × 24 × 30 × 0.45 | 2.0 TB |
| 365 days | 6.16 × 24 × 365 × 0.45 | 24 TB |
These are decimal estimates derived from bitrate and duration arithmetic, not measured results or guaranteed capacity requirements. The 24-hour figure is roughly 66 GB, and retaining the same one stream for a month brings the estimate to about 2.0 TB. A year is around 24 TB before overhead, additional recordings or backup copies. Rounding is deliberate: the assumptions are approximate, and a real encoder’s average output can differ.
The numbers apply only if 6.16 Mbps is the total bitrate of one recorded stream and the recording is retained for the stated period. If that rate is video-only, add the audio rate. If it represents a stream that is also saved as a separate rendition or copy, count the additional output too. This distinction is often the difference between a useful planning estimate and a drive that fills earlier than expected.
Do not read “2.0 TB” as a recommendation to buy a drive labelled 2 TB for a month of recordings. That estimate is media payload only, with no allowance for file system, container overhead, fluctuations in output, other files or a safety margin. In addition, a computer may show available storage in binary units even when the drive’s advertised capacity is expressed in decimal units. Compare usable capacity as shown by the system, not only the label on the box.
Adjust for renditions, feeds and backup copies
Count every distinct recording that occupies space. A service or encoder may save a high-quality master and a lower-bitrate copy for review, or multiple renditions for different playback needs. If each is retained for the same period, estimate each output separately and add the results. Do not multiply automatically if the system replaces an old file or stores only one version; count what remains on disk at the same time.
Separate camera and screen feeds need the same treatment. If the recorder stores a camera angle and a screen capture as two independent files, size each based on its own bitrate and duration. A composite picture that combines both sources into one encoded output is a single stream for this calculation. Know whether your workflow saves isolated tracks as well as the final programme, particularly if you may want to edit or retrieve a lesson later.
Backups are another full capacity decision, not a small overhead. A second complete copy of the archive roughly doubles the media payload being held across both locations. If you retain a local working copy and an off-site copy, calculate each copy’s retention period and storage class separately. A shorter off-site retention window, or backing up only selected lessons, changes the total and should be explicit in the plan.
Cloud storage can suit an off-site archive or a team that needs access from more than one place, while local storage gives you direct access without depending on a download. Costs and suitability depend on the retention and retrieval pattern; cloud planning may also need to include metadata and different renditions. For example, Amazon IVS recording documentation describes recorded media and metadata being written to an S3 prefix. That documents a recording path, not a recommendation or current cost for every education channel.
A local hard drive or NAS drive is a direct option when you need recordings close at hand. Compare usable capacity, write workload, access by the people who need the files, warranty and how you will recover data if a drive fails. An off-site copy addresses a different risk than having more space in the same room. Neither approach removes the need to decide what can be deleted and when.
Allow for overhead and operating headroom
The formula estimates the encoded media payload. Actual occupied space can be higher because of container and file-system overhead, recording variation, ancillary files and the way the recorder splits or indexes long recordings. The research arithmetic does not specify a universal overhead percentage, so do not add an invented fixed percentage and call it exact. Instead, treat the estimate as a baseline and leave practical headroom.
Headroom means the system can keep recording while a file is finalised, a new recording starts, temporary files are written or an archive copy is made. A nearly full drive can also leave no room for other work or for correcting a mistaken retention setting. Decide on a reserve based on how the recorder behaves and how you manage files; check the usable capacity and remaining space over time rather than planning to use every last labelled gigabyte.
If you record on the same computer that plays or manages the stream, consider what else shares that storage. Source videos, editing exports, logs and operating-system files are not part of the bitrate formula, but they consume the same usable space. Keeping the recording destination separate from the system drive can make it easier to see what the archive is using, although it does not by itself provide a backup.
For a cloud archive, distinguish stored payload from other possible charges and requirements. The amount of data retained is one part of the plan; how often people retrieve it, how quickly they need it, and whether metadata or alternate renditions are kept can affect the choice. Check the provider’s current official documentation and pricing before selecting a storage class. Avoid treating an example from one provider as a general cloud-storage price.
There is also an operating choice behind the storage calculation. Running a recorder continuously from your own computer means that computer and recording workflow need to continue through the night. If the pain point is keeping a machine on solely to transmit a prepared file, StreamNeo can remove that particular burden by running the uploaded video as a 24/7 YouTube live stream while your computer is off; it does not change how much archive storage your own retained recordings require.
Plan capacity against retention time
Choose the retention period before choosing a drive. A school or tutor may need recent lessons for revision and older sessions only for a shorter review window; another organisation may need an archive for an entire course cycle. The calculation is straightforward once you decide how long each recording stays, but retention should follow the real access need rather than a vague intention to keep everything.
A simple planning sequence is:
- Decide how many days or months each recording must remain available.
- Measure or estimate the recorder’s average total bitrate, with audio included.
- Calculate
Mbps × hours × 0.45for decimal GB, then multiply by recording duration. - Add each simultaneously retained rendition, isolated feed and backup copy.
- Allow for overhead and operational headroom, then compare the plan with usable capacity.
- Set a review or deletion rule so retention does not grow unnoticed.
For a 24/7 channel, hours are continuous, not just teaching hours. If the encoder records a loop or a holding slate between lessons, it still produces a file for those hours. If recording is intentionally paused overnight or between classes, use the actual hours saved rather than 24 for each day. Write that assumption down so the next capacity estimate reflects the real workflow.
If space is tight, options include shortening retention, reducing the recorded bitrate where quality allows, keeping selected lessons rather than every stream, or moving older material to a different archive. Each choice has a cost: shorter retention can remove useful revision material, lower bitrate can reduce legibility, and off-site storage can add retrieval time or charges. Test changes on a representative lesson before applying them across a term.
Use the internal guide to creating a YouTube radio station or always-on channel when mapping the continuous channel workflow, but keep the archive decision separate. For a live channel, changing a playlist or source does not necessarily mean old recordings are deleted; check where files are stored and how your recorder handles them.
The final purchase comparison should use total usable capacity and the measured retention plan. Include whether you need local access, off-site protection, sharing for teachers, write capacity during continuous operation, recovery arrangements and cloud retrieval. No particular drive has been tested here. Size it from the workload rather than selecting by a “24/7” or “1080p” label.
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 many GB does a 24-hour stream use?
It depends on the total average bitrate recorded, including audio. As a planning estimate, each 1 Mbps uses about 10.8 decimal GB over 24 hours before overhead; for the 6.16 Mbps example in this article, the rounded estimate is about 66 GB for a day.
Is 1080p enough information to estimate storage?
No. Resolution does not tell you the recorder’s bitrate, whether audio is included, or whether multiple feeds and copies are being saved. Use the actual recording settings or measure a representative file, then calculate against the retention period.
Should I include a backup drive in the calculation?
Yes, if it holds another retained copy of the same recordings. Estimate that copy separately and add it to the total capacity across your locations; a second full archive roughly doubles the payload held, before overhead.
Is the 6.16 Mbps figure a drive recommendation?
No. It is an arithmetic example using 6 Mbps video and 160 Kbps audio, with rounded decimal estimates. Your recorder’s output, extra renditions, feeds, copies and overhead determine the usable capacity you should plan for.