For a 24/7 waterfall stream, start with 1080p30 at YouTube’s recommended 14 Mbps H.264 bitrate if your source and sustained upload can support it. If they cannot, try 720p30 at 8 Mbps H.264, then test the actual moving water before settling on a setting.
Those figures are YouTube’s general recommendations for incoming video, not waterfall-specific rules and not guarantees of stability. The right choice depends on the detail your source captures and the connection and encoder you will use for the broadcast.
Start with what your source and connection can sustain
Resolution is one part of the picture, not a quality setting that works in isolation. The incoming stream sent to YouTube is shaped by the source resolution, frame rate, codec, bitrate and the encoder’s ability to keep producing frames. Your sustained upload also has to carry that stream reliably over time. A camera recording at 1080p does not by itself prove that a 1080p live feed will be a good choice.
Start by checking what the source actually provides. If you are streaming a recorded waterfall video, inspect the original file rather than relying on a player’s display setting. If you are using a camera, check its output mode and whether it can run for the intended period without interruption. A source that is already soft, noisy or heavily compressed may not gain useful detail when you send it at a higher resolution.
Then consider the internet connection where the encoder will run. A speed test is a useful snapshot, but it cannot tell you whether upload capacity will remain consistent through a long unattended broadcast. Other people or devices using the same connection, changes in Wi-Fi conditions and service interruptions can all affect delivery. YouTube’s guidance is to choose a quality that will result in a reliable stream based on your internet connection, and to test the upload bitrate rather than assume a mode will hold.
If your setup runs from a Windows PC, the practical details of keeping a loop playing and sending it live matter as much as the number beside “resolution”. The guide to running a YouTube live loop from a Windows PC in India is a useful companion when the source file and local machine are part of the plan.
A sensible first try: 1080p30 at 14 Mbps H.264
If your source can provide 1080p at 30 frames per second and your encoder and sustained upload can handle the mode, 1080p30 at 14 Mbps H.264 is a concrete place to begin. It offers a higher-resolution incoming image than 720p, which can help preserve fine patterns such as water flowing over rocks, spray, or the edges of a pool. That does not mean every waterfall needs 1080p or that YouTube has a special rule for nature streams.
The 14 Mbps figure is YouTube’s recommended incoming video bitrate for 1080p30 H.264. It is a target for configuring and testing the encoder, not a minimum connection-speed guarantee. Keep the distinction clear when planning: the encoder’s video bitrate is the rate of the video it sends; the health of your stream depends on the complete chain continuing to deliver the configured signal.
A waterfall may show more benefit from a higher-resolution source than a largely static image, but continuous motion also makes compression more demanding. Water changes shape from frame to frame, and foam, spray and ripples can look smeared or blocky when the available bitrate is not coping with the visual change. Sending a larger frame does not automatically solve this; inspect whether the extra detail is visible and whether the stream remains healthy.
YouTube says it transcodes live streams into multiple output formats so viewers can watch across different devices and network conditions. That means your incoming mode is not a promise that every viewer will see exactly that resolution. It is still worth supplying a clean, stable source, because YouTube needs a usable incoming stream to create those output formats.
For the encoder, YouTube recommends constant bitrate (CBR) and a two-second keyframe interval, with a maximum interval of four seconds. Those settings are separate from choosing resolution, but they belong in the same test because an otherwise suitable 1080p30 picture can still have a poor delivery configuration. See YouTube’s current live encoder settings, bitrates and resolutions before configuring a broadcast.
Step down to 720p30 at 8 Mbps if needed
Use 720p30 at 8 Mbps H.264 as a reasonable lower-bandwidth fallback when the source, encoder or connection cannot sustain the 1080p30 mode. The smaller incoming frame and lower recommended bitrate can be easier to maintain. For a distant viewing setup, or a waterfall shot where the viewer mainly wants a calm scene rather than fine texture, the trade-off may be acceptable.
The change is not simply “less quality”. It is a choice to send fewer pixels at a lower recommended bitrate, which can reduce the demands on the encoder and upload path. But if the source itself is 1080p and the connection was already stable, downscaling may discard detail that some viewers would notice. Judge the result on a representative screen and viewing distance, not only in the encoder preview.
YouTube recommends 8 Mbps for 720p30 H.264. Like the 1080p figure, it is a general incoming recommendation rather than a threshold that guarantees a reliable broadcast. If 720p30 at the recommended bitrate still coincides with dropped frames or poor stream-health messages, investigate the connection, encoder load and configuration instead of repeatedly changing resolution without evidence.
| Incoming mode | YouTube recommended H.264 video bitrate | When it may suit the test |
|---|---|---|
| 720p30 | 8 Mbps | Lower-bandwidth fallback; check whether water detail remains adequate |
| 1080p30 | 14 Mbps | Starting point when source and sustained upload support it |
| 1440p30 | 21 Mbps | A higher-detail mode to consider only if the source and full setup justify it |
The table compares general H.264 recommendations from YouTube, not measured performance for waterfall footage. YouTube also publishes recommendations for other frame rates and codecs. Do not take a higher number as an instruction to raise quality regardless of the source or connection. You can read more about practical configuration choices in this overview of free and paid cloud services for 24/7 YouTube streaming, especially if the computer that sends the stream is becoming the weak link.
Check the current codec guidance before configuring
The recommended bitrate depends on the incoming resolution, frame rate and codec. For 30 fps, YouTube’s current table lists 8 Mbps at 720p, 14 Mbps at 1080p and 21 Mbps at 1440p for H.264. It lists different recommendations for AV1 and H.265, so do not copy the H.264 number into an encoder configured for another codec. The full table also covers 60 fps and 4K, but those modes are not necessary starting points for a continuous waterfall stream.
The platform guidance can change. Check the official help page when you configure or revise the stream rather than treating an older tutorial as definitive. The same page documents RTMP and RTMPS ingest, supported video codecs and other encoder options. YouTube recommends RTMPS as the encrypted option; use the connection method your encoder supports and the account’s live-stream settings permit.
For a typical waterfall, 30 fps is a reasonable initial frame rate. A higher frame rate sends more frames per second and has a higher recommended H.264 bitrate at the same resolution. It may be useful for very rapid movement, but it also asks more of the encoder and upload. Do not move to 60 fps simply because the source or menu offers it: test whether the extra temporal smoothness is visible enough to warrant the extra demand.
YouTube’s guidance also identifies Rec. 709 and 8-bit for SDR video. If your material is ordinary SDR, keep the colour setup consistent from source through encoder instead of introducing an HDR configuration without a reason. For HDR, the platform lists different codec guidance; that is a separate workflow, not an automatic improvement to an SDR waterfall video.
Inspect water for detail and compression artefacts
A waterfall gives you useful visual clues during a test. Look at a section with thin streams, foam, spray and textured rocks. These details can reveal whether the source is genuinely sharp and whether compression is retaining texture or turning it into soft patches, blocks or flickering noise. Look at both the central cascade and darker areas near the banks, since an attractive wide shot can conceal loss of detail in shadow.
Check the picture at the size viewers are likely to use. A close-up preview on an editing monitor can make modest differences look larger than they will on a phone, while a small preview can hide artefacts. Watch the same scene on a representative device and compare the 1080p and 720p tests if both are viable. Ask whether you can see a useful difference, not merely whether one mode has a larger label.
Motion can expose a different problem from static sharpness. Freeze frames may look clean while the flowing water turns into a smeared surface during playback. Watch a stretch with continuous movement, then a calmer stretch if your source has one. If the picture breaks up, note whether the change appears at the same time as a stream-health warning, a network interruption or a heavy encoder load.
Do not use a single attractive frame to decide. A loop may have different lighting, camera movement or water speed in other sections. Include enough of the source to see those changes, particularly if the stream will repeat overnight. For advice on the wider viewing experience of a continuous nature or sleep channel, see how to monetise ambience and sleep channels without annoying viewers; the resolution choice should serve the experience, not become the experience.
Run a representative stream test
Before leaving the channel unattended, test the same source, encoder, connection and settings you intend to use. Include representative audio and movement, as YouTube advises, even if the finished waterfall stream will have only natural sound or no audio. Confirm the live preview appears as expected and inspect stream-health messages while the test is running. A test on a different connection or with a short, static clip will not tell you as much about the real setup.
Begin with 1080p30 and the 14 Mbps H.264 recommendation if the source and connection appear capable. Observe the stream rather than treating the configured bitrate as proof. If YouTube reports delivery trouble, or if the encoder cannot hold the chosen mode, test 720p30 at 8 Mbps. Keep other variables consistent where possible so you can tell whether the change helped. If you change resolution, bitrate, frame rate and encoder settings all at once, the cause of any improvement or new problem will be harder to identify.
A useful test checks several things together: the visible image, whether the encoder reports that it is keeping up, and whether YouTube reports a healthy incoming stream. Confirm that audio is present if the stream is supposed to include it. Verify the loop reaches its end and begins again, if it is a looping file. YouTube’s Live Streaming API documentation describes stream status and health information, including configuration and ingestion issues; you do not need to build an API integration to inspect the status surfaced in your usual live workflow.
A test cannot guarantee that a stream will remain uninterrupted for days. It can uncover configuration mismatches and show whether the chosen mode is suitable under the conditions you tested. If the source is a file and your local computer would need to stay on all night, include that operating requirement in the plan as well as picture quality. The guide to streaming a looping video with FFmpeg is relevant if you are evaluating a local software workflow and want to understand its operational trade-offs.
When a computer that must stay on becomes the main concern, a cloud-run file stream can remove the need to keep that local machine running; StreamNeo is designed for that specific uploaded-file-to-YouTube workflow. It does not change the resolution decision: you still need to prepare a suitable source and check how the resulting stream looks and reports health.
Monitor health after going live
Once the stream is live, keep an eye on the first period of operation and revisit it after meaningful changes to the source, encoder, network or stream settings. Look for YouTube stream-health messages, missed or mismatched video configuration, and signs of ingestion interruptions. A clean preview at the start is useful, but it does not tell you what happened later if the upload path changes or the machine encounters a problem.
If a health warning appears, note the wording and the time before changing settings. A low-bitrate message, frame-rate mismatch or video-ingestion starvation points to different parts of the chain. Check the encoder output and connection first, then use a controlled test of the lower mode if the higher mode is not holding. Resolution is one lever, not a general fix for power, network or source failures.
For a local PC setup, unattended operation adds practical questions: whether the machine stays awake, the loop advances properly and the connection remains available. A lower resolution may help with delivery demands, but it cannot keep a computer from sleeping or repair an unreliable Wi-Fi link. If Wi-Fi interruptions are part of your setup, the guide to fixing YouTube stream drops when using Wi-Fi covers the connection side of the problem.
Treat the chosen mode as a tested operating setting, not a permanent promise. Recheck after replacing a source file, changing an encoder or moving the stream to another connection. Keep a note of the tested resolution, frame rate, codec and bitrate, alongside the health result, so you can return to a known configuration if a later adjustment makes the picture or delivery worse.
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 1080p30 always better for a waterfall stream?
No. It is a useful starting point when the source, encoder and sustained upload support YouTube’s recommended 14 Mbps H.264 bitrate. If the source lacks fine detail or the connection cannot sustain the mode, 720p30 may be a more practical choice.
Does YouTube require a particular resolution for waterfalls?
No waterfall-specific resolution rule is cited in YouTube’s general encoder guidance. The 1080p30 and 720p30 suggestions here apply YouTube’s general bitrate recommendations to a moving-water test, so check your own footage and stream health.
Will 14 Mbps guarantee that my 1080p stream stays live?
No. It is YouTube’s recommended incoming H.264 video bitrate for 1080p30, not a stability guarantee or a fixed upload-speed threshold. Test the full setup and monitor YouTube’s health messages after going live.
Should I use 60 fps for moving water?
Start by testing 30 fps unless your particular source or viewing needs make the extra temporal smoothness worthwhile. YouTube recommends a higher H.264 bitrate for 1080p60 than for 1080p30, so the higher frame rate asks more of the encoder and upload and should be validated in a representative test.