Facebook Video Downloader

How does Facebook actually serve a video?

Every video on Facebook exists as a file sitting on Facebook's content delivery network. The post you are looking at — the caption, the reactions, the comment thread — is a wrapper around it. The video itself is a separate resource with its own web address, and when you press play, your browser or app requests that address and streams what comes back.

That separation is the reason a downloader can exist at all. A tool that resolves a Facebook link performs the same first step your browser does: it asks the page which video resource belongs to this post, and Facebook answers with an address. The difference is what happens after. A browser plays the stream and discards it. A downloader writes it to a file.

It also explains the one boundary that shapes everything else on this page, and it is worth putting up front because it saves a great deal of guesswork later. Facebook decides whether to emit that address before anything else happens. A post set to Public is served to anyone who asks, logged in or not, which means a plain link carries everything needed to reach the file. A post limited to a group, to friends, or to a custom list is resolved against the session doing the asking, and a request that arrives with no session attached receives the page rather than the file address.

So the useful mental model is not "which videos are protected" but "which videos Facebook hands to a stranger". Everything a logged-out visitor can watch is reachable by a link. Everything that asks that visitor to sign in first is served to accounts rather than to addresses. Once that distinction is clear, most of the confusion around Facebook video downloads resolves itself.

Which Facebook videos can be downloaded?

The dividing line runs along audience settings rather than along video type. Reels, feed uploads, Watch content and Page videos all use the same delivery machinery. What differs is who Facebook serves them to.

Public posts from personal profiles

A person who set a post's audience to Public has told Facebook to serve it to everyone, including people with no account. Those videos resolve from a link.

Page videos

Pages are public by design. A business, a news outlet, a musician, a creator — anything posted from a Page is visible to the open web unless it carries an age or region restriction. This is the largest category by far and the one most searches are actually about.

Public Reels

Reels posted from Pages and from public profiles behave exactly like public feed videos. They are shorter and vertical, and otherwise identical in how they are served.

Videos in public groups

A group set to Public shows its content to visitors, and video posted inside it follows that setting.

There is a two-second test that settles any individual case: open the post in a private or incognito window where you are not signed in. Whatever plays there is what a link can reach. Whatever shows a sign-in prompt is being served to sessions.

Why do private videos stay out of reach?

This is the question people ask most often, and it deserves a straight technical answer rather than a shrug, because the answer changes what you do next.

When you open a friends-only post while signed in, Facebook checks the relationship between your account and the poster's before it produces anything. That check runs on Facebook's servers, and its output is one of two documents: a page that contains a video address, or a page that contains an invitation to sign in. A link handed to any tool arrives without a session, so the second document is what comes back. The video file address was never generated for that request.

That is a meaningfully different situation from what people often picture, and the difference matters. A weak restriction is one that exists in the interface over data the browser already holds — a hidden button, a blurred image that has fully loaded, a disabled right-click menu. Those can be walked around because the content is already on your side of the wire. Facebook's audience setting is the other kind. The video is filtered before transmission, so there is nothing in transit to capture and no amount of address manipulation produces a location that was never issued.

The practical consequence is clean. For a video in a closed group, a friends-only post, or a custom-audience post, the route that works is the human one: ask the person who posted it. Facebook has a built-in path for exactly this — the poster can send the video in Messenger, or download it themselves from their own activity log and share the file. That takes one message and produces a better copy than any link-based route would have.

Any page advertising downloads of private Facebook videos is describing an outcome that requires the account's own session, which is precisely what the sign-in exists to establish. Knowing that in advance is worth more than trying five of them.

What does this page do with the link you paste?

This page reads the public link you paste. No password is ever requested and there is nothing to install.

The sequence is short. You paste a link to a Facebook post, Reel or video. The page normalises it — Facebook has several link shapes for the same content, and share sheets add tracking parameters that need stripping before anything else works. It then requests that post the way a logged-out visitor would, and reads the video resources Facebook lists in the response. What is listed is what appears as an option.

Nothing about that sequence involves your Facebook account. There is no sign-in step, no browser extension, no desktop application, and no permission grant. The one input is a link that anyone on the open web could have opened, which is the whole reason the process is as simple as it is.

It is worth being clear about the second half of that, too: because the page works from a public address, what it can offer is whatever Facebook publishes at that address — the renditions, the resolutions and the audio arrangement described further down. Those are properties of the file Facebook made, and the sections below explain how they came to be that way.

How do you copy the right Facebook video link?

Most reports of a link that behaves oddly turn out to be the wrong link copied, so this is worth doing precisely. Facebook has several link formats and they do not all point at the same thing.

On desktop

Click the three-dot menu at the top right of the post and choose Copy link. That gives you the canonical post address. Alternatively, click the post's timestamp to open it on its own page and copy the address bar. Both work; the timestamp route is more reliable when the video sits inside an album or a multi-video post, because it isolates the one you clicked.

In the mobile app

Tap the three-dot menu on the post, then Copy link. On some screens this appears as Share followed by Copy link. Either produces a short fb.watch address, which is a redirect to the full post URL. Short addresses work fine — they resolve to the same place — but if you ever need to see what a link actually points at, opening it in a browser and reading the resulting address bar shows you.

For Reels

Tap the share icon on the right-hand rail of the Reel, then Copy link. Reel addresses contain /reel/ and a numeric identifier.

For videos inside Watch

Use the three-dot menu on the video card. Copying the browser address while a Watch feed is scrolling can capture the feed rather than the individual video.

One detail that saves time: a link copied from a search results page or from a notification sometimes carries a long string of parameters after a question mark. Everything from the question mark onwards is tracking and can be deleted without changing where the link goes.

Why is the resolution lower than the original?

This surprises people more than any other part of the subject, and the explanation is entirely on Facebook's side rather than the tool's.

When someone uploads a video to Facebook, the file they chose is not the file Facebook stores for playback. Facebook re-encodes every upload into its own set of renditions — several versions of the same video at different resolutions and bitrates, all generated from the uploaded file and all compressed to Facebook's targets rather than the uploader's. This is how adaptive streaming works: the player picks a rendition to match the viewer's connection and switches between them mid-playback as conditions change.

What that means for a download is direct. The file you receive is one of Facebook's renditions. It is a re-encoded copy, made by Facebook's encoder at Facebook's chosen bitrate, and it is the best available version of what Facebook publishes rather than a copy of what the uploader originally had. A 4K master uploaded to Facebook is served as 1080p or below to almost everyone; a phone recording uploaded at high bitrate is served at a considerably lower one.

This is also why re-uploading a downloaded video to another platform produces a visibly softer result than the uploader's own copy would. You are encoding an already-encoded file, and each pass discards detail the previous pass kept. Anyone who needs the genuine original has exactly one reliable route, and it is the human one: ask the person who made it. For your own uploads there is a better path, described further down.

Which quality should you pick?

When more than one rendition is available, the choice is straightforward once you know what each one is for.

The highest offered resolution is right for anything you intend to watch on a large screen, edit, or keep. It is the largest file and it preserves the most of what Facebook published.

A mid rendition — typically 720p — is the sensible default for phone viewing and for sending to someone over a messaging app, where the recipient's app is likely to compress it again anyway. The difference between 1080p and 720p on a phone screen held at arm's length is far smaller than the difference in file size.

The lowest rendition exists for slow connections and for cases where you only need the content rather than the picture — a reference clip, something you want to transcribe, a video you are archiving for the words in it.

One rule that saves regret: if you plan to re-encode, crop or edit the file later, always take the highest rendition. Every subsequent operation compounds the loss from the one before it, so starting with the most information available is the single decision that matters most in the chain.

Why does the audio sometimes arrive separately?

Occasionally a downloaded Facebook video plays perfectly but silently, and the reason is structural rather than accidental.

Adaptive streaming formats — the family that Facebook's web player uses — carry video and audio as separate tracks rather than as one interleaved file. The player fetches both simultaneously and combines them at playback time. That design is what allows the player to switch video quality mid-stream without interrupting the sound, and it is standard across every major streaming platform, not something particular to Facebook.

The consequence is that a video address and an audio address are two different things. A download that produces picture without sound has retrieved the video track on its own, and the fix is to make sure the file you take is a combined rendition — the progressive MP4 that Facebook also publishes for most videos — rather than a track from the adaptive set. Where a page offers both an SD and an HD option, those are usually the combined ones, which is part of why the simple choice is often the right one.

If you already hold a silent file and the matching audio, any general media tool can mux the two into a single MP4 without re-encoding either, which takes seconds and preserves both tracks exactly as they were.

Can you download Facebook Reels?

Reels are served through the same delivery system as feed videos, so the same rules apply: a Reel from a Page or a public profile resolves from its link.

Two things about Reels specifically are worth knowing. The first is aspect ratio — Reels are 9:16, and Facebook stores them that way, so the file you receive is vertical and will be letterboxed if you play it on a wide screen. That is the shape of the original rather than a cropping artefact.

The second is audio licensing. Reels made with a track from Facebook's music library have that track mixed into the rendition Facebook serves, so it comes down as part of the video. That mixed audio is licensed for use inside Meta's own apps, and carrying it elsewhere is a separate question from whether the file downloaded cleanly. If you plan to re-post a Reel anywhere, this is the detail most likely to cause a claim on the re-upload, and it is worth checking before rather than after.

Reel addresses are short and stable, which makes them the easiest kind of Facebook link to work with — facebook.com/reel/ followed by an identifier, with nothing else required.

What about story videos?

Stories behave differently enough to deserve their own section, and the difference comes down to time and audience.

A story is visible for 24 hours and then leaves the surface it was published on. During that window, a story posted by a Page is public in the same sense a Page video is, and its address resolves the way any Page content does. A story posted by a personal profile follows that profile's audience setting, which for most people is friends — so it is served to sessions, exactly as described earlier.

The 24-hour window is the part that catches people out. A story link copied yesterday points at content Facebook has since retired from public view, and the request comes back with an expired-content response rather than a file. If a story matters, the moment to save it is while it is live.

There is one path worth mentioning for your own stories, because it is the reliable one and it involves nothing external: Facebook keeps your published stories in your own archive, and you can retrieve them there at the quality Facebook stored, long after the public window has closed.

Is downloading someone else's Facebook video legal?

This deserves an honest answer rather than a disclaimer, because the honest answer is genuinely useful and most pages on this subject skip it entirely.

A video posted to Facebook is a creative work, and the person who made it holds the copyright in it. Uploading it to Facebook grants Facebook a licence to host and display it; it does not place the work in the public domain and it does not transfer any rights to viewers. That is true of a news clip, a brand advertisement and a friend's holiday footage alike.

What follows from that is a distinction between two acts that are often discussed as if they were one.

Saving a copy for your own viewing — watching it offline on a flight, keeping a video a family member posted, holding a reference clip for your own work — is a personal, private use. In most jurisdictions this sits in the same territory as recording a broadcast to watch later. It is the ordinary case, and it is what the large majority of people searching for this are doing.

Publishing the copy — re-uploading it to your own page, cutting it into your own video, running it as an advertisement, monetising a channel with it — is republication of someone else's work, and copyright applies with full force. Neither the fact that it was publicly visible nor the fact that you credited the creator changes that. Public visibility is a distribution decision by the rights holder, not a grant of rights to redistribute.

There is a middle ground that genuinely exists: quotation, commentary, criticism, news reporting and parody are treated as exceptions in many legal systems, under names like fair use or fair dealing. Those exceptions are real, but they are narrow, they are assessed case by case on how much was taken and to what purpose, and they are not a general permission to repost. If your use is commercial, assume you need permission.

What changes the moment you want to repost?

If the plan is to publish rather than to watch, the practical checklist is short and it is entirely worth doing.

Ask. A direct message asking to use a clip is answered affirmatively far more often than people expect, and it converts an uncertain position into a clear one. Keep the reply — a written yes is the record you would want if the question ever arose.

Check the audio separately. Video rights and music rights are distinct. A creator can grant you their footage and still have no authority over the licensed track playing under it, and the automated matching systems on YouTube, Instagram and TikTok detect music far more aggressively than they detect footage.

Expect the matching systems. Meta operates Rights Manager, a fingerprinting system that lets rights holders register reference files and act automatically on matches. Other platforms run their equivalents. A re-uploaded video is compared against those references at upload time, and the outcome — a claim, a takedown, a block in some territories — arrives without human involvement.

Prefer sharing to reposting where you can. Facebook's share button, an embed, or a link accomplishes most of what a re-upload was meant to accomplish, keeps the view count with the person who earned it, and raises none of these questions.

How do you get your own uploads back at full quality?

If the video is yours, there is a route that beats every link-based method, and a surprising number of people never learn it exists.

Facebook's Download Your Information tool — in Settings, under Your Facebook Information or Accounts Centre depending on your app version — exports your own content as a file archive. Select Posts and Videos, choose High for media quality, pick a date range, and Facebook prepares an archive you download when it is ready. It contains your videos at the highest quality Facebook holds for them, which is better than any rendition the public player is served.

Two smaller routes are worth knowing alongside it. Your activity log lists your posts individually and offers a download on each one, which is faster when you want a single video rather than an archive. And for videos posted from a Page you manage, the Meta Business Suite content library offers a download directly from the video's row.

None of these require anything external, and all of them produce a better file than a public link ever could, for the simple reason that Facebook serves an account its own content at a quality it does not publish to visitors.

What does it mean when a link comes back as a page?

When a link resolves to a page rather than to a file, the cause is almost always one of a handful of specific and identifiable things, and each has a clear next step.

• The audience is not public. Friends-only, group-only or custom-audience posts are served to sessions, as described above. The incognito-window test confirms this in seconds.
• The post has been removed. Deleted by the author, or taken down after a report or a rights claim. The address stays valid in form and points at content that is no longer served.
• An age or region restriction applies. Some videos are gated by geography for licensing reasons, or require a signed-in account confirmed to be over a certain age.
• The link is a feed address rather than a post address. Copying from the browser bar while scrolling a Watch feed captures the feed. Use the post's own three-dot menu.
• A live broadcast is still running. A live video becomes a fixed file once the broadcast ends and Facebook finishes processing it, which usually takes a few minutes.
• The profile was deactivated. Content from a deactivated account leaves public view along with the account.

Working through that list in order identifies the cause in nearly every case, and the first item accounts for more of them than all the others combined.

Does the person who posted it find out?

Facebook does not notify anyone that their video was downloaded, and there is no viewer list on a feed video the way there is on a story.

What a Page owner does see is aggregate: view counts, watch time, retention curves, and broad audience demographics in their insights. Those are counts and distributions rather than identities, and a download registers there the way any other playback would — as one more number in a total.

Stories are the exception worth naming, because they work differently by design. A story shows its poster a list of the accounts that viewed it. That list is about viewing while signed in, though, not about downloading — and it is a good illustration of the general principle that what Facebook reports back to a poster is determined by the surface the content was published on.

What file do you end up with?

Almost always an MP4, containing H.264 video and AAC audio. That combination is the most widely supported pairing in existence: it plays on every phone, every desktop operating system, every browser and every smart television without extra software, and every editing application imports it directly.

Some Facebook renditions use newer codecs — VP9 or AV1 — which compress better at the same visual quality and are what the web player often chooses on a capable browser. Files in those codecs play in modern browsers and current media players, and older devices or editing suites sometimes want them converted first. If a file plays in your browser but not in a particular application, the codec is the likely explanation and a one-pass conversion resolves it.

File sizes follow from the rendition. A one-minute 1080p Facebook video typically lands somewhere between 10 and 25 MB; the same minute at 360p is a small fraction of that. Reels, being short, are almost always small enough to send over any messaging service without further compression.

Where does the file land on each device?

Desktop, any browser. The file goes to your Downloads folder. If a video opens in a browser tab and plays instead of saving, right-click the video and choose Save video as, or use the browser's own download control.

iPhone and iPad. Safari saves to the Files app rather than to Photos. Open Files, go to Downloads, and from there use the share icon and Save Video to move it into your camera roll if that is where you want it. This two-step behaviour is a design decision in iOS and applies to any downloaded video regardless of source.

Android. Chrome saves to the Downloads folder, and most gallery applications index that folder automatically, so the video appears alongside your photos within a moment or two. If it does not appear, opening it once from the Downloads app is usually enough to prompt the gallery to pick it up.

A note on filenames. Files arriving from a CDN often carry a long numeric name rather than anything descriptive. Renaming immediately, while you still remember what the video was, is a small habit that pays for itself the first time you have twenty of them.

What about live videos and premieres?

A Facebook Live broadcast exists in two states, and which one you are looking at determines what a link does.

While the broadcast is running, the stream is being generated in real time and there is no finished file yet. Once the broadcaster ends the stream, Facebook processes the recording and republishes it as an ordinary video post — at which point it behaves exactly like any other upload, and a public one resolves from its link. Processing usually takes a few minutes and can take longer for a long broadcast.

Premieres work the other way round. A premiere is a completed file with a scheduled public start time, so the video exists before the event does. It becomes reachable at the moment the premiere begins and the post goes public.

Broadcasters can also delete a live recording after the fact, which some do routinely for casual streams. If a live broadcast matters to you, the interval right after it ends is the window to act in.

Common questions

Do I need a Facebook account?

No. Working from a public link means the process runs entirely outside any account, which is why there is no sign-in step anywhere in it.

Is there a limit on how many videos I can save?

The page handles one link at a time and you can paste as many as you like, one after another. Practical limits come from your own connection and storage rather than from any counter on the page.

Why is the file smaller than I expected?

Because it is Facebook's rendition rather than the uploader's file. The re-encoding section above covers this in full — it is the single most common surprise on the whole subject.

Can I get just the audio?

The download gives you the video file. Extracting the audio from it is a separate operation that any media tool performs, and it is worth remembering that music inside a video carries its own rights independently of the video itself.

Does this work on a phone?

Yes. The whole process runs in a mobile browser, which is the point of a page that needs nothing installed. Where the resulting file lands differs by platform, and the device section above covers both.

Will the video be watermarked?

Facebook feed videos carry no platform watermark. Some Reels that were created in another app and cross-posted arrive with that app's watermark baked in by the original creator, which is part of the video itself.

Can I download a video someone sent me in Messenger?

Messenger videos are attachments in a private conversation rather than posts, and Messenger's own interface offers a save option on them directly — tap and hold the video, then Save. That is the built-in route and it is the right one.

What if the video is very long?

Length is a question of file size and patience rather than of capability. A two-hour video at 1080p is a large file, and a stable connection matters more than anything else; a mid rendition is often the more sensible choice at that duration.

The short version

Facebook serves video as files on a delivery network, and whether a link reaches one depends on a single thing: whether the post is public. Everything a signed-out visitor can watch resolves from its address; anything limited to friends, to a group or to a custom list is served to sessions instead, and the file is filtered before transmission rather than hidden after it. What comes down is Facebook's re-encoded rendition rather than the uploader's original, because Facebook re-encodes on upload — so take the highest rendition if you plan to edit, and use Download Your Information for your own uploads, which returns them at a quality the public player never sees. Adaptive streaming carries audio as a separate track, which is why a combined MP4 is the option to choose. And the distinction that matters most: keeping a copy to watch is an ordinary private use, while republishing it is a rights question with real answers, best settled by a message to the person who made it.