Understanding Threads Media URLs and Share Links

Executive Summary

Threads issues two primary link types: permanent canonical URLs (`threads.com/@username/post/POST_ID`) and short mobile share redirects (`threads.com/share/TOKEN`). Resolving media requires following the short link HTTP 302 redirect chain to discover the parent post object and extract public CDN media streams.

Threads generates two distinct URL structures depending on where you copy a post. Understanding these patterns is essential for developers, creators, and anyone troubleshooting link sharing.

The Two URL Structures

When you interact with Threads, URLs fall into one of two categories:

1. Canonical Post URLs

Permanent web links use the format:

https://www.threads.com/@username/post/POST_CODE
  • @username: The author handle on Threads.
  • post: The routing segment identifying single post views.
  • POST_CODE: An alphanumeric identifier (such as DdcPsEkH3NZ) mapping to Meta internal post identifier.

Legacy desktop URLs may also use threads.net instead of threads.com. Meta automatically treats both hostnames interchangeably.

2. Short Share Links

When you tap the Share icon inside the iOS or Android mobile application, Threads copies a short link:

https://www.threads.com/share/SHARE_TOKEN

The SHARE_TOKEN is a short base-62 token. It does not contain the author username or the post code directly in the URL path.

How Short Share Links Resolve

A short share link is not an endpoint that serves post content directly. Instead, Meta edge servers handle incoming share links by returning an HTTP 302 Found redirect:

HTTP/2 302 Found
location: https://www.threads.com/@mosseri/post/DdcPsEkH3NZ?xmt=AQGz...

When a browser or downloader requests a /share/ URL:

  1. The request hits Meta edge proxy.
  2. The proxy reads the short token from its lookup database.
  3. The server responds with a 302 status code and a Location header containing the canonical post URL.
  4. The client follows the Location header to load the underlying post metadata.

If you paste a share URL into Threaa, the server follows this redirect chain automatically, extracts the canonical post code, and resolves the media attachments without extra steps.

Media Attachment URLs

Once the post page resolves, media attachments are not served from the threads.com domain itself. Instead, media files are hosted on Meta global Content Delivery Network (CDN):

  • Video Streams: Hosted on domains such as scontent.cdninstagram.com, delivered as progressive MP4 video streams.
  • Image Candidates: Stored as JPEG files with multiple resolution variants (candidates) ranging from 150px thumbnails to 1440px full-detail images.

These CDN URLs contain temporary cryptographic signatures in their query parameters (including _nc_ht, _nc_cat, and oh). These signatures expire after a set time window, preventing permanent external hotlinking while allowing direct browser downloads.

Clean URLs vs Tracking Tokens

Mobile share URLs often append tracking tags:

?xmt=AQGz...&s=09

These parameters identify the share method (direct message, external copy, or cross-platform broadcast). They do not alter the underlying post content. Trimming everything from the question mark onward yields a clean canonical link that resolves identically.

For troubleshooting link issues, see our guide on Why Threads Share Links Fail to Resolve or learn How to Use Threaa Quick Mode.

References & Technical Sources