Why Your YouTube Shorts Download Fails (and How to Fix It)

Most failed downloads come down to a handful of causes, and nearly all of them are fixable in under a minute. Here they are, roughly in order of how often they actually happen.

"That does not look like a YouTube link"

The URL was not recognised as pointing at a single video. Usual culprits:

• A channel or profile URL (youtube.com/@creator). There is no video to fetch.
• A search or feed page.
• A shortened link from another service — a bit.ly or similar. Open it first, then copy the real YouTube URL.
• A link mangled by a messaging app. Some apps wrap links or strip characters. Open the link, then copy from the address bar.

A valid link contains an eleven-character video ID: youtube.com/shorts/dQw4w9WgXcQ, youtu.be/dQw4w9WgXcQ or youtube.com/watch?v=dQw4w9WgXcQ. How to copy a Shorts link covers every route.

"This Short cannot be downloaded"

The link is valid but YouTube will not serve the video. Reasons:

• Private video. Only the uploader can see it.
• Unlisted, and the ID has changed. Unlisted videos work if the link is current.
• Age-restricted. These require a signed-in account, which a downloader does not have.
• Deleted or removed. Including videos taken down for copyright.
• Region-blocked. Rare for Shorts, but it happens with music.

The quick test: open the link in a private or incognito window, where you are signed out. If it does not play there, no third-party tool can reach it.

"Too many requests, please wait a minute"

You hit the rate limit. It exists to keep the service usable for everyone and to avoid getting the whole site blocked upstream. Wait sixty seconds and try again — it clears on its own. Refreshing repeatedly during the cooldown just restarts it.

"This link expired"

Each parse produces a short-lived token, valid for ten minutes and tied to your connection. If you leave the result card open for a long time and then press Download, the token has aged out. Paste the link again — it takes a second, and the video is not going anywhere.

This also happens if your IP address changes mid-session, which is common on mobile when you move between Wi-Fi and cellular.

The download stalls at "Preparing converter"

Not an error, just the one-off 32 MB download of the in-browser converter. On a slow connection it can take a while. Switch to Wi-Fi if you can, and let it finish — it is cached afterwards, so this only happens once per browser.

If it does not complete after a couple of minutes, the connection dropped. Reload the page and try again.

"HD unavailable on this browser"

The in-browser converter needs WebAssembly. Very old mobile browsers, some locked-down corporate builds, and certain privacy extensions block it. Rather than fail, ShortsDL falls back to a direct 360p download that needs no conversion.

To get HD instead, use a current Chrome, Safari, Edge or Firefox, and check whether an extension is blocking WebAssembly.

The video plays instead of downloading

You are in an in-app browser — the one inside Instagram, Facebook, Telegram or TikTok. These intercept downloads and often just open the media instead. Tap the menu and choose Open in browser or Open in Chrome/Safari, then try again.

The download starts but never finishes

Usually storage. A Short is a few megabytes, but the converter needs working room while it merges. Free a few hundred megabytes and retry.

On iPhone, also check Settings → Safari → Downloads points at a location that exists.

The file is there but will not play

Almost always an incomplete download — the connection dropped partway. Delete the file and download again.

If it plays but has no sound, you did not get it from ShortsDL: the merge step exists precisely to prevent that. The quality guide explains why silent downloads are so common elsewhere.

Nothing happens at all

• Ad blocker or script blocker interfering. Try with it paused.
• Very restricted network — some school and office networks block media downloads outright.
• Browser out of date. Anything from the last few years is fine; much older is not.

Still stuck?

Note which step failed and what the message said, and get in touch. Errors that reproduce on a specific public Short are far easier to fix than "it does not work", so include the link if you can.