TL;DR. Yes, you can export your Twitter/X bookmarks in 2026. You just have three paths to choose from. X's developer platform is the right answer if you write code, a third-party bookmark manager is the right answer for everyone else, and a manual copy is the right answer when you only need a one-off batch.
Last reviewed June .
Why export your Twitter/X bookmarks?
Most people who export their bookmarks are doing it for one of five reasons: a permanent backup against future platform changes, migration to a different bookmark tool, feeding the data into a personal AI or notes system, archival research before leaving the platform, or simply pulling the data out of Twitter/X for safekeeping. The motivation matters because it changes which method makes sense for you.
The platform context is worth a sentence. Twitter rebranded to X in July , and the bookmarks feature carried over unchanged: same icon, same private behavior, same lack of a built-in export button. As of , there is still no one-click way to download your saves from inside the X app, which is why this guide exists.
A backup is the most defensive reason. Platforms change, accounts get suspended, services pivot, and a JSON file on your hard drive is the only artifact that survives all of those failure modes. The other reasons are forward-looking: feeding bookmarks into an AI tool for a personalized digest, migrating to a PKM system, or stripping the data out of an environment you no longer trust.
The three methods map neatly onto three kinds of users. If you write code, you go straight to X's developer platform. If you don't, you let a third-party service do the pulling for you. And if you only have a few dozen bookmarks and a quiet hour, you can copy them by hand.
Method 1. The X developer route (for developers)
If you're comfortable writing code, X offers a programmatic way to pull your bookmarks through its developer platform. It's the right method when you want full control over the data, plan to repeat the export on a schedule, or need to integrate Twitter/X bookmarks into a larger system. For everyone else, it's overkill.
The details change frequently, so the honest answer is to check X's current developer documentation when you actually sit down to implement. X has shuffled its developer tiers, pricing, and access rules several times since the rebrand, and anything this guide quoted today would be stale by next quarter. Budget for a real bill, too. Heavy users with thousands of bookmarks should expect paid-tier pricing to land somewhere meaningful for a full export.
A few durable patterns survive any of those changes. Store every raw response before you do any transformation, so you can reprocess later without refetching. Sync incrementally rather than refetching your entire bookmark history on every run, by keeping track of the most recent item you've already pulled and only asking for newer ones. Back off politely when the platform tells you to slow down, instead of hammering it.
One behavioral note that isn't obvious from the docs. Developer routes generally only return tweets that haven't been deleted by their author, so anything that vanished from the public timeline since you saved it is also gone from your feed. If preservation matters, export early and export often.
Method 2. A bookmark manager that syncs (for everyone else)
If you don't write code, the easiest way to export Twitter/X bookmarks is to sign into a bookmark manager that handles the sync with X on your behalf and offers a one-click export button. These tools do the backend work for you, then expose your bookmarks through their own UI with a "download" or "export" option that produces a JSON or CSV file in seconds.
Conceptually, what's happening is straightforward. You sign in once through X, granting the manager read access to your bookmarks. The manager pulls your library in the background and gives you both a UI to browse and a way to export the whole thing. From your perspective, none of the plumbing is visible.
There are a few well-known tools in this category as of . Bulkmark is a dedicated Twitter/X bookmark service that bundles four things into one workflow. Your bookmarks sync automatically in the background, so the library is always current. Every saved tweet is auto-tagged by theme as it arrives, so nothing ever needs to be filed by hand. A weekly AI-summarized email digest turns a week of saves into a three-minute skim. And an AI chat lets you ask questions across your entire saved library to pull back half-remembered threads on demand. Export to JSON is available for active users. Dewey is a Twitter/X-specific bookmark manager built around tagging and search, and it offers JSON and CSV exports of your full archive. Raindrop is a general-purpose bookmark manager with a Twitter/X integration: it stores your saved tweets alongside everything else you bookmark across the web, and exports to several formats including HTML and CSV.
For the full side-by-side comparison of these tools and a couple of others, including which ones are best for which use case, see the dedicated breakdown at the best Twitter bookmark managers of 2026.
The pros of this method are obvious. You write zero code. You get an ongoing sync instead of a one-shot export, which means your archive stays current without any work on your part. Most managers handle the backend heavy lifting for you, so even a bookmark library in the thousands shows up cleanly without timeouts or partial fetches. And exports are typically available in multiple formats, so you can pick JSON for programmatic use or CSV for a spreadsheet.
The cons are equally honest. A bookmark manager is a subscription (usually a few dollars to ten dollars a month), so this isn't free. You're also trusting a third party with read access to your private saves, so pick a vendor with a clear privacy policy. And if the manager shuts down, your synced archive lives at their mercy unless you've already exported a backup file. Always export at least once after signing up, even if you plan to keep the subscription.
Method 3. Manual copy (for one-off batches)
The manual method is the right choice when you have a small number of Twitter/X bookmarks (say under fifty) and you only need to do this once. It's the lowest-friction path because it requires no developer account, no third-party service, and no recurring cost. The trade-off is that it doesn't scale and it's tedious enough that you'll only ever do it for a single batch.
The basic procedure is the same on desktop and mobile. Open your bookmarks tab on X, scroll through the list, and for each tweet you want to export, copy the tweet's URL by tapping or right-clicking the share button. Paste the URL into a notes app, a plain text file, or a spreadsheet. Repeat until you've covered the bookmarks you care about.
A few small refinements make this less painful. On desktop, hovering over the timestamp of a tweet reveals a direct link you can right-click and copy without opening the tweet. On mobile, the share sheet's "copy link" option is the fastest path. If you want more than just the URL (the tweet text, the author handle, the date) you'll have to paste each element individually, which is the moment most people decide a bookmark manager is worth the eight dollars a month.
Be honest about volume. Manual copy works fine for ten or twenty bookmarks, gets painful at fifty, and is unworkable past a hundred. If you find yourself two hours deep, stop and switch to one of the other methods. Your time is worth more than the manager subscription.
Which method should you use?
The decision tree is short. Are you a developer who is comfortable writing integration code, and who needs ongoing programmatic access to your Twitter/X bookmark data? Use X's developer platform. The flexibility is unmatched and the long-term cost is manageable if you sync incrementally.
Do you want your bookmarks kept in sync going forward, with a UI for browsing and a one-click export when you need a backup file? Use a bookmark manager. This is the right answer for the vast majority of users: the time saved versus rolling your own export script is enormous, and a working manager subscription pays for itself in saved engineering hours within a month.
Do you only need to export under fifty bookmarks, just once, and never again? Use the manual copy method. There's no reason to set up a developer account or pay for a subscription for a one-time job that takes twenty minutes by hand. Just be honest about the size of your library before you start.
What to do with your exported Twitter/X bookmarks
Once you have an export file, the most common next steps are: feed it into a personal AI tool to generate summaries, archive it in your notes app, migrate it into a different bookmark tool, or build your own bookmark digest from scratch.
If the digest idea is what brought you here, see the manage Twitter bookmarks guide and the essay on why Twitter bookmarks pile up.
Bottom line
Three methods, three audiences. The developer route is flexible, powerful, and worth the setup if you need ongoing programmatic access. A third-party bookmark manager is the everyone-else route: zero code, ongoing sync, and a small subscription cost in exchange for never thinking about backend plumbing again. Manual copy is the last-resort route, fine for a one-off batch under fifty items and a bad idea for anything larger.
The landscape can shift when X updates its developer platform or pricing, and any specific detail in this guide may change. The three patterns themselves (direct developer access, third-party sync, manual copy) should remain the working categories regardless of which version of the platform is current. Pick the one that matches your situation and your tolerance for code, and back up the result somewhere safe so the next change to X's policies doesn't take your bookmarks with it.