Why a downloaded video will not open
Check whether the transfer completed before changing formats. A complete file may still use a container or codec that your player cannot handle. Confirm the actual media information, then try a compatible available output or player. Renaming the extension cannot convert the video or repair missing data.
Open the relevant downloader · Platform tools and access limits
Confirm that you are opening a complete media file
Find the exact saved copy through the browser's Downloads entry. Check that its size is nonzero and that the browser no longer reports an active or interrupted transfer. A temporary partial file is not a final video, even if its name resembles the intended download.
If the file opens as text or a web page, inspect whether you saved an error response rather than media. A very small HTML document cannot be repaired by assigning an MP4 extension. Return to the original source and obtain a fresh ready file. Keep the original error text until you know whether the failure happened during processing, transfer, or playback.
Compare the container and codecs with the player
A container packages streams; codecs describe how those streams are encoded. An MP4 name alone does not prove support for every possible video and audio codec inside it. Inspect the player's information or a trusted media-inspection utility to identify the actual combination.
Try opening the same complete file in a player that supports that combination. If it works there, your original player's compatibility is a likely limitation. If the source inventory offers an alternative suitable for your target device, choose it instead. Do not download codecs or installers from an unexpected pop-up promising to unlock the file.
Check audible sound with missing or black picture
When sound plays but picture is absent or black, inspect the completed file with ffprobe -v error -show_streams -of json saved-video.mp4 and identify whether an actual video stream exists. An audio-only file, a disabled video presentation and a stream the receiver cannot decode are different cases. A thumbnail is not evidence that the saved artifact contains the expected moving pictures.
Compare the same known scene in a compatible second receiver and with the authorized source reference. The scene itself may be intentionally dark; do not diagnose missing picture solely from one black frame. Keep the file unchanged while comparing the decoding and display paths. If the expected video is absent, use the actual source inventory or an authorized owner copy rather than relabeling sound as a complete video.
Troubleshoot damage and destination restrictions
Test the beginning, middle, and end where playback is possible. Failure at the same point in several players can indicate damaged or incomplete data, although the symptom alone is not a diagnosis. Compare against a fresh complete copy from the same authorized source.
Check that the file is actually local and readable. A cloud placeholder, disconnected drive, or inaccessible directory can prevent opening without involving codec support. Copy an authorized file to an accessible local folder and retest. Report the container, codecs, size, player, and exact error if the issue remains. Avoid repeatedly choosing higher resolutions: more pixels do not repair missing data or make an incompatible decoder available.
Worked example
Illustrative case: a nonzero WebM plays in a compatible desktop player but not in the receiving application. That points to the receiving application's supported formats. An offered MP4 with suitable codecs may be the practical alternative; changing the WebM filename is not.
Related guidance
Sources and verification
Reviewed 2026-10-13. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.