How Threaa Resolves Public Threads Media
Threaa operates as a stateless edge application on Cloudflare Workers. When you submit a URL, the edge worker normalizes the link, follows any short redirect chains, requests the public post HTML, parses the embedded media JSON payload, and returns direct, signed CDN URLs for browser-native streaming.
Step-by-Step Instructions
URL Normalization & Validation
The worker strips tracking query parameters and validates that the domain belongs to threads.com or threads.net.
Redirect Resolution (For Share Links)
If the URL contains /share/, the worker sends an HTTP HEAD request with manual redirect handling to capture the canonical location header.
Public Metadata Inspection
The worker fetches the public post page using an anonymous user agent, extracting the LSD token and JSON state object.
Media Candidate Extraction
The worker traverses the media tree (video_versions and image_versions2) and selects the highest resolution stream available.
Direct Client Streaming
The resolved media URLs are passed back to the user browser for direct, full-speed downloading from Meta CDN.
Device-Specific Tips
Zero Proxy
Because the file streams directly from Meta CDN to the client, Threaa servers never store or proxy video files.
Frequently Asked Questions
Does Threaa require user login or credentials?
No. Threaa operates anonymously and only processes publicly indexable post information.
References & Technical Sources
- Cloudflare Workers Runtime Documentation Official Documentation
- Threaa Product Capability Matrix Official Documentation
