Premium
Services
Premium

Best Twitter (X) Scrapers: Benchmarked

Nazlı Şipi
Nazlı Şipi
updated on Nov 16, 2026

Four web scraping APIs each received the same 1,000 X URLs, 500 profiles and 500 posts, for 4,000 requests in total. We recorded the success rate, completion time and number of parsed metadata fields of every response.

Twitter (X) scrapers benchmark

Page type
*Success rate vs. average completion time of successful requests, 500 pages per page type. The time axis uses a log scale, faster to the right.
NameAverage completion time (s)Success rate (%)Available metadata fieldsPages testedUse case
Bright Data7.5799.9291,000All pages
Decodo17.6299.70 (HTML)1,000All pages
Nimble7.7723.60 (HTML)1,000All pages
Zyte6.4999.50 (HTML)1,000All pages
Bright Data8.1810024500Profiles
Decodo17.7399.80 (HTML)500Profiles
Nimble6.77210 (HTML)500Profiles
Zyte6.5999.80 (HTML)500Profiles
Bright Data6.9699.834500Posts
Decodo17.5199.60 (HTML)500Posts
Nimble8.5626.20 (HTML)500Posts
Zyte6.3899.20 (HTML)500Posts

See our benchmark methodology for more details.

✅ structured JSON, ✓ HTML only, ✕ not supported.

X scrapers pricing

NameMonthly Pages$ Per 1k Pages (Lower = Cheaper)Monthly Pages$ Per 1k Pages
Bright Data10001.51k$1.50
Bright Data100001.510k$1.50
Bright Data1000001.5100k$1.50
Bright Data10000001.31M$1.30
Decodo1000191k$19.00
Decodo100001.910k$1.90
Decodo1000002.49100k$2.49
Decodo100000011M$1.00
Nimble100011k$1.00
Nimble10000110k$1.00
Nimble1000001100k$1.00
Nimble100000011M$1.00
Zyte10001.671k$1.67
Zyte100001.6710k$1.67
Zyte1000001.25100k$1.25
Zyte10000000.81M$0.80
Get our team to automate one of your business processes with AI agents, free of charge.
Automate a process

What data can be scraped from Twitter

When scraping X, you get the page either as rendered HTML, which you parse with CSS selectors, or as structured JSON from a dedicated X scraper. In our benchmark only Bright Data returned JSON. Decodo, Nimble and Zyte returned HTML, and we read the profile and post data from it with CSS selectors.

Bright Data’s X scrapers returned the fields below:

X profiles:

X posts:

The best Twitter scraping tools

Bright Data’s Twitter Scraper API returns X profiles and posts as structured JSON, so no HTML parsing is needed. In our benchmark it returned 24 fields per profile and 34 per post, including view, bookmark and quote counts, embedded media, parent and quoted post details and the verification type.

Bright Data offers four X scrapers:

  • Posts, collect by URL: extracts a post’s data from its URL
  • Posts, discover by profile URL: collects all post URLs and their data from a profile
  • Profiles, collect by URL: extracts profile details from a profile URL
  • Profiles, discover by user name: collects profiles by user name 

Bright Data also offers two ready-made X datasets, posts and profiles, with more than 152 million records in total and a $250 minimum order.

We used the profiles and posts scrapers, each collecting by URL. Bright Data succeeded on every profile and on 99.8% of posts; the one failed post had a like count that failed the value check. Profiles took 8.2 seconds and posts 7.0 seconds on average.

Decodo succeeded on 99.8% of X profiles and 99.6% of posts, with only three failed requests, and averaged 17.6 seconds per request. Our Decodo setup used the Web Scraping API’s generic endpoint, with headless rendering on and requests routed through the premium proxy pool. The response contains no parsed fields, so you write your own CSS selectors for the profile and post data.

Decodo has moved this Scraper API into its Web Data API, which groups /scrape with /search, /crawl and /map under a single key.

Zyte was the fastest provider on X at 6.5 seconds per request: 6.6 seconds for profiles and 6.4 for posts. It succeeded on 99.8% of profiles and 99.2% of posts. Zyte API returns the fully rendered page through browserHtml in a single call, so profile and post data have to be extracted with CSS selectors.

We ran Nimble’s Extract API with browser rendering and HTML output. Nimble succeeded on 21.0% of profiles and 26.2% of posts. In most failed responses the HTML held X’s page shell and scripts but no rendered profile or post, so the required fields were missing. Successful requests averaged 7.8 seconds.

Don’t miss our benchmarks and data-driven insights. The button opens Google; selecting AIMultiple confirms that you wish to see AIMultiple more often in Google search results.
GoogleAdd as preferred source

Twitter scraper benchmark methodology

The X results are drawn from our social media scraping benchmark, which measured web scraping providers on 6,500 pages across Instagram, Facebook, TikTok, X and LinkedIn. Four of those providers each received the same 1,000 X URLs: 500 profiles and 500 posts. Apify and SerpApi were not tested on X.

The social media scraping benchmark describes how we selected the URLs, which endpoint we used for each provider and which checks decide a successful response.

Cite this benchmark

Pick the format that matches where you're publishing. Pasting the link version into your CMS preserves the backlink.

Nazlı Şipi (2026) - "Best Twitter (X) Scrapers: Benchmarked". Published online at AIMultiple.com. Retrieved November 16, 2026, from: https://aimultiple.com/twitter-scraper [Online Resource]

Şipi, N. (2026, November 16). Best Twitter (X) Scrapers: Benchmarked. AIMultiple. https://aimultiple.com/twitter-scraper

@misc{sipi2026,
  author = {Şipi, Nazlı},
  title  = {{Best Twitter (X) Scrapers: Benchmarked}},
  year   = {2026},
  month  = nov,
  howpublished    = {\url{https://aimultiple.com/twitter-scraper}},
  note   = {AIMultiple. Retrieved November 16, 2026}
}
Download all data

Results and timestamps of 5.0 thousand data points. Download the summary data shown in this article's charts and tables as a ZIP file containing 7 CSV files and a README.

Last updated: November 16, 2026
Download

Want the granular data behind it? Join Premium

Changelog

21 updates
  1. Replaced the benchmarked scraper lineup, dropping Apify, NetNut, PhantomBuster and Octoparse for Decodo, Oxylabs and Zyte.

  2. Added a search market share breakdown section for Twitter scrapers and a price comparison section.

  3. Added an X API pay-per-use pricing subsection to the developer guide section.

  4. Removed the "How to scrape Twitter data" section.

Nazlı Şipi
Nazlı Şipi
AI Researcher
Nazlı is a data analyst at AIMultiple. She has prior experience in data analysis across various industries, where she worked on transforming complex datasets into actionable insights.
View Full Profile

Be the first to comment

Your email address will not be published. All fields are required. Comments are left in their original language.

0/450