Facebook makes sharing easy and analyzing hard. When users paste a link into Power Downloader, the most common Facebook formats we see are mobile share links (facebook.com/share/r/…), classic watch URLs (facebook.com/watch?v=…), and short fb.watch links. All three can work for public videos — but they fail for different reasons. Understanding the difference saves support time and sets realistic expectations.
What a share link really is
When you tap Share → Copy link in the Facebook app, you often get a URL under /share/r/ or /share/v/. That URL is a redirector. It encodes a referral context (who shared, which surface) and bounces through Facebook's login and tracking layer before landing on a watch page or reel viewer.
Download pipelines must follow redirects, extract a stable video ID, and sometimes recover IDs from login-page HTML when Meta serves a challenge to datacenter IPs. Share links work often enough that we accept them — but they are the noisiest format in error logs.
What a watch URL gives you
A canonical watch URL looks like https://www.facebook.com/watch?v=1234567890123456. The numeric v parameter is the video ID Facebook uses on the watch surface. When a video is truly public, this format is the most direct input for open-source extractors.
Practical tip: If analyze fails on a share link, open it in a desktop browser, let the watch page load, and copy the address bar URL. Retry with that watch link. Many "broken" reports disappear with this one step.
fb.watch short links
fb.watch/… URLs are another redirect layer — essentially link shorteners for Facebook video. They expand to watch or reel pages. Treat them like share links: fine when public, fragile when Meta injects interstitials or region blocks.
Reels on Facebook
Facebook Reels now have their own paths (/reel/… and share variants). They behave like Instagram reels in our stack: public reel, progressive MP4 when exposed, login wall when restricted. Share links to reels follow the same redirect story as share links to classic videos.
When every format fails
If watch, share, and fb.watch all fail with login-required or private-content errors, the video is probably:
- Friends-only or group-only
- Age-gated in your region
- Deleted or copyright-blocked
- Visible to you because you are logged in, but not to anonymous visitors
Run the incognito test: open the watch URL without logging into Facebook. If Meta asks you to sign in, third-party download tools cannot access the file ethically without your session — and session-based scraping violates platform rules and breaks often.
Quality and SD vs HD
Even with the perfect watch URL, Facebook may only expose a standard-definition progressive file on the public page. HD DASH manifests sometimes require authentication. That limitation comes from Meta, not from the URL shape. Our Facebook videos guide covers quality expectations.
How Power Downloader handles redirects
The resolve API normalizes many Facebook URL shapes, follows share redirects, and falls back to FastSaver when local extraction misses. That is why daily ops reports can show healthy analyze success even when cookie jars are missing or stale — FastSaver-primary mode does not depend on operator cookies for every request. Local cookie tiers matter for fallback paths and certain restricted clips.
Checklist for support teams
- Ask for the exact pasted string (share vs watch vs fb.watch).
- Confirm the clip plays in an incognito window without login.
- Retry with the watch URL from the address bar after redirect.
- Check whether the poster is a page (public) vs profile with audience restrictions.
- Escalate only after these steps — most tickets are restricted content, not outages.
Related resources
Supported link types · Facebook videos guide · Why Instagram stories fail