For a 24/7 aquarium loop, start by matching the encoder’s output frame rate to the video file, then choose the corresponding 1080p H.264 bitrate. For a 30 fps source, a sensible first test is 1080p30, CBR, RTMPS and a two-second keyframe interval.
Those settings follow YouTube’s encoder guidance, but they do not guarantee that your internet connection will carry the stream continuously or that every viewer will see the same playback quality. You still need to test the actual file, upload path, audio and stream health before relying on the channel overnight.
A practical starting profile for an aquarium loop
If your aquarium footage is 1080p at 30 frames per second, begin with these encoder settings:
| Setting | Starting choice for 1080p30 | Why it matters |
|---|---|---|
| Resolution | 1920 × 1080 | Matches a standard 1080p source |
| Frame rate | 30 fps | Avoids creating extra frames when the source is 30 fps |
| Video codec | H.264 | A straightforward option supported by YouTube’s encoder guidance |
| Rate control | CBR | Keeps the encoder’s target bitrate consistent |
| Video bitrate | 14 Mbps recommended by YouTube | A starting point for 1080p30 H.264 ingest, not a connection guarantee |
| Keyframe interval | 2 seconds | YouTube’s recommended interval |
| Protocol | RTMPS | YouTube recommends the encrypted ingest connection |
| Colour and audio | Rec. 709, 8-bit SDR; stereo at 44.1 kHz and 128 Kbps | Suitable baseline values for a straightforward SDR feed |
These values come from YouTube’s encoder settings and bitrate guidance, checked in 2026. Treat its recommended bitrate as a target for what your encoder sends to YouTube, not as a claim about the upload capacity available where your stream is produced. A connection that cannot sustain the encoder’s output can still drop frames or disconnect.
The first decision is not whether 60 fps sounds better. It is whether the footage you have actually contains 60 distinct frames per second and whether the connection can support the higher bitrate. Aquarium footage often contains slow movement, but bubbles, fish and plants can still move quickly; inspect a representative stretch before choosing a profile.
If you need help making a file repeat in an encoder, the practical steps in looping a video in Streamlabs Desktop may be useful. Looping and encoding are separate tasks: a file can repeat correctly while the outgoing stream still has unsuitable frame rate, bitrate or audio settings.
Match output frame rate to the source
A frame rate describes how many frames the video presents each second. If the source was recorded at 30 fps, sending it at 30 fps is generally the most direct choice. Setting the output to 60 fps does not recover motion detail that the original file never captured; the encoder has to repeat or generate frames to fill the output.
For a 30 fps aquarium file, 1080p30 also keeps the bitrate target aligned with YouTube’s 1080p30 recommendation. Consider 60 fps when the source itself is 60 fps or when you have a clear reason to retain the smoother motion of a 60 fps recording. Watch a moving fish cross the frame, bubbles rise, and water flow over rocks. If those details look natural at 30 fps, a higher output rate may not add enough to justify the extra upload demand.
When the file’s frame rate is not obvious, check its properties in your editing or media application rather than guessing from how smooth it looks. Some files use variable frame rate or have been exported at a rate different from the camera original. For a continuous broadcast, use an export that has a clear, consistent frame rate, and test the exact file you intend to loop. A conversion can change motion cadence, so do not assume it will look identical to the original.
A useful way to compare is to encode a short section at each candidate rate and inspect the same motion on the YouTube preview. Keep the resolution, codec and other settings fixed while comparing; changing several values at once makes it harder to see what helped. If your source is 30 fps, the 60 fps test is an intentional conversion, not a neutral upgrade.
Choose H.264 bitrate for 1080p30 or 1080p60
YouTube’s current H.264 table lists 14 Mbps recommended and 5 Mbps minimum for 1080p30. For 1080p60 it lists 17 Mbps recommended and 6 Mbps minimum. These are platform ingest recommendations, not thresholds that promise stable transmission, clear playback in every condition or a particular result for an aquarium scene.
| H.264 output | YouTube listed minimum | YouTube listed recommendation | Practical consideration |
|---|---|---|---|
| 1080p30 | 5 Mbps | 14 Mbps | A natural starting profile for a 30 fps source |
| 1080p60 | 6 Mbps | 17 Mbps | More upload demand; use when the source or desired motion calls for 60 fps |
The bitrate is the amount of encoded video data sent each second. Water texture, moving fish, fine plant detail and low-light noise can all affect how much detail is difficult to preserve. A still aquarium image may seem simple, but the actual footage is what matters: ripples and moving particles change from frame to frame. Use representative footage rather than a static title card to judge the result.
Do not choose 60 fps simply because the number is larger, and do not treat the minimum as the ideal target. The minimum is a listed lower bound in YouTube’s guidance; it is not a recommendation to use that rate for a particular scene. If your connection cannot consistently support the recommended target plus the rest of your network traffic, test carefully and consider whether 30 fps better matches both the source and the available upload path.
Keep other activity on the connection in mind. A household backup, video call or another stream can compete with the encoder’s upload. The bitrate table cannot tell you what your connection will manage at the time of day you plan to broadcast. Measuring at that location and testing while the network is being used normally is more useful than relying on a headline speed from an internet plan.
Set CBR, keyframes and RTMPS
CBR means constant bitrate: the encoder aims to send data at a steady rate. For a long live broadcast, this is a simple way to configure the encoder against YouTube’s listed live guidance. The picture’s complexity still changes, so CBR does not mean every frame contains the same amount of visual information. It means the outgoing rate is controlled around the target you set.
Set the keyframe interval to two seconds. YouTube says the recommended frequency is two seconds and advises not to exceed four seconds. A keyframe is a reference frame from which later video frames can be decoded. The interval affects how the stream is structured; it is not a way to fix a weak connection or compensate for an unsuitable bitrate.
Choose RTMPS if your encoder offers it. It encrypts the connection between the encoder and YouTube’s ingest service. YouTube’s workflow is to copy the server URL and stream key from the Live Control Room into your encoder, start the encoder and check the preview before going live. Treat the stream key like a password: do not post it in a screenshot, share it publicly or leave it in a file you distribute.
A 24/7 channel may need to restart or replace a source file eventually, so keep a private record of the settings and connection details you used. Store the stream key securely and know how to revoke or replace it if it is exposed. If you are comparing ways to run a repeated file, software and FFmpeg approaches to looping on YouTube Live can help you think through the operating workflow, but the encoder’s bitrate and keyframe choices still need to be tested for your own stream.
Check upload capacity and stream health
The encoder’s target is only one side of the setup. The connection needs to carry the outgoing stream continuously, and other devices or processes may consume upload capacity at the same time. Run an upload test from the same computer or network that will broadcast, at the time and under the conditions you expect to use. A single measurement is a snapshot, not a promise that the route will remain unchanged overnight.
Use a wired connection where practical, pause large uploads during initial testing, and watch for network activity that competes with the stream. These are troubleshooting steps, not a guarantee of reliability. If your test shows that the available upload is close to the stream’s target or varies substantially, reduce other traffic, investigate the connection, or reassess the output profile before scheduling a long run.
YouTube’s Live Control Room preview and stream health indicators help reveal problems after the encoder connects. Check for warnings and watch whether the preview remains consistent. If video freezes or drops frames, examine the encoder’s dropped-frame and network statistics as well as the YouTube indicators. If audio is missing, distorted or out of sync, changing video bitrate alone will not solve it.
A useful test includes a period of normal network use rather than a quiet moment with everything else switched off. If the channel will operate from a small business or home in India, test on the actual broadband or mobile connection and at the intended location; the country or provider name cannot tell you how that individual line behaves. Keep an eye on the connection after the first successful preview, too. YouTube’s guidance is about ingest settings, not your local service conditions.
For a non-technical operator, the main benefit of a managed broadcast workflow is avoiding the need to leave a personal computer running and checking it through the night; StreamNeo removes that specific computer-off and restart burden for an uploaded video loop, while you still need to prepare the file, configure the YouTube channel and assess the resulting stream.
Test the complete loop before relying on it
Do a test broadcast using the exact file, encoder profile, audio track and network route you plan to use. YouTube advises testing before going live and monitoring audio, video and stream health. Check the YouTube encoder workflow for its current instructions on connecting an encoder and previewing the feed. Your own test should include the transitions where the video reaches its end and starts again.
Watch more than the first few seconds. A loop can look fine at the beginning but reveal a visible jump, black frame or silence at the file boundary. Check moving fish, bubbles and fine plants for blockiness or judder, and listen for clipped peaks, hum, an unintended soundtrack or a sudden volume difference. If the aquarium is meant to be quiet, confirm whether the source audio is silent or contains pump noise; do not assume the playback system will mask it.
A practical checklist is to verify that the stream title and privacy state are correct, the preview appears, the encoder reports no persistent connection trouble, motion looks acceptable and audio behaves as intended. Also confirm that the loop actually repeats for several cycles if the file is short. A single successful connection proves only that it connected at that moment, not that the setup is ready for uninterrupted use.
Keep a local copy of the source and note the settings that worked in the test. If you change the file, frame rate, bitrate, encoder, audio or network, test again: each change can affect the result. YouTube notes that a verified channel without live-streaming restrictions in the preceding 90 days is needed to go live, so check the channel’s current eligibility before planning a launch rather than discovering an account restriction at the start.
A looped aquarium feed is still your content. Use footage and audio for which you have the necessary rights. YouTube scans live streams for third-party matches and may replace a stream with a placeholder or interrupt it if matching material remains; a claim may also be made if the stream is archived. If you are uncertain about a soundtrack, use material you are entitled to broadcast and check YouTube’s current live-streaming policies.
Plan for archive and viewer controls
A continuous channel and a complete replay are different goals. YouTube says it can automatically archive streams under 12 hours, but a stream longer than 12 hours may not be captured at all. If preserving a replay matters, keep a local recording and make a plan for the archive rather than assuming a single 24-hour broadcast will leave a complete video behind. YouTube’s archive guidance is the place to check for the current platform behaviour.
There is a related limitation for viewers: YouTube says DVR rewind may be limited or unavailable on streams longer than 12 hours. People watching a long-running aquarium channel may not be able to pause and rewind through the entire broadcast. If access to a replay or to earlier moments matters to your audience, consider whether shorter sessions and a separate local recording fit that need better than one uninterrupted stream.
The trade-off is operational. One long session can make a channel feel continuous, but it carries archive and DVR uncertainty. Shorter sessions may be easier to preserve as separate recordings, but they introduce planned transitions and require someone to manage the schedule. YouTube’s guidance does not guarantee that a specific approach will produce a complete replay, so test your workflow and retain the source independently.
If your production method needs a desktop loop, OBS media-source restart options are relevant to testing the point where a file repeats. They address playback behaviour in the encoder, not YouTube’s archive limits. Keep those two issues separate when you decide what viewers should expect from the channel.
If monetisation is part of the plan, do not assume that continuous playback or a technically correct encoder profile establishes eligibility. YouTube’s channel monetisation policy says content should be original and authentic and addresses repetitive or mass-produced material. The policy cannot predict whether a particular aquarium loop will pass review; the footage, presentation and wider channel context matter. Check YouTube’s current monetisation policies and avoid promising yourself or viewers a particular outcome.
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
What bitrate should I use for 1080p YouTube Live?
For H.264, YouTube lists 14 Mbps recommended and 5 Mbps minimum at 1080p30, and 17 Mbps recommended and 6 Mbps minimum at 1080p60. These are ingest recommendations, not a guarantee that your connection can sustain the stream. Match the frame rate to the source and test your own upload path.
Should an aquarium loop use 30 fps or 60 fps?
Use the source frame rate where possible. If the file is 30 fps, 1080p30 is a straightforward starting point; use 60 fps when the source or the motion you need to retain calls for it and your upload connection supports the higher target.
Will YouTube save a 24/7 livestream?
Do not count on YouTube capturing one uninterrupted 24-hour session as a complete replay. YouTube says streams longer than 12 hours may not be captured at all, so keep a local recording if the archive matters and check the current Help page.
Can viewers rewind a long live stream?
They may not be able to rewind the full duration. YouTube says DVR rewind can be limited or unavailable for streams longer than 12 hours, so tell viewers what to expect and consider shorter sessions if access to earlier moments is important.