Your Twitter Archive Doesn't Include Bookmarks. Here's What It Really Contains.
You did the responsible thing: Settings → Your account → Download an archive of your data. You waited a day, unzipped the file, and went looking for your bookmarks. They're not there. This isn't a bug or a missing download — X's official archive has never included bookmarks, and nothing in the 2026 update changed that.
The short version
- What the archive has: your own tweets, retweets, likes, DMs, profile data, follower/following lists, moments, and some media.
- What it doesn't have: bookmarks — the one collection you curated yourself, saved precisely because you didn't want to lose it.
- Why: a bookmark is a pointer to someone else's post, and the archive only packages data X considers "yours."
- The fix: export bookmarks separately — a browser extension that reads your bookmarks page can capture them all, media included.
What's actually inside the X archive
Requesting your archive (Settings and privacy → Your account → Download an archive of your data) kicks off a preparation job that typically takes 24 hours or more. What arrives is a ZIP with an HTML viewer plus a pile of JavaScript and JSON files:
| Included | File (typical) | Notes |
|---|---|---|
| Your tweets | tweets.js / tweets-part*.js | Full text, timestamps, IDs — split into parts for large accounts |
| Retweets | retweeted-tweets… | Retweets of others' posts |
| Likes | likes.js | IDs and text of posts you liked |
| Direct messages | direct-messages… | Both sides of your conversations |
| Profile & account | profile.js, account.js | Bio, email, phone on file, creation date |
| Followers / following | followers.js, following.js | Usernames and display names, as a snapshot |
| Some media | data/tweets-media/ | Your own uploaded photos/videos — often re-encoded, not always original quality |
That's genuinely useful. For your own content, the official archive is the best bulk export X offers — which is exactly why the omission stings.
The gap: bookmarks are nowhere to be found
Search the unzipped folder for "bookmark" and you'll come up empty. There is no bookmarks.js. This has been true since the archive feature existed (it predates bookmarks' 2017 launch, and bookmarks were simply never added to the export). The May 2026 "History" redesign that moved bookmarks into a History tab didn't change the archive's contents either.
The reason is structural. The archive packages data you created: your tweets, your likes, your DMs. A bookmark is a reference to a post authored by someone else, so X treats it as account metadata rather than your content — and leaves it out.
The irony: bookmarks are the collection you actively curated. Tweets happen by accident; bookmarks are chosen. Yet the official export covers the accidental stuff and skips the curated stuff.
Other gaps worth knowing about
- Likes are included but lossy in practice.
likes.jsgives you IDs and text, but if the liked post was deleted, there's nothing left to resolve — same pointer problem as bookmarks. - Media isn't guaranteed original quality. Archive media is re-encoded; large videos may arrive downscaled or absent.
- It's a snapshot, not a sync. The archive reflects the moment it was generated. Anything you save next week requires requesting the whole thing again — and waiting another 24 hours.
- Deleted-by-others content is simply gone. The archive can't contain posts that no longer exist on X, and neither can any export tool that reads X.
Can the X API get my bookmarks instead?
Yes — partially, and expensively. The developer API has a GET /2/users/:id/bookmarks endpoint, but:
- It requires user-context OAuth (you authenticate as yourself), and an app at the paid tiers.
- It paginates out at roughly 800 of your most recent bookmarks. Older saves may exist on your account but the API won't return them.
- Rate limits are tight — on lower tiers it's about one request per user per 15 minutes, so bulk-pulling a large collection is slow.
- It returns post JSON, not media files. You'd still need a separate step to download every image and video.
For most people, the API route costs money, hits the 800 wall, and still doesn't hand you the actual media.
How to back up bookmarks (the part the archive misses)
The practical route in 2026 is a browser extension that reads your bookmarks page as your browser loads it — the same page you can already see, just captured systematically:
- Install the extension from the Chrome Web Store.
- Open
x.com/i/bookmarksand scroll so items load (the extension records what renders). - Export to CSV / JSON / Markdown, and download attached photos and videos as real files.
Because it captures from your logged-in browser session rather than the developer API, it isn't bound by the API's 800-item pagination — the ceiling is how far you scroll. And it can save the actual media bytes to your disk, not just URLs.
Export what the official archive skips
XVault backs up your X bookmarks, tweets, replies and media to your own device — CSV, JSON, Markdown, plus original-quality photos and videos. The free Chrome extension handles up to 1,000 rows per data type per export; PRO ($19.99 once) removes the row cap. Nothing is uploaded anywhere.
Get XVault for ChromeA sensible backup strategy: archive + bookmarks
The official archive and a bookmark exporter aren't competitors — they cover different halves:
| X official archive | Bookmark/media exporter | |
|---|---|---|
| Your tweets | ✅ Full history | ✅ (tweets export) |
| Likes | ✅ IDs + text | ✅ (likes export) |
| DMs | ✅ | ❌ |
| Bookmarks | ❌ Missing | ✅ Full text + media |
| Media files | ⚠️ Re-encoded, yours only | ✅ Original quality, saved posts |
| Freshness | ⚠️ 24h snapshot on request | ✅ Whenever you browse/export |
| Cost | Free | Free tier / one-time PRO |
Request the official archive once or twice a year for your own content, and keep bookmarks + saved media on a rolling export. Together they cover what neither does alone.
Frequently asked questions
Will X ever add bookmarks to the archive?
There's no announced plan. The History redesign of May 2026 reorganized bookmarks in the UI but didn't touch the data export. Treat the omission as permanent and export separately.
My archive's likes.js is there — why are some likes missing?
Likes of deleted posts can't be resolved, and very old like data is sometimes sparse. The file contains what X could still reconstruct at generation time.
Is using an extension to export bookmarks against X's rules?
Extensions that read pages your own logged-in browser renders don't use hidden APIs or scrape other people's accounts — you're exporting content you can already see. As always, respect X's terms and other people's copyright when you reuse saved media.
Can I get media from the archive instead of an extension?
Only media you uploaded yourself, and re-encoded. Media inside posts you bookmarked belongs to other accounts and isn't in your archive at all.