A 24/7 YouTube loop needs disk space for the files you keep on the Contabo VPS, not for every replay. One video that plays continuously remains one video file on disk; your estimate should also include Ubuntu, streaming software, logs, temporary working space, and any backups or alternate encodes.
There is no universal plan that suits every loop. Check the actual file sizes and workload, compare their total with the usable capacity shown for the plan, and leave room for routine operation rather than filling the disk to its limit.
Start with the files you will keep
Begin with an inventory, not a plan name. Write down each item that will remain on the VPS: the main video, alternate versions, graphics, audio files, playlists or configuration files, and any backup copy stored there. Add their actual sizes. The answer depends on what is retained at the same time.
A single 20 GB source file contributes about 20 GB to that inventory whether it plays for an hour or for a month. If you keep a second 20 GB copy on the VPS, the two copies contribute about 40 GB. If you replace the original with a smaller encode and delete the original, count only the version that remains; if you keep both, count both.
This is different from a video library where the stream cycles through many files. A folder containing several videos occupies the sum of those files’ sizes, even if only one is playing at any given moment. Likewise, images and audio retained alongside the loop count towards storage, but the time spent on air does not add another copy.
Make the inventory reflect the working arrangement you intend to use. If you upload a source, encode a smaller delivery copy, and keep both during testing, both occupy space during that period. If the source is removed after the final version is checked, it no longer contributes to the steady-state requirement. Be clear about whether you are sizing for setup day or normal operation.
For a visual loop, the source itself may be one long clip or a set of clips played in sequence. A seamless fireplace loop guide can help with the playback side, but a seamless transition does not change the capacity calculation: count the files that are actually present.
Why replaying a video does not add copies
A playback application reads the file repeatedly and sends encoded audio and video towards YouTube. Reading the same path again does not, by itself, create another copy of the source. The disk holds the file once; the live output is a continuing stream of data over the network.
Disk use can still change for other reasons. You might create a second encode, download a replacement, save a recording, or accumulate temporary files. Those are separate files or data, and they should be counted if they remain on the VPS. They are not an automatic consequence of pressing repeat.
This distinction matters because storage and bandwidth answer different questions. Disk capacity is about the data you retain. Bitrate is about the amount of live data sent over time. A stream can send the same video content again and again without expanding the source file on disk, while its outbound network use continues for as long as it is live.
YouTube’s live encoder settings describe recommended live ingest settings by codec, resolution, and frame rate. For H.264 at 1080p and 30 frames per second, the guide lists 5–14 Mbps. That is a stream-setting range, not a required source-file size or a disk multiplier. A different codec, quality target, or frame rate changes the relevant output choice, not the fact that a single retained file remains a single file.
A useful mental model is two separate ledgers. In the disk ledger, record each file kept at rest. In the network ledger, consider the chosen live bitrate and the duration of broadcasting. Do not multiply the first ledger by the number of replays, and do not treat a large disk as proof that the network path can carry the stream reliably.
Calculate the source-file footprint
Use the file manager or a command that reports the actual file size, rather than estimating from duration alone. Two clips of equal length can occupy very different amounts of space because compression, codec, resolution, frame rate, and image complexity differ. A file’s extension does not tell you its exact size.
Then list every version that will be kept. For example, suppose a channel has a 20 GB master file and a 7 GB delivery encode. If both remain on the VPS while you compare them, the video portion of the inventory is 27 GB. If you remove the master after checking the delivery file, the steady-state video portion is 7 GB. These figures illustrate the addition of stated file sizes; they are not a benchmark for any Contabo plan or an expected size for a particular duration.
For a playlist, add the files together. If a devotional channel stores several bhajan videos, an opening slate, and a closing graphic, count each retained item once. If some assets are downloaded only when needed and are not kept locally, they should not be included in the VPS’s retained-file total. Do include any local cache or scheduled download that your setup deliberately keeps.
If you do not yet have the final export, use a representative test file cautiously. A short sample can show the approximate file size per minute for that export’s settings, but it cannot guarantee the final size if the full video has different scenes or encoding behaviour. Once the actual file is ready, replace the estimate with its measured size before choosing capacity.
Reducing file size can lower the source-file portion of the total, but changing an export can affect visual quality or compatibility. The MP4 size reduction guide explains that trade-off. Keep the original during a trial only if you need it; the storage worksheet should reflect whether it will still be there after launch.
Add Ubuntu, software, logs, and working space
The video is not the entire VPS disk. Ubuntu and installed packages occupy space, as do the streaming application, its settings, and other tools you choose to run. The exact requirement depends on the installation and updates, so do not substitute a generic operating-system allowance for checking the disk actually used on your machine.
Logs and caches are also part of ordinary operation. A running service may write diagnostic information, and package updates or an encode may need temporary files. If you are troubleshooting a dropped stream, logs can help explain what happened, but retaining every log indefinitely is not always useful. Set sensible retention and check that logs are not growing without limit.
Working space matters most during changes. Uploading a replacement before deleting the old file means both versions are present temporarily. Re-encoding locally on the VPS can require the input and output at once, plus temporary data created by the software. A copy operation may also briefly need room for both source and destination. Size for the state you will actually create, not only the clean final folder.
Create a simple worksheet with separate rows for video files, other media, operating system and software, logs and caches, and temporary work. Some values may be measured after installation rather than known in advance. That is fine: mark them as estimates, check them on the running VPS, and revise the remaining headroom rather than pretending the first calculation is exact.
Free space is operational capacity, not wasted capacity. If the disk is nearly full, an update, a new upload, or a log write may fail at the moment you are trying to recover the stream. Leave space for ordinary changes and investigate what is using it when the available amount falls unexpectedly. The OBS crash recovery article is about a different failure mode, but it illustrates why recovery procedures matter alongside the file inventory.
Account for backups and alternate encodes
A backup stored on the same VPS is another retained copy and consumes space there. It may protect against accidentally overwriting a file, but it does not protect the data if that VPS or its disk becomes unavailable. If you keep a separate copy elsewhere, count it in that other location’s storage plan, not in the VPS total. Decide which copy is meant to help with which failure.
Alternate encodes are common when you are testing resolution or compatibility. Count every version left in the folder. A 20 GB original plus a 12 GB alternate is 32 GB of video files while both are retained. If you delete the unneeded version after testing, the ongoing footprint falls accordingly. The calculation is based on the given sizes, not on how often either one plays.
Do not confuse an upload staging folder with a backup policy. A partially uploaded replacement or an old export may be forgotten and sit alongside the production file. Use clear names, verify the new file before removing the previous one, and retain a copy somewhere appropriate if losing the source would be costly.
If the channel uses a folder of videos rather than a single asset, its total can grow through routine additions. Set a simple review habit: after a new episode or seasonal loop is uploaded, remove files that are no longer required, after confirming that the current stream uses the intended file. For playlist-based playback, the folder playback guide may help you think through the retained set, but storage still depends on the contents of that folder.
Compare the total with VPS disk capacity
Once the inventory is complete, compare it with the capacity listed for the VPS and reserve room for the system, updates, temporary work, and normal variation. Do not assume the nominal disk figure is all free for video. The installed operating system and other files consume part of the available capacity, and a plan that only fits the present files with no room to work is a poor fit for a channel that needs occasional maintenance.
Contabo documents distinct VPS families and their storage options. Its Storage VPS documentation lists capacities from 300 GB to 1.4 TB SSD and describes the family as suited to storage-heavy use. Its VPS documentation also describes Core and Performance VPS families with different listed storage ranges and storage types. These are vendor specifications, not evidence that any particular plan is sufficient for your workload. Check the current capacity, terms, and upgrade procedure on Contabo’s site before ordering; plan details can change.
| What you are comparing | What to count or check | What it tells you |
|---|---|---|
| Retained media | Main file, playlist assets, alternate encodes, and local copies | The video and media portion of disk use |
| System and operation | Ubuntu, software, logs, caches, and temporary work | Space needed beyond the media files |
| Usable room | Current free disk and room for updates or replacement uploads | Whether routine changes can fit without filling the disk |
| VPS capacity | The chosen plan’s documented disk capacity and family | Whether the planned total fits the offer you are considering |
| Streaming workload | Encoder method, resolution, frame rate, bitrate, CPU and RAM needs | Whether the VPS can do the work, a separate question from storage |
| Network conditions | Port and traffic terms, plus the actual route to YouTube | Whether continuous outbound streaming is plausible to test |
A large-capacity storage-oriented VPS may suit someone whose main constraint is retained media. Another family may be more appropriate when compute performance or a different storage type matters. Do not choose NVMe simply because video is playing, nor choose a storage-heavy family solely because the disk number looks large. A prerecorded file sent without re-encoding and a workload that encodes live can place different demands on CPU and memory. Check the method you plan to use and the relevant resources as well as disk.
Storage capacity does not establish stream reliability. YouTube’s streaming tips advise leaving upload bandwidth headroom and testing and monitoring stream health. The traffic sent by a continuous broadcast is separate from the stored source; Contabo also publishes fair-use terms for network traffic in its product information. Verify those current terms and test the actual stream rather than inferring performance from a disk specification.
If you would rather not keep a computer on or manage server files and restarts, StreamNeo removes the specific chore of keeping your own machine running for the loop: you upload the video, connect the YouTube stream key, and the broadcast can run with your computer switched off. It is YouTube-only, so make sure that matches the channel you are operating.
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
Does looping a video use more storage?
No. Replaying one file does not make extra copies of it on disk. Storage rises only if your setup creates or retains additional files, such as another encode, a backup, a recording, or temporary work.
How much space does a 24/7 loop need on Contabo?
Add the actual sizes of all files you will keep, then include the operating system, streaming software, logs, working space, and free room for normal operation. Compare that total with the usable capacity of the specific VPS you are considering; no plan can be called sufficient without the capacity and workload details.
Does bitrate change the disk size of my source video?
The live bitrate describes the outgoing stream, while the source file’s size is a property of the retained file. A bitrate choice affects network use and the encoder setup, not the number of copies of the source that looping creates. If you export and retain a separate file at another quality, count that file separately.
Should I keep a backup on the same VPS?
You can, but count it as another copy and remember that it shares the VPS’s failure exposure. A separate backup location may be more useful if your concern is losing the VPS or its disk. Keep the backup policy clear and leave enough room for any temporary overlap while replacing the live file.