GrabSilo / CODE-BACKED REFERENCE
Threads downloader compatibility
A maintained reference for accepted public Threads URLs, returned content, export formats, failure states, and the direct media path used by GrabSilo.
Threads / Scope
What does the Threads downloader support?
GrabSilo accepts an exact public Threads post URL, a public profile URL, or a Threads share URL. It can return the post text, available photos and videos, quoted-post context, public replies exposed by Threads, and public profile posts. It does not bypass private, deleted, login-only, age-restricted, or otherwise unavailable content.
Current compatibility snapshot
These are product capabilities, not marketing estimates. The page is updated when URL validation, resolver behavior, export formats, or browser limits change.
accepted URL types
Exact post, public profile, and Threads share link.
text export choices
Copy, TXT, HTML, JSON, and CSV.
media files stored
Photos and videos travel from Meta CDN to the browser.
Supported Threads URL types
The validator accepts only narrow, recognizable public routes. Tracking parameters may be ignored, but credentials, explicit ports, unrelated product routes, and lookalike hosts are rejected.
| Input | Example pattern | Status | What happens |
|---|---|---|---|
| Exact public post | threads.com/@user/post/POST_ID | Supported | The exact post is normalized to threads.com and resolved without crawling a feed or profile timeline. |
| Public profile | threads.com/@user | Supported | GrabSilo returns the public profile details and the posts Threads currently exposes, with a complete or partial label. |
| Threads share link | threads.com/share/SHARE_ID | Supported | The share URL is followed only to a validated Threads destination. A different host or unexpected target is rejected. |
| Feed, search, replies tab, or private URL | threads.com/explore or /@user/replies | Rejected | GrabSilo does not crawl timelines, search results, private areas, or unsupported account routes. |
Content and export compatibility
Availability depends on what Threads exposes for that public item at request time. GrabSilo labels partial data rather than inventing missing posts, replies, or files.
| Content | Available action | Status | Important limit |
|---|---|---|---|
| Post text | Copy, TXT, HTML, JSON, CSV | Supported | Text-only posts are valid results. Main text, quoted posts, and replies stay structurally separate. |
| Photos and carousels | Individual originals or browser ZIP | Supported | ZIP batches are limited to 10 files and 100 MiB. Browser CORS can block ZIP even when individual files still open. |
| Video | Direct original-file save | Supported | Only files currently exposed by Threads are shown. GrabSilo does not create a resolution or audio track that is absent upstream. |
| Public replies | Nested reply view plus text exports | May be partial | When Threads reports more replies than its public response returns, the loaded and expected counts are shown separately. |
| Quoted post | Separate text and media context | Supported when exposed | Quoted content is not merged into the main post, so the source relationship remains visible. |
| Public profile export | Copy, TXT, HTML, JSON, CSV, media ZIP batches | Supported | The export includes only profile posts present in the current public response and marks incomplete timelines explicitly. |
Known limits and failure states
- Private, deleted, suspended, login-only, age-restricted, or region-restricted content cannot be opened.
- Threads can temporarily block automated public-page access. GrabSilo reports an upstream-blocked state instead of retrying indefinitely.
- A platform page-format change can stop parsing until the resolver is updated. GrabSilo rejects ambiguous media rather than guessing.
- Public reply and profile totals can be larger than the content returned to a logged-out request. Partial results remain usable but are labeled partial.
- Temporary Meta CDN URLs can expire. Resolving the source again is safer than reusing an old media URL.
- Browser CORS rules can prevent a multi-file ZIP. Individual direct links may still work because the browser opens the original CDN file.
How this reference is kept accurate
The accepted URL patterns mirror the same frontend validator and backend normalizer used before a request reaches the resolver. Tests cover exact posts, public profiles, share URLs, lookalike hosts, credentials, ports, unsupported paths, and canonical conversion from threads.net to threads.com.
The output matrix mirrors the response model and browser export code. It distinguishes post, profile, quote, reply, image, video, text, and ZIP behavior, including the conditions that produce partial results or browser-only failures.
This page does not publish a fabricated success-rate percentage. Reliability depends on current Threads behavior, public availability, region, and browser rules. Changes are recorded below when the implemented contract changes.
Change log
Reviewed exact post, public profile, share-link, reply-completeness, direct-media, and browser ZIP behavior against the current implementation and regression tests.
Reference sources
- Introducing Threads: A New Way to Share With TextMeta Newsroom
- New Features for the Threads Web ExperienceMeta Newsroom
- GrabSilo privacy policyGrabSilo