If OBS says a media source file is missing after a reboot, first identify the source named in the warning. A missing local file needs its saved path restored or updated; a stopped YouTube playlist or other network input needs a separate playlist and playback diagnosis.
The distinction matters because changing a local file path cannot repair a network stream that has stopped. Check the source type and its own properties before changing scene settings, reinstalling software, or rebuilding the broadcast.
Identify the source named in the warning
When the warning appears, note the exact source name and, if shown, the file name or path. In OBS, a scene can contain several sources, and the source that reports a problem may not be the one you think of as the main video. Select the relevant scene and inspect its source list; the OBS sources guide explains how sources are organised in scenes.
The wording is a clue, not a complete diagnosis. A message that names a local media file suggests OBS cannot find a file reference used by a Media Source, or by a local-file entry inside a playlist. If the source is instead a VLC Video Source containing playlist entries, or a browser or other network input, the source may still be listed while playback is unavailable. Those situations call for different checks.
Open the source's properties and identify what it is configured to read. A Media Source is intended for a media file. A VLC Video Source can hold a playlist and depends on VLC being installed. The OBS Media Sources documentation describes both source types and their controls. Do not infer that rebooting itself changed anything: it may simply be when you noticed a pre-existing path or playback problem.
A quick comparison helps keep the two investigations separate:
| What you see | Input to investigate | First check |
|---|---|---|
| Warning names a missing local video or audio file | Media Source, or a local-file playlist entry | Does the file exist at the saved location? |
| Playlist source remains in the scene but stops or freezes | VLC Video Source or another network input | Are the entries available, and does the source play in OBS? |
| Source plays in the OBS preview but is absent to viewers | Scene or outgoing stream path | Check visibility, scene selection, and stream output separately |
If you are building a long-running channel rather than fixing one source, keep the source diagnosis distinct from the broader choice of workstation or cloud workflow. The comparison in OBS versus cloud streaming for a 24/7 YouTube channel can help with that operational decision, but it does not replace checking the source that OBS has actually flagged.
Restore or update a missing local file path
For a local Media Source, select it in the scene and open Properties. Check the file path shown there. Then locate the actual file in your file manager and compare the location and name, including the file extension. If the file was moved, either put it back at the saved location or use the browse control in the source properties to point OBS to its present location. OBS community guidance for a missing-file case likewise describes updating the location or removing a source that is no longer needed; it is an example rather than a universal diagnosis (forum discussion).
Check that the file itself is accessible and that you selected the intended copy. It is easy to have two versions with similar names, for example an older intro video in a downloads folder and the current one in a channel-assets folder. Pointing OBS to the wrong copy may clear the warning while leaving the scene with outdated content. If the warning concerns audio, follow the same location check and then listen for playback in OBS.
Consider what changed between the last working session and the reboot. A file may have been renamed, moved into a different folder, or stored on a drive or removable device that is not available now. A drive letter or mount point can also differ across setups, but do not assume that is the cause until you inspect the path and confirm the storage is present. Reboot is a timing clue, not proof of a reboot-specific failure.
If the file is on removable or network storage, make sure that storage is connected and available to the user account running OBS before opening the project. For a channel expected to remain on overnight, a source on a drive that is disconnected or not mounted at startup can fail even when the project file itself opens normally. Choose a stable location you can keep available, then update the source to that location and test it.
If the media is no longer part of the programme, remove the obsolete source instead of leaving a broken reference in the scene. Before removing it, check whether another scene uses the same source. OBS scenes can reuse sources, so removing a source from a scene or deleting it from the project may have different consequences depending on the action and version. Confirm the visible result in the scene before saving.
After updating the path, use the source's preview or the OBS canvas to see whether the intended picture appears. If it does not, recheck the selected file and format rather than turning to playlist settings. For a larger repeating programme made from local files, the non-stop YouTube loop encoder checklist is a separate guide to broadcast preparation, not a substitute for correcting this individual reference.
Distinguish Media Source from VLC Video
Media Source and VLC Video Source sound similar but serve different jobs. Media Source points to media files. VLC Video Source can manage a playlist, including multiple entries. If you place a YouTube playlist URL into a workflow based on VLC, that is not the same as a Media Source pointing to a video file on disk. The local-path repair described above only applies when the failing reference is local.
For VLC Video Source, OBS documents a dependency on VLC being installed. It also notes that 64-bit OBS requires 64-bit VLC. If a playlist source is missing or fails to load after a system change, check that VLC is installed and matches the OBS architecture before changing its playlist. This requirement does not establish that VLC is the reason for every stopped stream; it is one specific prerequisite to verify.
Open the playlist source's properties and review its entries. A playlist may mix local files and URLs, so inspect the failed entry rather than treating the whole source as one kind of input. For a local entry, verify the file and location. For a network entry, determine whether the URL or service remains accessible using the relevant source's own playback behaviour. A path update for one local entry does not restore an unavailable URL, and a valid URL does not fix a missing local file elsewhere in the list.
Also distinguish visibility behaviour from availability. OBS's VLC controls include options related to looping and what happens to playback when the source becomes visible or hidden. A playlist that starts over when shown, or stops when hidden, can look like a reboot failure if you only inspect the scene after switching to it. Review these settings when the symptom is unexpected stopping or restarting, and compare the result with what the source does in the preview.
A practical channel often has an intro, a recurring visual, and a playlist as separate sources. Name them plainly, such as “Intro file” and “Music playlist”, so the source in an error message is easier to identify. If you are deciding how to handle a playlist assembled from local assets, the guide to adding background music to a nonstop stream offers a different workflow context; it does not change OBS's source-type distinction.
Check a playlist or network input separately
If the warning does not name a missing local file, or the source is a playlist/network input, leave the local file repair aside and inspect that input. Start with the source's properties: are the expected playlist entries still listed, and do they point to the intended local files or network locations? For local entries, test file availability individually. For network entries, confirm that the address and service are still valid and that the source can reach them. Avoid treating a YouTube playlist as if it were a video stored in a folder.
Then check the VLC prerequisite if the source is VLC Video Source. Confirm VLC is installed, and, when using 64-bit OBS, use 64-bit VLC as OBS's documentation specifies. If VLC is unavailable or mismatched, address that dependency and reopen OBS to test. If it is already present and correctly matched, continue to the playlist and playback checks rather than repeatedly reinstalling it.
Review loop and visibility options in the VLC source. Decide what should happen when the playlist reaches its end and when the source is hidden or made visible. If the source sits under another source, or the scene changes during a loop, visibility changes may affect its playback depending on the selected behaviour. Test those transitions deliberately: show the scene, hide it, and show it again while watching the preview. This isolates a setting-related restart from a network input that has stopped responding.
Network playback can fail for reasons that have nothing to do with a local path: the URL can be unavailable, the remote stream can pause, or the source application can stop decoding. First establish whether the input works at all in OBS. A reported freeze of a VLC source ingesting a YouTube playlist exists in an OBS forum thread, but one user's report is not evidence of a common cause or a universal remedy (discussion). Do not conclude from the word “YouTube” alone that YouTube, VLC, or OBS is at fault.
If the playlist contains a direct network URL, check the source's exact URL and whether the source type supports the content you are giving it. Do not swap in a different URL or source type just to clear an error unless you know what that change does to playback and rights for the content. For music and devotional channels, keep an inventory of which entries are local files and which are network feeds; that makes the next failure quicker to narrow down without implying that either type is inherently more reliable.
Test the source before changing the broadcast
Use the OBS preview as a boundary between source troubleshooting and outgoing-stream troubleshooting. Select the scene and make the relevant source visible. If the expected image or sound does not appear in the preview, work on that source: confirm its path if local, or its playlist, VLC dependency, visibility and network behaviour if it is a playlist or network input. Save changes only after the correct content appears.
If the preview shows the source correctly, avoid changing its file path or playlist without reason. The problem may instead involve scene selection, source order, visibility, or the stream output. OBS's sources guide covers source arrangement and layering, which is useful if the source is playing but covered by another item. Check that the intended scene is active and that the source is not hidden or cropped out of the canvas.
Separate the local preview from what viewers receive. A source can render inside OBS while the outgoing live stream is disconnected or using a different scene. Conversely, the outgoing connection may be live while a specific source is blank. Observe the preview first, then verify the stream's status and the actual live picture using an appropriate monitoring view. This is a troubleshooting sequence, not a guarantee: it helps identify which part needs attention without assuming every failure has one cause.
For a repeatable test, make one change at a time and write down what you changed. For example, if you browse to a new file location and playback returns, save the project and test again without also changing loop behaviour. If you adjust playlist visibility settings, leave the URL alone until you know whether that adjustment changed the symptom. Changing several settings at once makes it difficult to tell which one mattered.
Before returning to a 24/7 broadcast, let the source play long enough to observe the behaviour relevant to the problem. For a file, check the opening and an ordinary section. For a playlist, watch an entry transition and, if relevant, the loop or hide/show transition. This is not a promise about future uptime; it is a way to check that the selected source behaves as intended under the test conditions.
Verify playback after reboot
Once the preview works, save the OBS project and test the same scene after a normal reboot when practical. Reopen OBS, confirm any removable or network storage is available, and inspect the source again. A source that works before restart but fails after it points you towards something that changes at startup, such as storage availability, a changed location, or a dependency that is not ready. Verify the actual condition rather than assuming a particular operating-system cause.
For local media, make sure the repaired path still resolves after login. If the source is on a drive that is mounted later, open the project only after that drive is available, or relocate the media to a stable accessible location and update the source. For VLC playlists, confirm VLC remains installed and the expected entries and settings remain in the source. For network inputs, check the input's playback independently after restart; a local-file path change is not a remedy for a network source that is no longer playing.
Finally, confirm the programme that leaves OBS, not only the scene editor. Check that the intended scene is selected, the source is visible, and the broadcast output is running as expected. If you monitor a 24/7 channel remotely, distinguish a blank source from a disconnected live output; the remote monitoring guide for an OBS 24/7 stream discusses that separate operational task.
If repeated reboot checks are difficult because the computer must stay on for the channel, StreamNeo removes the specific burden of keeping your own computer running for a file-based 24/7 YouTube stream: you upload a video, provide your YouTube stream key, and the broadcast can continue with your computer off. It is YouTube-only, and it does not repair an OBS source or diagnose a network playlist; decide whether that workflow fits only after the content and channel are ready.
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 does OBS say a media source file is missing after reboot?
OBS cannot resolve the local file reference used by that source, or by a local-file entry in a playlist. Check the source properties and verify that the file exists at the saved location; reboot timing alone does not prove the reboot changed the path.
Will changing the Media Source path fix my YouTube playlist?
No. Changing a Media Source path addresses a local file reference, not a stopped network input. Inspect the playlist entries, VLC availability where relevant, playback settings, and whether the source renders in OBS.
Does a VLC Video Source need VLC installed?
Yes. OBS documents that VLC Video Source depends on VLC, and that 64-bit OBS requires 64-bit VLC. Check this prerequisite, but do not assume it explains every playlist stop or freeze.
What if it plays in the OBS preview but viewers see nothing?
Then inspect the selected scene, source visibility and ordering, and the outgoing stream separately. A working preview is evidence that the source can render in OBS, not proof that the broadcast output is reaching viewers.