How to Export Your X Bookmarks (2026)

X's data archive doesn't include your bookmarks, so getting them out takes a workaround. Three methods work in 2026: copy them by hand, pull them through the X API, or run a browser extension that reads your bookmark list directly. Here's what each one costs you and which one fits.

Why X's official archive won't help

The obvious move is to request your data: Settings and privacy → Your account → Download an archive of your data. That archive is thorough. It has your posts, replies, reposts, direct messages, media, your followers and following lists, the Lists you made, even the ads you interacted with.

It does not have your bookmarks. That gap has been there for years, and X still hasn't closed it as of July 2026. So the archive route is a dead end for this one job — you have to pull bookmarks separately.

The manual method: free, and fine for a few dozen

Open x.com/i/bookmarks, scroll, and copy the links you care about into a note or a spreadsheet. It costs nothing and needs no tools.

The catch is scale. X doesn't publish a cap on how many bookmarks you can save, but long lists get slow to scroll, and older saves get hard to reach the further back you go. Copying by hand stops being reasonable somewhere past a few dozen bookmarks. If you've been saving posts for years, this is not your method.

The API method: precise, but now you're a developer

X exposes your bookmarks through the endpoint GET /2/users/{id}/bookmarks. To call it you need a developer account and API credits.

Pricing changed this year. X dropped the old fixed Basic and Pro monthly plans for new signups and moved to pay-per-use. Reading your own data — posts, likes, followers, bookmarks — falls under what X calls Owned Reads, priced at $0.001 per resource, or 1,000 bookmarks for about $1. That's the rate published on X's own pricing docs as of July 2026.

The API gives you clean, structured data and full control over the format. The cost is setup: registering an app, getting a token, buying credits, and writing or borrowing a script to page through the results. Worth it if you're comfortable with that. Overkill if you just want your bookmarks back.

The browser-extension method: reads your whole list in minutes

An extension logs into your existing X session in the browser and walks your bookmark list the same way the app does — no developer account, no per-request bill. This is the least hands-on route for a large collection.

Open-source options exist: twitter-web-exporter and xarchive both pull bookmarks (and, in xarchive's case, folder assignments) to CSV or JSON. Paid tools like Tweetsmash and Dewey do the same with a hosted interface and extras like search or Notion sync. Circleboom leans toward bookmark management and cleanup. Pick based on where you want the data to land.

Whatever you choose, an extension reads your bookmarks through your logged-in session, so check that it's open source or clearly explains what it does with your auth token before you run it.

So the export is done. Then what?

A CSV of 900 bookmarks is a pile of links, not a memory. You still can't find the thread about retrieval-augmented generation you saved in March, because a link doesn't know what's inside it.

Animus is our product, so read this section as a pitch — but every claim in it is checkable. Animus is the AI bookmark manager that reads what you save. It reads the text of each post you save, so you search by what a bookmark says rather than by remembering who posted it. The Animus Exporter is an open-source Chrome extension that pulls your X bookmarks in batches of 100 to a JSON file; you import that file and everything becomes searchable. The step-by-step is in Import Your X Bookmarks Into Animus.

Try Animus free and search your X bookmarks by what they actually say.

Which method should you pick?

Under a few dozen bookmarks: copy them by hand. No tools, done in one sitting. Comfortable with a developer account: use the API for clean, structured output at roughly $1 per thousand. Hundreds or thousands of bookmarks and you want them fast: use a browser extension. If you want the export to end in something you can actually search, an extension that imports straight into a reading tool saves you the second step.

Questions people actually ask

Does X's data download include my bookmarks?

No. The archive you request under Settings → Your account → Download an archive of your data includes your posts, direct messages, likes, media, and follower lists, but bookmarks are left out. That's still true as of July 2026, so you need a separate method to export them.

Can I export my X bookmarks for free?

Yes. Copying links by hand from x.com/i/bookmarks costs nothing, and open-source browser extensions like twitter-web-exporter and xarchive export your full list to CSV or JSON at no charge. Paid tools and the API mainly buy you convenience or structured output, not access you can't get otherwise.

How much does the X API cost to pull my bookmarks?

Reading your own bookmarks counts as an Owned Read on X's pay-per-use pricing: $0.001 per resource, so about $1 for 1,000 bookmarks, per X's developer docs in July 2026. You'll also need a developer account and prepaid credits. Rates can change, so check the current pricing page before you budget.

Is there a limit on how many bookmarks I can save on X?

X doesn't publish a hard cap on the number of bookmarks. In practice, very long lists load slowly and older saves get harder to reach as you scroll. Bookmark folders, which help you organize the list, require an X Premium subscription rather than a free account.

Will I keep my bookmark folders when I export?

It depends on the tool. Most exporters give you a flat list of bookmarks without folder structure. A few, like the open-source xarchive, capture folder assignments too. If your folders matter, check the tool's description for folder support before exporting, since folders are a Premium feature and not every exporter reads them.