Direct answer · local cancellation checks

Instagram Reel downloader: what happens if you close the tab mid-download?

Keep the Vidlune tab open while it says Preparing. The page waits for the whole response before asking the browser to save a file. If you close it before that handoff, do not assume you have a saved file or a resumable download. This implementation check does not establish exactly when the production server notices a closed tab.

Receiving the file is not the same as saving it

The published form awaits response.blob(), creates an object URL, then clicks a download link. Its “download has started” message follows that click; it is not confirmation that the final file is on disk. The Blob API reads the response to completion. After a save starts, check the browser's download list and open the completed local file rather than relying on the page message.

Two stages: receive the complete response, then start the browser save. Neither stage guarantees continuation after closing the tab.

Two cancellation paths tested locally

During preparation

On October 6 we started the route with a deliberately slow fake downloader, waited for its process registry, then triggered the request's AbortController. The route returned HTTP 499; the test verified that the downloader process tree exited and its temporary directory was removed. This tests handling of a delivered cancellation signal, not closing a real Chrome tab.

After a response stream exists

A separate fixture returned HTTP 200. We then aborted its request and cancelled the response body; its temporary directory was removed. The concurrency test also confirmed that after aborting a preparing task, a subsequent fixture could acquire the released slot. Those results do not prove Cloudflare will immediately relay every browser disconnection to the origin.

Environment: October 6, 2026 at 11:18 (Asia/Shanghai), DESKTOP-OC01O77, Windows 11 Pro 10.0.28000 x64, Node v24.19.0. These were local handler tests in the ig-reels-downloader.com project, with no browser involved and no production media request. Different machines and runtime versions can change results.

Reproduce the controlled checks

In the project, run the command below. The suite uses a fake downloader and synthetic request identities locally; it does not bypass the production allowance. Look for the request-abort, stream-abort and slot-release tests. All 19 tests passed in this run.

node --import ./scripts/test-typescript-imports.mjs --test tests/download-route.test.mjs

If you closed the tab before the file appeared

First check whether the browser already saved a playable file. If not, reopen the tool and submit the public link again; this is a new request, not a resume from the interrupted byte position. The form has no persisted transfer identifier or resume control. In the inspected handler, quota is recorded before the response stream finishes, so an interrupted save must not be assumed to restore a free download. The production quota effect of closing a tab was not measured.

No production Chrome tab-close, phone backgrounding or post-close disk-save experiment was performed here. We cannot promise that closing the tab stops the backend, that a started save survives it, or that a retry is free.

Use the instagram reel downloader to start a new request. For locating a completed file, see the phone download guide. For an unexpected saved name, see the filename guide.