How to Export ALL Your X (Twitter) Bookmarks in 2026 (Past the 800 Limit)
You saved them, so they must be yours to download, right? Wrong. X has no export button for bookmarks, the official data archive leaves them out entirely, and most third-party tools silently stop after about 800 of them. Here's every route that actually works in 2026 — and the wall you'll hit on most of them.
The short version
- X has no built-in bookmark export. Not in the app, not in Settings, not in the official "Download your data" archive.
- The API only paginates back ~800 bookmarks. Every tool built on the API inherits that ceiling — even on the $200/month developer tier.
- A bookmark is a pointer, not a copy. Export a list of URLs and half of them will be dead links within a year.
- The reliable fix is browser-side capture — a tool that reads what your own logged-in session renders as you scroll, with no 800 cap, and downloads the media too.
Why exporting X bookmarks is harder than it looks
There are three separate problems stacked on top of each other, and most guides only mention the first one.
1. There is no official export
X's Settings → Your account → Download an archive of your data gives you your posts, likes metadata, DMs and account history as a pile of JSON — but not your bookmarks. That's a deliberate product decision, not an oversight. Bookmarks are meant to keep you inside the app.
2. The API caps out around 800
The developer endpoint GET /2/users/:id/bookmarks returns only the most recent ~800 bookmarked posts. Worse, developers have reported intermittent pagination bugs through 2025–2026 where the next_token cursor stops after two or three pages — so for some accounts the real ceiling is closer to 200–400. The bookmark-folder endpoint is shakier still (reports of it capping at 20 items with no pagination).
The uncomfortable implication: a paid "sync all your bookmarks" SaaS that reads through the API is, in practice, syncing your last 800. Anything older is unreachable no matter how long you keep paying.
3. Bookmarks rot
Even the bookmarks you can export are usually just URLs. A bookmark points at a post living on X's servers. The author deletes it, goes private, or gets suspended — and your "saved" item resolves to nothing. A spreadsheet of dead links isn't a backup.
Every method that works, compared
| Method | Gets past 800? | Real copies (media)? | Effort |
|---|---|---|---|
| Official X archive | No bookmarks at all | No | Low |
| X API + a script | No (~800 cap) | Only if you fetch media separately | High (paid tier, OAuth) |
| Open-source userscript (e.g. twitter-web-exporter) | Yes (reads the page) | Partial (bulk media download) | Medium (Tampermonkey, manual scroll) |
| Free one-click extensions | Varies — many hit the same wall | Rarely | Low |
| Local-first archiver (XVault) | Yes | Yes — original quality | Low |
Method A: Browser extension (easiest)
The fastest way to get bookmarks out of X. Install, open x.com/i/bookmarks (now under the History tab), click the icon, pick a format, export. Look for one that captures as you scroll rather than calling the API — that's the difference between "your last 800" and "all of them." Check that it downloads media, not just links.
Method B: Open-source userscript (most control)
Tools like twitter-web-exporter run in Tampermonkey and read directly from the page as you scroll, bypassing the API ceiling. Powerful, free, and technical — you manage the script manager, and for large collections you scroll (and wait) a lot.
Method C: The API yourself (not worth it for bookmarks)
You can pull bookmarks via the API with OAuth 2.0 user context — but it's behind a paid developer tier (~$200/month at the time of writing) and still capped at ~800. For personal backup this is the worst value of all the options.
Method D: A local-first archiver
This is what XVault does, and it's the approach we'd recommend regardless of which tool you pick. Instead of extracting links after the fact, it captures the full post — text, author, and the actual image/video files — into a folder on your own device while you browse. No server holds your data, there's no 800 ceiling, and the archive survives the original being deleted.
Back up every bookmark — with the media, past the 800 limit
XVault is a free Chrome extension that archives your X bookmarks, tweets and media to your own device. Nothing is uploaded. Ever.
Get XVault for ChromeStep by step: export with XVault
- Install XVault from the Chrome Web Store (free, no account).
- Make sure you're signed in to x.com in the same Chrome profile.
- Click the XVault toolbar icon and press Back Up Everything. It reads your bookmarks (including folders), tweets, likes, followers — and downloads images/videos in original quality.
- Press Export backup and choose CSV, JSONL or Markdown. The file lands in the folder you connected (or your Downloads).
- Re-run any time — it resumes from a watermark and only fetches what's new (incremental backup is a PRO feature).
Frequently asked questions
Can I export X bookmarks for free?
Yes. XVault's free plan backs up all your data types and exports CSV/JSONL/Markdown up to 1,000 rows per type per export. Open-source userscripts are also free but require more manual work.
Are bookmarks included in the Twitter/X data archive?
No. The official archive includes posts, likes, DMs and account history — bookmarks are excluded. You need a separate tool.
Why can't I see my older bookmarks?
X's bookmarks timeline practically stops loading older items around 800–1,000, and the API paginates out at a similar point. The items may still exist on your account but are unreachable through normal means — which is exactly why capturing them early matters.
Is a third-party bookmark exporter safe?
Choose one that processes data locally, requests minimal permissions, is read-only on x.com, and doesn't route your data through its own servers. XVault sends nothing anywhere — you can verify with any network monitor.