A failed download tells you almost nothing. The message is usually some variation of "could not fetch media," which covers five completely different problems with completely different fixes. Three of them you can solve in seconds. One of them is not solvable by any tool that exists. Knowing which one you are looking at is the whole game.
The causes below are ordered by how often they turn out to be the real answer, and each has a test that rules it in or out quickly. Work down the list and you will land on the right one long before you start trying different websites at random.
1. The link is not the kind of link you think it is
This is the most common failure by a wide margin, and it is invisible because the link you copied is a perfectly valid link — just not to a single post.
Every platform has several kinds of URL that look similar. A profile link points at a person. A board or collection link points at a group of posts. A search results or feed link points at a query. Only a post link points at one specific piece of media, and that is the only kind a downloader can resolve, because it is the only kind that identifies which file you mean.
The tells are structural. A Pinterest pin URL contains /pin/ followed by a long number, or it is a pin.it short link. A TikTok post URL contains /video/ after the username, or it is a vm.tiktok.com short link. An X post URL contains /status/ followed by a number. If the address in your clipboard has none of those markers, nothing downstream will work.
The fix: open the individual post first, then copy the link. Using the app's own share menu is more reliable than long-pressing or copying from the address bar mid-scroll, because the share menu always produces a canonical link to that one post. A surprising number of failures are simply a link to the page someone was scrolling when they tapped copy.
2. The content is not actually public
This is the one that cannot be fixed, and it is worth understanding properly rather than treating it as a bug.
A downloader fetches a post the same way a logged-out stranger's browser would. That means the visibility rules the platform applies to strangers apply to the tool as well. A protected or private account, a secret board, a post restricted to followers, a deleted post, an age-gated post, or something blocked in the region the request comes from all return the same thing to a logged-out request: nothing.
The test takes about five seconds. Open a private or incognito window, paste the link, and look. You are not signed in there, so you see exactly what a downloader sees. If the post does not load for you in that window, it will not load for any tool, and a site that claims otherwise is either asking for your password — which is the actual product in that transaction — or simply lying.
This limitation is a feature. A tool that could read protected posts would be a tool that had defeated a privacy setting somebody deliberately chose. The public versus private posts guide goes through each visibility state in more detail.
3. The media exists, but not in the form you expected
Sometimes the download works perfectly and the result still feels wrong. Almost always this is a mismatch between what the platform stores and what you assumed it stored.
The frequent surprises:
- A GIF saves as a video. Most platforms do not store animated posts as
.giffiles at all — they convert them to short silent video loops because the file is dramatically smaller. The MP4 you received is the animation. This is covered in GIF vs MP4. - The video has no sound. Some posts genuinely have no audio track, and some formats separate audio from video. A silent file is not necessarily a broken one.
- A multi-part post arrives as separate files. Photo slideshows and multi-segment posts are several pieces of media in one container, so they come back as several files rather than one.
- The resolution is lower than the post looked. The player streams whichever rendition suits your screen and connection. The available renditions are what they are, and the original upload caps all of them — see video quality explained.
The fix: read the result list before saving. A tool that shows you what is available lets you pick deliberately instead of discovering the format afterwards.
4. The file saved somewhere you did not look
A large share of "it did not download" reports are files sitting exactly where the operating system put them.
On Android and on desktop browsers, downloads land in the Downloads folder and are indexed normally. On iPhone and iPad, Safari treats a downloaded video as a document rather than a photo, so it goes to the Files app — under On My iPhone → Downloads or iCloud Downloads — and not into your Photos library. To move it, tap the file, tap Share, and choose Save Video.
Chrome on Android sometimes warns that "this type of file can harm your device" for ordinary MP4s. That warning fires for essentially any file downloaded outside an app store and says nothing about the file itself. The device-by-device walkthrough is in saving videos on iPhone and Android.
5. The tool itself is broken
Only after the first four should you suspect the site. Platforms change how they serve media without notice, and when they do, every tool that reads that platform breaks until it is updated. Sites that were abandoned or cloned from someone else's code never get that update — they keep loading, keep showing a paste box, and keep failing.
The test: try a different post on the same platform, ideally a well-known public one. If every link fails, the tool's parsing is broken. If only your link fails, the problem is one of causes 1 through 3 and switching sites will not help.
Two warning signs worth acting on immediately, regardless: a "downloader" that asks you to sign in to the platform, and one that asks you to install an app for a job a browser already does. The first is a credential harvest. The second wants permissions the task does not require.
The one-minute diagnostic
Put together, the whole process is short:
- Does the link contain the post marker for that platform (
/pin/,/video/,/status/, or a known short link)? If not, re-copy from the post itself. - Does the post load in a private window while signed out? If not, stop — it is not reachable, by anything.
- Did you get a file that is simply a different format than expected? Then nothing failed.
- Checked Downloads on Android and desktop, and Files on iOS?
- Does a different post on the same platform also fail? Then the tool needs updating, not your link.
Four of those five have an answer you can act on in under a minute. The fifth is a genuine limit rather than a malfunction — and knowing the difference saves you from working through six alternative sites that were all going to fail for the same unavoidable reason.
If you want the underlying pipeline that produces these failure modes, the how it works page walks through each stage. The tools themselves are the Pinterest downloader, TikDown for TikTok, and TwitDown for X.