[Blog](https://scrapfly.io/blog) / [python](https://scrapfly.io/blog/tag/python) / [4 X (Twitter) Scrapers on GitHub That Still Work in 2026](https://scrapfly.io/blog/posts/best-twitter-scrapers-github) # 4 X (Twitter) Scrapers on GitHub That Still Work in 2026 by [Mohab Yousry](https://scrapfly.io/blog/author/mohab-yousry-9396552a) Sep 17, 2026 18 min read [\#python](https://scrapfly.io/blog/tag/python) [\#scrapeguide](https://scrapfly.io/blog/tag/scrapeguide) [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fbest-twitter-scrapers-github "Share on LinkedIn") [ ](https://x.com/intent/tweet?url=https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fbest-twitter-scrapers-github&text=4%20X%20%28Twitter%29%20Scrapers%20on%20GitHub%20That%20Still%20Work%20in%202026 "Share on X") [ ](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fbest-twitter-scrapers-github "Share on Facebook") Summarize this article with [ ](https://chat.openai.com/?q=Summarize%20this%20article%20and%20explain%20how%20Scrapfly%20helps%20me%20scrape%20any%20website%20at%20scale%20and%20bypass%20anti-bot%20systems%20for%20my%20use%20case%3A%20https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fbest-twitter-scrapers-github) [ ](https://claude.ai/new?q=Summarize%20this%20article%20and%20explain%20how%20Scrapfly%20helps%20me%20scrape%20any%20website%20at%20scale%20and%20bypass%20anti-bot%20systems%20for%20my%20use%20case%3A%20https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fbest-twitter-scrapers-github) [ ](https://x.com/i/grok?text=Summarize%20this%20article%20and%20explain%20how%20Scrapfly%20helps%20me%20scrape%20any%20website%20at%20scale%20and%20bypass%20anti-bot%20systems%20for%20my%20use%20case%3A%20https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fbest-twitter-scrapers-github) [ ](https://www.perplexity.ai/search/new?q=Summarize%20this%20article%20and%20explain%20how%20Scrapfly%20helps%20me%20scrape%20any%20website%20at%20scale%20and%20bypass%20anti-bot%20systems%20for%20my%20use%20case%3A%20https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fbest-twitter-scrapers-github) [ ](https://www.google.com/search?udm=50&aep=11&q=Summarize%20this%20article%20and%20explain%20how%20Scrapfly%20helps%20me%20scrape%20any%20website%20at%20scale%20and%20bypass%20anti-bot%20systems%20for%20my%20use%20case%3A%20https%3A%2F%2Fscrapfly.io%2Fblog%2Fposts%2Fbest-twitter-scrapers-github) X's open-source scraping ecosystem has been hollowed out in two ways. Technical changes shut down anonymous guest access and repeatedly broke the private endpoints older tools depended on. Legal pressure then reached Nitter: its README says X Corp sent cease-and-desist letters on Aug 24, 2026, and GitHub marked the repository archived on Sep 11. The survivors are not interchangeable. twscrape and Scweet need X account sessions for their useful search and follower features. the-convocation can read limited public data as a guest. Scrapfly's example sends public post and profile pages through a managed fetch API, but the user still owns the parsing code and any X accounts needed for login-gated data. This guide compares four repositories that remain useful for specific jobs. The ranking uses current repository state, coverage, account burden, and the infrastructure each approach leaves to you. ## Key Takeaways - **X scraping projects disappear in two ways:** platform changes break their technical dependencies, while direct legal pressure can end maintenance. Nitter experienced both and is now archived. - **twscrape remains the breadth pick:** it covers search, profiles, followers, and GraphQL reads if you operate an X account pool. - **Scrapfly is the managed-fetch pick for public pages:** the Web Scraping API handles retrieval, proxy routing, and anti-bot infrastructure for public posts and profiles. - **Managed fetching does not supply X accounts or maintain your parser:** login-gated data still needs your account sessions, and the repository's extraction code remains yours to maintain. - **Stars are not a health check:** Twint and snscrape still attract attention despite being archived or broken since 2023. - **The official API is a paid alternative:** Post reads cost $0.005 and pay-per-use plans are capped at 3 million post reads per monthly billing cycle. **Get web scraping tips in your inbox**Trusted by 100K+ developers and 30K+ enterprises. Unsubscribe anytime. ## Which Open-Source X (Twitter) Scraper on GitHub Should You Use? Use twscrape when breadth matters and you can operate X accounts. Use Scrapfly's example when you need managed retrieval for public posts and profiles and are comfortable maintaining the parser. Use Scweet for resumable account-based exports. Use the-convocation for a TypeScript stack and limited guest reads. Quick picks by job: - Search and GraphQL breadth with your own accounts: **twscrape** - Managed retrieval for public post and profile pages: **Scrapfly twitter-scraper** - Resumable long scrapes with CSV or JSON output: **Scweet** - TypeScript or Node.js stack: **the-convocation/twitter-scraper** | Tool | Repo | Language | Stars (Sep 17, 2026) | Latest commit | License | Access model | Best for | |---|---|---|---|---|---|---|---| | twscrape | [vladkens/twscrape](https://github.com/vladkens/twscrape) | Python | ~2,779 | Aug 28, 2026 | MIT | Your X account pool | Search + GraphQL coverage | | Scrapfly twitter-scraper | [scrapfly/scrapfly-scrapers](https://github.com/scrapfly/scrapfly-scrapers/tree/main/twitter-scraper) | Python | ~1,082 repo-wide | Jul 2, 2026 module | NPOSL-3.0 | Scrapfly API; no X account for public pages | Managed public-page fetches | | Scweet | [Altimis/Scweet](https://github.com/Altimis/Scweet) | Python | ~1,627 | Sep 15, 2026 | MIT | Your cookies or account pool | Resumable CSV/JSON exports | | the-convocation/twitter-scraper | [the-convocation/twitter-scraper](https://github.com/the-convocation/twitter-scraper) | TypeScript | ~639 | Apr 1, 2026 | MIT | Guest reads; your cookies for gated data | TypeScript projects | These are dated repository snapshots, not permanent scores. Check the current branch and issue tracker before adopting one. For the technique itself rather than which repo to clone, check [How to Scrape Twitter (X.com) with Python in 2026Scrape public Twitter (X.com) profiles and tweets with Python in 2026, and learn why guest tokens and doc\_ids break DIY scrapers.](https://scrapfly.io/blog/posts/how-to-scrape-twitter) If you scrape more than one social platform this article compares options across eight platforms in one table: [The Best Open-Source Social Media Scrapers for 2026Ranked guide to the best open-source social media scraping tools in 2026. Eight maintained scrapers for Instagram, X, LinkedIn, TikTok, YouTube, Reddit, Threads, and Facebook, backed by one anti-bot reliability engine.](https://scrapfly.io/blog/posts/best-social-media-scraping-tools) The ranking below favors current capability and operational fit over historical popularity. ## How Did We Rank These Twitter Scraper Repos? The ranking uses five checks: current default-branch activity, capability coverage, X account requirements, ongoing maintenance burden, and license. No shared performance benchmark ran across all four, so this is not a speed or success-rate leaderboard. The order follows the job each repository can honestly own: 1. **twscrape** has the widest current read coverage, but you operate the account pool. 2. **Scrapfly twitter-scraper** has narrower public-page coverage, but moves fetching, proxies, and anti-bot handling to a managed service. 3. **Scweet** is current and resumable, but search and scale still depend on cookies and account pools. 4. **the-convocation/twitter-scraper** is the TypeScript option, with limited guest reads and slower recovery after X changes. "Open-source" here means a repository with source and a license you can inspect. A required API key is not disqualifying when the repository contains runnable parsing code, but it changes the operating model and is shown in the table. `mahrtayyab/tweety` is actively maintained (last committed Sep 13, 2026) but ships no LICENSE file, so it is not open source in the legal sense. `d60/twikit` is the most-starred living repository in this lane (roughly 4,679 stars, MIT), but its last commit was Mar 10, 2026. It logs in with username and password, its README still marks the separate login helper as under development, and current issues report 429 and login challenges. That maintenance and authentication profile keeps it outside this four-entry list. Stars and repository activity are supporting evidence, not proof of current output. This comparison does not treat old committed result files as a live test. ## 1. twscrape: Best for Search and GraphQL Coverage with an Account Pool twscrape is the most capable open-source X (Twitter) scraper on GitHub in 2026 if you can supply authorized accounts. It covers search plus nearly every GraphQL read endpoint, and it manages rate limits by rotating your account pool automatically. It is an async Python library and CLI by vladkens (MIT, roughly 2,779 stars, last committed Aug 28, 2026) with the widest coverage in this lane: search, tweet details, replies, threads, profiles, followers, lists, communities, and trends. A few things stand out: - Sessions persist in a local SQLite database. - The account pool rotates automatically the moment one account hits a rate limit. - An optional curl-based backend adds browser-like TLS fingerprinting. Adding an account means supplying `auth_token` and `ct0` from a logged-in browser session. Testing this with a placeholder cookie pair confirmed real validation rather than silent failure. The CLI accepted the cookie format then rejected the first search with a `Logged-out X web app` error. A real currently logged-in account clears that same check and returns tweets. Limits: - Account acquisition and ban churn are on you, and the project's README says X's Terms of Service discourage using multiple accounts. - The GitHub issue tracker shows active maintenance but also live breakage reports, missing tweets and ordering issues dated within the last month, the kind of churn that comes with tracking a platform that changes weekly. **Best for:** developers who need search or follower data at volume and accept the account-pool overhead that comes with it. bash```bash pip install twscrape twscrape add_cookie burner1 "auth_token=YOUR_AUTH_TOKEN; ct0=YOUR_CT0_TOKEN" twscrape search "web scraping python" --limit 10 ``` The account pool is the whole point of twscrape, and it is also the most expensive part to run. The next entry changes the operating model by moving public-page fetching to a managed API. ## 2. Scrapfly twitter-scraper: Best Managed Fetch for Public Posts and Profiles Scrapfly's open-source twitter-scraper is the managed-fetch option in this list. It sends public X post and profile URLs through the Web Scraping API, then parses the JSON-LD embedded in the returned page. The Python example lives in the `scrapfly-scrapers` monorepo (roughly 1,082 stars repo-wide, with the Twitter module last committed Jul 2, 2026, NPOSL-3.0). The module contains `twitter.py`, a runnable `run.py`, and separate functions for public post and profile pages. What Scrapfly manages: - HTTP retrieval, proxy routing, and anti-bot handling through the Web Scraping API. - Public post and profile fetching without an X account for those two documented page types. - The same managed fetch layer across the maintained Python, TypeScript, Go, and Rust SDKs, although this repository example is Python. What remains your responsibility: - X accounts and cookies for any login-gated workflow. Scrapfly does not provide or maintain X accounts. - Parsing and schema maintenance. The repository is example code, not a hosted Twitter data API with a fixed output contract. - Search, replies, and follower lists, which the documented module does not implement. It needs a Scrapfly API key (`SCRAPFLY_KEY`). Signup includes 1,000 free credits with no card and no expiry, which covers evaluation; sustained scale is paid. **Best for:** teams that want managed retrieval for public X pages while keeping their own parsing code. It is not an account supplier or a complete X data feed. bash```bash git clone https://github.com/scrapfly/scrapfly-scrapers.git cd scrapfly-scrapers/twitter-scraper poetry install export SCRAPFLY_KEY="YOUR_SCRAPFLY_KEY" poetry run python run.py ``` The next entry trades managed fetching for cookie-based search, resume support, and file exports. ## 3. Scweet: Best for Cookie-Based Scraping with Resume and CSV/JSON Output Scweet is the best pick for long, resumable scrapes that land directly in CSV or JSON. It authenticates from a single `auth_token` cookie, pools multiple accounts with per-account proxies when you need scale, and can pick up an interrupted run where it stopped. It is a Python library and CLI by Altimis (MIT, roughly 1,627 stars, last committed Sep 15, 2026) covering tweet search by keyword, hashtag, user, and date range, profile timelines, followers and following, and user profiles. A few things stand out: - Auth is the lowest-friction in this lane. Point it at one `auth_token` and it bootstraps the CSRF `ct0` token itself, or load a `cookies.json` for a multi-account pool. - State lives in SQLite with resume support, and both sync and async APIs are available. - A `manifest_scrape_on_init=True` flag re-scrapes fresh query IDs from X's JavaScript bundle at startup, a direct answer to the internals-rotation problem that trips up other scrapers. Limits, straight from its own README: - Only public content is reachable, cookies expire, and both need periodic refreshing. - A single account typically handles hundreds to a few thousand tweets per day before rate limits bite. Scale means a multi-account `cookies.json` plus proxies. - Username and password login is deliberately unsupported. The maintainer's own reasoning is that automated login triggers account locks faster than cookie-based auth does. **Best for:** researchers and data teams doing bounded, resumable collections that need to land in a file rather than a database. python```python from Scweet import Scweet s = Scweet(auth_token="YOUR_AUTH_TOKEN") tweets = s.search("web scraping", limit=50, save=True, save_format="json") print(f"{len(tweets)} tweets saved") ``` Scweet refreshes query IDs from X's current bundles. The last entry takes a different approach, reverse-engineering x.com's frontend API in TypeScript for teams on a JavaScript stack. ## 4. the-convocation/twitter-scraper: Best for TypeScript and Node.js Projects the-convocation/twitter-scraper is the strongest open-source option for TypeScript and Node.js stacks, a typed port of the archived n0madic Go scraper, with cookie-based auth for anything login-gated and unusually honest documentation about what breaks. It is a TypeScript library (MIT, roughly 639 stars, last committed Apr 1, 2026) that reverse-engineers x.com's own frontend API rather than calling anything official. Perks: - Node.js 16 and up, with bundled types out of the box. - The README states plainly, "No API rate limits. No tokens needed," for the guest-accessible parts of the API. - Cookie export from a logged-in browser session covers everything else that's login-gated. Limits: - Any account you log in with is "subject to being banned at any time." - The frontend's rate limits are dynamic and have paused requests for up to 13 minutes in documented cases. - Endpoint fixes after an X change "typically take at least a few days to go out." Its upstream, n0madic/twitter-scraper in Go, is archived, so this TypeScript port is the living branch of that lineage. An optional CycleTLS entrypoint adds TLS fingerprinting for Node projects that need it. **Best for:** JavaScript and TypeScript teams that want native types and a scraper that works without login for public data, instead of shelling out to a Python process. javascript```javascript import { Scraper } from '@the-convocation/twitter-scraper'; const scraper = new Scraper(); const profile = await scraper.getProfile('x'); console.log(profile.name, profile.followersCount); for await (const tweet of scraper.getTweets('x', 3)) { console.log(tweet.id, tweet.text.slice(0, 80)); } ``` Those are the four standalone repos. If none of them fit the job, the next question is what an account pool actually costs you. Scrapfly #### Scale your web scraping effortlessly Scrapfly handles proxies, browsers, and anti-bot bypass — so you can focus on data. [Try Free →](https://scrapfly.io/register)## Do You Need an Account Pool to Scrape X (Twitter)? You do not need an X account for every public page, but search, replies, followers, and other login-gated surfaces require an authenticated session in the maintained tools covered here. Managed fetching does not remove that product boundary. Three operating models remain: - **Public-page retrieval** covers a limited set of posts and profiles. Scrapfly manages the fetch infrastructure for its documented public-page example; the-convocation exposes limited guest reads. - **Single-account cookies** work for bounded Scweet or the-convocation jobs, but the user supplies the X account and refreshes its session. - **Account pools with proxies** expand twscrape and Scweet coverage, but account acquisition, cookie health, proxy assignment, and ban churn remain the operator's responsibility. Scrapfly does not sell or maintain X accounts. It manages the fetch, proxy, rendering, and anti-bot layer for the requests you send; your application owns authenticated sessions and parsing. The real cost of "free" X scraping is usually account and parser maintenance, not the installation command. ## Prefer to Build Your Own? General Frameworks for X (Twitter) Scraping on GitHub If no ready-made repo fits, these general open-source frameworks are what you would build a custom X (Twitter) scraper with. None of them is a Twitter scraper out of the box, and X's defenses make the DIY path the highest-maintenance option on this whole list. | Framework | Repo | Best for | Honest limit | |---|---|---|---| | Playwright | [microsoft/playwright](https://github.com/microsoft/playwright) | Driving a logged-in session and capturing background GraphQL calls | Heavy, and default fingerprints are detectable without stealth patches | | Selenium | [SeleniumHQ/selenium](https://github.com/SeleniumHQ/selenium) | Broadest language support, or maintaining an existing script | Slower and more detectable, and most stale Twitter repos on GitHub are built on it | | Scrapy | [scrapy/scrapy](https://github.com/scrapy/scrapy) | Crawl orchestration at scale | X's login walls and rotating query IDs mean you supply the entire session and anti-bot layer | | requests + BeautifulSoup | [psf/requests](https://github.com/psf/requests), [BeautifulSoup](https://www.crummy.com/software/BeautifulSoup/) | Teaching baseline | x.com is JavaScript-rendered, so raw HTTP and HTML parsing gets almost nothing back | A minimal Playwright sketch that opens a profile and listens for background API calls looks like this. Tested live, a bare guest visit fires no capturable X API calls at all now, X server-renders public profile data into the page instead of fetching it over GraphQL. The technique itself is still correct for logged-in sessions or scroll-triggered pagination, a guest profile view is just the one case with nothing to catch. Treat this as a starting point, not production code: javascript```javascript const { chromium } = require('playwright'); (async () => { const browser = await chromium.launch(); const page = await browser.newPage(); page.on('response', (res) => { if (res.url().includes('graphql')) { console.log(res.status(), res.url()); } }); await page.goto('https://x.com/x'); await page.waitForTimeout(3000); await browser.close(); })(); ``` None of these four frameworks handle X's anti-bot on their own. You supply the guest tokens, doc\_id rotation, and GraphQL capture logic yourself. Building your own gets you full control over what you extract. It also means you inherit every rotation X ships, which is the same maintenance burden the dead tools below eventually lost to. ## Which Twitter Scrapers on GitHub Are Dead or Should Be Avoided? The old X scraping ecosystem was hollowed out through both technical and legal pressure. Twint and snscrape lost the anonymous guest-access assumptions they depended on. Nitter's public-instance network had already collapsed when X later demanded permanent takedowns and the repository was archived. - **Twint, roughly 16,395 stars, archived.** GitHub's banner says the owner archived it on Mar 30, 2023. Its star count is historical popularity, not a working-status signal. - **snscrape, roughly 5,449 stars, broken since 2023.** Its Twitter modules relied on the anonymous guest access X shut down that year. - **Nitter, roughly 14,473 stars, archived Sep 11, 2026.** Its README says X Corp sent cease-and-desist letters on Aug 24, 2026 demanding permanent takedown of Nitter instances and the repository. The public-instance network had already collapsed after X blocked the guest accounts it used. The repository is now read-only. - **Hosted-API funnel repos.** A repository that only wraps someone else's paid endpoint is not an open-source scraper. Requiring an API key is different when the repository still contains the parsing logic, as Scrapfly's example does. - **Automation toolkits mislabeled as scrapers.** Posting and browser-console projects solve a different job from data collection, regardless of star count. Not every dead project was directly taken down by X. Some became obsolete when access changed; Nitter is the clear case where direct legal pressure followed the technical lockout. ## Why Do Open-Source X (Twitter) Scrapers Break So Fast? X applies pressure at both layers these projects depend on: it changes the technical surface and enforces its restrictions against projects that restore access. - **GraphQL query IDs rotate without notice**, and a working scraper has to refresh every operation it depends on. - **Login walls moved the boundary.** Search, replies, and follower lists now require account sessions, so guest-era claims remain visible long after their code stops working. - **Account health became infrastructure.** Cookie refresh, proxy assignment, rate limits, and bans sit outside the scraper's parsing functions. - **Direct pressure can end a project.** Nitter archived after X Corp demanded takedown of its instances and repository. - **Fixes lag breakage.** A repository can commit frequently and still trail X's current page or frontend behavior. A managed [Web Scraping API](https://scrapfly.io/products/web-scraping-api) reduces one part of that burden. It can handle retrieval, proxy routing, rendering, and anti-bot infrastructure while your application keeps its own parsing logic. It does not supply X accounts or cookies for login-gated data, and it does not turn the example repository into a hosted Twitter data API. ## FAQ What is the best Twitter (X) scraper on GitHub?twscrape is the breadth pick for search and GraphQL reads when you can operate an account pool. Scrapfly's twitter-scraper is the managed-fetch pick for public posts and profiles. Scweet fits resumable cookie-based exports, and the-convocation/twitter-scraper fits TypeScript projects. Can I scrape X (Twitter) without an account or API key in 2026?Public posts and profiles can still be reachable without an X account through limited guest reads or Scrapfly's managed fetch example. Search, replies, followers, and other login-gated data need an X account session. Scrapfly does not provide those accounts or cookies. How do you use twscrape?Install with `pip install twscrape`, add an account from browser cookies with `twscrape add_cookie username "auth_token=...; ct0=..."`, then run `twscrape search "query" --limit 20` from the CLI or call the async API directly. It rotates accounts automatically when one hits a rate limit. How many tweets can one X account scrape per day?Roughly hundreds to a few thousand, per Scweet's maintainer guidance (checked Aug 2026), and it shifts with account age and activity. Past that, you need a multi-account pool with proxies, and the ban risk that comes with it. Is it legal to scrape X (Twitter)?X's terms bar scraping without express written permission and add liquidated damages for requesting, viewing, or accessing more than 1,000,000 posts in any 24-hour period: $15,000 USD per million under the US terms effective April 10, 2026, or EUR 15,000 under the EU, EFTA, and UK terms effective January 15, 2026. The legal position also depends on the jurisdiction, access method, data, and use case. Get advice for the specific workflow. Why did so many open-source Twitter scrapers stop working?They did not all fail for the same reason. Twint and snscrape depended on anonymous guest access that X shut down. Nitter's public instances lost their guest accounts, and X later sent cease-and-desist letters demanding takedown of the instances and repository. The current repository is archived. ## Conclusion X did not hollow out its scraping ecosystem through one universal takedown. Technical changes killed guest-era tools first; direct legal pressure later pushed Nitter to archive. The projects left standing survive by narrowing their scope, making users operate accounts, or moving the fetch layer to managed infrastructure. Choose twscrape for the broadest account-based coverage, Scweet for resumable cookie-based exports, and the-convocation for TypeScript. Choose Scrapfly's example when the job is public post or profile retrieval and you want the fetch, proxy, rendering, and anti-bot layer managed. One option is to maintain X accounts, cookies, query IDs, and proxy infrastructure yourself. The managed alternative is to use Scrapfly for the fetching/API layer and its proxy, rendering, and anti-bot infrastructure. You still supply any X accounts needed for login-gated data and maintain the parser. [**Twitter Scraper**github.com/scrapfly/scrapfly-scrapers/tree/main/twitter-scraper](https://github.com/scrapfly/scrapfly-scrapers/tree/main/twitter-scraper) Build it yourself if you want full control over X accounts, cookies, query IDs, and proxy infrastructure. Use Scrapfly's Twitter example when you want the fetching/API layer and infrastructure managed instead. Scrapfly does not provide X accounts or maintain the parser; those remain yours. ### Web Scraping API Scrape any website with our powerful API. Anti-bot bypass, JavaScript rendering, and rotating proxies built-in. [Try Web Scraping API](https://scrapfly.io/docs/scrape-api/getting-started) [ Add as a preferred source ](https://google.com/preferences/source?q=scrapfly.io) Table of Contents Table of Contents- [Key Takeaways](#key-takeaways) - [Which Open-Source X (Twitter) Scraper on GitHub Should You Use?](#which-open-source-x-twitter-scraper-on-github-should-you-use) - [How Did We Rank These Twitter Scraper Repos?](#how-did-we-rank-these-twitter-scraper-repos) - [1. twscrape: Best for Search and GraphQL Coverage with an Account Pool](#1-twscrape-best-for-search-and-graphql-coverage-with-an-account-pool) - [2. Scrapfly twitter-scraper: Best Managed Fetch for Public Posts and Profiles](#2-scrapfly-twitter-scraper-best-managed-fetch-for-public-posts-and-profiles) - [3. Scweet: Best for Cookie-Based Scraping with Resume and CSV/JSON Output](#3-scweet-best-for-cookie-based-scraping-with-resume-and-csv-json-output) - [4. the-convocation/twitter-scraper: Best for TypeScript and Node.js Projects](#4-the-convocation-twitter-scraper-best-for-typescript-and-node-js-projects) - [Do You Need an Account Pool to Scrape X (Twitter)?](#do-you-need-an-account-pool-to-scrape-x-twitter) - [Prefer to Build Your Own? General Frameworks for X (Twitter) Scraping on GitHub](#prefer-to-build-your-own-general-frameworks-for-x-twitter-scraping-on-github) - [Which Twitter Scrapers on GitHub Are Dead or Should Be Avoided?](#which-twitter-scrapers-on-github-are-dead-or-should-be-avoided) - [Why Do Open-Source X (Twitter) Scrapers Break So Fast?](#why-do-open-source-x-twitter-scrapers-break-so-fast) - [FAQ](#faq) - [Conclusion](#conclusion) Join the Newsletter Get monthly web scraping insights Scale Your Web Scraping Anti-bot bypass, browser rendering, and rotating proxies, all in one API. Start with 1,000 free credits. No credit card required 1,000 free API credits Anti-bot bypass included [Start Free](https://scrapfly.io/register) [View Docs](https://scrapfly.io/docs/onboarding) Not ready? Get our newsletter instead. ## Related Articles [ python headless-browser ### 12 Python Web Scraping Projects for 2026 12 Python web scraping projects laddered from static HTML to Scrapy crawls and AI agents, each with skills, a data sourc... ](https://scrapfly.io/blog/posts/python-web-scraping-projects-from-beginner-to-advanced) [ python hidden-api ### 3 Best Open-Source Job Scrapers for Multi-Board Data in 2026 Three open-source job scrapers ranked by board coverage, schema, and dated maintenance, plus a source-available Scrapfly... ](https://scrapfly.io/blog/posts/best-open-source-job-scrapers) [ python scrapeguide ### 5 Best Open-Source LinkedIn Scrapers on GitHub in 2026 Five open-source LinkedIn scraper repos on GitHub ranked by auth model, dated maintenance and honest ban risk, with live... ](https://scrapfly.io/blog/posts/best-linkedin-scrapers-github) ## Related Questions - [ Q What Python libraries support HTTP2? ](https://scrapfly.io/blog/answers/what-python-libraries-support-http2) Scale your web scraping effortlessly, **1,000 free credits** [Start Free](https://scrapfly.io/register)