Pricing

Rating

Developer

Actor stats

Categories

Share

👁 ParseForge Banner

🧵 Threads Profile Scraper

🚀 Pull public Threads posts from any profile. Text, post URL, posted date, author handle. Camoufox + residential proxy bypasses Meta anti-bot. No login.

🕒 Last updated: 2026-05-01 · 📊 7 fields per post · 🧵 200M+ monthly users · 📱 Meta-owned platform · 🦊 Camoufox bypass

The Threads Profile Scraper visits public Threads profiles using a Camoufox browser with residential proxy rotation and returns each post's text, post URL, post code, posted timestamp, profile URL, and author handle. Aggressive scrolling captures up to 25 posts per profile and the Actor walks multiple usernames in sequence to reach 100+ posts per run.

Threads has crossed 200 million monthly active users since launch and is Meta's competitor to X. It is increasingly the public posting surface for tech founders, journalists, and creators. Anonymous HTTP scraping returns only the SPA shell because Meta's anti-bot fingerprints the TLS handshake. This Actor uses Camoufox to mimic a real browser and serves the SSR-rendered profile feed.

📋 What the Threads Profile Scraper does

Three filtering workflows in a single run:

• 👤 Multi-profile fanout. Submit an array of usernames and the Actor visits each profile.
• 📜 Aggressive scroll. Up to 15 scroll rounds per profile loads more posts beyond the first viewport.
• 🛡️ Anti-bot bypass. Camoufox headless: virtual plus residential proxy serves the real SSR feed.

Each row reports the username, post short code (extracted from the post URL), full post URL, post text up to 1500 characters, posted timestamp from the <time> element, profile URL, and a scrape timestamp.

💡 Why it matters: Threads is now where many tech and media voices post first. Brand teams need to track mentions there, journalists watch it for breaking takes, and marketers measure influencer reach. The HTTP layer alone returns nothing useful, but a properly-fingerprinted browser session can read the public feed.

🎬 Full Demo

🚧 Coming soon: a 3-minute walkthrough showing how to go from sign-up to a downloaded dataset.

⚙️ Input

Example: 100 posts across 14 popular usernames.

{
"maxItems":100,
"usernames":[
"zuck","mosseri","openai","mkbhd","apify",
"instagram","threads","nytimes","cnn","theverge",
"techcrunch","wired","garyvee","sahilbloom"
]
}

Example: track a single brand handle.

{
"maxItems":25,
"usernames":["apify"]
}

⚠️ Good to Know: Threads enforces strong anti-bot, so this Actor uses Camoufox with headless: virtual and Apify residential proxy. Cold-start is around 4-6 seconds, then each profile takes 6-10 seconds depending on scroll depth.

📊 Output

Each post record contains 7 fields. Download as CSV, Excel, JSON, or XML.

🧾 Schema

📦 Sample records

✨ Why choose this Actor

📊 In a single 80-second run the Actor returned 71 posts across 14 popular Threads profiles.

📈 How it compares to alternatives

Same SSR feed Meta serves to any logged-out browser, accessible via Camoufox session.

🚀 How to use

1. 🆓 Create a free Apify account. Sign up here and get $5 in free credit.
2. 🔍 Open the Actor. Search for "Threads Profile" in the Apify Store.
3. ⚙️ Add usernames. One or many Threads handles without the @.
4. ▶️ Click Start. A 100-post run typically completes in 80 to 120 seconds.
5. 📥 Download. Export as CSV, Excel, JSON, or XML.

⏱️ Total time from sign-up to first dataset: under five minutes.

💼 Business use cases

🌟 Beyond business use cases

Data like this powers more than commercial workflows. The same structured records support research, education, civic projects, and personal initiatives.

🔌 Automating Threads Profile Scraper

Run this Actor on a schedule, from your codebase, or inside another tool:

• Node.js SDK: see Apify JavaScript client for programmatic runs.
• Python SDK: see Apify Python client for the same flow in Python.
• HTTP API: see Apify API docs for raw REST integration.

Schedule daily runs from the Apify Console to track new posts on a list of handles. Pipe results into Slack, Google Sheets, S3, BigQuery, or your own webhook with the built-in integrations.

🤖 Ask an AI assistant about this scraper

Open a ready-to-send prompt about this ParseForge actor in the AI of your choice:

• 💬 ChatGPT
• 🧠 Claude
• 🔍 Perplexity
• 🅒 Copilot

❓ Frequently Asked Questions

👤 What usernames are supported?

Any public Threads handle without the @ prefix. Private accounts return zero rows because the public profile feed is empty for them.

📜 How many posts per profile?

Threads typically loads 5-25 posts per profile in a single browser session, depending on profile activity. The Actor scrolls aggressively to reach the upper end.

🛡️ Why does this need Camoufox?

Meta fingerprints TLS handshakes, browser-API surfaces, and HTTP/2 frame ordering. Camoufox is built specifically to defeat that detection. Standard fetch or Playwright Chromium gets blocked.

🔢 What does the postCode field contain?

The 11-character base64-style ID Meta uses internally for each post. Stable, unique, and works as a primary key across runs.

📅 Can I get likes, replies, and reposts?

The post text often ends with engagement counters like 1.2K\n256\n102\n36 (likes, replies, reposts, quotes). v1 leaves them embedded in the text; structured parsing is on the roadmap.

🔍 Can I search by hashtag or keyword?

Currently profile-scoped only. Hashtag and keyword search require a different Threads URL pattern and are out of scope for v1.

📦 How many posts can I pull?

Free plan caps at 10. Paid plans up to 1,000,000. Per-run the multi-profile fanout reaches 70-100 posts depending on profile activity.

🛡️ Will this break when Meta updates their site?

Possibly. Camoufox keeps up with browser fingerprints, but Meta occasionally changes the post DOM selectors. The Actor monitors for selector drift and gets updated when needed.

💼 Can I use this for commercial work?

Yes for permissible purposes. The Actor reads only what Threads serves to any logged-out browser. Always honor Meta's terms when republishing post text.

💳 Do I need a paid Apify plan?

The free plan returns up to 10 posts per run. Paid plans return up to 1,000,000.

⚠️ What if a profile returns zero posts?

Most often it's a private account or a banned handle. Verify by visiting the profile in a logged-out browser. Open a contact form and include the run URL if a public account returns empty.

⚖️ Is this legal?

The Actor reads only data Meta publicly serves to every browser visitor. Posting public content is the explicit purpose of the platform. Always verify your specific use case complies with Meta's terms and your local law.

🔌 Integrate with any app

• Make - drop run results into 1,800+ apps.
• Zapier - trigger automations off completed runs.
• Slack - post run summaries to a channel.
• Google Sheets - sync each run into a spreadsheet.
• Webhooks - notify your own services on run finish.
• Airbyte - load runs into Snowflake, BigQuery, or Postgres.

🔗 Recommended Actors

• 🔍 Skip Trace People Search - lookup people behind handles you find.
• 🅱️ Bing Search Scraper - run web searches on viral Threads posts.
• 🦆 DuckDuckGo Search Scraper - alternative SERP signal alongside Threads activity.
• 📚 Wikipedia Pageviews Scraper - cross-reference Threads spikes with public-interest data.
• 🐙 GitHub Trending Repos Scraper - capture the developer-attention layer next to Threads activity.

💡 Pro Tip: browse the complete ParseForge collection for more pre-built scrapers and data tools.

🆘 Need Help? Open our contact form and we'll route the question to the right person.

Threads is a registered trademark of Meta Platforms, Inc. This Actor is not affiliated with or endorsed by Meta. It reads only the public profile feed every logged-out browser can access.