Threads Scraper: Posts, Replies, Profiles & Search

Threads scraper for Meta Threads, no login: type a keyword, a username or a post link and get posts, replies, profiles and view counts as a table.

Type	User	Post / bio	Likes	Replies	Followers	Posted
profile	mosseri	Father of three boys, married to an amazing woman,…	–	–	1,046,035	–
post	mosseri	Three DM settings worth knowing about. Let me know…	226	57	–	2026-10-02
post	zayacoffee.co	Meet ZAYA. Three coffees. Three distinct flavor pr…	0	0	–	2026-10-03

What you can scrape

Input	You get
🔍 Search terms (coffee, #booktok, a Threads search or tag URL)	Posts that mention the term, Top or Recent: often a few hundred per term (see Search depth). Or, with Search for: Accounts, up to 100 accounts per term with followers, bio and links
👤 Usernames (mosseri, @mosseri, a profile URL)	The profile, the account's posts (paged to the end), its replies to others (each with the post it answers) and its reposts
🔗 Post URLs (threads.com/@user/post/..., threads.com/t/...)	Its replies and the replies to those (3 levels), Top or Recent, each with its view count; then the post itself with its views and how many replies were collected

Mix them in one run. A post or profile that several inputs find is in your dataset, and charged, once. Plain HTTPS on Apify datacenter IPs, no browser: first rows in seconds, and a run needs only 256 MB.

Use it to track a brand or topic on Threads, collect posts for research or AI training, find creators and their contacts for outreach, or monitor an account's posts and replies on a schedule.

Search depth

Threads shows logged-out visitors one page (13-20 posts) per search. This Actor reads the term through every page Threads offers (its default and top lists, the hashtag, the singular or plural form, and up to 8 related topic tags). When those run out before your Max results per input, Search deeper (on by default) reads the newest posts of the authors it found and of the accounts Threads' account search ranks for the term, and keeps only posts whose own text, topic or hashtags contain your words. Each row says where it came from (searchSource: default, tag:coffeelover, author:runcoachmike, account:unwind_ai, ...).

Search term	Threads' search and tag pages	With Search deeper
coffee	155	363
skincare	124	506
real estate	99	391
marathon training	40	160-204
ai agents	28	136-149

Turn off Only posts that mention the search term to also keep the loosely related posts Threads' search shows, or Search deeper to get Threads' search pages only. Account searches return up to 100 accounts per term. A profile's posts and replies, and a post's replies, page to the end; reposts: Threads shows the latest 25.

Output

The Output tab has three tables:

• 📊 All results: every post and profile, with Overview and Stats views.
• 🧵 Posts and replies: posts only, with Posts, Media, Replies and Views and authors views.
• 👤 Profiles: profiles only, with Profiles and Contacts (accounts search) views.

The run summary (OUTPUT) lists every input with its status, result count and why it stopped. Every field has a label and a description in the dataset schema; the full list:

Posts and replies (one flat row each):

• who: profilePicUrl, username, fullName, isVerified
• what: text (the whole post; long posts include their full body, also in attachmentText), textSnippet, url
• engagement: likeCount, replyCount, repostCount, quoteCount, shareCount (Threads hides many zero counts; those come back empty) and viewCount (see below); createdAt
• media: mediaType (Text, Image, Video, Carousel, Link, GIF), thumbnailUrl, mediaUrl, images, videos, carouselCount, mediaWidth, mediaHeight, hasAudio, isGif, isSpoiler, accessibilityCaption
• topicTag, hashtags, mentions, links (real URLs, not Threads' redirect links), emails, link preview (linkPreviewUrl, linkPreviewTitle, linkPreviewDescription, linkPreviewImageUrl, linkPreviewDisplayUrl)
• replies: isReply, replyToUsername, rootPostUsername, selfThreadCount, parentPostId, parentPostUrl, parentPostText, parentPostUsername, parentPostLikeCount, parentPostReplyCount, parentPostCreatedAt, rootPostId, replyDepth (1 = a direct reply, 2 = a reply to a reply, ...)
• quotes: isQuotePost, quotedPostUrl, quotedPostText, quotedPostUsername, quotedPostCreatedAt, quotedPostUnavailable (the quoted post was deleted or hidden)
• reposts: isRepost, repostedByUsername, repostedAt, repostedFromUsername, repostedPostUrl (a repost row is the original post, with who reposted it)
• isPinned, isEdited, isPaidPartnership, isLikedByAuthor, isAiGenerated, replyControl, poll (pollOptions, pollVoteCounts, pollTotalVotes), musicTitle, musicArtist, podcastEpisode, podcastUrl, locationName, taggedUsers, language
• author (on by default, one lookup per author per run): authorFollowerCount, authorBio, authorProfilePicHdUrl, authorProfileTags, authorInstagramFollowerCount, authorBioLinks
• also: imageCount, gifUrl, gifDescription, canReply, areCountsHidden, transparencyLabel
• ids: postId, code, timestamp, userId, isPrivateAuthor, mentionedUserIds, topicTagId, replyToUserId, quotedPostId, quotedPostCode, repostedByUserId, locationId
• where it came from: inputType, input, searchQuery, searchSource, keywordMatch, sourceTab; scrapedAt last

Profiles: profilePicUrl, username, fullName, bio, bioSnippet, url, followerCount, instagramFollowerCount, instagramFollowingCount (the linked Instagram account), isVerified, isPrivate, profileTags (the topics the account shows), bioLinks, emails and phones found in the bio and links, profilePicHdUrl, hasThreadsBadge, isThreadsOnlyUser (no linked Instagram), transparencyLabel, latestPosts (its 10 newest posts: text, likes, replies, date, link), userId, inputType, input, searchQuery, scrapedAt.

Times are UTC, like 2026-10-03T14:05:09Z. Picture and media links are signed by Threads and stop working after a few days: download what you need to keep.

View counts

Threads sends a post's view count with the post's own page. 👁️ View counts on every post is on by default (🧾 Output section): the Actor reads those pages in parallel and each row goes out as soon as it's ready, so the first row isn't held back. Post URLs always get theirs, and so do their replies (View counts on replies too, on by default). 👤 Author details on every post (on) adds the author's followers, bio, HD photo, topics, Instagram followers and bio links, looked up once per author. Turn either off for faster big runs; the price stays the same.

Recent search sends each search page as it arrives, newest first (the first one at once), so the order is newest first within each batch. Recent, strict waits for every page and sorts all of them, so its first row comes later.

Speed and reliability

Apify runs of this Actor, 2026-10-03, default 256 MB, all SUCCEEDED with results = charged results:

Run	Results	First result	Whole run	Peak memory
Prefilled run (search "coffee" + @mosseri, 40 each)	81	10 s after Start	24 s	73 MB
One profile's posts (@cnn, 1,000)	1,001	4 s	64 s	64 MB
One post's replies and replies to replies (500)	501	6 s	44 s	78 MB
10 search terms, 15 posts each	150	7 s	52 s	111 MB

Bigger runs, same code through Apify datacenter IPs: 2,000 posts of @cnn in 128 s, 1,000 replies in 96 s, 10 search terms × 100 posts in 161 s. Inputs are read one after another, so a run's time grows with the number of inputs.

A refused request is retried on a new IP. If Threads answers with a page that looks empty but isn't a real answer, the run checks a known-good search or profile: if that comes back empty too, the input is reported as refused (and nothing is charged) instead of "no results". If every input fails, the run fails with a clear message. A run that Apify restarts never charges a result twice.

Dates

Posted after and Posted before take a date (2026-09-01) or a period (7 days). Posts outside the window are skipped and not charged. Threads' own date filters need a login, so the window applies to what the inputs return.

Pricing

Pay per result: $2.29 per 1,000 on Free, $1.99 per 1,000 on Starter, Scale and Business. No start fee. Only results in your dataset are charged; filtered posts and repeats are free. Set a maximum cost per run in the run options and the run stops exactly there.

FAQ

Do I need a Threads or Instagram account? No. Everything comes from what Threads shows logged-out visitors.

Is there a Threads API? Meta's official Threads API only reads your own account. This Actor works like a Threads API for public data: call it from the Apify API, a schedule or an integration and get JSON, CSV or Excel.

Private accounts? You get their public profile only; the run summary says so.

Followers or following lists? Threads shows those only to logged-in users, so this Actor doesn't offer them. You get the follower count, plus the linked Instagram's follower and following counts.

Which proxy? Keep the default. Residential is used only as a fallback when Threads refuses datacenter IPs, at no extra cost to you.

Related Actors

• Threads Search Scraper: posts or accounts by keyword or hashtag.
• Threads Profile Scraper: followers, bio, links and the linked Instagram's counts.
• Threads Posts Scraper: every post of an account, or posts by URL with views.
• Threads Replies Scraper: every reply under a post, 3 levels deep.

Feedback

Missing a field or an input type? Open an issue on the Actor's page; we answer quickly. If the data helped you, a short review on the Store page helps others find it, and helps us a lot.