Before you try to repair a video that OBS will not play or stream, inspect it with ffprobe, VLC or MediaInfo to learn what is actually in the file. If it is readable and the problem appears to be its container, remuxing may help; neither inspection nor remuxing guarantees recovery of missing or damaged video data.
The useful distinction is between a packaging problem and a damaged stream. Start with a read-only check, keep the original untouched, and only then consider a specific next step. These free tools help you gather evidence; they cannot promise to restore every broken recording.
Inspect before trying to repair
A video file is more than its filename extension. It has a container, such as MP4 or MKV, that holds streams such as video and audio, and the streams have their own codecs and properties. A file named recording.mp4 might contain a stream that a particular player cannot decode, or it may be incomplete. Changing its extension does not fix either condition.
First note what happens when you open the file. Does playback start and then stop at a particular point, show a black picture with sound, fail immediately, or play normally in a separate player but not in OBS? These symptoms are clues, not diagnoses. The failure could be in the file, the player, OBS settings, or the live-stream connection.
A simple sequence reduces guesswork:
- Make a separate copy of the file, if you have enough storage.
- Read its properties with a probe or information tool; do not begin with a conversion.
- Try playback in a player such as VLC and note whether audio and video behave differently.
- If the file is readable and the evidence points to a container issue, consider remuxing the copy.
- Re-open and inspect the output before replacing anything in your OBS workflow.
This is a triage process, not a recovery recipe. If the file is absent, truncated, or its encoded stream is damaged, the information available from a probe cannot recreate the missing data. For a broader view of video properties and broadcast settings, see our guide to video encoding and YouTube Live settings.
Check the file with ffprobe
ffprobe is the media-inspection command-line tool in the FFmpeg toolset. It can report information about a file and the streams inside it without requiring you to start a conversion. The FFmpeg project documents both ffprobe and its wider documentation.
If you are comfortable using a terminal, a basic probe is often the quickest way to confirm whether the file can be read and what streams it reports. A common command is:
ffprobe recording.mp4
Replace recording.mp4 with the file's path. If it is in another folder, provide the full path, taking care with spaces in the filename. The exact output depends on the file and the FFmpeg build, but you are looking for whether ffprobe recognises the container and lists video or audio streams, along with codec and basic stream details.
Do not treat a long report as a verdict. A file may return stream information yet still fail later during playback because the data ends unexpectedly or contains a damaged section. Conversely, an error message may reflect an unsupported format, a path typo or a permission issue rather than irreparable corruption. Read the whole message and check that you probed the intended file.
ffprobe suits repeatable checks and gives more detail than a filename or a basic properties panel. Its trade-off is the command line: you must install FFmpeg from a trusted source, choose the correct file path and understand which output matters. If that friction is likely to make you mistype an operation, use VLC or MediaInfo for an initial graphical inspection instead.
Keep the first command read-only. FFmpeg can also process, remux and convert media, but those are separate actions that require deliberate options. If all you need now is to identify streams, do not paste in a repair command from a forum without understanding whether it copies, changes or discards data.
View codec information in VLC
VLC gives you a graphical first check. Open the file in VLC, then use Tools → Codec Information to see codec details. VideoLAN’s Windows FAQ describes this route; labels and menus can differ between versions and operating systems.
This can be useful if the terminal is unfamiliar. You can see whether VLC opens the file at all, whether picture and sound are present, and what codecs it reports. If playback works in VLC but not in OBS, that is evidence that the file is at least readable by one application. It does not prove OBS can use it in the way your scene or media source is configured.
Note where playback fails. If it reaches a point and then stops, write down approximately where; if it shows sound without picture, note that too. The observation will help you compare the file with a remuxed copy or investigate an OBS source setting. Avoid changing several settings at once, because that makes it harder to tell what affected the result.
VLC is also a player, which makes it convenient for a quick visual check. But playback alone is not a full integrity test, and a successful open does not prove every frame is sound. If VLC reports little useful detail, use MediaInfo for a more organised specification report or ffprobe for a command-line view.
Keep the file inspection separate from a live connection problem. If OBS plays your media correctly but a broadcast drops frames or disconnects, the file may not be at fault. OBS provides its own Help Portal for streaming and connection troubleshooting. You may also find it useful to compare the symptoms with our guide to why a 24/7 YouTube stream keeps disconnecting.
Use MediaInfo for detailed specifications
MediaInfo is useful when you want a more detailed, readable report about a media file’s technical properties. VideoLAN recommends it for fuller specifications when VLC’s codec information is not enough. It can help you record the container, video and audio codecs, dimensions and other reported properties without first attempting to alter the file.
That report is valuable when you need to explain a problem to someone else or compare a working file with one that fails. Capture the report before making changes, then compare it with a file that OBS accepts if you have one. Differences may point to a compatibility or configuration question, but they do not by themselves establish which difference caused the failure.
MediaInfo’s focus is reporting, rather than repairing. It is a sensible choice when you prefer a graphical report and need more than a basic player view, but it does not make an unreadable stream readable. If its report is blank or incomplete, that is not proof of a particular cause; it may simply be unable to parse the file sufficiently.
For a live channel built around a repeatable playlist, record the details of the source files that work. That gives you a practical reference when a replacement file behaves differently. Our article on updating lesson files without stopping a 24/7 stream covers the operational side of changing media; the inspection step here helps you check the replacement before it becomes part of that process.
When remuxing may help
Remuxing means taking existing media streams out of one container and putting them into another, without re-encoding the audio or video. It is a packaging operation. VideoLAN’s remuxing documentation describes the process in VLC, and FFmpeg can also work with media containers.
Consider a remux only when the file can be read and you have a reason to suspect that its container or packaging is the issue. For example, a player may read the streams but an application may have difficulty with the way they are packaged. That possibility is not a diagnosis: a codec incompatibility, a damaged stream, incomplete recording, or a separate OBS setting could produce a similar symptom.
A remux does not reconstruct frames or audio that were never written, and it does not repair damaged encoded data merely by moving streams into a different container. If a process reports errors while reading the source, do not assume that producing an output file means the result is complete. Keep the original and test the output from beginning to end, especially around any point where the source failed.
VLC offers a graphical route for some remuxing tasks, while FFmpeg offers a command-line route with more explicit control. Which is appropriate depends on your comfort with the interface and the options required. Check the current official documentation for the tool and version you use, and avoid options that re-encode or discard streams when your intention is only to change the container.
If a file is not readable enough to identify streams, stop and preserve it rather than repeatedly writing over it with different outputs. More specialised recovery depends on the actual format, failure and source of the damage; this guide cannot identify a safe universal procedure without those details. No free utility can be assumed to repair every damaged recording.
Keep the original and verify the output
Make the original read-only in your workflow: keep it where it is and direct any attempted operation to a separate copy. This matters because a failed conversion or an incorrect command can leave you with a new file that is no better, while an overwritten source may remove your only usable version. If storage is tight, at minimum avoid overwriting the source and make a copy before a tool writes an output.
Give the output a distinct, descriptive name, such as recording-remux-test.mkv, rather than using the original name. Keep a note of the tool, the operation and any error message. This small record helps you distinguish the untouched source, the test output and any later version. It also makes it easier to stop repeating an attempt that did not change the result.
Then verify the output in more than one way. Inspect it again with the tool you used before, check that the expected audio and video streams are listed, and play it in VLC. Seek near the beginning, middle and end, and check the point where the original failed. A file that opens is not necessarily complete; a file that plays once is not proof that every segment is intact.
If the output works in VLC but still fails in OBS, test it in a simple OBS scene with the relevant media source and review the source settings. Do not infer that another remux is the answer until you have separated file playback from OBS configuration. For stream encoding settings, our keyframe interval guide for YouTube Live is a separate reference; it addresses broadcast configuration rather than repairing a source file.
OBS itself is free software, and its official Help Portal describes it as open source under GPLv2 and suitable for commercial use without restrictions. That says nothing about whether a particular video file is healthy or compatible. Keep the two questions distinct: is the file readable, and is the stream configured and connected correctly?
For a 24/7 channel, repeatable checks are particularly useful when replacing a loop or preparing a new programme. If your source is ready but you do not want your own computer to remain on to keep a file-based YouTube broadcast running, StreamNeo removes that specific operational burden: you upload the video once, provide your YouTube stream key, and the channel can run with your computer off. It is YouTube-only, so check that this matches your workflow; it does not remove the need to prepare and verify your media.
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
Can free software repair any broken video file?
No. ffprobe, VLC and MediaInfo can help you inspect a file, and remuxing can be worth trying when the streams are readable and a container problem is suspected. None of those steps guarantees recovery of missing, truncated or damaged stream data.
Should I start with VLC or ffprobe?
Start with VLC if you want to see whether the file plays and prefer a graphical interface. Choose ffprobe if you are comfortable with a terminal and want a repeatable report of streams and properties; either can be followed by MediaInfo for a more detailed readable specification.
Does remuxing change the video quality?
A remux changes the container while carrying the existing streams; it is not the same as re-encoding the video. It cannot restore information missing from those streams, and the outcome depends on whether the source can be read and packaged successfully.
What if the video plays but my YouTube live stream drops frames?
That symptom may come from the streaming path, network or OBS configuration rather than a damaged source file. Check OBS’s current official troubleshooting guidance and investigate the broadcast separately from file repair.