An OBS Profile lets you save and switch between separate output configurations, so you can use one for 720p and another for 1080p without rebuilding your scenes. The two choices are not guaranteed to work on every computer or connection: match each profile’s frame rate and bitrate to your source, system and stable upload capacity, then test it.
The key distinction is that Profiles hold settings such as output resolution, while Scene Collections hold your scenes and source layout. Make both profiles deliberately, keep the intended collection selected, and check the stream health before relying on either for a long-running loop.
Understand Profiles and Scene Collections
In OBS, a Profile is a saved set of settings related mainly to output. The Profile menu lets you create, duplicate, rename, remove, import and export profiles. Video and Output settings are among the settings saved there. OBS gives using different output resolutions as an example of why you might keep separate profiles. See the OBS Profiles guide for the documented menu and behaviour.
Scenes are not stored in Profiles. They belong to Scene Collections. That separation is useful for a loop channel: your collection can contain the media source, overlays, background and audio routing, while a profile changes the encoded output settings. Switching to a different resolution profile does not automatically select a different scene layout.
A practical naming scheme is “YouTube Loop 720p” and “YouTube Loop 1080p”. Names should describe the output rather than the content, so you can still recognise the correct choice if you later use the same collection for a devotional loop, an ambience stream or a study channel. Before starting, confirm both the profile and the Scene Collection in their respective menus.
If you maintain a more involved production, treat the collection as the visual programme and the profile as the delivery configuration. That also makes it easier to diagnose problems: a misplaced overlay is likely a scene or source issue, while an unexpected stream resolution points towards the active profile or its Video settings. For broader software context, the YouTube streaming software guide discusses the role of tools such as OBS in a creator’s workflow.
Create a profile for 720p output
Open OBS’s Profile menu and create a new profile, or duplicate a profile whose other settings you already understand. Give it a clear name such as “YouTube Loop 720p”. A duplicate can save setup time, but do not assume that every inherited setting is appropriate: inspect Video and Output after creating it, especially if the original was configured for recording or a different stream.
Go to Settings → Video. Set Output (Scaled) Resolution to 1280×720. This is the encoded stream size you are asking OBS to send. Keep Base (Canvas) Resolution appropriate to the media and scene layout, as discussed below; it does not have to be changed merely because this profile outputs 720p.
Then open Settings → Output and inspect the streaming encoder settings. Choose the intended encoder and codec, set the frame rate you will actually use, and set a live bitrate using the matching YouTube guidance rather than a prerecorded-video upload recommendation. If your loop is 30 fps, use the 30 fps guidance; if it is 60 fps, use the 60 fps guidance. Codec matters too, because the figures in the table below are specifically for H.264.
YouTube’s live guidance calls for constant bitrate (CBR) and a two-second keyframe interval, with a maximum interval of four seconds. Set these deliberately rather than relying on a recording preset. OBS also notes the value of consistent keyframes for transitions between viewer quality options; its transcoding guidance explains that context.
Do not choose a higher bitrate just because the output is 720p and the number appears within a published range. The upper end still needs to fit your connection for the duration of the broadcast, alongside audio and ordinary network variation. A conservative tested setting is more useful for an overnight loop than a setting that only works when the connection is quiet.
Create a profile for 1080p output
Create a second profile, preferably by duplicating the first once its shared encoder and audio choices are correct. Name it “YouTube Loop 1080p”. In Settings → Video, set Output (Scaled) Resolution to 1920×1080. Retain the same Base (Canvas) Resolution if it suits your scene and source. This avoids rebuilding source placement simply to change the delivered resolution.
Review Output settings again. The 1080p profile may need a different bitrate because YouTube’s H.264 live ranges differ by resolution and frame rate. Keep CBR and the two-second keyframe interval consistent unless a specific encoder limitation requires another choice. Also check that the encoder selected by the duplicate profile is the one you intend to use for live streaming.
Higher output resolution can raise rendering and encoding load. This is separate from what the internet connection can carry: a profile can be network-capable but still overwhelm a computer, or be easy to encode but exceed stable upload capacity. Use OBS Stats and YouTube’s stream health to distinguish rendering or encoding trouble from connection trouble.
If the 1080p version is unstable, do not immediately shrink the canvas. First reduce the output resolution or frame rate and test again. OBS’s encoding performance troubleshooting guide describes reducing output demands as a way to address overload. Changing canvas dimensions can disturb source placement and sizing, so reserve it for cases where the system constraint genuinely calls for it.
Distinguish canvas size from output size
Base (Canvas) Resolution is OBS’s work area. It is the coordinate space in which you place and size sources: the loop video, text, logos and other scene elements. Output (Scaled) Resolution is the size of the encoded stream sent to YouTube. OBS describes the latter as the stream output resolution in its Studio overview.
For example, suppose a loop source and its overlays are arranged on a 1920×1080 canvas. In the 720p profile, setting output to 1280×720 scales that composition down for the stream. In the 1080p profile, setting output to 1920×1080 sends it at that size. The sources stay in the same scene; only the output dimensions change. Check fine text and thin lines after scaling, since details that look clear at 1080p may be less legible at 720p.
The canvas should reflect the composition you want to build, not a bitrate target. A 720p output does not require a 1280×720 canvas, and a 1080p output does not require you to reconstruct the scene from scratch. If your source is natively 1280×720, sending it at 1920×1080 does not create new detail; it enlarges the picture. Conversely, a higher-resolution source can be scaled down, though OBS still has to render the composition.
Keep the two profiles’ canvas choice aligned unless you have a genuine layout reason to vary it. When sources are already positioned correctly, output scaling is the simpler adjustment. If you do need a different canvas for a separate design, inspect every source’s position, crop and size afterwards. OBS’s overview of the interface and settings can help orient you to the broader OBS workflow, but the resolution distinction itself remains in Settings → Video.
Set encoder and frame-rate options
Decide first whether the loop should run at 30 or 60 frames per second. Use the source’s actual cadence and the look you want rather than selecting 60 simply because it is available. For static devotional artwork, a study lecture or slow ambience, 30 fps may be sufficient; for motion that benefits from smoother movement, 60 fps may be appropriate. These are editorial choices, not guarantees about load or quality.
The encoder can be software-based or hardware-based, depending on your computer and OBS options. Keep the choice consistent between profiles while testing so that a change in resolution is not mixed with an encoder change. If hardware encoding is available and suitable, it may reduce CPU work, but the machine’s GPU and other running tasks still matter. Do not infer performance from the profile name; watch OBS Stats under the actual loop workload.
Set the same intended frame rate in both profiles unless you have a clear reason to change it. If you use a different frame rate in one profile, its bitrate selection must match that frame rate’s YouTube row, and you should test that specific combination. Likewise, the codec affects which YouTube guidance applies. The table here covers H.264 only; do not carry those figures across to another codec without checking YouTube’s current encoder settings page.
When performance trouble appears, separate the symptoms. Encoding lag suggests that the system cannot encode the chosen settings consistently; rendering lag points to scene rendering load; dropped frames commonly indicate a network path issue. OBS Stats can help identify which is happening. Lowering output resolution or frame rate is often a more direct first adjustment than changing the canvas and then repositioning every source.
Choose a bitrate using YouTube live guidance
YouTube publishes live encoder bitrate recommendations by codec, resolution and frame rate. For H.264, the current figures on its live encoder settings page are the ranges below. They are for live ingest, not for uploading a prerecorded video to YouTube.
| Output resolution | H.264 at 30 fps | H.264 at 60 fps |
|---|---|---|
| 1280×720 (720p) | 3–8 Mbps | 3–8 Mbps |
| 1920×1080 (1080p) | 5–14 Mbps | 6–17 Mbps |
Choose the row matching the active profile’s output resolution and frame rate. These ranges are guidance, not a promise that every setting in them will be reliable on your connection. In particular, do not confuse YouTube’s live ingest settings with bitrate suggestions for uploading video files. The use case and recommendations differ.
YouTube’s guidance also specifies CBR, a recommended two-second keyframe frequency and a maximum four-second interval. Set these in OBS’s stream encoder options. If you are using a codec other than H.264, revisit YouTube’s page and use the corresponding codec guidance rather than treating this table as universal.
Within the relevant range, begin with a value that your stable connection can sustain, then test. A higher setting can preserve more detail, but it uses more upload capacity and may make drops more likely on a variable connection. The best choice is not automatically the largest number in the row. For a low-motion loop, a stable stream with adequate detail may be preferable to a fragile setting at the top of the range.
If you want a separate reference focused on connection-side choices, the YouTube RTMP bitrate guide for a 24/7 stream in India addresses bitrate in that continuous-stream context. Still verify the current official encoder page before configuring a live broadcast, because platform guidance can change.
Check stable upload capacity
The relevant question is not only what speed test reports at one moment, but whether your upload connection can sustain the chosen stream bitrate over time. Other household or office activity can consume capacity, and wireless conditions or an ISP route can vary. A speed test is a useful first check, not a guarantee for an all-night broadcast.
Leave room for audio and network variation rather than planning to use every available bit of upload. If the connection is shared, test while it is in its usual operating conditions. OBS’s network troubleshooting guidance offers broad connection advice, but it is not a YouTube-specific promise that a given fraction of a speed-test result will work. Use YouTube stream health and OBS dropped-frame readings to judge the actual path.
If the connection cannot sustain the bitrate, lower the bitrate within the relevant YouTube range and run another test. If a reliable setting cannot be found within that range, reduce output resolution or frame rate and test again; neither profile is guaranteed on any connection. For a 1080p option to be useful, it must stay stable in the conditions where you intend to run it, not just pass a short test in ideal conditions.
Keep a brief record of what you tested: profile name, resolution, frame rate, codec, bitrate, whether other devices were using the connection and what OBS or YouTube reported. That makes later diagnosis more useful than changing several settings at once. If a loop stops overnight, a guide to tracing an OBS or FFmpeg stream interruption can help separate a configuration issue from a process interruption.
Test and switch profiles before going live
Select the profile from OBS’s Profile menu before starting the broadcast. Confirm the active output resolution in Settings → Video, then confirm that the intended Scene Collection is selected independently. A profile switch will not restore a different scene layout for you. Check the audio source as well, especially if the loop’s sound is supplied separately from the video.
Run a private, unlisted or otherwise suitable test before using either profile for a public continuous stream. Test a representative segment of the loop, including a scene change, any overlay or ticker, and the audio level. Watch OBS Stats for dropped frames and rendering or encoding lag, and inspect YouTube’s stream health. YouTube recommends testing and monitoring stream health in its live encoder guidance.
Test each profile separately. A successful 720p test does not establish that the 1080p profile will encode smoothly or that the connection can sustain its bitrate. Likewise, a stable 1080p test at a lower frame rate does not validate a 60 fps configuration. Change one variable at a time when troubleshooting, then repeat the test long enough to reveal conditions relevant to your intended use.
Before an actual start, use a short checklist: correct profile, correct collection, intended resolution and frame rate, selected encoder, bitrate and keyframe settings, audio present, and no persistent health warning. If you rely on a computer staying on for a loop, include power settings, updates and network stability in your operating plan. OBS profiles make output switching easier; they do not remove the need to monitor the setup.
For a 24/7 channel, you may decide that running OBS continuously is not the right operational fit if the computer, power or connection is unreliable. StreamNeo can remove the need to leave that computer running by turning an uploaded video into a YouTube live stream, but it is YouTube-only and does not replace choosing or testing the right source and channel setup.
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
Do OBS Profiles include my scenes?
No. Profiles save output-related settings such as Video and Output configuration, while scenes are held in Scene Collections. Keep the intended collection selected separately when you switch between 720p and 1080p.
Should I change Base (Canvas) Resolution for 720p?
Usually, you can leave the canvas suited to your source and composition, then set Output (Scaled) Resolution to 1280×720 in the 720p profile. The canvas is your layout work area; output resolution is the encoded stream size. Lowering the canvas can require repositioning and resizing sources.
Which bitrate should I use for 1080p?
For H.264 live ingest, YouTube’s guidance is 5–14 Mbps at 30 fps and 6–17 Mbps at 60 fps. Choose a value your connection can sustain, use CBR and a two-second keyframe interval, and test the profile; these figures are not upload recommendations for prerecorded video.
Can I switch profiles while a stream is live?
Set and confirm the intended profile before starting, then test it. Do not treat a mid-broadcast profile change as a substitute for a planned test: output, encoder load and stream health can all be affected, and OBS profiles do not change the Scene Collection.