← Power Downloader

Step-by-step guides for Instagram reels, Facebook videos, and troubleshooting

What “public” really means for Instagram and Facebook links

Logged-in visibility and open-web visibility are not the same thing — and that gap causes most downloader confusion.

Last updated: July 8, 2026

← Blog

Users say a link is "public" because it plays on their phone. Support teams say a link is "private" because the server got a login wall. Both can be true at once. Understanding that gap is the single most useful concept when you use or operate a tool like Power Downloader.

Two different definitions of public

App-public: You follow the account, you are logged in, and Instagram or Facebook shows you the reel, story, or video in the native app. Your social graph and session unlock content that is invisible to strangers.

Web-public: A visitor with no account, using a generic browser in incognito mode, can open the URL and see the media without signing in. Download tools and search crawlers only get this second definition. They do not inherit your follows, blocks, or Close Friends lists.

The 30-second incognito test

Before blaming a downloader or rotating cookies, do this:

  1. Copy the exact URL you want to save.
  2. Open a private/incognito window with no Facebook or Instagram login.
  3. Paste the URL and press Enter.
  4. If the platform asks you to sign in, shows "content isn't available," or loops on a login page — the link is not web-public.

No third-party tool can ethically bypass that wall without impersonating your personal session, which violates platform terms and breaks frequently anyway.

Cases that look public but are not

  • Followers-only posts on public profiles — the profile is public, each post may still be audience-limited.
  • Stories from accounts you follow — almost always app-public only.
  • Age-gated or region-blocked videos — visible to you, blocked to the server's region or anonymous viewer.
  • Deleted or expired content — the app may cache a thumbnail while the URL is already dead on the CDN.

Why this matters for operators

Daily ops reports may show bursts of YTDLP_LOGIN_REQUIRED errors even when cookie jars probe healthy. Often those bursts are story URLs or restricted reels from users who paste app-visible links. Separating "content restricted" from "infrastructure broken" prevents unnecessary cookie rotations and false alarms.

What to paste instead

Prefer stable feed URLs: instagram.com/reel/…, /p/…, or Facebook watch?v=… links that pass the incognito test. See our supported link types guide and Facebook share vs watch article.

Legal angle

Web-public does not mean "free to republish." Copyright and platform terms still apply. Read our copyright guide before resharing someone else's clip.