Fast movement can look blocky on a YouTube stream even when OBS is configured correctly: each frame changes more, so a fixed bitrate has more image detail to encode. YouTube’s H.264 bitrate figures are useful starting points, not guarantees; connection stability, encoder capacity and your output settings still matter.
Start by checking the configured output and stream health, then test with movement that resembles what viewers will see. If the connection is stable but fast scenes remain pixelated, try a lower output resolution or frame rate and compare the same scene again.
Why fast scenes can pixelate
A still image or slowly changing shot is relatively easy to compress. Between successive frames, much of the picture remains similar, so the encoder can represent changes without sending every detail afresh. A quick camera pan, moving leaves, gameplay, a dance performance or a busy street changes a larger part of the frame. At the same bitrate, the encoder has less room for fine detail and may simplify textures into visible blocks.
That is why a stream can look clean during a quiet introduction and lose detail when the action begins, despite using the same settings throughout. It does not automatically mean that your bitrate is wrongly configured. The chosen rate may be a reasonable platform recommendation and still be a limit for particularly complex motion at that resolution and frame rate.
Pixelation is also different from dropped frames. Compression artifacts make the picture look smeared or blocky; dropped frames interrupt motion or make it judder. A connection that cannot sustain the configured bitrate can cause dropped frames, while the encoder may produce a blocky picture even when the connection is steady. These symptoms can overlap, so do not respond to every quality complaint by raising bitrate.
The output you send is only one part of what a viewer sees. YouTube transcodes live streams into viewer formats, and a viewer’s chosen quality, device and connection affect playback. Your job is to send a stable, well-configured source stream, not to assume every viewer will receive the same rendition. YouTube’s live encoder settings guidance is the primary reference for ingest settings; OBS also explains how YouTube transcodes streams.
Check the output resolution and frame rate
Before changing anything, note what OBS is actually sending. In Settings → Video, distinguish the base (canvas) resolution from the output (scaled) resolution. The canvas describes the working layout; the output resolution is the size of the picture sent to the platform. Check the selected common FPS value as well. A canvas set to 1920 × 1080 does not establish that your stream output is 1080p, and a 60 fps setting is not the same workload as 30 fps.
Then check Settings → Output for the active streaming encoder, rate control and bitrate. OBS’s overview of its settings describes where output resolution, frame rate and streaming controls fit into a setup. Write down the current values before editing them. Changing one setting at a time makes it easier to tell whether the improvement came from resolution, frame rate, bitrate or a change in encoder load.
The content matters when you interpret those values. A devotional image with a mostly static background has different compression demands from a camera moving across a crowded procession. A lecture slide with a small talking-head window differs from gameplay or a wedding dance. If your channel mixes quiet and busy material, test a demanding segment rather than judging the configuration by its easiest scene.
A useful comparison records the output mode, codec and configured bitrate together. Rates below are YouTube’s recommendations for the listed H.264 combinations, not a promise of a particular appearance:
| Output and codec | YouTube recommended video bitrate |
|---|---|
| 1080p60 H.264 | 17 Mbps |
| 1080p30 H.264 | 14 Mbps |
| 720p60 H.264 | 8 Mbps |
| 720p30 H.264 | 8 Mbps |
These figures are for video bitrate, not a combined total for video and audio. The table is deliberately limited to common H.264 modes relevant to the question; check YouTube’s current table for other resolutions, frame rates or codecs. Its recommendations can change, and the codec selected for the stream affects which row applies.
Use YouTube’s H.264 recommendations as a starting point
For a 1080p60 H.264 stream, YouTube currently lists 17 Mbps; for 720p60 H.264, it lists 8 Mbps. Those recommendations are useful reference points when setting OBS, but they do not guarantee artifact-free fast scenes. A complex image can be hard to compress at the recommended rate, and a weak or unstable upload connection may not sustain it.
Compare the row that matches your actual output and codec, rather than copying a number from a different mode or relying on old forum advice. For example, 1080p30 H.264 has a different recommendation from 1080p60 H.264. A difference in frame rate changes how many frames are encoded each second, while resolution changes the amount of spatial detail. Keep the comparison like for like when you are evaluating results.
If your OBS bitrate is below the matching YouTube recommendation, that is one setting to investigate, provided your upload connection can support an increase. If it is already at the recommendation, simply raising it further is not a dependable fix. First establish that the connection is stable, that the encoder is keeping up, and that the pixelation appears in the source stream rather than only on one viewer’s device or playback quality.
YouTube also lists rates for AV1 and H.265, which differ from H.264. Do not use an H.264 number as if it applied to another codec. Encoder availability and compatibility depend on your setup; if you choose a different codec, use the corresponding current YouTube guidance and verify that your streaming path supports it. The practical principle remains the same: match codec, resolution and frame rate, then test actual content.
Set CBR and a two-second keyframe interval
For YouTube live ingest, configure OBS for constant bitrate (CBR) and a two-second keyframe interval. YouTube’s encoder guidance specifies CBR and recommends a two-second interval, with a maximum of four seconds. These settings provide a consistent basis for testing, but they do not determine whether your internet connection can sustain the bitrate or whether the encoder can represent every busy frame cleanly.
In OBS, the exact labels shown can vary with the selected encoder. Check the streaming output settings and confirm the rate-control field is CBR. Set the keyframe interval to two seconds where the control is available. Avoid changing several encoder options at once simply because a scene looks poor; first make sure the fundamental ingest settings match the platform guidance.
A constant bitrate does not mean every frame receives identical visual quality. When there is more motion or detail to encode, the encoder has less flexibility to allocate extra bits to a difficult moment. That is the mechanism behind a clean static shot followed by a blocky moving shot at an unchanged bitrate. The setting helps make the stream predictable for the platform; it cannot remove the trade-off between detail and available data.
If you are maintaining a continuous channel rather than broadcasting only when you are at the computer, a failed overnight test can be difficult to diagnose. Keep a short record of the output mode, OBS bitrate, keyframe setting and any dropped-frame indication. For context on how power interruptions affect a continuous setup, see keeping a 24/7 forest ambience stream live during power cuts. The useful lesson here is to make one controlled change, not to treat a restart or a larger number as proof that the underlying issue is solved.
Test with representative movement
Test before relying on the stream. Use a private or otherwise non-public broadcast if appropriate for your channel, and include a segment with movement similar to the real programme. YouTube advises testing with similar movement and audio and monitoring stream health. A static title card is not a sufficient test for a stream that will later show a moving camera, dancers, gameplay or traffic.
Choose a repeatable section of footage or a consistent camera movement. Watch the result at the same playback quality when comparing settings. Note whether blockiness appears only during motion, whether the image is consistently soft, and whether motion stalls. If possible, compare the received stream rather than only the OBS preview: the preview is not the same as a viewer’s YouTube playback.
Use a small test log. Record the scene, output resolution, FPS, codec, bitrate, whether OBS showed dropped frames and what you observed in playback. Change one variable, then run the same scene again. That stops an apparently successful adjustment from being confused with a different scene, an improved connection at that moment or a viewer watching at a different quality level.
Keep the test practical for your content. A study channel can use a page turn or a moving presenter; an ambience stream can include wind moving foliage; a local news loop can use street footage or a camera pan; a bhajan channel can include a close view of musicians and percussion. This is not a contest to find the highest number. You are looking for a stable output that preserves acceptable detail in the movement viewers will actually encounter.
Check connection and encoder capacity
Watch OBS’s dropped-frame indicator while streaming. OBS says dropped frames indicate that the connection is unstable or unable to sustain the set bitrate. If the indicator rises during the test, investigate connection stability before raising the bitrate. OBS’s stream connection troubleshooting guide recommends checking the connection and adjusting the bitrate to a sustainable level.
A speed test is only a snapshot. Your available upload can vary with Wi-Fi conditions, other people using the connection, background uploads and the route to the ingest service. Prefer a wired connection for testing where practical, pause avoidable uploads, and repeat the test at the time the channel normally runs. OBS offers using 75% of total upload speed as a starting heuristic, not a guarantee. Treat measured speed as a ceiling that can fluctuate, not as capacity you should fill without checking stability.
There are two separate limits to distinguish. The network must deliver the stream consistently; the computer must render and encode frames on time. If the local recording also looks poor, or OBS reports encoding or rendering overload, investigate the encoder and system load. A network-only problem is less likely to explain artifacts in a clean local recording, though multiple problems can happen together.
Check which encoder is selected and whether the computer can sustain the chosen output. OBS notes that hardware encoder generations differ in quality at a given bitrate, so switching to hardware encoding is not automatically a visual improvement in every situation. Hardware encoding can reduce CPU workload, which may help a constrained system, but the symptom alone does not establish that you need new equipment. See OBS’s hardware encoding notes before changing encoders, and compare with the same movement under the same output settings.
If dropped frames appear, lower the video bitrate enough to fit a reliably sustainable connection and repeat the test. A stable lower bitrate can be preferable to a higher configured rate that repeatedly loses frames. If the connection is steady and the encoder is not overloaded but fast scenes remain blocky, move on to output resolution or FPS rather than increasing bitrate without limit.
Adjust output when quality remains poor
When the connection is stable and the encoder keeps up, but high-motion sections still look blocky, test a lower output resolution first. Reducing the number of pixels gives the encoder less image data to represent at the same bitrate. For example, compare a 1080p output with a 720p output while holding the content, codec and other settings constant. Viewers will receive a smaller output image, so this is a quality trade-off, not a hidden correction with no consequence.
If preserving resolution matters more than smooth motion, test a lower frame rate instead. Moving from 60 fps to 30 fps means fewer frames each second need to be encoded, but movement will look less fluid. There is no universal best choice: a lecture may tolerate 30 fps well, while a dance performance or gameplay stream may benefit more from retaining smoother motion. Judge using the actual viewing purpose, not a rule that all channels should use one mode.
You can compare choices in this order:
| What you observe | First test | Trade-off to consider |
|---|---|---|
| Blocky fast scenes, stable connection and encoder | Lower output resolution | Smaller picture, with fewer pixels to encode |
| Motion judders or OBS reports dropped frames | Reduce bitrate to a sustainable rate and check the connection | Less data sent, but a lower rate may show more compression |
| Encoding or rendering overload | Reduce workload or compare a suitable encoder | Encoder choice can alter system load and image quality |
| Static scenes look clean but busy scenes do not | Test with representative motion, then compare resolution or FPS | The hardest content, not the easiest, sets the practical limit |
Run the same moving segment after each adjustment. If a lower resolution improves the busy scene and remains acceptable at normal viewing size, it may be a sensible channel setting. If the image becomes too small, restore it and test a lower FPS instead. Do not lower both immediately unless a test shows the combined output is necessary; changing one factor at a time preserves a clear comparison.
These checks may also inform whether OBS should run continuously on your own equipment. If keeping a computer on and available is itself the difficulty, how to keep a YouTube live stream running without a PC in India discusses that separate operating question. StreamNeo can remove the need to leave your own computer running for a file-based channel, but it does not change the need to choose an appropriate output and assess the result on YouTube.
For a recorded lecture channel, the source material and movement are often predictable, so a repeatable private test can identify a suitable output before a longer run; see creating a YouTube 24/7 lecture stream from recorded classes. For any format, keep a known-good configuration written down. If you later change a source video, encoder or network, you can test against the same baseline rather than rebuilding settings from memory.
The practical sequence is simple: match YouTube’s current recommendation to the codec and output, confirm CBR and a two-second keyframe interval, test representative movement, separate dropped frames from compression artifacts, and then adjust the output if needed. No one setting guarantees clean detail in every scene. The aim is a stable stream with a trade-off you understand.
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 1080p60 H.264 on YouTube?
YouTube’s current live encoder guidance recommends 17 Mbps for 1080p60 H.264. Treat that as a starting point, not a promise that every fast scene will be free of blockiness. Your connection must sustain the rate and your encoder must keep up.
Why is my stream pixelated only when I move?
Fast movement changes more of the image between frames, making it harder to compress at a fixed bitrate. A static scene can look clean at the same settings because it contains less changing detail. Test using movement that resembles your real content before changing settings.
Should I increase bitrate if OBS shows dropped frames?
Not as a first response. OBS associates dropped frames with an unstable connection or one that cannot sustain the configured bitrate, so raising the rate can make that symptom worse. Check connection stability and reduce bitrate to a sustainable level, then test again.
Should I lower resolution or frame rate first?
If the connection and encoder are healthy but fast scenes remain blocky, test lower output resolution first, then consider lower FPS if needed. Resolution reduces pixel detail; frame rate affects motion smoothness. Compare the same moving scene and choose the trade-off that suits your channel.