Threads Scraper - Scrape threads.net Posts, No Login

Threads Scraper — Posts, Profiles, Replies & Engagement (No Login, No API Key)

Scrape Threads (threads.com / threads.net) — Meta's text-based social network — by username, post URL, or keyword/#tag. Pull public posts with full engagement — likes, replies, reposts and quotes — plus text, hashtags, mentions, media (images & videos), language, author and date. It needs no login, no cookies and no API key — it reads only public data through residential proxies, so there's zero risk to any Threads or Instagram account.

🏆 Why this Threads scraper?

3 input modes (username · post URL · keyword/#tag) · full engagement metrics · reply-thread expansion (turns ~25 into 300–700 posts per profile) · media, hashtags & author context · no login, no cookies, 0% ban risk · export to JSON / CSV / Excel. The unofficial Threads API alternative for content analysis, social listening and post datasets.

---

✨ What this Actor does / Key features

• 🧵 3 input modes — scrape by username, by post URL, or by keyword / #tag; mix them in one run.
• 📦 Recent public posts — collects each target's most recent public posts (login-free window).
• 📊 Full engagement — likes, replies, reposts & quotes for every post.
• 🔁 Reply-thread expansion — opens each post's page to also collect its visible reply thread (~25–30 posts), the main volume multiplier.
• 🖼️ Media included — image and video URLs, including carousels.
• 🏷️ Rich post data — hashtags, mentions, language, reply flag and paid-partnership flag.
• 👤 Author context — username, full name, verified status and avatar per post.
• 🛡️ Login-free & safe — public-page access over residential proxies; no account, no ban risk.
• 🔑 No API key — reads only public data; only an Apify account required.

🚀 Quick start (3 steps)

1. Configure — provide at least one of usernames, postUrls or searchTerms. Keep reply expansion on for maximum volume.
2. Run — click Start. The Actor walks timelines/searches, expands reply threads, de-duplicates by post id and streams posts into your dataset.
3. Get your data — open the Output tab and export to JSON, CSV, Excel or HTML, or pull it via the Apify API.

📥 Input

Provide at least one of usernames, postUrls or searchTerms. Everything else is optional.

Example — profiles + a hashtag (max volume)

{
  "usernames": ["zuck", "https://www.threads.com/@mosseri"],
  "searchTerms": ["#ai"],
  "maxResults": 0,
  "includeReplies": true,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "US" }
}

Example — a single post + its reply thread

{
  "postUrls": ["https://www.threads.com/@zuck/post/DY11ZLWG_eY"],
  "maxRepliesPerPost": 100
}

Example — keyword social listening

{
  "searchTerms": ["startup", "#travel", "ai"],
  "expandFromSearch": true,
  "maxResults": 0
}

Field	Type	Description	Default
usernames	array	Threads @handles or profile URLs (e.g. ["zuck", "@mosseri"]).	–
postUrls	array	Threads post URLs (post + visible replies).	–
searchTerms	array	Keywords or #tags to search (e.g. ["ai", "#travel"]).	–
maxResults	integer	Max posts per target (timeline + expanded replies). 0 = unlimited (recommended).	0
includeReplies	boolean	Expand each target post's reply thread (~25–30 posts each). Main volume multiplier.	true
expandFromProfiles	boolean	Expand reply threads of posts collected from profiles.	true
expandFromSearch	boolean	Expand reply threads of posts returned by searches/tags.	false
maxExpandPerTarget	integer	How many of a target's posts to open for expansion.	30
maxRepliesPerPost	integer	Cap on replies kept per expanded post.	50
proxyConfiguration	object	Residential proxy (Threads blocks datacenter IPs).	RESIDENTIAL · US

Tip: breadth wins — add many handles, tags and post URLs in one run; they aggregate and de-duplicate automatically. Keep the RESIDENTIAL default. Prefix with # for tags, or use plain keywords for full-text search.

📤 Output

Each item is one Threads post — exportable to JSON, CSV, Excel or HTML. Here is a trimmed sample record:

{
  "postId": "3906263078447871896",
  "code": "DY11ZLWG_eY",
  "url": "https://www.threads.com/@zuck/post/DY11ZLWG_eY",
  "text": "Today Biohub is sharing a major scientific advance...",
  "createdAt": "2026-05-27T14:02:00.000Z",
  "lang": "en",
  "likeCount": 1948,
  "replyCount": 385,
  "repostCount": 124,
  "quoteCount": 25,
  "isReply": false,
  "isPaidPartnership": false,
  "hashtags": [],
  "mentions": [],
  "media": [{ "type": "image", "url": "https://scontent.cdninstagram.com/..." }],
  "author": {
    "id": "63055343223",
    "username": "zuck",
    "fullName": "Mark Zuckerberg",
    "isVerified": true,
    "profilePicUrl": "https://scontent.cdninstagram.com/..."
  },
  "fromSource": "zuck",
  "scrapedAt": "2026-07-06T12:00:00.000Z"
}

📈 Volume & limits (honest numbers)

Threads gates logged-out visitors. Here is what each mode actually returns, measured live:

Mode	Raw public window	With reply expansion
Profile (usernames)	~25 posts (1 timeline page, then login wall)	~300–700 posts per profile
Post URL (postUrls)	post + full visible reply thread (~30 posts)	already includes the thread
Search / tag (searchTerms)	~20 posts (no guest pagination)	~20 × replies if expandFromSearch on

How the multiplier works: a profile timeline gives ~25 posts before the login wall. The Actor then opens each post's page, and each page also embeds its reply thread (~25–30 more posts). Aggregating and de-duplicating those turns ~25 into several hundred. Realistic max per run = (number of seeds) × (per-seed yield) — e.g. 10 profiles → roughly 3,000–6,000 posts. Every post is deduped by id across the run.

The hard cap that remains: the profile timeline itself is capped at ~25 posts for logged-out access — Meta does not paginate a profile or search deeper without a login, and this Actor uses no login (zero ban risk). You cannot get a profile's full historical post list; what you can do is multiply rows via reply threads and scale breadth across many seeds.

💡 Use cases

• Content & competitor analysis — see which Threads posts and formats win in your niche.
• Brand & creator monitoring — archive an account's output with engagement over time.
• Social listening — track keywords and #tags across public Threads conversations.
• Data science & ML — build labelled post datasets for NLP, sentiment and trend analysis.

👥 Who uses it

Social-media marketers & agencies · brand and competitor analysts · social-listening and PR teams · creators and community managers · data scientists building social datasets · researchers studying online discourse.

💰 Pricing

This Actor runs on a simple pay-per-result model — you pay for the posts you extract, with no separate Apify platform fees to calculate. Try it on the free tier first, then scale up. See the Pricing tab on this page for the current rate.

❓ Frequently Asked Questions

Is this a Threads API alternative? Yes. It scrapes public Threads posts without any official Threads / Meta API, developer account or app keys — just give it usernames, post URLs or keywords and run. There is no public Threads data API, so this is the practical way to export post data.

Does it need a Threads or Instagram login? No. It reads public pages only — no login, no cookies you provide, no account. There's no account involved at all, so there's zero ban risk.

Can it scrape a Threads profile without an API key? Yes. Point it at any @handle to scrape a public Threads profile's recent posts and engagement — no API key, no developer account and no login required.

How many posts can I get per profile? The profile timeline is capped at ~25 posts for logged-out access, but with reply expansion (on by default) the Actor also pulls each post's reply thread, so a single profile usually yields 300–700 posts. Run many profiles/tags in one go to reach several thousand.

How do I scrape all posts from a Threads profile without logging in? Add the @handle to usernames and keep reply expansion on — the Actor walks the profile timeline and expands each post's reply thread, turning about 25 posts into several hundred.

Can it scrape replies to a Threads post? Yes — pass the post URL and it returns the post plus its visible reply thread (~30 posts). This is also what powers the profile volume multiplier.

How do I search Threads posts by hashtag or keyword? Put keywords or #tags in searchTerms and the Actor pulls matching public posts with full engagement — likes, replies, reposts and quotes — no account needed.

Which domains work — threads.com or threads.net? Both. threads.com and threads.net handles and URLs are accepted interchangeably.

How do I export Threads data to CSV or JSON? Run the Actor, then download the dataset from the run's Storage tab or pull it via the Apify API. Threads posts export to CSV, JSON, Excel or HTML.

🔗 More social-media scrapers by logiover

Building a cross-platform social dataset? Pair Threads with these:

Actor	What it does
Instagram Media Downloader	Download Instagram photos & videos
TikTok Hashtag Video Scraper	Videos & metrics by hashtag
Reddit Search Scraper	Posts & comments by keyword
Reddit Subreddit Scraper	Full subreddit feeds
YouTube Search Scraper	Videos & channels by keyword
Bluesky-style discovery via Hacker News Search	Tech discussion by keyword
Substack Newsletter Scraper	Newsletter posts & authors
LinkedIn Top Content Scraper	Top posts by keyword/creator

👉 Browse all logiover scrapers on Apify Store — 180+ actors across real estate, jobs, crypto, social media & B2B data.

⏰ Scheduling & integration

Schedule this Actor on Apify to track handles, tags and conversations daily or weekly. Export results to JSON, CSV or Excel, sync to Google Sheets, or push to your database, BI tools and webhooks through the Apify API. Connect it to Make, n8n or Zapier to build automated social-listening pipelines.

⭐ Support & feedback

Found a bug or need an extra field? Open an issue on the Issues tab — response is usually fast. If this Actor saves you time, a ★★★★★ review on the Store page genuinely helps and is hugely appreciated. 🙏

⚖️ Legal

This Actor collects only publicly available Threads data and accesses no private or login-gated content. You are responsible for using the data in line with Threads' / Meta's Terms, applicable laws (including GDPR/CCPA) and privacy regulations. Do not use scraped personal data for spam or unlawful purposes.

---

This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by Threads; Threads and all other trademarks mentioned here are the property of their respective owners.

How much Threads data can you extract in one run?

A single run returned 25 posts in 17 seconds on the example input. That example is deliberately narrow; the result limit and the input list are both yours to widen. That is roughly 88 posts a minute.

There is no hard ceiling built into this Actor. What bounds a run is the result limit you set, the breadth of the input you give it, and how much Threads itself publishes. Because billing is per result, a wider run costs proportionally more and a narrow one costs almost nothing — so it is worth starting small and scaling once the output looks right.

Threads scraping — frequently asked questions

Do I need a Threads API key, account or login?

No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.

How do I export Threads data to CSV, Excel, JSON or Google Sheets?

Open the Storage tab after a run and pick the format you want — CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.

Can I schedule this Threads scraper to run daily or hourly?

Yes. Use the Schedules tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the posts you care about really do change that fast.

How many posts can I get, and what does it cost?

See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.

Is scraping Threads legal?

This Actor collects only information that Threads publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.

What happens if Threads blocks the run or changes its layout?

A refused exit IP is swapped for a fresh one within a quarter of a second and retried, and rate limiting is waited out rather than fought. If nothing gets through, the run fails with the reason instead of reporting success with zero rows — so an empty result always means "no matches", never "the source would not answer".

Can I use this with an AI agent, LangChain or an MCP client?

Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.

📝 Changelog

2026-11-01

• Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
• README refreshed: 2 links to renamed Actors updated, 2 links to retired Actors removed; independence disclaimer added.

2026-10-15

• Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
• A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
• A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
• Runs with a short timeout (API and AI-agent calls) now finish inside it with what they collected, instead of being cut off.
• Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.

2026-09-23

• Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
• Output verified on a live run: 18 columns returned, 77.6% of cells populated.
• Run reliability reviewed: 99.5% of public runs succeeded in the last 30 days.
• Input schema, output schema and pricing configuration reviewed.
• Noted that 2 column(s) came back empty in this sample (lang, hashtags); these are under review.

2026-09-01

• Fleet-wide health check. Verified against this Actor's real run history: 30-day success rate, output row counts, per-field fill rates, and peak memory against the configured memory limit.
• Reviewed for the failure patterns that have cost this fleet runs — unguarded proxy setup, retry loops that can outlast the run's own time budget, and full-page HTML parsing that can exhaust a small container.
• No change to input, output fields or scraping logic.

2026-08-12

• Runs are now roughly 250x cheaper. Measured on identical input: $0.6011 → $0.0024.
• Switched the default proxy from the RESIDENTIAL group to datacenter. Threads does not block datacenter IPs — verified side by side, both tiers return the same posts and datacenter is faster. A proxy is still required; direct requests get an interstitial. Residential remains available and is used automatically if datacenter ever fails to return a usable page.
• Profile pages are now read over plain HTTP first. The browser pass is kept only as a fallback for when HTTP returns nothing, so most runs no longer launch Chromium at all — faster, lighter, and without the intermittent proxy tunnel failures.
• Restored profile scroll depth and patience that had been cut to save bandwidth.
• More retries before changing proxy tier, so a single transient failure no longer pulls an entire run onto the expensive path.

2026-08-11

• Maintenance release: refreshed the build and dependencies.
• Re-verified live execution, non-empty structured output and dataset field/type integrity.
• Reviewed reliability (retries, pagination) and output quality as part of a full-fleet QA pass.

2026-08-01

• Completed the August 2026 full health check: verified empty/programmatic default, Console UI default, and two source-informed alternative inputs on Apify.
• Confirmed successful live execution, non-empty structured output, dataset-field/type integrity, and logical sample quality within the 5-minute quality window.
• Declared 18 dataset fields from typed live cloud samples so the output contract is no longer an empty placeholder.
• Declared 18 nullable dataset fields from typed live cloud samples so the output contract is no longer an empty placeholder or brittle to sparse modes.

2026-07-06

• ✨ README overhaul: standardized structure, richer output sample, three ready-to-run example scenarios, expanded social-media cross-links, and clearer quick-start.

2026-07-01

• Maintenance pass: re-verified end-to-end on live data and confirmed successful runs within the 5-minute quality window on the default input.
• Sharpened Store metadata (SEO title & description) and expanded the FAQ with high-intent, long-tail questions for easier discovery in Google and Apify Store search.
• Added ready-to-run example tasks that cover common real-world use cases.

2026-06-15

• Reliability pass: re-verified end-to-end on live data with real-world inputs. Routine maintenance build.

2026-06-07

• Docs: added coverage for using the Actor as an unofficial Threads API alternative, exporting Threads data to CSV/JSON, and scraping a Threads profile without an API key.

2026-06-05

• 🛡️ Reliability fix: results are no longer dropped by strict output validation — runs now complete cleanly even at high volume (thousands of results).
• ⚡ Stability & performance hardening; fresh rebuild.

---

*Maintained: last verified 2026-11-01 — checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).