← Blog · 2026-04-28

Twitter's Official Archive vs. Continuous Backup: What's the Difference?

If you've heard you should "back up your Twitter data," you might have already done it — gone to Settings, requested your archive, downloaded a zip file. Done, right?

Not quite. There's a meaningful difference between a Twitter archive and a backup, and most people don't realize it until it's too late.

What the Official X Data Archive Actually Is

X (formerly Twitter) lets you download a copy of your data from Settings → Your account → Download an archive of your data. This generates a zip file containing:

Your tweets (text and metadata)
Direct messages
Follower and following lists
Account details and settings
Ad impression data
Moments you created

This is genuinely useful. But it has four critical limitations.

Limitation 1: It's a snapshot, not a stream

Your archive captures everything up to the moment you request it. Every tweet you post after that download is unprotected. If you downloaded your archive six months ago and haven't done it since, you're missing six months of content.

Limitation 2: It doesn't include bookmarks

This is the big one. Your bookmarks — arguably your most intentionally curated collection of content on X — are not included in the official data export. This has been a known issue since bookmarks launched in 2018, and X has never addressed it.

Limitation 3: Liked tweets are just IDs, not content

The archive includes a list of tweet IDs that you liked, but not the content of those tweets. If the original tweet is later deleted, you have no record of what you actually liked. The IDs become meaningless pointers to nothing.

Limitation 4: It requires active effort to keep current

To keep your archive reasonably up to date, you'd need to remember to request a new download every few weeks, wait for the file to generate, and store each version somewhere. This is a manual process that almost nobody actually maintains.

What Continuous Backup Adds

A continuous backup service solves all four of these limitations.

It runs automatically

You set it up once and it stays current. New tweets are captured as you post them. New bookmarks are saved when you add them. New likes are recorded when you make them. No manual effort required.

It captures bookmarks

Because a continuous backup service uses the X API directly (not the archive export system), it can pull your bookmarks in real time. Every bookmark you save goes straight into your backup.

It stores liked tweet content, not just IDs

Rather than just recording tweet IDs, a proper backup fetches and stores the actual content of liked tweets at the time you like them. If the original is deleted later, you still have what you saved.

It maintains history over time

A continuous backup doesn't just give you a snapshot — it gives you a timeline. You can see exactly when you tweeted something, when you bookmarked something, how your activity changed over time.

A Concrete Comparison

Feature	Official X Archive	Continuous Backup (GrokThyself)
Your tweets	✅	✅
Tweet content at time of capture	✅	✅
Bookmarks	❌	✅
Liked tweet content (not just IDs)	❌	✅
Stays current automatically	❌	✅
Portable format (plain text/JSON)	Partial (HTML + JSON)	✅ (structured files)
Searchable with standard tools	Partial	✅
Stored under your control	❌ (zip on your computer)	✅ (your GitHub repo)
Available if account is suspended	❌	✅

The "I Already Downloaded My Archive" Misconception

The most common response to "you should back up your X data" is: "I already downloaded my archive."

The archive is better than nothing. But consider:

When did you download it? Everything since then is unprotected.
Do you have your bookmarks anywhere? Almost certainly not.
Can you quickly search your liked tweets by content? Probably not.
Is it versioned and organized? The zip file isn't.

The official archive is a good starting point. Continuous backup is what makes that data actually resilient.

The Complementary Approach

You don't have to choose. The ideal setup is both:

1. Download your official archive now as a foundation. This gets you everything up to today in X's structured format.

2. Set up continuous backup (GrokThyself) to keep everything current from this point forward, including bookmarks and full liked tweet content.

Together, these give you the most complete possible record of your X activity — including content that the official archive never captures.

How GrokThyself Stores Your Data

When you connect X and GitHub to GrokThyself, it creates a private repository in your GitHub account with a structure like:

tweets/
  2026/
    04/
      2026-04-07.md
bookmarks/
  2026-04-07-bookmark-123456.md
likes/
  2026-04-07-like-789012.md

Each file contains the full tweet text, author, URL, and timestamp. It's plain text, human-readable, and searchable with any standard tool. No proprietary format, no vendor lock-in.

The Cost of Doing Nothing

Every day you don't have a continuous backup is another day of unprotected content.

X accounts get suspended unexpectedly. Tweets get deleted in bulk (by you or others). Bookmarks reference content that can disappear at any time. Liked content evaporates when the original author deletes.

The official archive is a good step. Continuous backup is what actually protects you.

GrokThyself continuously syncs your X tweets, bookmarks, and likes to a private GitHub repo. Set it up once; it stays current automatically. Start for $8/month.

GrokThyself backs up your X tweets, bookmarks, and likes to a private GitHub repo — automatically.

Get started for $8/month