How to Test an X/Twitter Video Download Result
Record a reproducible X/Twitter link check, inspect the saved MP4 tracks with ffprobe, and distinguish an audible result from a silent AAC stream.
Record the post ID and a recognizable moment in the original. Test both the detected media and the actual saved file. A post that resolves correctly can still yield missing audio, a short preview or an unusable file.

Start with one unambiguous post
Open the post permalink while signed out and identify the clip you mean. A quote-post can include another post; note which author and opening frame you saw. Watch a passage with sound and write down a short cue you can recognize again. If the post is private, removed or requires a login, stop and request an authorized copy.
A dated example with a deliberately limited result
On November 3, 2026, we submitted a public space-agency post about the Fermi telescope anniversary (account and status shortened here: NASA…/status/…8859139). Both the x.com and twitter.com forms returned the same title and one MP4 entry in the production web checker. The local yt-dlp list identified one HTTPS MP4 format; resolution and codecs were unknown. No saved X file was inspected in this comparison. The entry to put in a test log is matching candidate found. A blank “saved file” field prevents that result from turning into a false playback claim. See the side-by-side URL comparison.
Verify picture, duration, seeking, and audio
Open your permitted saved copy from local storage. Play the first few seconds, seek to the reference cue, then play the ending. Check both sync and duration. To see what streams the container holds, run:
ffprobe -v error -show_entries stream=index,codec_type,codec_name:format=duration,size clip.mp4
If there is no codec_type=audio, the file contains no recognized audio stream. If an AAC stream appears, the file can still contain silence. Compare a passage known to contain speech in the original and confirm your output device works using another clip.
Compare an AAC track listing with the silent clip it describes. Record what you hear during playback separately from what the metadata reports.
Keep a record another person can reproduce
Write down the date, browser/device, post ID and expected clip, the returned format or visible error, and the saved file’s byte size and duration if available. Finish with one sentence describing what you actually saw and heard. “One MP4 detected; no file saved” and “the final line of speech plays in sync” communicate different outcomes. Record the observed result before changing player, URL form or rendition so a later comparison has a clear starting point.
FAQ
Does seeing AAC in ffprobe mean the soundtrack is audible?
It identifies an encoded audio stream. Listen to a known passage to distinguish silence, an output-device problem and the wrong track.
What should I record when the post resolves but the save fails?
Keep the matching title and returned format, then record the failed stage and visible message. Leave file size, duration and playback unverified.
Related pages
Twitter Video Download Failed or No Video Found? What to Check
Troubleshoot a failed X/Twitter video download or 'no video could be found' message by checking public access, canonical /status/ URLs, HLS streams, and retry limits.
X/Twitter Video Download Has No Sound? Check and Fix Missing Audio
Fix a silent X/Twitter download: check whether the source has sound, inspect the saved audio track, and distinguish a video-only file from a player problem.
X/Twitter video download test methodology
A reproducible method for testing permitted public X/Twitter video URLs without turning one result into a universal support claim.
Twitter GIF Downloader: Save Public X GIFs as Video
Learn why X/Twitter GIFs often download as MP4 video, how to save a public GIF-style post, and when a true .gif conversion is unnecessary.