YouTube Live can show a lower resolution because it detected a lower-resolution source at ingest, or because a viewer is looking at one of YouTube’s lower playback renditions. Those are different situations: a low playback option does not, by itself, prove OBS sent a low-resolution stream.
To answer “Why does YouTube Live show a lower resolution than OBS is sending?”, compare OBS’s actual encoder output with YouTube’s ingest details, then inspect the viewer’s quality menu separately. YouTube automatically detects encoder settings and transcodes live video into multiple formats; its encoder guidance explains both behaviours.
Check what changed when switching to 60 fps
If the display changed after you switched from 30 to 60 frames per second, treat the timing as a clue, not a diagnosis. Moving to 60 fps does not alone establish why the picture looks soft or why YouTube reports a particular resolution. It does change the combination of settings to check: YouTube’s bitrate recommendations depend on codec, resolution and frame rate, and the same bitrate has more frames to carry when the frame rate rises.
Write down the before-and-after settings rather than changing several at once. Record the intended resolution, frame rate, codec and configured bitrate, along with whether you changed the OBS output scale, encoder, rate-control mode or YouTube stream key. If you changed only frame rate, compare the current ingest bitrate recommendation for that codec and resolution before changing anything else. If you also changed output scaling, you need to check what the encoder is sending rather than infer it from the canvas.
A practical example is a channel that previously sent 1080p30 and now sends 1080p60. YouTube’s current H.264 guidance lists 14 Mbps as recommended for 1080p30 and 17 Mbps for 1080p60, with minimums of 5 Mbps and 6 Mbps respectively. These are ingest recommendations, not promises about how every viewer’s connection will receive the stream. Check YouTube’s current table for your codec and settings rather than applying those H.264 figures to another codec.
Confirm the encoder’s actual resolution and frame rate
OBS’s canvas or source dimensions are not the same thing as the encoded output. A scene may be arranged on a 1920 × 1080 canvas while the encoder output is scaled to a smaller resolution. Conversely, a source asset’s dimensions do not prove the final encoded stream has those dimensions. Check OBS’s output or encoder settings and compare those values with the resolution and frame rate YouTube reports receiving.
Then distinguish three checkpoints:
| Checkpoint | What it tells you | What it cannot establish alone |
|---|---|---|
| OBS canvas and source dimensions | The workspace and media sizes used to compose the scene | The dimensions actually encoded and sent |
| OBS output or encoder settings | The intended dimensions and frame rate of the outgoing video | That YouTube detected or received the same values |
| YouTube Live Control Room ingest details | The resolution and frame rate YouTube detected at ingest | Which quality a particular viewer selected or can receive |
The comparison is useful because it narrows the fault. If OBS’s encoder output is already lower than you intended, investigate scaling or output configuration there. If it shows the intended settings but YouTube detects something else, check the stream key and ingest information before assuming that the preview or playback menu is reporting the source resolution.
YouTube detects resolution and frame rate automatically by default. A custom stream key can have a manual-resolution setting that overrides automatic detection, so check whether one is in use and whether its setting matches the intended output. You can review the platform’s live stream settings and stream-key overview. For a separate explanation of which value goes in OBS, see this guide to the YouTube stream key and stream URL.
Compare bitrate with YouTube’s guidance
Once you know what OBS is encoding, check the configured bitrate against YouTube’s guidance for the same codec, resolution and frame rate. Do not compare a 1080p60 stream with a recommendation for 720p30, or use a figure for H.264 as though it necessarily applied to HEVC or AV1. YouTube’s table is a starting point for ingest configuration, not a guarantee of a particular visual result or viewer rendition.
For H.264, YouTube currently lists these figures:
| Resolution and frame rate | Minimum bitrate | Recommended bitrate |
|---|---|---|
| 720p30 | 3 Mbps | 8 Mbps |
| 720p60 | 3 Mbps | 8 Mbps |
| 1080p30 | 5 Mbps | 14 Mbps |
| 1080p60 | 6 Mbps | 17 Mbps |
These values are from YouTube’s encoder recommendations as listed on its site in October 2026. They apply to the stated H.264 combinations; consult YouTube’s current table for other codecs and settings. If your bitrate is below the relevant range, it is reasonable to test a setting closer to the recommendation, provided your upload connection can sustain it. Increasing bitrate will not always fix softness: the source may be scaled, the visual may contain little detail, the encoder may be struggling, or you may be comparing a lower playback rendition with the ingest feed.
YouTube also recommends constant bitrate and a two-second keyframe interval, with a maximum interval of four seconds. Those are separate encoder checks rather than explanations for every low-resolution report. If the source is rejected or behaves unexpectedly, format compatibility can be another checkpoint; this guide to fixing unsupported FFmpeg pixel formats covers a related but distinct ingest problem.
Consider motion, bitrate and encoding together
A still devotional image with a slow visualiser is easier to encode than a busy news ticker, fast camera movement or a detailed study video with page turns and moving highlights. At the same resolution and bitrate, rapidly changing detail gives the encoder more work. A stream can therefore look soft during motion even when its nominal resolution matches the setting you selected. That does not mean the frame-rate change alone caused the softness; assess motion, bitrate and encoding together.
Use a segment that resembles the real channel. Include the fastest movement, the densest text, and any transitions or overlays that matter. If you use a loop, inspect a passage with both a static frame and a change between scenes. Look for whether fine detail is consistently blurred, whether the picture breaks down mainly during motion, or whether text is unreadable even on a still frame. These observations help separate a scaling problem from bitrate pressure or the viewer’s selected rendition.
Avoid compensating for one symptom with several simultaneous changes. If you raise resolution, frame rate and bitrate together, an improvement or regression will not tell you which adjustment mattered. Change one relevant setting, test again, and compare the encoded output and ingest report. Keep an eye on the upload connection too: a configured bitrate that the connection cannot sustain can introduce instability rather than improve the result.
For a channel built around recorded material, the file itself is part of the chain. Check that the source is genuinely high enough in resolution for the intended output and that text or artwork is not being enlarged from a small image. A recorded archive may benefit from a different preparation workflow than a live camera feed; this example of streaming a recorded archive on YouTube explains that broader use case.
Inspect stream-health messages
Live Control Room’s stream-health messages can make the difference between a configuration issue and a temporary delivery problem clearer. Read the message at the time it appears, and note whether the detected resolution or frame rate changes alongside it. YouTube recommends monitoring stream health and testing ahead of the event; a single viewer’s quality menu is not a substitute for the ingest information.
If the health panel indicates a problem, record the wording and the time before changing settings. Check the outbound bitrate and whether the connection is holding it steadily, then compare OBS’s output values with YouTube’s detected values. A message about a dropped or unstable feed points you towards delivery and encoder conditions; a stable ingest report with a lower playback option points you towards transcoding, viewer device or network instead. Follow the message and the evidence rather than treating every soft picture as the same fault.
Also confirm that you are looking at the right stream and stream key, particularly if you keep a test stream and a scheduled broadcast. A manual stream-key resolution can conflict with an output change. If the stream appears healthy but YouTube detects a lower resolution, return to the OBS output configuration and key settings before experimenting with unrelated hardware. YouTube’s encoder setup page is the primary reference for its current ingest checks and recommendations.
Separate ingest from viewer playback
YouTube transcodes a live source into multiple output formats so people on different devices and networks can watch. OBS’s explanation of transcodes and transcoding also notes that YouTube transcodes streams, including the source feed. As a result, an option such as 720p in a viewer’s quality menu does not necessarily mean OBS sent 720p; it may be one available playback rendition.
Compare like with like. In Live Control Room, inspect the ingest resolution and frame rate. In the viewer, open the quality menu and see which options are available and selected. Then test on another capable device and network. If the ingest details show your intended resolution while one viewer sees only a lower option, investigate playback conditions or rendition availability rather than changing OBS immediately. If the ingest details themselves are lower, focus on the encoder output and stream-key configuration.
This distinction is particularly useful when you are monitoring a 24/7 channel from a phone while travelling or checking it over mobile data. A constrained connection or device may choose a lower rendition even though the source ingest is correct. For a longer-running channel, the planning guide for a 24/7 channel can help you think about monitoring and operations beyond this specific resolution check.
Test a representative segment before going live
Do not wait for an overnight broadcast to find out that the output is scaled or the connection cannot sustain the chosen bitrate. YouTube recommends testing before the event. Send a representative segment that includes the content’s normal audio and movement, then compare OBS output settings, YouTube’s ingest details and playback quality. A short, controlled test is more informative than repeatedly changing settings during a live channel.
Use a simple test record: intended resolution and frame rate; codec and bitrate; OBS’s actual output values; YouTube’s detected ingest values; stream-health messages; and the quality options visible on a second device. If those values disagree, the record shows where. If they agree at ingest but playback looks different across devices, the issue is more likely to involve playback selection or network conditions than a mismatch in the encoder’s source settings.
For an unattended channel, consider how the stream will be monitored and recovered if the source computer or connection fails. If the specific operational burden is leaving your own computer running and checking that a broadcast has resumed after a drop, StreamNeo removes that task by turning an uploaded video into a YouTube live stream that runs with your computer switched off and is monitored and restarted if it drops. It does not change YouTube’s ingest recommendations or establish that a resolution problem is solved, so verify the encoder and playback evidence first.
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 a lower quality option mean OBS sent a lower resolution?
Not necessarily. YouTube creates multiple playback formats from a live feed, and a viewer may be offered or using a lower rendition. Compare the ingest resolution in Live Control Room with the viewer’s quality menu before deciding that OBS output was lower.
Does switching to 60 fps make the stream look soft?
The frame-rate change alone does not establish the cause. Check the encoder’s actual resolution and bitrate against YouTube’s recommendations for the codec, resolution and frame rate, then test representative motion and inspect stream health.
Why does YouTube detect a lower resolution than the OBS canvas?
The canvas is the scene workspace, not proof of the encoded output. Check OBS’s output or encoder resolution, and check whether a custom stream key has a manual-resolution setting that overrides automatic detection.
Should I always increase the bitrate to improve picture quality?
No. A higher bitrate may help when the current setting is low for the chosen codec, resolution and frame rate, but it cannot correct every cause of softness. Check scaling, source quality, motion, encoder behaviour and the viewer’s playback rendition, and only test a bitrate your connection can sustain.