Facebook publishes two shapes, and only one can be handed over as one file
Under the hood a Facebook post can expose its media in two different ways, and the difference decides whether an HD row appears in the download list at all:
- Progressive single files. These are the
sdandhdrenditions: one MP4 that already contains the picture and the sound. They carry no width, height or bitrate values at all, so the format id is the only quality signal Facebook publishes for them. - Split (DASH) pairs. Facebook also publishes higher resolutions as a video-only stream plus a separate audio-only stream. Neither half is a file you can play on its own: the video has no sound, the audio has no picture.
Joining a split pair means running a merge across the entire file before a visitor gets anything. FBClipFast does not do that. Its rule is explicit: only a rendition that already holds both streams is offered, and streams carrying only one of them are filtered out.
So the ceiling is not "the biggest picture Facebook has". It is the biggest single file Facebook published for that post. On a post where the 1080p exists only as a video-only stream, that ceiling is the 720p progressive file — and the list will show it, correctly, as the best available.
One Reel, measured end to end (2026-10-28)
One public Reel was read twice: once with the extractor alone, to see everything Facebook publishes for it, and once through FBClipFast, to see what the list actually offers. The post is facebook.com/reel/2277713513083702 — Meta's own page, Andrew Bosworth on AI agents, 74.6 seconds. Nothing about this post is unusual; that is the point of picking it.
What Facebook publishes for that Reel
| Stream | What it is |
|---|---|
sd and hd | Two single files, each already containing picture and sound. No width, height, codec or bitrate is stated for either. |
| Video-only DASH, 720×1280 | Seven bitrate tiers between 132 and 1,090 kbps, AV1 codec, no audio track. |
| Video-only DASH, 1080×1920 | 1,594 kbps, AV1 codec, no audio track. |
| Audio-only DASH | HE-AAC, 69 kbps, no picture. |
So the top resolution Facebook has for this Reel is 1080×1920, and it exists only as a silent video stream that has to be paired with a separate audio stream. That is the whole gap this page is about, now with a real post behind it.
What the tool listed, and what the files turned out to be
The list came back in 4.7 seconds with two rows. Both were downloaded and read with ffprobe, so the right-hand column is measured from the delivered file, not copied from the page:
| Row | Label | Size shown | What the file actually is |
|---|---|---|---|
| v0 | HD | 12,395,088 B | 720×1280, H.264 High, 1.25 Mbps, HE-AAC stereo 68 kbps, 74.75 s |
| v1 | SD | 2,844,818 B | 360×640, H.264 Main, 252 kbps, HE-AAC stereo 48 kbps, 74.65 s |
- The row called HD is 720×1280. Facebook's label for that rendition is "HD"; it is not a statement about pixel count, and 720×1280 is what the file really is.
- 1080×1920 is 2.25 times the pixels of 720×1280. That is the size of the gap you are looking at when the player offers 1080p and the download does not.
- Below the list the page shows its own note: "Higher quality exists, but not as a single file" — "the source also publishes 1080×1920… it offers that resolution as a separate video stream and a separate audio stream". The note is driven by the video-only stream being present, so it appears exactly when a higher video-only version exists.
- Both size figures were exact. The bytes shown before downloading matched the delivered file on 2 of 2 rows, to the byte — the 16-byte range probe is reading the real length, not an estimate.
What the list can and cannot show you
People often read the list as if it were a quality menu with pixel counts. It is a list of files, and it looks like this:
| What you see | Why it looks that way |
|---|---|
An HD or SD label with no pixel number | Facebook's progressive renditions publish no width, height or bitrate. The short id is the only quality word the platform gives, so it is used as the label. A machine id is not turned into a made-up label. |
| At most three rows | The tool shows a maximum of three renditions. More exist upstream; three is the cap on what it will present and probe. |
| Every row has sound | Audio-only and video-only streams are rejected before the list is built, so nothing offered can arrive silent. |
| No separate "audio only" download | Same rule. The sound is inside each MP4. Extracting it is a conversion you do afterwards, not a second download. |
| A smaller file ranked above a larger one | Sorting is by picture height first, then the extractor's own quality ranking, then bitrate — not by byte count. A bigger file is not automatically the better one. |
| A size in bytes you can trust | Sizes are measured with a 16-byte range request against the CDN before you download, not guessed from the page. An over-limit file is refused up front instead of dying halfway. |
What the list cannot show is a resolution Facebook never published for that post. If the 1080p only exists as a video-only stream, no row can honestly claim 1080p.
The limits that decide more downloads than quality does
These are the live values the service reports about itself, not marketing numbers:
| Limit | Value | What happens at the edge |
|---|---|---|
| Maximum length | 30 minutes (1,800 s) | A longer video is refused as too long, before any transfer starts. |
| Maximum file size | 200 MiB (209,715,200 bytes) | A rendition above the ceiling is dropped; if every rendition is above it, the request fails as too large. |
| Simultaneous resolves / transfers | 2 / 2 | A third request waits its turn. A short pause under load is a queue, not a fault. |
| Media link lifetime | Signed, roughly four days | Facebook signs each media address with an expiry. A saved result page used days later can point at a dead address; resolve the post again. |
| Link reads per network | 12 per 10 minutes | The next request inside that window is refused as RATE_LIMITED (HTTP 429). Re-reading the same post counts again. |
| Downloads per network | 60 per 10 minutes | Same counter on the transfer endpoint, so it bites later than the link limit and is rarely the one you hit. |
When a download fails, which failure is it
Failures are separated by cause, and each one points at a different next step. Retrying blindly is what makes people conclude the tool is broken.
| What you get | What it means | What to do |
|---|---|---|
| No single file version | The post only exposes split video and audio streams, so there is no complete file to hand over. | Nothing to fix on your side. Try the post again later, or ask the poster for the source file. |
| Too long / Too large | Over 30 minutes or over 200 MiB. | Pick a shorter clip or a lower rendition if one is offered. |
| Login required | The link resolves to a path only signed-in users can see (private post, closed group, some video.php and /posts/ links). | The tool never asks for an account and never uses one. A private video is not downloadable here — that is deliberate. |
| Too many requests | The same network asked for more than 12 links in 10 minutes, or more than 60 downloads. | Wait it out — the counter window is 10 minutes. The on-screen message calls the wait short; on a shared or office network where several people use the tool, it can be the full ten. |
| Source rejected | The CDN refused every rendition the tool offered. | Wait and retry once. Repeated failure on a public post is worth reporting. |
| Invalid link | The address is not a Facebook video page this tool accepts. | Copy the link from the post itself rather than from a chat preview. |
| Short link dead | A fb.watch or share code no longer resolves. | Open the post and copy the full watch or Reel URL instead. |
Short links: what is actually confirmed
fb.watch and share links are handled differently from ordinary links, so they get their own answer rather than a promise.
On 2026-10-21 a request was sent with an invented short code, https://fb.watch/ZZZZZZZZZ/. The service accepted the shape (it was classified as a short link, phase "expanding"), then failed with SHORTLINK_DEAD — HTTP 410. A link on a non-Facebook host and an Instagram link both came back as INVALID_URL, HTTP 400.
What that proves is the boundary, not the happy path: the shape is recognised, expansion is attempted with a hop limit of four, and a dead code is reported as a dead code instead of as a generic error. No live fb.watch or share link has been confirmed working in our records — every code found in public sources was already expired. So if a short link fails while the video plays normally for you, the link is the problem: open the post and copy the full watch or Reel URL.
Expansion never downloads the page body. It reads the status line and the redirect target of each hop and stops there, which is also why a short link cannot be used to reach anything other than a Facebook page.
How to tell what you actually got
Two checks take under a minute and settle the question:
The label HD is Facebook's word for one of its progressive renditions. It is a name, not a measurement.
If you need the higher resolution Facebook serves
Being straight about this is more useful than another workaround: when the high-resolution stream is video-only, a browser tool that does not merge streams cannot produce a playable file from it. The realistic options are:
- Ask the poster for the source file. Anyone who uploaded in 1080p usually still has it, and that file beats anything re-encoded by the platform.
- Check whether a merged high-resolution file exists for that post. If Facebook published one, it will appear in the list — the tool does not hide renditions it can serve.
- Skip "4K downloader" claims. Enlarging a 720p file to 4K adds pixels, not detail, and usually adds file size for nothing.
What was verified, and what was not
Most of this page is a description of how the service behaves. This list separates what was measured from what was read out of the code, on the dates stated:
- Measured 2026-10-28 (the Reel in the table above): Facebook's own stream list for that post, including the video-only 1080×1920 AV1 stream; the two rows the tool listed, 720×1280 and 360×640 as read back from the delivered files with ffprobe; both audio tracks present and stereo; the exact byte match on 2 of 2 rows; the "higher quality exists" note firing on the 1080 video-only stream; and 4.7 seconds from paste to a usable list.
- Verified 2026-10-28 from configuration: the 12 link reads and 60 downloads per network per 10 minutes. These are settings on the running service, not observations of a refusal — the limit itself was not triggered in order to produce a 429 on demand.
- Verified 2026-10-21, still standing: the public limits endpoint (30 minutes, 200 MiB, 2 concurrent resolves, 2 concurrent transfers); the rendition filter that admits only single files carrying both streams; the three-row cap; the size probe that reads 16 bytes and checks for an MP4 header; one live short-link test that ended in
SHORTLINK_DEAD; andINVALID_URLfor non-Facebook input. - Not verified: no post has yet been found that produces the "Only split streams are available" result — the code path exists, but every post tried so far also had a complete file. Also unconfirmed: the 2560p video-only stream quoted from build notes dated 2026-10-01, and any iPhone or Safari run of this flow.
- Not measured at all: success rate. This page reports no percentage because none is measured; a per-post outcome depends on the post.
FAQ
Why does the downloader show 720p when Facebook plays the video in 1080p?
Because Facebook publishes the higher resolution as a video-only stream and the sound separately. Only renditions that already contain both are offered, so the largest file available is the largest single file Facebook published — often 720p.
Does the downloaded Facebook video have sound?
Yes. Every version offered contains both picture and sound in one file. Streams that carry only video or only audio are filtered out and never appear in the list.
Can I download only the audio as an MP3?
No. The tool returns MP4 files with the sound inside. Turning that into an MP3 is a local conversion on your own device — the audio guide walks through that difference.
Can I download a Facebook video in 4K?
Only if Facebook published a single 4K file that already carries audio, which is uncommon on ordinary posts. Tools advertising 4K by enlarging a smaller file add pixels, not detail.
Why does it say "too many requests" when I paste a valid link?
Because the limit counts requests per network, not per video: 12 link reads in 10 minutes. Once that is used up, even a good link is refused until the window rolls over. Wait up to ten minutes, or switch networks if several people share the same connection.