Do you mean controls you can see in OBS while operating it, or controls viewers can see in the stream? OBS’s media controls belong to its interface; their presence there does not prove they are in the encoded scene. If viewers see them, trace the scene source that is rendering them, then hide, remove or replace it.
For one local video, use an OBS Media Source with Loop enabled. For several files, use a VLC Video source with Loop Playlist enabled. A browser page or player is a different case: its controls may be part of the page content, and there is no universal setting that removes controls from every embedded player.
First check what viewers actually see
Look at the stream output, not only the OBS editing window. Preview or program output can help you inspect the composed scene; if you need to confirm what reaches viewers, make a short private or unlisted test and check its playback. Do not infer the result from the presence of a toolbar beside a source in OBS.
This distinction matters when you are running a devotional channel overnight, looping recorded classes, or showing a local news sequence. You may see playback buttons while selecting or operating a source, while the scene itself remains clean. Conversely, a scene can contain a captured desktop or browser page that includes buttons, even though those buttons are not OBS’s own toolbar.
If you can see the controls in the actual output, pause before changing random OBS preferences. Note the scene selected, inspect its Sources list, and identify what each source represents. A quick way to narrow it down is to hide one likely source with its eye icon, observe the preview, then restore it if it was not responsible. Avoid changing several sources at once: that makes it harder to tell which change fixed the picture.
If a test stream is not appropriate, inspect the scene preview and source visibility carefully, but remember that the preview is still an operator-side check. A source can be visible in the scene without being the source you thought it was. The cause cannot be determined without knowing whether the controls appear only in OBS, in the stream output, or inside a browser or player source.
OBS interface controls are not scene content
OBS exposes media playback controls as part of its operator interface. Depending on the version and layout, a source toolbar or context bar may appear while you select a media source. Those controls help you operate playback; their appearance in OBS alone does not mean they are being sent to YouTube.
If you only want to clear the controls from your working view, deselect the media source or use the relevant toolbar/context-bar interface command. OBS’s English interface strings include “Show Source Toolbar” and “Hide Context Bar”, though wording and placement can differ between releases. Treat this as a change to what you see while operating OBS, not as proof of a change to the encoded video.
If viewers are seeing controls, hiding an OBS toolbar is not the right diagnosis by itself. Instead, inspect what the scene is capturing. A display capture can show the whole monitor, including OBS; a window capture can show an application window; a browser source can render a web page or player. In each case, the controls may be part of the captured or rendered content rather than an OBS interface overlay.
Keep the two questions separate: “How do I tidy the OBS workspace?” and “How do I remove controls from the broadcast?” The first is an interface preference. The second is a scene-source problem. This separation is useful when following setup advice too: a guide to a prerecorded-video YouTube channel can help you plan the broadcast, but it cannot identify which source in your own OBS scene contains a visible control bar.
Inspect display and window captures
Start with sources named Display Capture, Window Capture, or similar. Read the source name and look at the image in the preview. If the source captures the monitor on which OBS is open, it may include OBS itself, along with source lists, playback controls, and other operator-only elements. A window capture can likewise show controls if it points at a media player window rather than the intended clean content window.
Check the capture’s target and crop. If the intended output is a video image, a capture that includes the player’s surrounding interface is likely the wrong source path. Where practical, use the original video as a media source instead of capturing the desktop player. If you need to capture an application, select the intended window and adjust the crop so unrelated areas are not included. Then inspect the preview again.
A source may be obscured by another source or may sit above it in the composition. OBS documents that source ordering affects what is drawn on top, and the eye icon controls whether a source is shown. The OBS sources guide explains visibility and ordering. A control bar visible only in one scene may come from a capture source that is enabled there but hidden in other scenes.
Test with reversible changes. Toggle the eye icon for one capture source and note whether the controls disappear. If they do, you have identified the source to replace, recrop, or leave hidden. If the video disappears but the controls remain, restore it and inspect another source; the toolbar may be coming from a browser source or a separate overlay.
Check browser and player sources
An OBS Browser Source displays a web page inside the scene. That page might be a custom HTML player, a dashboard, or an embedded video player. If controls appear within the page area, they may be generated by the page or player rather than by OBS. The OBS Browser Source documentation describes it as a browser page source and covers its dimensions and custom CSS support.
Inspect the URL or local HTML used by the source. Ask whether the controls move with the page content, and whether hiding the Browser Source removes them from the preview. If the page is under your control, review its player configuration and styles. Do not assume that CSS can remove controls from every third-party or YouTube player; the documentation does not establish a universal method for doing so.
A browser player may also show controls only on interaction or when the pointer is over it. Check the source preview and the actual output after the page has loaded, not just the moment you add it. If the page has a loading state or a play prompt, that can be a separate visible element from the playback controls. Resolve the page or player behaviour at its source where possible, or use a clean local media source instead.
If you use a YouTube Live Control Room break slate, distinguish that from ordinary media controls. YouTube documents a specific break overlay workflow and notes that its Browser Source can be hidden using the source eye icon if the break cannot be ended in Live Control Room. That guidance applies to the documented break slate, not to every player toolbar; see YouTube’s break slate instructions.
Hide, remove or reorder the responsible source
Once you have identified the source, choose the least disruptive fix. Hide it if it is not needed during the broadcast. Remove it if it was added by mistake and has no role in the scene. Replace it if it is the wrong way to provide the loop—for example, replace a captured desktop media player with a Media Source for a local file.
If the source needs to remain, consider its order and dimensions. A source higher in the list is drawn on top of lower sources, so a separate source could be covering part of the video with a control panel. Reordering can reveal whether that is the issue, but it will not remove controls that are baked into the image of a capture or rendered within a web page. Fix the source content in that case.
After each change, inspect the preview and, where needed, run a short private or unlisted test. Confirm the intended image still appears, the controls are gone from output, and the audio remains as expected. Save the scene collection after a confirmed fix so you do not have to repeat the diagnosis after restarting OBS.
If you are comparing ways to run a long playlist, remember that the encoding path and the scene content are separate decisions. A playlist-transcoding guide concerns preparing a playlist for broadcast; it does not change what an OBS capture includes. For a long-running setup, choose the path you can inspect and restart reliably, then test the scene that actually goes live.
Use Media Source Loop for one local file
For a single video file stored on the computer running OBS, add a Media Source and select the file. Enable Loop in that source’s properties. OBS describes Loop as replaying the file when playback completes; the Media Sources guide covers the source and its properties.
This is usually cleaner than opening the file in a separate desktop player and capturing that player window. The media is then a scene source rather than a window with its own playback interface. If controls remain visible after you change to a Media Source, check whether another capture or browser source is still visible; changing the file’s loop setting cannot remove controls rendered by a different source.
Check the file path and the scene’s source visibility before leaving the channel unattended. If the file is moved or renamed, the source may no longer refer to the intended media. Start playback, watch past the end of the file to confirm it restarts, and check the outgoing composition. A local loop is suitable for one file; it is not a playlist manager and its Loop setting does not handle a multi-file playlist.
For readers comparing local playback with other broadcast approaches, the practical question is what needs to run and be monitored while your own computer is on. A comparison of VPS options for looping video can help frame that separate operating decision. Regardless of the method, confirm that the outgoing image itself does not include a desktop or player control bar.
Use VLC Video Loop Playlist for several files
For a playlist of files, use OBS’s VLC Video source rather than trying to make a single Media Source act as a playlist. Add the files to the VLC Video playlist and retain or enable Loop Playlist. OBS notes that VLC must be installed for the VLC Video source type to be available; its Media Sources guide covers both source types.
If VLC Video is missing, install VLC and reopen or check OBS. The guide notes that a matching 64-bit VLC installation is needed when using 64-bit OBS. Menu wording and setup details can vary by version, so consult the current OBS documentation if the source does not appear after installation.
Check the playlist order and each file before relying on it for an overnight stream. Confirm that the source plays through the files and returns to the start of the playlist, and inspect the output at a transition. The Loop Playlist setting is for the VLC Video playlist; it is not a setting in Media Source that makes a collection of separate files loop.
| Source path | Best fit | Loop behaviour | Where to look if controls appear |
|---|---|---|---|
| Media Source | One local video file | Enable Loop to replay that file | Other visible sources, or controls included in a captured image |
| VLC Video | A playlist of local files | Use Loop Playlist | Source visibility, source order, and the actual outgoing preview |
| Browser Source | A web page or embedded player | Depends on the page/player | The page, player configuration, or local HTML |
| Display/window capture | Capturing a screen or application | Depends on the captured app | The capture target and whether its interface is inside the captured area |
The table is a diagnostic distinction, not a recommendation that one source fits every channel. A web player may suit a page-based presentation; a local file or playlist can avoid capturing a separate player interface. Choose based on the content and how you intend to maintain it, then check the actual scene rather than assuming the source type guarantees a clean output.
If you need a longer-term way to keep a prerecorded stream running without leaving your own computer on, StreamNeo removes that specific need to keep the local machine operating: upload the video, provide your YouTube stream key, and the broadcast runs from the cloud. It is YouTube-only, so it is not the answer if your workflow needs another platform or live scene switching in OBS.
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
Why can I see media controls in OBS but not in the stream?
OBS’s media toolbar or context bar is part of the operator interface, not proof that the controls are in the scene. Check the preview or a private/unlisted test to confirm what viewers receive. If the output is clean, adjust the interface view only if the controls distract you while operating OBS.
Why are viewers seeing controls over my loop?
A display or window capture may include a media player or the OBS desktop, while a Browser Source may render controls as part of its page. Inspect the Sources list and hide one likely source at a time with the eye icon. If the controls disappear, replace, recrop, reorder, or configure that source as appropriate.
Should I use Media Source Loop or VLC Video Loop Playlist?
Use Media Source with Loop for one local file. Use VLC Video with Loop Playlist for several files, and make sure VLC is installed if OBS does not offer that source. The single-file Loop setting does not turn multiple separate files into a playlist.
Can CSS hide controls in a Browser Source?
It depends on the page and player. OBS Browser Source supports custom CSS, but that does not establish a universal way to hide controls on every third-party or YouTube player. Inspect the page or player configuration you control, and use a different source path if you cannot remove unwanted controls reliably.