Threads Video Downloader Shortcut for iPhone

One-tap saving from the Share sheet

The Shortcut is built around the iOS Share sheet, because that is where saving naturally starts on an iPhone. You are reading a Threads post you want to keep, you tap the share icon, and the Share sheet appears. Choosing the iThreadsVideoDownloader Shortcut hands the post's link straight to the downloader without copying, switching apps, or pasting.

The same Shortcut also reads a link from the clipboard, which is useful when a link came through a message or a browser rather than the Threads app. Either entry point ends at the same place: this site opens with the link pre-filled into the downloader input.

One tap is the entire point of the page title and the design. Frequent downloaders describe the copy, paste, and switch routine as the part of saving they wish would disappear. The Shortcut removes exactly those steps and leaves the parts that matter: previewing the media and choosing what to keep.

What the Shortcut does with your link

When the Shortcut receives a link, it runs a short, fixed sequence. It takes the link from the Share sheet or the clipboard, encodes it so every character survives the trip into a URL, and opens this site with the encoded link as the url parameter.

The site reads that parameter and pre-fills the downloader input. From there the flow is identical to typing a link by hand: the page resolves the post, lists every video and image attached to it with its own preview, and lets you download the files you actually want, one at a time.

Because the Shortcut only moves a link, it has no behavior of its own to get out of date. If the site changes its flow, the Shortcut keeps working, because it never knew anything about the flow in the first place. The recipe in this repository is a short, auditable list of actions that anyone can read and verify.

Why the Shortcut stays thin

An iOS Shortcut could in principle try to read a page's media and save it directly, but this Shortcut deliberately does not. The site's service already handles the hard parts: reading the public post, locating the exact media attached to it, signing expiring download links, and streaming the files. Duplicating any of that inside a Shortcut would be fragile, because Shortcuts cannot run the kind of server-side validation the site performs.

Delegation also keeps the Shortcut auditable. The recipe in this repository is a short list of actions that anyone can read and verify. There is no hidden logic inside the Shortcut, because there is no logic inside the Shortcut at all beyond moving a link.

That matches how the site itself is designed. The downloader is one tested service with one set of rules: public posts only, original files, signed links. The Shortcut is a convenience that points at that service, not a second implementation with different behavior.

What the Shortcut will not do

It will not bypass privacy controls. If a post is private or follower-only, the downloader reports that it cannot be read, exactly as it does for any pasted link. The Shortcut cannot reach content that the site itself cannot reach.

It will not download files in the background or save them silently. Downloads happen through the site's preview-and-choose flow, in your browser, the same way every other download on this site works. Nothing is stored on our side and nothing is saved without you tapping the download button.

It will not be a bulk tool. The Shortcut handles one link at a time, one post at a time, which is the same scope as every tool on this site. There is no batch mode and no plan to add one.

Availability and the signing requirement

An installable Shortcut on iPhone is a signed file or an iCloud share link produced by Apple's Shortcuts tooling. The repository cannot manufacture that signed artifact, and it will not present its unsigned plist source as installable. The signing guide in the repository explains the exact Apple interaction involved.

When a real signed artifact exists, whether an iCloud share link or a downloadable Shortcut file, this page will link to it and go live. Until then the page stays staged so that no visitor is promised an install link that does not actually work.

The recipe in the repository lets anyone with the Shortcuts app reproduce the intended flow manually right now. Building the four actions by hand takes about a minute and produces the same behavior the signed Shortcut will have.

How the Shortcut is reviewed

Because the Shortcut is nothing but a short list of actions, it can be reviewed end to end without running it. The recipe in this repository lists every action, the input each one receives, and the URL it produces, and the plist source shows the same flow in the format the Shortcuts app itself uses. Anyone who wants to know exactly what the Shortcut does can read both and compare them.

That auditability matters more for an automation than for a website. A Shortcut receives the links you share and can open URLs in your browser, so knowing precisely what it does with them is part of deciding whether to use it. Here the answer is simple and visible: it takes the link, encodes it, and opens this site with it.

The signing guide covers the other half of the story, which is how a reviewable source becomes an installable artifact. Signing is an Apple operation, and the guide explains the exact interaction required and why the repository cannot fake it. Together the recipe and the guide give a complete, honest picture of the Shortcut's behavior and its release path.

What happens after the download

The Shortcut's job ends when the downloader opens with your link. What happens next is the same as any other download on this site: you resolve the post, preview the media, and choose the files you want.

On iPhone, a downloaded video lands in Safari's download location, which maps into the Files app. From there a long press and Save Video moves it into Photos, the same step the site's iPhone guide describes in detail. Photos save the same way, with Save Image instead of Save Video.

Because the Shortcut does not intercept or redirect the download, nothing about these device steps changes. The file that arrives is the MP4 or JPEG the site served, at the quality Threads provides, with no re-encoding and no watermark. If a signed link expires while you are working through a post, resolving it again issues a fresh one, exactly as it would after any other resolve.

Keeping the download path standard is a feature. The Shortcut removes the friction of getting the link into the downloader, and leaves the well-tested saving flow untouched, so there is no new behavior to learn and no new failure mode to debug.