How to export your X (Twitter) bookmarks

You've got thousands of bookmarks on X and you want them out: into a spreadsheet, a notes app, or just a backup you actually control. So you go looking for the export button, and there isn't one. You download your official X archive instead, open it up, and your bookmarks aren't in there either.

That's not you missing a setting. X has no native way to export your bookmarks, and the official data archive deliberately leaves them out. Here are the routes that do work in 2026, what each one costs you, the wall they all run into, and how to keep a copy that doesn't rot.

The short answer

There are three ways to get your bookmarks out of X, in rough order of how practical they are:

1. A browser extension that reads your logged-in Bookmarks page and downloads it as a CSV, JSON, or Markdown file. Easiest for most people.
2. The official X API, if you're a developer and don't mind paying for it.
3. Copying them by hand, one post at a time, which only makes sense for a handful you really care about.

All three share the same two limits: they tend to dry up around the first 800 bookmarks, and everything they save is still a link back to X, so it breaks when the original post is deleted. We'll cover each, then the way around both.

Why there's no export button

X treats your bookmarks as something that lives inside X. There's no "export" in Settings, and the one place you'd expect to find them, the official archive, skips them entirely.

When you download your X archive, the ZIP holds your posts, likes, DMs, and follower list, but not your bookmarks. It's a deliberate gap, and it's the reason people go looking for another way. (The archive has a second problem too: every entry is just a link back to X, so even the data it does give you rots when the original is removed.)

How to export your X bookmarks

1. A browser extension (the practical route)

The most reliable option is a browser extension that opens your Bookmarks page while you're logged in, reads the posts, and downloads them as a file. The better ones export to CSV, JSON, or Markdown, so you can drop them into a spreadsheet, a database, or a notes app.

• Best for: most people who just want a file out of X without touching code.
• Watch out: an extension that can read your bookmarks needs access to your logged-in X session, and some send your data through their own servers to do it. Prefer an open-source exporter that processes everything locally in your browser, check what permissions it asks for, and remove it once you've got your file.

2. The X API (for developers)

X does publish a bookmarks endpoint (GET /2/users/:id/bookmarks) that returns the authenticated user's saved posts. If you're comfortable writing a bit of code, you can pull your bookmarks directly.

• Best for: developers who want a structured, repeatable export.
• Watch out: it sits behind X's paid developer tiers (the entry paid tier runs $200 a month at the time of writing) and requires an OAuth 2.0 user-context login. In practice it also paginates back only the most recent ~800 to 1,000 bookmarks before the results run dry, which is the same wall the extensions hit, because most of them call the same underlying API.

3. Copy them by hand (free, but slow)

For a small, high-value set, you can just open each post and save it yourself: screenshot it, or run it through a tweet-to-text converter to keep the words and a citation. Tedious at scale, but it's free, needs no account access, and the copy you keep is real text that survives the original being deleted.

The catch every method shares

Two problems follow you across all three routes.

The 800 wall. You can save as many bookmarks as you like; X lifted its old bookmarking cap years ago, and plenty of people now sit on tens of thousands. But getting them back out is where the ~800 limit reappears, because the export endpoint only paginates so far back. The oldest bookmarks, often the ones you most want to rescue, are frequently the ones you can't reach.

They export links, not content. A CSV of bookmark URLs looks like a backup right up until you click one and find a deleted post. An exported bookmark is still a pointer to something on X's servers, so it rots exactly like the original did. This is link rot, and a spreadsheet full of dead links is still full of dead links.

Skip the export: keep bookmarks as real copies

The reason exporting is such a pain is that you're trying to extract copies after the fact, from a system that never kept copies in the first place. The cleaner fix is to make the copy at save time, so there's nothing to export later and nothing left to rot.

That's what Stashr does. Its browser extension can import your existing bookmark history out of X, and from then on it captures each new bookmark in full, the text, the author, and the media, the moment you tap the ribbon. Because these are real copies in a library of your own:

• They survive deletion. The original post can vanish; your copy stays put.
• You get the whole picture, not a URL: the media and context come with it, not just a link.
• You can search by meaning. Every save is AI-tagged on the way in, so plain English works, not just exact keywords:

stashr.search("that thread about pricing psychology");
// → returns your captured copy, even if the original was later deleted

• X stops being a silo. Your bookmarks land in the same searchable library as your Reddit, Instagram, and TikTok saves.

The first two get you a file, but it's a file of links capped at ~800. Copying by hand keeps real content, but only for the few you have the patience to save. Capture-first is the only row that keeps the full content of your whole library.

Common questions

Can you export your X bookmarks?

Not through X directly. There's no export button in the app or Settings, and the official data archive doesn't include bookmarks. To get them out you need a third-party browser extension or the paid X API, and both usually reach only the most recent ~800 bookmarks.

Are bookmarks included in the Twitter/X data archive?

No. The archive you request from X includes your posts, likes, DMs, and account history, but bookmarks are left out entirely. It's a common surprise, and it's why a separate export step (or a capture-first backup) is the only way to keep them.

Is it safe to use a third-party bookmark exporter?

It can be, with care. Any tool that reads your bookmarks needs access to your logged-in X session, so prefer an open-source extension that processes your data locally in your browser, review the permissions it requests, and uninstall it once you have your file. Be wary of tools that route your bookmarks through their own servers.

Why can't I export all of my bookmarks?

Because the export endpoint only paginates back through roughly the last 800 to 1,000 bookmarks before it stops returning results. You can save far more than that, but the tools that read them out, both extensions and the API, hit the same wall, so your oldest saves are often unreachable.

How do I back up my X bookmarks so they don't disappear?

Keep a copy of the content, not the link. Exports give you URLs that rot when posts are deleted. A capture-first tool like Stashr copies the full post at save time and can import your existing bookmark history, so your saves survive no matter what happens to the originals.