Explainer
Facebook video quality, explained
Why a Facebook video offers HD and SD but not 4K, what the streaming ladder is, and why a file taken from it downloads without sound.
Last updated · Published by FDownloader
One upload is not one file. When a Facebook video page is read, its public metadata describes several different representations of the same recording, and the gap between those representations explains nearly every complaint people have about saving video from this platform: why the choice is between two qualities rather than six, why nothing offers 4K, and why a file obtained elsewhere sometimes turns out to be silent.
What follows is the reasoning behind what this tool puts in front of you. It comes from watching what Meta's servers return on every lookup rather than from a specification, because Meta publishes no format guide for anyone outside its own player.
The two things Facebook publishes
Progressive MP4 passes
Complete files. Picture and sound sit in one container, so the bytes you receive play as they are. Facebook commonly publishes two — a larger pass it labels HD and a smaller one it labels SD — and sometimes just one.
Status: Offered here, HD at the top.
An adaptive streaming ladder
The rungs Facebook's player steps between when your connection wobbles, delivered as separate video and audio streams that the player combines while it plays. Rungs advertise precise pixel dimensions, which is what makes them tempting.
Status: Ignored here, on purpose.
Both describe the same minutes of footage. Only one of them is a video in the sense of a thing you can keep.
Why the ladder looks better than it is
Adaptive streaming exists so a player can change quality mid-playback without starting over. Facebook's ladder is published in the DASH shape, the same broad approach most large video services use. To make switching cheap, the picture is cut into one set of streams and the sound into another. The player fetches from both at once and stitches them together in memory, switching video rungs as bandwidth allows while the audio carries on uninterrupted.
That architecture is excellent for playback and useless for downloading. Take a rung and write it to disk and you have written down half the video: the frames are all present, correct and sharp, and there is no sound anywhere in the file, because the sound was never in that stream to begin with. Combining the two back together is a separate job requiring a muxer, and it is a job most download sites skip.
They skip it because the ladder reads so well in a list. Its rungs carry exact pixel dimensions, sometimes higher than anything the progressive passes offer, and a long menu of numbered resolutions looks more generous than a choice between two.
A shorter list, deliberately
So the list you get here has two rows on a typical video and one row on plenty of others. That is not a reduced feature set; it is the complete set of files Facebook publishes that are whole videos on their own. HD sits first because it is the larger of the two, and whichever row you pick is streamed through untouched — not re-encoded, not resized, not watermarked, not stamped with a logo.
One caveat belongs next to that. A minority of videos hand their larger pass only to a viewer Facebook recognises as logged in, and no session is ever held here, so in those cases the smaller pass is what comes back. Fewer rows than Facebook's own player shows is occasionally the price of never being asked for a password.
Why 4K is not on the menu
Facebook re-encodes what you upload. The files it then serves are its own encodes, produced to be delivered millions of times rather than to preserve every bit the uploader had. The HD pass is the best copy Facebook itself distributes, which makes it the ceiling for any tool that reads what Facebook distributes — this one included.
The uploader's untouched original is not published anywhere. It exists on their phone or their hard drive, and asking for it politely does not help. So a download page promising 4K from an arbitrary Facebook link is doing one of two things: relabelling a smaller file with a bigger number, or enlarging it. Enlarging invents pixels. Stretching a 720-line frame to 2160 lines gives you a heavier file that looks marginally softer than the one you started with, which is why nothing here upscales.
Two related answers in the FAQ if you want the short versions: which of HD and SD to take and why some videos only offer one.
What decides the quality you can actually get
Four things, in the order they happen. Only the last is anything to do with a downloader.
What left the uploader's device
Resolution and bitrate at the source set the ceiling for everything downstream. A clip shot at 480p does not become sharper by being posted.
Whether it was squeezed before upload
Video forwarded through a chat app, re-exported from an editor, or uploaded on a weak connection often arrives at Facebook already compressed. That loss is baked in before Facebook touches it.
Facebook's own encode
Uploads are transcoded to formats the platform can serve at scale. This is where an original file stops being reachable by anyone, including us.
Whether a second pass was published
Publishing one progressive file or two is Facebook's decision per video. One row means one row exists, not that a row was withheld.
When only one row appears
There are two easy ways to work out whether you are looking at the larger pass or the smaller one. Open the video on Facebook and check its own quality control: if the player offers no way to switch up, there is no second pass to find. Failing that, file size is a fair proxy — at the same running time the HD pass is markedly the heavier of the two, so a download that feels small for the length of the clip is the SD pass.
Photos, and the extension that lies
Stills follow a different path. Meta keeps uploaded photographs in HEIC, the format modern iPhones shoot, and converts them as they leave its network. The consequence is a URL that can still end in .heic while the bytes travelling down it are an ordinary JPEG.
Name the saved file from the extension in that URL and you produce something with a mismatched name: a Windows desktop or an older Android phone looks at.heic, decides it cannot open the thing, and refuses — even though the contents are a JPEG it handles every day. The fix is not clever. Read theContent-Type the server sent with the response and name the file from that, which is what the download proxy here does, so photos land as .jpg and open on the first attempt. There is a longer note on formats in the FAQ.
What the labels on this site mean
HD and SD are Facebook's words, not a threshold invented here. When Facebook publishes two progressive passes it distinguishes them itself, and those labels are passed straight through so that the row you pick corresponds to something real on Meta's side.
Exact pixel dimensions are shown when the metadata states them. When it does not — and for some videos it does not — the row says HD or SD and stops there rather than printing an estimate. A confident 1080p label that turns out to be 720p is worse than no number at all, since a reader can check a file they were given honestly and cannot check one they were misled about.
That is the whole model: two kinds of representation, only one of which is a file you can keep. The field for pasting a link sits on the front page, and the step-by-step guide covers copying the link on a phone or a desktop.