For a typical 16:9 loop, use a 16:9 OBS canvas that preserves the source composition and consider 1920×1080 output at 30 fps as a starting point, provided your source, encoder and sustained upload can support it. It is a conditional baseline, not a setting that suits every computer or connection.
Canvas resolution is the workspace where OBS arranges your sources; output resolution is the size of the video YouTube receives. Match the output to the source detail and the capacity you have tested, then choose 60 fps only if the motion benefits from it and your system can sustain it.
A practical starting point for a 16:9 loop
If your video is landscape and has useful detail at 1080p or above, try a 1920×1080 canvas and output at 1920×1080, 30 fps. This gives you a straightforward baseline for a devotional visual, lofi station, study scene or local news loop. YouTube describes 16:9 as its standard computer-player aspect ratio, but the starting point here is an editorial recommendation rather than a platform requirement.
The qualification matters. A 1080p output asks more of the encoder and upload path than a lower output, and it cannot add original detail to a smaller source. If your file is 720p, your machine struggles during a long test, or your upload varies, begin at 1280×720 and test that instead. A stable, clear 720p stream is a better operational choice than an unstable 1080p stream.
Keep the source's shape intact. A 16:9 file placed into a 16:9 canvas can usually be fitted without distortion. If the source is square or vertical, decide whether you want bars, a deliberate crop, or a layout designed around that shape; stretching the image changes faces and objects rather than creating useful detail. For a longer-running setup, use a representative section of the loop during tests, including its busiest motion and audio.
This is an operating decision, not simply a question of selecting the largest menu value in OBS. Your output needs to suit the material, the encoder and the network together. The remaining sections explain how to make that choice and how to check it before leaving a channel live overnight.
Canvas resolution and output resolution are different
In OBS, Base (Canvas) Resolution is the space in which you position and size sources. Think of it as the layout board: it defines the coordinates for the video, image, text, overlays and other elements in your scene. OBS’s overview guide explains the distinction between the canvas and the scaled output.
Output (Scaled) Resolution is the video size OBS sends to the stream after scaling. For example, you can arrange a scene on a 1920×1080 canvas and send a 1280×720 output. OBS then scales the composition down. The viewer receives the smaller output, regardless of the larger canvas dimensions.
The two settings do not have to be identical, but each change has consequences. Changing the canvas may alter how sources fit, so check their positions and scale afterwards. Changing the output changes the delivered stream size; reducing it can ease the workload, while increasing it does not restore detail that was absent in the original file.
For a simple loop with no elaborate scene layout, matching a 16:9 canvas to the source’s intended composition keeps the setup easy to inspect. Choose the output separately according to the useful source detail and tested capacity. If you need to adapt older material, verify that text and important details remain legible at the output resolution you intend to use.
Choose output resolution to match the source
Start by checking the video file’s native resolution and aspect ratio, not just what the player window looks like on your computer. A file may be displayed at a larger size than its actual pixels, or contain a crop or letterboxing. Set the canvas around the composition you want, then choose an output that does not pretend the source contains more detail than it does.
| Loop source and conditions | Reasonable output to test | What to check |
|---|---|---|
| 1080p or higher, landscape, with dependable encoding and upload capacity | 1920×1080 | Look for stable stream health and readable fine detail over a sustained test. |
| 720p landscape source, or limited capacity | 1280×720 | Check that the image is clear and the encoder is not overloaded. |
| Lower-resolution source or a constrained system/network | A matching or lower 16:9 output | Confirm that scaling does not introduce distracting softness or other artefacts. |
| Vertical or square source intended for a landscape player | A deliberate layout or crop before choosing output | Make sure key content is not stretched or cut off. |
These are options to test rather than guarantees. The right choice depends on the file and on what the system can run continuously. YouTube also transcodes live feeds into formats for viewers, so your chosen ingest size is not a promise that every viewer will see precisely the same rendition.
Upscaling can make the file dimensions larger without bringing back detail that the camera, render or original export never captured. For instance, sending a 720p animation as 1080p may add encoding work without making its linework genuinely sharper. If you have a choice between preserving a clean 720p feed and an unreliable upscaled 1080p feed, test the former first.
For a channel with several clips, inspect the most demanding one rather than choosing from an easy still frame. Fine patterns, scrolling text, particle effects or a busy news ticker may reveal scaling problems that a mostly static scene hides. If the playlist contains mixed aspect ratios, decide how each one should appear in the scene before you commit to a continuous broadcast. A guide to rotating a YouTube playlist with PowerShell may help with clip order, but resolution and scene fit still need their own review.
When 30 fps or 60 fps makes sense
Frame rate is the number of distinct video frames sent each second. A static image, slow devotional background or gradual rain scene often has little visible motion that needs 60 fps. In those cases, 30 fps is a sensible first test: it gives motion a regular cadence without asking the encoder to process as many frames as 60 fps.
A loop with quicker movement may benefit from 60 fps: consider moving graphics, fast camera pans, sports footage or rapid transitions. But the choice should follow what you can actually see, not a belief that a larger number is always better. OBS notes that 60-fps streaming can be substantially more demanding than 30 fps and advises testing capacity. If the picture looks no better to you at 60 fps, the extra workload may not be useful.
If you want to compare, use the same output resolution, bitrate and representative loop segment in both tests. Check the motion on the YouTube preview and watch for dropped frames, stutter or encoder overload. Then let each setting run long enough to reveal a problem that a brief preview might miss. A short scene change can also help you assess titles, transitions and audio synchronisation.
YouTube’s encoder guidance lists settings for both 30 and 60 fps, but platform support does not mean a particular computer can encode either reliably. For a slow or still loop, stay with 30 fps unless you have a visible reason to change. If 60 fps gives no useful improvement, return to 30 fps and spend the available capacity on a stable stream.
Check encoder and sustained upload capacity
Resolution and frame rate are only part of the job. OBS must encode each frame in time, and the connection must carry the resulting stream steadily. A computer can appear comfortable while a low-motion scene is running, then fall behind when the loop shows detailed animation. Likewise, an upload test taken at one moment does not show whether the connection stays consistent through a long broadcast.
YouTube’s live encoder recommendations give codec-specific bitrate ranges and other ingest settings. For H.264, the published recommendation for 1080p30 is 14 Mbps, with 5 Mbps as a minimum; for 1080p60 it is 17 Mbps recommended, with 6 Mbps as a minimum. At 720p30 and 720p60, YouTube lists 8 Mbps recommended and 3 Mbps minimum. These figures are YouTube’s guidance, not a guarantee that your connection can sustain them or that they will be optimal for every picture.
Do not treat your measured upload rate as if all of it were available for video. Leave headroom for variation and other household or business traffic, then test the intended bitrate for a sustained period. If the connection fluctuates, lower output resolution or frame rate, reduce the bitrate in line with YouTube’s guidance, or investigate competing traffic before raising the setting again.
Encoder symptoms and network symptoms are different clues. If OBS reports that encoding is overloaded, try reducing frame rate or output resolution and check which encoder setting is active. If OBS shows network-related dropped frames or YouTube reports an unstable stream, investigate the upload path and bitrate rather than assuming a new canvas size alone will solve it. Make one change at a time so you can tell what helped.
YouTube’s guidance recommends CBR and a two-second keyframe interval, with an interval no longer than four seconds. It also recommends RTMPS and lists supported codecs and frame rates on the same official page. Treat these as ingest settings to configure and verify, not as evidence that a particular encoder can handle every combination.
An always-on channel also needs a plan for the machine and power around it. If you run OBS on a computer at home, a brief power cut or restart can interrupt the stream irrespective of resolution. Our guide to keeping an OBS sleep-sounds stream running during power cuts in an Indian apartment covers the separate power problem; for video quality, keep the resolution test focused on encoding and upload behaviour.
Set and verify OBS video settings
In OBS, open Settings, then Video. Set Base (Canvas) Resolution to the working layout size you want, normally a 16:9 size for a landscape composition. Set Output (Scaled) Resolution to the size you have chosen to test. Select a downscale filter if scaling is needed, then set the common FPS value to 30 or 60 as appropriate for the content and your test results.
If you alter the canvas after arranging a scene, inspect every source. An overlay that was aligned to a corner may move relative to the new canvas; a video source may need to be fitted or cropped again. Use the transform controls intentionally rather than stretching an image to fill the frame. Keep important titles away from edges, where they may be obscured by player controls on some devices.
For standard SDR material, YouTube’s encoding settings guidance specifies Rec. 709 colour, square pixels and progressive scan. Use settings consistent with the source and OBS workflow rather than changing colour values at random to make one monitor look brighter. Check the preview on the display you use for setup, and if colour is important, compare it on another device before the long run.
Before going live, review the Output and Stream settings as well as the Video tab. Confirm the intended encoder, rate control and bitrate, and make sure the correct YouTube stream key is selected. Do not paste or display a stream key in a public screenshot. If you are also using OBS to keep a feed running while you are away, this guide to monitoring a YouTube stream offline can help you plan how you will notice interruptions.
Write down the settings that passed the test, including resolution, frame rate and bitrate. That makes it easier to return to a known configuration after an experiment. If you change the loop file, add an animated overlay or move to a different network, repeat at least the relevant parts of the test: a working combination is specific to the content and operating conditions you tested.
Test the YouTube stream before leaving it live
Start with a private or unlisted test if that suits your channel workflow. Inspect the YouTube live preview for framing, sound and motion. YouTube’s live streaming tips advise testing and monitoring quality; use that preview to catch a wrong scene, muted audio or unexpected crop before viewers encounter it.
Let the representative loop run, rather than judging the setup from a static frame. Include its most detailed or active section, a transition, and any text that viewers need to read. Watch OBS’s status information and YouTube’s stream health. Note dropped frames, encoder overload, buffering warnings or visible softness, then change one setting at a time and repeat the test.
A practical sequence is to begin with the source-matched resolution at 30 fps, confirm the bitrate is within YouTube’s guidance for the chosen codec, and monitor a sustained test. If video quality or stability is poor, reduce one of resolution, frame rate or bitrate as indicated by the warning; do not raise all three at once. If the stream remains stable and the image is adequate, you have evidence for that setup under the conditions tested, not a guarantee for every future network or night.
Keep a local copy of the loop file and, if a replay matters, think separately about recording. YouTube says a live stream under 12 hours may be automatically archived, while a stream longer than 12 hours may not be captured at all; see its archive guidance. Do not rely on one uninterrupted 24-hour broadcast to create a complete on-demand replay. Verify that any local recording is present and growing if you depend on it.
For a creator who wants to run an uploaded loop without leaving a personal computer on all night, StreamNeo removes that specific computer-running burden while the resolution and source-quality decisions still need to suit the channel. Whatever workflow you use, retain a copy of the source and make a test before making the feed part of a nightly routine.
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
Should my OBS canvas and output resolution match?
They can match, and for a simple 16:9 loop that is often the easiest arrangement to check. They serve different purposes: the canvas lays out sources, while output resolution sets the size sent to YouTube. If you use a larger canvas and smaller output, inspect the scaled result and confirm that sources remain correctly aligned.
Is 1080p30 the best setting for every 24/7 YouTube loop?
No. It is a useful starting point when the source has enough detail and your encoder and sustained upload can handle it. If the file is lower resolution or the test shows overload or stream-health trouble, try a lower output and retest.
Should I use 60 fps for a lofi, bhajan or ambience loop?
Usually begin by asking whether the loop has motion that visibly benefits from the higher frame rate. Slow scenes often do not need it, and 60 fps can demand more encoding capacity. Compare the same representative segment at both rates rather than assuming the larger setting looks better.
Will YouTube save the replay of a 24-hour broadcast?
Do not count on a single stream longer than 12 hours being captured as a complete archive. YouTube says streams exceeding that duration may not be archived, so check its current archive guidance and keep a local recording or a separate replay plan if the recording matters.