If a downloaded MP4 will not play, first decide whether you have a complete media file or only an interrupted, expired, or incorrectly saved response. Check that the download finished, the file has a plausible size, and a second current player also rejects it. An .mp4 extension identifies a container; it does not guarantee that every device can decode the video and audio streams inside.
A zero-byte or unusually tiny file points to an incomplete save. A file that works in one player but not another points to codec support. A file that fails everywhere but still has valid streams may be damaged or unfinished. Renaming the extension does not repair any of these conditions.
Confirm that the download actually finished
Look in the browser's Downloads panel before opening the file from a notification. It should show a completed state rather than paused, canceled, or failed. Then inspect the local size. A two-minute video is not expected to be a few kilobytes; a tiny result may be an error page, redirect response, or partial file rather than the video.
Pullvio completed jobs expose temporary provider links. “Ready” means the result was available when the job finished, not that a provider URL will remain permanent. Save the file promptly and let the browser complete the transfer before closing the tab or moving the file. If the link expired before the save began, start a new authorized job; if a complete local file already exists, refreshing the old link will not change its codec.
On mobile, confirm that you opened the finished item from Files or Downloads, not a temporary browser preview. The iPhone and Android download guide lists the normal save locations.
MP4 is a container, not a single video format
An MP4 file can contain H.264/AVC, H.265/HEVC, AV1, or another video stream, plus AAC or a different audio stream. The filename can be correct while an older phone, television, editor, or system player lacks the required decoder. MDN's video codec guide recommends H.264 video with AAC audio in MP4 for broad browser compatibility, but MP4 itself does not enforce that combination.
This explains a useful diagnostic: if the file opens in one maintained player but not in another app, the download is probably intact. The failing app may not support the codec profile, bit depth, resolution, frame rate, or audio stream. Update the operating system and player before converting the file.
Do not solve this by changing .mp4 to .mov, .mkv, or .avi. A new suffix changes the label that software sees; it does not rewrite the streams or container structure.
Inspect the file instead of guessing
On a computer with FFmpeg installed, ffprobe can show whether the file contains recognizable streams and how they are encoded:
ffprobe -v error -show_entries format=format_name,duration,size -show_entries stream=index,codec_type,codec_name,width,height -of default=noprint_wrappers=1 your-video.mp4A normal result should identify an MP4-family format, a positive duration and at least one video stream. If ffprobe reports invalid data, reaches an unexpected end of file, or finds no streams, the transfer may be incomplete or the saved response may not be video. The official ffprobe documentation explains that the tool gathers information from a multimedia stream and returns a failure code when a file cannot be opened or recognized.
Do not upload a private file to an unknown “repair” site simply to learn its codec. Local file properties, a trusted player, or ffprobe can answer the first questions without sending the media elsewhere.
Why playback can fail on one device
Hardware and software limits matter. A device may decode ordinary 1080p H.264 but reject 4K HEVC, a 10-bit profile, or a frame rate beyond what its hardware handles. Apple notes that HEVC support varies on older devices and that 1080p at 60 fps or below is more broadly compatible there. Its HEVC support guidance also describes exporting as H.264 for greater compatibility.
Try a current browser or a maintained media player on the same device, then try a second device if available. If every device rejects the file and ffprobe cannot read it, suspect the file. If one device plays it, preserve that original and treat the problem as compatibility.
A black picture with audible sound, or sound with a frozen first frame, is also useful evidence. It suggests one stream is decoding while another is not. That is different from the no-audio diagnosis, where the video picture already plays normally.
When conversion is appropriate
For media you own or are authorized to modify, one conversion to a broadly compatible H.264/AAC MP4 can help when the original streams are valid but the target device cannot decode them. Keep the original first. Conversion is lossy in most everyday workflows, so do not run the result through several online converters in succession.
Conversion cannot reconstruct an interrupted file whose final data never arrived. It also cannot turn an HTML error response into a video. If ffprobe cannot find a valid stream, return to the source and make one clean save while the authorized public link is still available.
For your own upload, the camera master or editing export is a better starting point than a platform copy. For someone else's work, ask the rights holder for a compatible authorized file rather than bypassing private, paid, regional, or DRM restrictions.
How to handle an unplayable Pullvio result
When a Pullvio job reaches Ready, start the browser download while its temporary result link is active and wait for completion. If the browser reports a failed transfer, one new request can be reasonable. If it reports success and the complete file fails in two players, collect evidence before using another provider request.
Record the source URL, platform, Video or Audio mode, requested quality, local filename and size, device, player, completion time, and any ffprobe error. Submit those details through the Pullvio contact page. Never send account cookies, private links, access tokens, or a copyrighted file you are not permitted to share.
For an authorized public YouTube source, the YouTube downloader produces the selected result from the available provider response. A repeated failure across unrelated public sources may indicate a provider incident; a single file that only one old player rejects is more likely a local compatibility issue.