← Blog

How to Export Your X (Twitter) Bookmarks Before They Rot

Noah Kagan · July 4, 2026

Here's the trap: you've been bookmarking tweets for years, you finally request your X data archive, you unzip it… and your bookmarks aren't in it. Likes are there. Bookmarks aren't. X treats them as ephemeral app state, not your data.

Meanwhile the tweets themselves keep dying — deleted, accounts suspended, or locked behind login walls. A bookmarked tweet is a bookmark to a coin flip.

What actually works

Scroll-and-save (free, manual). Open your bookmarks, and for each one you care about, save it somewhere you control. Tedious but honest. Fine for under 50 bookmarks.

Browser-automation exporters (free-ish, fragile). Various extensions will scroll your bookmarks page and scrape it to JSON or CSV. They break every time X changes its DOM, which is roughly quarterly. Check the reviews from the last month before trusting one, and expect to get URLs and text only.

Save tweets properly as you go (my answer). I built this into Marks because I got burned by dead tweets one time too many. With the extension, saving a tweet captures the full text, images, and thread context at save time — so when the tweet inevitably dies, your copy doesn't. Tweet hashtags even become tags automatically. There's also an importer for bulk-migrating an existing bookmark stash.

The mindset shift

Stop thinking of X bookmarks as storage. They're a to-do list with a memory leak. Anything you'd be sad to lose should live in a tool whose business model is keeping your stuff, not maximizing your scroll time. Export what you have, then change where the save button points.

Marks is a free bookmark manager and read-later app. Try it at getmarks.sh