Share flows make copying easy and analyzing harder. When users paste a link into Social Saver, we most often see mobile share links, watch-page URLs copied from the browser, and short redirect 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 source app, you often get a redirect link. It records who shared and which surface opened the clip, then bounces through the platform's login and tracking layer before landing on the watch or short-form video viewer.
Download pipelines must follow redirects, extract a stable video ID, and sometimes recover IDs from login-page HTML when the platform 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 watch-page link copied from the browser address bar after the video loads usually points at one stable video ID. When a clip is truly public, that link 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 link. Many "broken" reports disappear with this one step.
Short redirect links
Short links are another redirect layer — essentially shorteners for public video. They expand to watch or short-form video pages. Treat them like share links: fine when public, fragile when the platform injects interstitials or region blocks.
Short-form video posts
Short-form video posts use the same Share → Copy link flow as classic videos. They behave like other public clips in our stack: progressive MP4 when exposed, login wall when restricted. Share links to short-form videos follow the same redirect story as share links to longer videos.
When every format fails
If watch, share, and short redirect links 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 link without logging into any account. If the platform 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 a stable watch link, the platform may only expose a standard-definition progressive file on the public page. HD streams sometimes require authentication. That limitation comes from the source, not from how you copied the link. Our public video links guide covers quality expectations.
How Social Saver handles redirects
Social Saver follows share redirects automatically and works with the resolved watch link when needed. If analyze fails on a share link, open the video in a browser and copy the address-bar URL — that step fixes most redirect-related errors.
Checklist for support teams
- Ask how the user copied the link (Share → Copy link vs address bar vs short redirect).
- Confirm the clip plays in an incognito window without login.
- Retry with the address-bar URL after the watch page loads.
- Check whether the poster is a public page vs a profile with audience restrictions.
- Escalate only after these steps — most tickets are restricted content, not outages.
Related resources
Supported link types · Public video links guide · Why disappearing posts fail