How to Reach Older Posts Past X's Media Limit

There is a specific, quiet way that a Twitter/X archive fails. Nothing errors. No feed shows a warning. The tool reports success on every check. And yet the archive of a heavy poster stops somewhere around a thousand posts back, with years of older material simply absent. This post explains where that limit comes from, why it is so easy to miss, and what can actually be done about it.

Where the limit comes from

X does not serve a creator's entire media history. It serves the most recent stretch of it.

The practical boundary sits somewhere around the newest thousand posts, and once you reach it, that is the end. Requesting more does not return more. Waiting and requesting again does not return more. Changing your check interval, your settings, or your tooling does not return more, because the limit is on the platform's side of the connection.

This is not a rate limit, which is worth being clear about, because the two get conflated constantly. A rate limit says "not right now, try again shortly" and resolves itself with patience. This says "there is nothing further here" and stays that way permanently.

Why it fails silently

The reason this catches people is that the failure looks exactly like success.

Think about what a monitored feed does on a routine check. It asks for the creator's recent media, compares what comes back against what it already has, and downloads anything new. If the creator has not posted since the last check, the correct outcome is to find nothing new and finish.

Now consider a feed that has hit the limit. It asks for the creator's recent media. It gets back the same recent stretch it already has. It finds nothing new. It finishes successfully.

From the tool's point of view, those two situations are indistinguishable. There is no error, no warning, no flag. The feed reports a clean check, its status stays healthy, and your dashboard shows everything working. Meanwhile the older half of that creator's output has never been fetched and never will be by that mechanism.

The only reliable tell is knowing the creator. If you are aware they were posting in 2021 and your archive of them starts in 2024, you have found it. If you are not, an archive can sit incomplete for years without ever looking wrong.

Who this actually affects

It is worth being proportionate here, because this does not affect everyone.

If you follow creators who post a few times a week, a thousand posts covers several years and you will likely never touch the limit. Your archive genuinely is complete.

The people this hits are those archiving heavy posters. An account that posts a dozen times a day burns through a thousand posts in under three months. For accounts like that, the newest-thousand window is a rolling few weeks, and everything before it is out of reach through normal checks. Anyone archiving news accounts, prolific artists, high-volume communities or anyone who treats X as a running commentary is squarely in this category.

Going past the limit

In StreamStash, this is what Deep Sync is for.

Running it on a Twitter feed recovers posts from well before where an ordinary check gives up. On busy creators that can be thousands of items reaching back years. They arrive in the feed like anything else: searchable, favouritable, and playable in the built-in player, sitting alongside the material you already had.

It is worth setting expectations honestly. This goes as far back as X still allows, which is considerably further than a routine check but is not unlimited and is not a guarantee of a creator's complete history. Posts that have been deleted are gone. Posts that X no longer serves through any route are gone. What Deep Sync recovers is the gap between what a normal check reaches and what the platform still holds, and on a heavy poster that gap is where most of their work lives.

Why it runs in stages

A large backlog is a lot of work, and there is an obvious way to get this wrong: let one feed monopolise everything until it is finished.

That would mean pressing Deep Sync on a prolific account and watching the rest of your library stop being checked for hours. New posts from every other creator you follow would queue up behind a historical catch-up, which is precisely backwards, since the new posts are the ones at risk of disappearing.

So it works through the backlog in stages. The feed takes a turn, hands back to your other feeds, then picks up exactly where it stopped on its next turn. You press Deep Sync once and it carries on by itself until it is done. A note on the feed shows that it is in progress and roughly how much is left, including while it is waiting its turn, so a long catch-up never looks like a stalled one.

What it does not override

One thing that would be easy to get wrong, and is worth knowing has not been: a deep pass does not quietly ignore the limits you set.

If you have capped how much tweet text a feed collects, or how many reposts it keeps, those caps apply exactly as before. The deeper pass only looks for photos and videos. It fills in the media history without dragging in text or reposts you deliberately asked it to leave alone.

This matters because the settings that keep a feed's scope under control are usually chosen precisely because that creator posts a lot, which is the same reason you would want a deep pass on them. Having one silently undo the other would be a nasty surprise.

New feeds do it automatically

Any Twitter feed added from this version onwards goes after the full history on its first check, whatever its text and repost settings. There is nothing to remember and nothing to turn on.

Deep Sync is therefore mainly a remedial tool, for creators you were already following before this existed. If you have been archiving X for a while, it is worth going through your heaviest posters once and running it on them. That is where the missing years are, and unlike new posts, older material does not become more recoverable with time.

If what you want to follow is a subject rather than a person, that is a different shape of problem with its own answer, covered in how to archive X search results.

FAQ

Why does my Twitter archive stop after about a thousand posts?

X serves only the most recent stretch of a creator's media through the interfaces an archiver can use, somewhere around the newest thousand posts, and then stops. It is a platform-side limit, not a setting in your tool, so checking more often or changing your configuration will not push past it.

How do I know if my archive is missing older posts?

That is the difficult part, because nothing fails. The feed keeps checking on schedule, keeps reporting success, and simply finds nothing new. The signal to look for is a heavy poster whose archive has a clear oldest item that never gets older, especially if you know they were active before that date.

Can I get the older posts back?

Yes, up to a point. Running Deep Sync on a Twitter feed in StreamStash recovers posts from well before where an ordinary check gives up, which on busy creators can be thousands of items reaching back years. It cannot recover posts that have been deleted, or that X no longer serves at all.

Will a deep pass hold up my other feeds?

No. A large backlog is worked through in stages: the feed takes a turn, hands back to your other feeds, then picks up exactly where it stopped. You press Deep Sync once and it carries on until it is done, with a note on the feed showing progress including while it is waiting its turn.

Does it ignore my text and repost settings?

No. If you have capped how much tweet text or how many reposts a feed collects, those caps apply exactly as before. The deeper pass only looks for photos and videos, so it fills in the media without dragging in text or reposts you asked it to leave alone.

Do I need to run it on new feeds?

No. Any Twitter feed added from this version onwards goes after the full history on its first check, whatever its text and repost settings. Deep Sync is only needed for creators you were already following beforehand.