Inspect a local video with FFprobe without converting it

Start with the correct local file

Locate the completed file using your browser's download history and operating system. Confirm its identity before inspecting it: a preview URL, HTML error document and partial transfer are different objects. Preserve the copy while gathering evidence; inspection does not require overwriting it.

Use a trusted installation of FFprobe associated with the FFmpeg project. This is an optional local diagnostic utility, not software the site requires you to install to perform an ordinary download. Avoid installers presented by unrelated advertisements, and use the distribution method appropriate to your computer or managed environment.

Run a report rather than a conversion

A useful command for a file in the current folder is: ffprobe -v error -show_format -show_streams -of json -i "saved-video.mp4". Replace the quoted filename with the actual local path, retaining appropriate shell quoting for spaces. This command requests a structured report; it does not specify an output media file or ask FFmpeg to transcode.

FFprobe documents separate format and stream sections and a JSON output writer. The format section describes the enclosing resource. Stream records describe individual video, audio or other components. Inspect all returned streams instead of assuming the first record is the soundtrack or that every file has exactly one video and one audio stream.

Record only the fields needed for the question

For picture compatibility, look for the video codec and relevant dimensions or encoding constraints. For silence or language selection, inspect audio stream count, codec, channel information and any supplied tags or disposition flags. Record missing information as unknown, not as a guessed language or channel position.

A container name and an extension can differ in specificity. Likewise, an audio sample format is not the same measurement as encoded bitrate. Use the reported fields to identify what the player must handle, then consult the receiving application's actual requirements. The report is evidence for diagnosis rather than an automatic choice of the best format.

Verify playback and sanitize a shared report

Play representative passages in a compatible application after inspecting the metadata. Header information can be readable even when later data is incomplete or a decoder cannot handle the stream. Conversely, one program's inspection failure needs its actual error investigated; it does not identify every possible storage or access cause.

Before sharing output, remove unnecessary local usernames, folder paths and sensitive metadata while preserving the technical fields relevant to the problem. Do not substitute account cookies or private media URLs for the local input. SocialVidDownloader does not use this article as a private-content retrieval workflow, and a local inspection cannot create missing tracks or reconstruct an absent recording.

Worked example

A saved MP4 plays silently in one app. FFprobe reports one video stream and one AAC audio stream, so the observation does not support the claim that the file contains no audio. Test that same file in a compatible player and inspect stream selection. If no audio stream is reported instead, investigate the actual selected source/output rather than trying to invent audio by renaming the file.

Related guidance

• Video container versus codec: diagnose the right layer
• Why a downloaded video will not open
• Downloaded video has no sound: identify the missing stage
• Report a download error without exposing credentials

Sources and verification

• FFprobe options, stream sections and JSON writer
• FFmpeg stream and container concepts
• OWASP minimizing sensitive diagnostic data

Reviewed 2026-10-08. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.