Download failures are rarely mysterious, but they are usually mislabelled. The same "something went wrong" message covers at least six different situations, each with a different fix. Retrying is only the right response to one of them.
Here is each failure with its real cause.
"This link is not valid"
Cause: the URL is incomplete or was truncated when it was copied.
Instagram share links are long and contain an identifier that must survive intact. Messaging apps, email clients and some note-taking apps wrap long URLs and quietly drop the tail when you copy them.
Fix: re-copy the link directly from Instagram using Share, then Copy link. Paste it without editing. If you are copying from a browser address bar, make sure you selected the whole thing.
"This link is not a Reel"
Cause: the link is a different content type, or the tool only recognises one URL shape.
A link containing /p/ is a feed post, /tv/ is a long-form video, and /stories/ is a Story. None of them are Reels. Separately, some tools only accept /reel/ and reject the equally valid /reels/.
Fix: check the path segment, then use the tool that matches. The Post Downloader handles /p/ links, the Story Downloader handles /stories/ links, and the Carousel Downloader handles multi-slide posts. If the path is /reels/ and a tool rejects it, that is a parser limitation - see why /reel/ and /reels/ links behave differently.
"This content is private"
Cause: the account is private, or the specific post is restricted.
Fix: there is none. This is the correct behaviour, not a bug. Only public content is retrievable, and any tool claiming otherwise is either mistaken or doing something you should not want it to do.
"Too many requests" or a rate limit
Cause: the request volume from your network exceeded what the service allows in a time window.
This is the one error where waiting is the actual fix. Rate limits protect the service from a single visitor consuming capacity that everyone else needs.
Fix: wait a short while, then continue. If you are downloading many items in a session, space the requests out. If you are on a shared network - an office, a campus, a VPN exit used by many people - the limit may be counting traffic that is not yours, in which case waiting is still the only remedy.
"The file downloaded but it will not play"
Cause: an interrupted download, or a player that does not support the container.
Fix: check the file size first. A file that is a few kilobytes is a truncated download, not a video. Delete it and fetch again on a stable connection. If the size looks right, try a different player - MP4 is widely supported, but some lightweight players handle it inconsistently.
"The Story is gone"
Cause: Stories expire 24 hours after posting.
Fix: none for that Story. If it was saved into a Highlight, the Highlight copy does not expire, and the Highlight Downloader can retrieve it.
"Nothing happens when I press the button"
Cause: almost always the browser, not the service.
- An aggressive content blocker or privacy extension is blocking the request.
- An old cached version of the page is running.
- The tab was restored from a previous session and lost its script context.
Fix: reload the page, and if that fails, try a private window. If it works there, an extension is the culprit.
A short decision tree
- Did the link come straight from Instagram's Copy link? If not, re-copy it.
- Is the path
/reel/,/reels/,/p/,/tv/or/stories/? Use the matching tool. - Is the account public? If not, stop - this is expected.
- Have you sent many requests in the last few minutes? Wait, then retry.
- Does the page respond at all? If not, it is your browser or an extension.
Working through those five questions resolves the overwhelming majority of failures without a support request.
Frequently asked
Does retrying immediately ever help?
Only for a transient network error. For rate limits, retrying immediately makes the wait longer. For private media, retrying will never work.
Why did the same link work yesterday and fail today?
Usually the post was deleted, the account went private, or a Story expired. The link is unchanged; the content behind it is not.
Can a downloader be blocked by Instagram?
Instagram can change how it serves public media at any time, and services adapt. When that happens the correct behaviour is a clear error message rather than a silent failure, which is what we aim for.
Errors that are actually features
Three of the messages above are the service working correctly, and it is worth recognising them so you do not waste time trying to fix them.
Private content is refused
This is the policy, not a limitation to work around. A tool that returns private media is either misreporting what it did or doing something you should not want it to do.
The rate limit triggers
A rate limit is the mechanism that keeps the service usable for everyone. If it never triggered, a single visitor could consume the capacity the rest of the audience needs. The correct response is to wait, not to look for a way past it.
A Story has expired
Stories last 24 hours by design. Once gone, the only surviving copy is one saved into a Highlight - which is precisely why Highlights exist.
When to stop troubleshooting
If you have re-copied the link, confirmed the content type, confirmed the account is public, waited out any rate limit, and tried a private browser window, and it still fails, then the problem is not on your side. At that point the useful action is to note the exact link and the exact message, because a reproducible failure with a specific link is something a service can actually investigate. Retrying the same thing a tenth time is not.