If a picture in your continuous YouTube stream stops on one frame, the image alone cannot tell you why. First identify the OBS source, then compare what appears in OBS preview, a local recording and YouTube playback before changing settings.
The same symptom can come from media playback ending, a source or decoder stalling, OBS rendering or encoding pressure, or a problem on the route from OBS to YouTube. Audio behaviour and OBS’s own statistics help narrow the branch; they do not prove a cause by themselves.
Identify the source and the exact symptom
People often call any moving picture in OBS a “media source”, but OBS has distinct source types. The built-in Media Source is used for a media file. VLC Video is a separate source type that uses VLC, while a Browser Source displays web content such as a page or player. A camera or capture device has a different input path again. OBS’s Media Sources guide describes these distinctions and the relevant playback properties.
Write down the exact source name shown in the Sources list and what it points to. Is it a local video file, a URL or browser page, a playlist in VLC Video, or a connected device? If it is VLC Video, confirm that VLC is installed and that its architecture matches OBS: the OBS guide notes that 64-bit OBS needs 64-bit VLC. Do not install or replace anything merely because a frame froze; first establish which source is actually being used.
Describe the symptom precisely. Does the video stop at a particular point and remain still, disappear, turn black, or resume after a delay? Does the source item still appear in the scene? Does the freeze recur at roughly the same part of a loop, or at an unpredictable time? These observations help distinguish ordinary end-of-file behaviour from an intermittent playback problem, but none settles the diagnosis alone.
If a local file has reached its end, OBS can leave its final image visible. The Media Source properties include “Show nothing when playback ends”, which can prevent that final frame from remaining on screen. That option is relevant only when playback has ended; it is not a general remedy for a file that should still be playing or a continuous YouTube stream that has stalled.
For a repeating file, inspect whether looping is enabled and whether the source is configured to restart on activation, if that matches how your scene works. “Close file when inactive” and hardware-decoding controls are also source-specific properties. Change one relevant property at a time and test the same content again, so you can tell whether the behaviour changed. Avoid applying a Media Source setting to a Browser Source, VLC Video or capture-device problem.
Check whether the OBS preview is frozen
Look at the scene in OBS while the problem is happening. Note whether the source itself appears stuck in the preview, whether the entire scene stutters, or whether the preview moves normally while viewers describe a freeze. Record the time and, if possible, keep a note of the source and scene that were active. A screenshot can preserve what the interface shows, but a short recording of the incident is more useful when the symptom comes and goes.
A source frozen in preview means the problem is already visible before you judge YouTube playback. Playback or decoding is one possible branch; OBS rendering is another. A preview that moves smoothly does not demonstrate that the outgoing stream is sound, and a preview that appears frozen does not, on its own, identify which OBS component stopped producing new frames.
Avoid restarting OBS as the very first response if you can safely observe the issue for a moment. Restarting might clear the symptom, but it also removes useful evidence about whether audio continued, whether counters were climbing, and whether the source had reached its end. If the channel needs immediate recovery, prioritise restoring it, then make a note of what you saw before the restart.
Keep the comparison controlled. Check the same source and scene rather than switching between different tests, and note if another animated element in the scene continues moving. If the media picture is fixed but a clock, transition or other source still animates, that is different evidence from a wholly static scene. It still does not prove the media file itself is defective.
Compare preview, local recording and YouTube
A local recording gives you an observation outside the preview, while the public YouTube playback shows what reached the platform and what a viewer can receive. If you have a recording from the time of the freeze, inspect the matching interval. If not, make a short test recording during a controlled run rather than assuming what was present in an older file. Compare the same moments and note whether the recording contains a frozen picture, smooth motion, a black image or missing frames.
Then check the stream as a viewer, preferably from a separate device or connection if practical. YouTube playback can lag behind OBS, so match the event by its content or timestamp rather than expecting the preview and player to be in sync. A single viewer’s buffering report may reflect that viewer’s connection or playback conditions, not necessarily a frozen outgoing video.
| What you observe | Branch to investigate first | Useful next check |
|---|---|---|
| Preview, recording and YouTube all show the same frozen picture | Source playback, decoding, or local processing | Confirm the source type, playback position and whether the file reached its end; inspect OBS performance indicators |
| Preview looks frozen, but a recording or YouTube shows motion | Preview or local display behaviour | Check whether the recording actually covers the same interval; inspect rendering indicators and repeat a controlled test |
| Preview and local recording look normal, but YouTube playback freezes | Outgoing connection, ingest or viewer playback | Check OBS dropped frames and disconnections, then compare playback from another viewer or connection |
| OBS and local recording are normal, while one viewer buffers | Viewer-side or platform playback conditions | Check OBS dropped frames first; ask whether other viewers see the same symptom |
| No recording or statistics are available | Cause not yet isolated | Capture the next incident with the source type, audio behaviour, recording and OBS log |
These are triage routes, not verdicts. More than one issue can coexist: for example, a scene can place load on the computer while a viewer also has a weak connection. Do not treat one normal recording or one report from YouTube as proof that every part of the chain is healthy.
For a black image rather than a frozen image, the source and capture path still matter. The separate guide to fixing a black screen when streaming video with OBS is relevant when the picture is absent; it should not be used as evidence that a still frame has the same cause. If your setup instead centres on a local video playlist, the guide to looping a video on YouTube Live with VLC can help you review the playback workflow, but first confirm you are using VLC Video.
Note whether the audio continues
Listen to the stream and to a local recording from the same time. If audio keeps moving while the picture stays still, the audio and video paths may be behaving differently. That points you towards checking the video source, decoding and rendering, but does not establish that the network or encoder is uninvolved. If both picture and sound stop, note whether the whole stream disconnected, the source stopped, or only the viewer’s player paused.
Also check which audio you mean. A Browser Source may include its own sound, while a separate audio input or mixer source can continue independently of the picture. A music bed continuing does not show that audio embedded in the frozen source continued. In OBS’s mixer, note whether the expected meter is active; in the recording, listen for a gap, a repeated segment or a clean continuation.
On a devotional channel, for example, a bhajan track might continue from a separate audio source while a background video holds on one image. That would tell you not to assume the whole stream stopped, but it would not tell you whether the background file ended, its decoder stalled or OBS failed to render new frames. The next check is still to compare recording and playback, then review the applicable source and performance evidence.
If the public player buffers but the audio continues, record what the player actually does rather than describing every interruption as a frozen OBS source. Viewer playback conditions and what OBS sends are separate parts of the path. The OBS guide on stream buffering troubleshooting advises checking OBS’s dropped-frame counter first, while recognising that viewers can have buffering problems without OBS reporting dropped frames.
Separate source playback from rendering and encoding
Once you know where the image stops, separate three parts of the chain. The source must provide frames; OBS must composite and render the scene, then encode it; finally, the outgoing connection must carry the stream to YouTube. A fault in one part can produce a similar picture to a fault in another, so make the next test fit the observations rather than changing every setting at once.
For a local Media Source, check the playback position and whether the file has ended. If it is meant to loop, verify its loop and restart behaviour in that source’s properties. If the freeze happens at different points, try the file outside the scene to see whether it plays through, but treat that as a comparison, not a guarantee that OBS uses the same decoding path. If the source is a Browser Source, check that the page or player remains active and that the source has not navigated or stopped; do not apply local-file end-of-playback settings to a webpage.
For a capture device, check whether its picture is still moving in the device’s own preview or utility, if available, and whether the device remains selected and connected in OBS. Avoid changing capture resolution or replacing a card without evidence that the device is the failing source. For VLC Video, confirm the source uses the intended playlist or file and that VLC is available as OBS requires. Changing source types can alter playback behaviour, so use it as a deliberate test rather than a default fix.
Rendering and encoding are local OBS work. OBS’s encoding performance troubleshooting guide explains that OBS needs GPU resources to composite and render scenes. If the preview stutters, OBS reports rendering or encoding trouble, or the computer is busy with other GPU-heavy work, close competing applications where possible and simplify the scene for a test. You might temporarily disable a complex browser overlay or reduce unnecessary animated sources, then compare the same scene under similar conditions.
If evidence points to sustained performance pressure, consider reducing output resolution or frame rate to a level appropriate for the content and computer. Make one change at a time and check the result in a local recording as well as on YouTube. Do not infer from a single frozen frame that you need a GPU upgrade, or that one output setting will solve every source, render or encoding problem.
Connection trouble is a separate branch. OBS’s stream connection troubleshooting guide says dropped frames mean the connection to the remote server is unstable or cannot keep up with the configured bitrate. If the counter rises or OBS disconnects, check that branch: test a suitable ingest server or service, compare the configured bitrate with stable upload capacity, and review whether a VPN, security software, network software or drivers may be interfering. If Wi-Fi is unstable, OBS recommends trying a wired connection.
Dynamic bitrate may accommodate congestion by changing the bitrate, but that can reduce picture quality and does not repair an unstable connection. If OBS shows no dropped frames, do not treat a viewer’s buffering report as proof of connection failure at your end. Follow the evidence to its layer, and remember that several problems can happen together.
Inspect OBS Statistics and logs
Open OBS Statistics while the stream is running and note the values at the time of the symptom. In particular, check dropped frames, rendering lag and encoding lag, and whether the stream disconnects. The counters help distinguish a connection branch from local rendering or encoding pressure; they do not identify the precise failing source. Write down whether a counter is increasing during the freeze, rather than relying on a later glance after the stream has recovered.
If dropped frames rise, follow OBS’s connection guidance and note the configured bitrate, network type and any VPN or security software in use. If rendering or encoding lag rises, reduce competing GPU activity or simplify the scene for a controlled test. If neither appears while viewers report buffering, compare with another viewer and check platform playback conditions. A quiet counter narrows the evidence; it does not prove that all viewers can receive the stream smoothly.
Save the OBS log from the relevant session. OBS’s Overview Guide recommends including a log when asking for support. Along with the log, provide the OBS version, operating system, exact source type, what the source points to, the approximate time of the freeze, whether audio continued, and what preview, recording and YouTube each showed. If you changed a source property, say what it was and what changed in the next test.
For a channel intended to stay live overnight, take notes before the next long run rather than waiting for a second incident. A short controlled test can establish whether a file reaches its end or whether the source freezes while still expected to play. If your content is generated from a fixed local file, the black-screen rain stream guide using FFmpeg offers a different workflow to consider when comparing playback approaches; it is not a diagnosis or a universal replacement for OBS.
Where operating the computer continuously is itself the recurring problem, StreamNeo removes the need to leave your own computer running for the broadcast by turning an uploaded video into a continuous YouTube stream. That is a workflow choice for a file-based channel, not a repair for an OBS source that has frozen, and you should still verify that your video and channel are ready before changing how you operate.
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 one frozen frame mean my internet connection is failing?
No. A frozen picture can arise in source playback, rendering or encoding, or in the outgoing connection, and the symptom alone does not select one. Check OBS’s dropped-frame counter and compare preview, recording and YouTube before following the connection branch.
Why does OBS keep showing the last image from a video?
A local media file may have reached its end, and OBS can leave the final image visible. Check the file’s playback position and Media Source properties, including “Show nothing when playback ends”; that setting applies to end-of-playback behaviour, not every live freeze.
What if OBS looks fine but YouTube viewers see a freeze?
Compare a local recording from the same interval with YouTube playback and check OBS Statistics for dropped frames or disconnections. If OBS is not dropping frames, viewer connectivity or platform playback may still be involved, so ask whether the symptom is shared rather than assuming the source is at fault.
What should I send when asking for help?
Include the OBS log and the exact source type, along with whether audio continued and what the preview, local recording and public playback showed. Add the relevant Statistics observations and any source-property changes you tested; those details make it possible to investigate without guessing from the still frame.