Threads Downloader App for Android

Saving from the Share sheet

The most convenient entry point is the Share sheet. Open a public Threads post in the Threads app, tap the share icon, and choose ThreadSave from the share targets. The app extracts the link from the shared text and takes you straight to the preview screen.

You can also paste a link directly into the app's input field, the same way you would on the website. The app accepts the same URL shapes the site does: public post links, share links, and profile links, all on threads.net or threads.com.

Whatever the entry point, the app then asks the same service the website uses to resolve the post. That shared service means the app and the site behave identically: the same public-post boundary, the same media discovery, the same signed, expiring download links.

Previewing and choosing media

Once a post resolves, the app lists every video and image attached to it as its own item, with a preview you can check before saving anything. A carousel with several photos shows each photo separately, and a mixed post with photos and a video shows each file on its own.

This per-item list is the same deliberate design as the website. You never have to download a bundle of files you do not want. A six-photo carousel lets you take the second photo only, and a post with a single video gives you exactly that one file.

Because the preview is the real file, what you check is what you save. The resolution you see is the resolution that downloads, with no upscaling and no re-encoding anywhere in the flow.

Downloads, progress, and where files land

When you start a download, the app hands the work to Android's WorkManager, which runs the download as a background job that survives the app being closed. The app shows the file's state as it moves through queued, downloading, and saving, with a progress percentage while the bytes stream.

A completed download is saved into your device's Downloads collection, the standard Android location that most gallery and file-manager apps watch. If the download hits an error, the app reports it clearly, including the case where a signed link has expired, in which case resolving the post again issues a fresh link.

The app also enforces the same 15-minute token expiry and size limits the site enforces. A download that cannot proceed because a link lapsed or a file exceeds the limit surfaces a readable message rather than a silent failure.

The app's boundaries

The app reads only public posts, the same boundary as every tool on this site. It never asks for a Threads login, never stores credentials, and never touches private accounts or follower-only content.

There is no bulk mode and no background scraping. The app resolves one link at a time, the link you give it, and nothing else. It does not crawl profiles, build lists of accounts, or offer any kind of automated collection of other people's media.

The app is also deliberately honest about quality. Videos download at the resolution Threads serves for that post, typically up to 1080p when the creator uploaded a high-resolution source, and photos download at the size Threads serves. Nothing is upscaled, and the app never claims a 4K tier that the platform does not provide.

Availability

The app is fully implemented in this repository as a native Kotlin and Jetpack Compose application with the permanent package identifier com.threadsave.downloader. Building it requires Android Studio, and its release distribution goes through the Google Play Store.

This page is staged until the Play Store listing exists. Publishing a page with an install link before a listing is ready would only mislead visitors, so the page stays draft, exactly like the extension and Shortcut pages, until its release gate opens.

When the listing is live, this page will link to it and go live. The source in the repository can be reviewed now, including its download service, its URL handling, and its test suite.

How the app stays in sync with the website

The app and the website talk to the same service, which is what keeps their behavior identical. When you resolve a post in the app, the request goes to the same resolver, subject to the same validation, rate limits, and media allowlist that protect the website. The app does not implement its own copy of the downloader logic; it calls the same one.

That shared service is the reason the rules never drift between platforms. Public posts resolve, private posts do not, media hosts are checked before anything is offered, and every download link is signed and expires after 15 minutes. A behavior you rely on in the browser behaves the same way in the app, because underneath they are the same downloader.

The app's own code is responsible only for the Android-specific surface: the share target, the input screen, the preview list, the WorkManager download jobs, and the notifications that report progress and completion. Those pieces are tested in the repository alongside the app's URL handling and API response parsing, so the client-side behavior has the same test discipline as the server.

Keeping the client thin is also what keeps the downloader honest on a new platform. There is no second code path where a rule could quietly change, and no client-side logic that could weaken a server-side check. The app is a well-behaved client of the same public-post service, nothing more and nothing less.

Using the app responsibly

The app works only with public posts, and public posts are still someone's content. The same guidelines that apply to the website apply here: download media you own, media you have permission to save, or content shared with the clear intent of being public.

Downloading a public post does not transfer ownership of the media, and re-uploading someone's work as your own is not something any tool can authorize. Reusing a profile picture or a creator's logo carries its own rights considerations, which is why the site's profile picture tool documents them on its own page.

Because the app delegates every resolution to the shared service, the site's safeguards apply unchanged on Android. Every download still uses a signed link that expires after 15 minutes, and the server still validates the media host, content type, and file size before streaming anything. The app adds no workaround and no hidden mode that could reach content the site itself would refuse.