Troubleshooting
Why a private or restricted post cannot be fetched
Short answer
ClipKoala only fetches what is publicly reachable without an account. If a post sits behind a follow request, a login wall, an age gate, a paid membership, or a regional block, there is no version of the request that succeeds, because the platform does not serve the file to anyone who is not signed in and permitted. This is a deliberate boundary rather than a limitation waiting to be worked around.
What to do
- 1
Test the link while logged out
Open a private browsing window and paste the link. If you cannot see the post there, no downloader can. This single check identifies the cause of most failures in about five seconds.
- 2
Identify which restriction you hit
A login wall means a private account or a followers-only post. An age warning means an age gate. A join or subscribe prompt means members-only. A message about availability in your country means a region lock. Each has a different real answer, and none of them are technical.
- 3
Ask, if it is someone's own content
For a private account, the person who posted it can send you the file directly. That is not a workaround, it is the correct route, and it takes one message.
- 4
Do not use a service that asks for your login
Any site offering to fetch private posts if you sign in with your platform account is harvesting credentials. ClipKoala will never ask for a platform password, and neither should anything else.
What each platform calls it
Instagram and TikTok use private accounts and friends-only posts. YouTube has private, unlisted, age-restricted, and members-only, which behave very differently from each other. Facebook restricts by friends, groups, and events. X has protected accounts and age-gated media. Reddit has private and quarantined subreddits. Twitch VODs are subscriber-gated for some channels.
They fail in the same way from the outside, which is why the error message cannot always be more specific than it is.
Unlisted is not private
An unlisted YouTube video is not in search or on the channel page, but anyone holding the link can watch it, and it can be fetched normally. If you have the link legitimately, an unlisted video will work. If you do not, having the link does not make sharing the file appropriate.
Why this boundary is not going to move
A tool that could reach private content would need either stolen credentials or a platform vulnerability. Both are lines worth refusing to cross, and any product that crosses them is one bug report away from being a very different kind of story.
It also protects you: the same boundary means nobody is using this to pull your private posts either.
Last checked .