Most downloader pages only explain what they can do. This one lists what this tool refuses to do, what it returns when it refuses, and which of those answers are worth acting on. Every number below was read out of the code serving this page.
Why a page about limits exists at all
A tool that only advertises success pushes every failure back onto you. You paste a link, something goes wrong, and the page either spins or says the link is invalid — when the link was fine. You then spend ten minutes re-copying a link that was never the problem.
So every failure here is classified into one of twelve codes, and each code answers three questions: whose problem it is, whether retrying can help, and what HTTP status it comes back with. That last part matters if you are a script or an assistant rather than a person, because a bare 429 and a bare 502 call for opposite reactions.
The one-sentence version: 12 lookups and 60 downloads per address every 10 minutes, 200 MB per file with no duration ceiling, a 15-minute download link, and twelve named failures — never a bare "failed".
The twelve limits
Each line gives the value, then the constant it comes from. If a value here ever disagrees with what the tool does, the constant is right and this page is wrong — please say so.
1Link lookups per address — 12 every 10 minutesOne lookup is one paste-and-read. The window is fixed rather than rolling, so a full window resets all at once rather than sliding. config.ts → RATE_LIMIT_RESOLVE_MAX = 12, RATE_LIMIT_RESOLVE_WINDOW_MS = 600000
2File downloads per address — 60 every 10 minutesCounted separately from lookups. Downloading a file never spends one of your twelve lookups. config.ts → RATE_LIMIT_DOWNLOAD_MAX = 60, RATE_LIMIT_DOWNLOAD_WINDOW_MS = 600000
3When you hit a limit — HTTP 429, and the body does not tell you how longThis is the one place where we are less helpful than we could be: the response carries RATE_LIMITED and a 429 status, but the wait is a fixed ten-minute window rather than a countdown. Treat any 429 as: stop, wait out the window, then retry once. errorCodes.ts → RATE_LIMITED: 429; rateLimit.ts fixed window
4Largest file we will hand over — 200 MBMeasured on the file Instagram actually serves, not on what the post implies. A post that looks like a short Reel but resolves to a long upload is refused with FILE_TOO_LARGE. config.ts → MAX_FILE_BYTES = 209715200, confirmed in .env.production
5Longest video — No duration ceilingUnlike some downloaders we do not refuse a video for being long. The only ceiling is the 200 MB file size, which a very long high-bitrate upload can reach before a short one does. config.ts → no maxDurationSeconds key; MAX_FILE_BYTES is the only ceiling
6Lookups running at the same time — 2A third visitor waits for a free slot. If nothing frees up the request fails with SERVICE_BUSY (HTTP 503) — that is a queue that ran out, not a bad link. config.ts → MAX_CONCURRENT_RESOLVES = 2
7Downloads running at the same time — 2The relay is the expensive part, so it gets its own budget of the same size. This is why a busy moment feels slow rather than broken. config.ts → MAX_CONCURRENT_TRANSFERS = 2
8How long a lookup result stays fresh — 5 minutesPaste the same link again inside five minutes and the stored answer is served instead of a new fetch — which also means it does not cost you one of your twelve. config.ts → RESOLVE_CACHE_TTL_MS = 300000
9How long a download link works — 15 minutes, and only in the session that created itThe link is a signed token with an expiry stamped into it. After 15 minutes it returns LINK_EXPIRED. Opened in another browser it fails as well, because the signature is bound to the session rather than to the file. config.ts → DOWNLOAD_TOKEN_TTL_MS = 900000; tokens.ts → HMAC payload with exp
10How long a resolved job stays in memory — 30 minutesAfter that the job is gone and the download button stops working, even inside the 15-minute link window. Whichever expires first wins. jobs.ts → new TtlCache<Job>(30 * 60_000, 2000)
11Which links we accept — Instagram Reels, posts and IGTV onlyAn exact hostname allowlist — instagram.com, www., m., l., instagr.am — plus an exact path shape: /reel/<code>/, /reels/<code>/, /p/<code>/ or /tv/<code>/. Stories, explore, direct, accounts, reels/audio, reels/remix, about, legal, developer, api, web and graphql are refused with UNSUPPORTED_CONTENT. Media is only fetched from cdninstagram.com or fbcdn.net, https only. validateUrl.ts → PAGE_HOSTS, UNSUPPORTED_PATH_RE, MEDIA_HOST_SUFFIXES
12How long we wait on Instagram — 30 seconds, retried twiceInstagram is often slow rather than down. Two retries under the same 30-second ceiling; past that the answer is UPSTREAM_TIMEOUT and the delay is on their side. config.ts → RESOLVE_TIMEOUT_MS = 30000, RESOLVE_MAX_RETRIES = 2
The twelve error codes
This is the part that makes the page worth reading. A failure that only says "failed" forces you to guess, and the usual guess — try again — is wrong for most of these. Retrying a private post burns your allowance and gets the same answer.
The four groups are not decorative. Yours means changing the link can fix it. Instagram's means the link was fine and the source said no. Ours means the failure happened on this machine. One code is deliberately ambiguous and says so.
1INVALID_URL · HTTP 400 · Yours · retry: NoThe text is not a web address, or it is missing the shortcode that identifies a post. Editing it will not help; copy the link again from Instagram's share menu.
2UNSUPPORTED_CONTENT · HTTP 422 · Yours · retry: NoA real Instagram address, but not one that holds a single readable post: a profile, a Story, explore, direct messages, a reel's audio page, or an about or legal page. The address is valid and the answer will not change.
3NO_VIDEO · HTTP 422 · Instagram's · retry: NoThe post is readable but holds no video — a photo, a photo carousel, or an image post. There is nothing for us to hand over, and this is a final answer.
4NOT_FOUND · HTTP 404 · Instagram's · retry: NoThe post has been deleted, or Instagram returned an empty media response. The shortcode resolves to nothing.
5ACCESS_RESTRICTED · HTTP 403 · Instagram's · retry: NoInstagram answered with a login wall, an age gate, a region lock or a private account. The link is fine; the content is not public. We do not hold Instagram credentials and never will, so this is not a bug waiting to be fixed.
6RATE_LIMITED · HTTP 429 · Instagram's, or ours · retry: LaterInstagram answered 429 or "too many requests". Two quite different things land here and we cannot always tell them apart: this particular post being throttled, or our whole outbound connection being throttled. Either way, waiting is the only useful response — retrying immediately makes it worse.
7UPSTREAM_TIMEOUT · HTTP 504 · Instagram's · retry: YesWe waited 30 seconds, twice, and got no answer — a timeout, a dropped connection, or a DNS failure. The link is probably fine and Instagram was slow.
8EXTRACTOR_FAILED · HTTP 502 · Ours · retry: OnceOur reader did not understand the response. This is explicitly our problem and is never reported as a bad link, because telling someone their perfectly good link is wrong is the single most useless error a downloader can give.
9LINK_EXPIRED · HTTP 410 · Ours · retry: No — resolve againThe 15-minute download link ran out. Paste the original post link again for a fresh one.
10SERVICE_BUSY · HTTP 503 · Ours · retry: YesBoth lookup slots were taken and no outbound connection was free in time. This is queueing and capacity, not a fault, and it normally clears in seconds.
11FILE_TOO_LARGE · HTTP 413 · Ours · retry: NoThe file is over 200 MB. Since there is no duration ceiling here, this is the one limit a long upload can hit. It is a final answer for that rendition.
12DOWNLOAD_FAILED · HTTP 502 · Ours · retry: OnceThe transfer started and then broke — the CDN dropped us mid-file, or the relay could not finish. Worth one more attempt.
If you only remember one line: the codes worth retrying are UPSTREAM_TIMEOUT, SERVICE_BUSY, DOWNLOAD_FAILED and EXTRACTOR_FAILED, plus RATE_LIMITED after waiting out the ten-minute window. Every other code gives the same answer the second time.
Three things this tool will not do
1We do not log in to InstagramACCESS_RESTRICTED is a real answer, not a temporary glitch. Private accounts, age gates and region locks stay out of reach, and there is no honest route around that.
2We do not claim to remove something that was never addedIf Instagram served the file with a watermark or overlay, that is the file. We pass on what the source gave us and do not pretend otherwise.
3We do not tell you your link is broken when we simply failedAn unreadable response becomes EXTRACTOR_FAILED, not INVALID_URL. The two look similar to a machine and are completely different to a person: one means re-copy the link, the other means try again in a minute.
What is kept and what is not
1The video fileNever stored. It is relayed through as you download it, which is also why a download link expires in 15 minutes — there is nothing on disk to serve later.
2Your link and the resultHeld in memory for 30 minutes so the download button keeps working and so pasting the same link again is free. Then it is gone.
3Nothing that identifies youNo account, no email, no login. We see a client address for rate limiting and nothing else.
Questions people actually ask
What are the actual limits of this tool
Twelve of them, all listed above with the value and the source constant: 12 link lookups and 60 downloads per address every 10 minutes, a 200 MB file ceiling with no duration ceiling, 2 concurrent lookups and 2 concurrent downloads, a 5-minute result cache, a 15-minute download link, a 30-minute job lifetime, an exact Instagram host and path allowlist, media only from cdninstagram.com or fbcdn.net, and a 30-second upstream timeout retried twice.
Which failures are worth retrying
UPSTREAM_TIMEOUT, SERVICE_BUSY, DOWNLOAD_FAILED and EXTRACTOR_FAILED are worth another attempt. RATE_LIMITED is worth retrying only after waiting out the ten-minute window, since trying sooner makes it worse. Everything else is permanent for that request: retrying INVALID_URL, UNSUPPORTED_CONTENT, NO_VIDEO, NOT_FOUND, ACCESS_RESTRICTED, LINK_EXPIRED or FILE_TOO_LARGE changes nothing and only spends your allowance.
Why is there no error that just says failed
Because an unclassified failure was the problem we set out to avoid. Reporting an unknown error as a bad link is worse than saying nothing: you go and re-copy a link that was perfectly fine, and the real cause never gets looked at. Every failure path here is classified into one of twelve codes, and EXTRACTOR_FAILED exists specifically so that our own failure never gets blamed on your link.
What does each HTTP status mean here
400 means the text was not a link. 403 means Instagram requires a login, an age check or the account is private. 404 means the post is gone. 410 means the download link expired. 413 means the file is over 200 MB. 422 means the link is understood but holds no video, or is not a single post. 429 means you or we are being throttled. 502 is our side. 503 is us out of capacity. 504 is Instagram too slow.
Can I download a private Instagram video
No, and ACCESS_RESTRICTED is the honest answer rather than an error to work around. A video that needs a login to watch needs a login to fetch, and we do not accept Instagram credentials.
Why does a download link stop working after 15 minutes
The link is a signed token with an expiry stamped into it and bound to the session that created it. After 15 minutes it returns LINK_EXPIRED. Opening it from another browser fails as well, because the signature no longer matches a session we know. Pasting the original post link again issues a new one.
Is there a limit on how long a video can be
No. We do not refuse a video for its duration — the only ceiling is 200 MB of file size. A very long upload can hit that ceiling before a short high-bitrate one does, which is why the size limit, not a clock, is what you can actually run into.
Does pasting the same link again cost another lookup
No, if you do it within five minutes. The result is cached for 300 seconds and served from memory without touching your twelve-lookup allowance.
Why did it say the post is restricted when I can open it fine
Because being able to open it in your browser is not the same as being fetchable without one. You are logged in; the fetch is anonymous. Instagram treats those two differently, and the wording of the refusal we get back does not always make it obvious which wall we hit.
What counts as a link you will accept
Instagram Reels, posts and IGTV — /reel/<code>/, /reels/<code>/, /p/<code>/ or /tv/<code>/ on instagram.com, www., m., l. or instagr.am, with a shortcode of 5 to 32 letters, digits, underscores or dashes. Stories, explore, direct messages, accounts, reel audio pages and every non-post path return UNSUPPORTED_CONTENT.
Do you keep the videos or my links
Videos are never stored — they are relayed through as you download. Your link and the resolved result sit in memory for 30 minutes, then they are gone. There is no account and no email address.
Paste a link and see the real answer
If it fails, you will get one of the twelve codes above — not a spinner.
Open the downloader