Facebook Video Downloader
Save videos, reels, and Watch clips from any public post
Paste any Facebook link — video pages, /reel/ links, Watch URLs, share links or fb.watch shortcuts — and SnapDown fetches the video as an HD MP4. No login, no watermark, free.
How to download a Facebook video in three steps
The flow is identical in the Facebook app and on the web — the only difference is how you grab the link. There's nothing to install and no account to create: the link itself is all SnapDown needs to find the video and pull the file.
Copy the Facebook link
In the Facebook app, tap Share under the video and choose 'Copy link'. On facebook.com in a browser, open the video and copy the URL from the address bar — or right-click the post's timestamp and copy its link.
Paste it here
Drop the link into the box above — video pages, Watch links, /reel/ links, share links and fb.watch short links all work, from any device.
Save your video
Click Download Free and SnapDown fetches the video in the best quality Facebook serves. Save the MP4 straight to your device — no watermark, no login.
On iPhone, downloads land in Files → Downloads (use Share → "Save Video" to move clips into Photos) — and if Safari asks whether to allow downloads from this site, tap Allow; it's a one-time prompt. On Android, files go straight to your Downloads folder and appear in your gallery automatically. On desktop, check your browser's Downloads folder.
Facebook link anatomy: one video, many link shapes
Facebook has been hosting video since 2007, and every era left its own URL format behind — classic /videos/ page links, the Watch tab's ?v= parameter, the newer /reel/ paths, opaque /share/ redirects from the mobile share sheet, and the fb.watch short domain. They all point at the same kind of underlying video object, and SnapDown accepts every one of them — but knowing what each looks like makes broken-link debugging trivial.
The Watch link
- ▸/watch — the Facebook Watch player; the same format the desktop site uses when you open a video full-screen.
- ▸v=… — the numeric video ID. This is the part that matters; extra tracking parameters after it are ignored.
- ▸Classic page links — facebook.com/PageName/videos/ID — and reel links (/reel/ID) carry the same ID in a different wrapper.
Share links & fb.watch
- ▸The mobile app's share sheet produces these compact redirects — no page name, no video ID, just an opaque token that resolves to the real URL.
- ▸fb.watch/… links are the same idea on a shorter domain, mostly from older shares of Watch videos.
- ▸SnapDown follows the redirect automatically. If a share link fails, the post was deleted or made private — open it in a browser and copy the full URL it lands on.
One last link detail: links copied from the app often carry long tracking tokens (?mibextid=… and friends) on the end. Paste them as-is — SnapDown ignores query parameters it doesn't need — but if you're archiving links for later, the clean permanent URL is everything before the question mark.
How to copy the link, per surface
What a Facebook link can point to — and what you can save
Facebook video comes in several flavors. Here's exactly what SnapDown extracts from each type it meets.
Feed videos
Classic videos posted to a page, profile, or group feed. They save as MP4 with the original audio, in the highest rendition Facebook serves — typically 720p or 1080p when the uploader published in HD.
Reels
Facebook's short vertical clips at facebook.com/reel/. They download as vertical MP4 files exactly as served — no watermark added, no cropping, original audio intact.
Watch videos
Longer-form content from Facebook Watch at facebook.com/watch?v=. Episodes, creator uploads, and page shows all resolve the same way as feed videos — one link, one MP4.
Live replays
Finished live broadcasts that the creator published as a replay. Once the stream has ended and the replay is public, its link behaves like any other video link. Ongoing streams can't be saved mid-broadcast.
Private groups, friends-only posts, and restricted profiles can't be fetched — Facebook privacy is enforced server-side, and no legitimate tool can bypass it.
Ongoing live streams have no finished file yet — wait for the replay to be published, then paste its link.
Whatever the link shape, the fetch works the same way: SnapDown resolves the link once, finds the best rendition Facebook serves, and hands you a direct download. Files keep their original format — MP4 with the original audio — and nothing is re-compressed, cropped, or stamped on the way through. If a fetch comes back empty for a video you can see while logged in, check it in a private browsing window first: if it's not visible there, it's not public, and that's the reason.
No download button — and the truth about HD vs SD
Facebook does have a "Save video" option — but it only bookmarks the post inside Facebook; nothing lands on your device. A real save-to-device button has never shipped for ordinary posts, and given how Meta's feed products work, it likely never will: media stays in-app, where plays are counted and ads are sold. The closest Facebook gets is letting you download your own uploads through the Download-your-information export, which is built for account backups, not for grabbing a single clip.
Quality is the detail most downloaders gloss over. Facebook transcodes every upload into multiple renditions — at minimum an SD stream and, when the source allows it, an HD stream up to 1080p. Which one you see while browsing depends on your connection and player settings, not on what exists on the server. SnapDown requests the video the way a browser does, picks the best rendition available, and never re-encodes: the MP4 you save matches the top of the ladder. But the ceiling was set the moment the poster hit publish — a video uploaded in 480p has no hidden HD version for any tool to find.
Privacy works exactly the way you'd expect from Meta. Public post: served to logged-out visitors — which is effectively what SnapDown is — so fetching works. Friends-only post, private group, restricted page: nothing is served anonymously, and no honest downloader can retrieve any of it. If a tool asks for your Facebook login to "unlock private videos," close the tab — that's a credential-harvesting pattern, not a feature.
And a quick word on rights, because it matters here as much as anywhere: downloading a public video doesn't transfer any ownership. The clip still belongs to the person who made it, and any music in it may carry its own license. Saving for offline viewing, personal archives, or research is the normal, low-risk use. Re-uploading someone's video as your own content — on Facebook or anywhere else — invites takedowns and copyright strikes. Want to feature someone's clip in your own work? Ask in the comments or by message first.
What people actually use this for
A downloader is only as legitimate as its use cases. These are the four we see most on Facebook — and the reason each one needs a local file rather than a bookmark.
Your own archive
Pages get unpublished, accounts get restricted, and old videos disappear in cleanups. Creators who post natively to Facebook keep local copies of their own uploads — the platform is not a backup service.
Cross-posting workflows
Marketers who publish to Facebook first often need the clean file back later — to reuse the same clip on YouTube, a newsletter, or a client report without re-exporting from the editing project.
Reporting and receipts
Journalists and researchers archive public statements and viral clips before they're edited or deleted. A timestamped file in your own storage beats a dead link when the story develops weeks later.
Reference libraries
Video editors and social teams collect examples of hooks, formats, and ads that perform on Facebook specifically — and a local folder is the only collection that survives deletions and page purges.
Field notes: Facebook quirks that affect downloads
Small platform behaviors that regularly confuse people saving videos from Facebook — collected here so they don't confuse you.
"It works for me" doesn't mean it's public
The most common failed fetch: a video visible in your feed that lives in a group you belong to or a friends-only post. You can see it because you're logged in; an anonymous fetch can't. Open the link in a private browsing window — if it asks you to log in, that's your answer.
Raw media links expire — save the file, not the URL
The direct media addresses behind a fetch point at Meta's CDN, and those URLs carry time-limited signatures — they stop working after a while by design. Don't bookmark or share the raw link from a result card. Download the file to your device; that copy is permanent.
Shared videos point at the original post
When someone shares a video to their timeline, the video file still belongs to the original post. SnapDown resolves the share to the source media — so if the original was deleted or private, the share link fails even though the share itself is still visible in the feed.
Watch party and crossposted videos can mislead
Pages often crosspost the same video, and Facebook serves it under several URLs at once. If one link fails, search the original page for the same clip — the primary upload usually fetches fine. And a "video" that's actually a YouTube link preview needs the YouTube downloader, not this one; check the domain the post really points to.
Facebook or Instagram? Pick the right tool
Same company, often the same clip — but different apps and different downloaders. A ten-second look at the link tells you which one you need.
Cross-posting note: Meta lets creators publish the same reel to both apps at once. If your link says instagram.com, use the Instagram tool even if you found the clip on Facebook — the file is hosted where the link points. The reverse holds too: a facebook.com/reel/ link belongs here, even when the watermark says Instagram.
Facebook download FAQ
The details — link formats, share links, reels, live videos, privacy, and quality.
Want more detail?
The companion guide walks through every device with screenshots — plus fixes for stubborn share links and videos that only fetch in SD.
Read the full step-by-step guide