How to Archive an X Search, Not Just an Account

Archiving tools generally assume you know whose account you want. That is fine when you are following a specific creator, and no help at all when what you care about is a subject, an event, a hashtag or a phrase that dozens of accounts will post about. This post covers how to save an X search as an ongoing feed, how to narrow it before you commit to it, and the two failure modes that make naive search archiving useless.

Why account-only archiving falls short

Nearly every social archiver is built around the account as the unit of work. You supply a username, it walks that user's timeline, it keeps what it finds. That model is a good fit for the most common case, which is wanting a specific creator's work preserved.

It breaks down as soon as the thing you care about is not a person.

Consider a live event, an ongoing news story, a niche community's shorthand, or a piece of media that keeps resurfacing. In each case the content you want will be posted by accounts you have never heard of, and by the time you have identified them the posts you wanted are already several days deep and possibly deleted. Building a list of accounts to monitor is chasing the problem rather than solving it.

The thing you actually want to follow is the search.

Saving a search as a feed

In StreamStash, this is deliberately the same flow as adding a creator, because a saved search is meant to behave like any other feed once it exists.

1. Open Add User.
2. Choose Twitter.
3. Switch the box from Account to Search.
4. Type what you are looking for, instead of a username.

From that point it works the way the rest of your library does. The feed is checked on the interval you set, new matching posts are downloaded into your local library, and each post is credited to whoever actually posted it rather than being attributed to the search. Its contents show up in search and in the library alongside everything else, and removing the search wipes its files like any other feed.

Saved searches get their own section on the Twitter page rather than being mixed in with your creator feeds, which matters more than it sounds. A search feed and a creator feed behave the same but mean different things, and having twenty of each in one undifferentiated list gets confusing fast.

Narrowing the search before you commit

This is the part worth spending time on, and the part most people skip.

Anything you would type into X's own search box works here. That gives you a lot of control before a single post is downloaded:

• Restrict to posts from a particular account, so you follow a topic only as one person covers it.
• Require that a post has media attached, which cuts an enormous amount of noise if what you want is images and video.
• Set a minimum number of likes, which is a crude but effective quality filter on a busy term.
• Exclude a word entirely, which is usually how you deal with a term that collides with something unrelated.

You can also paste a search link straight from X. That is often the easiest route: build the search on X where you can see the results as you tune it, and paste the finished thing in once you are happy with it.

Start narrower than you think you need to. A broad search on a popular term can match thousands of posts an hour. That is not a rate limit problem so much as a storage and attention problem: you end up with a feed nobody can review, full of content that only technically matched. It is far easier to loosen a search that is too tight than to clean up after one that was too loose.

The viral-post problem

Here is the failure mode that makes naive search archiving worthless, and it is worth understanding because it is not obvious until it happens to you.

When a post does well, it gets shared by hundreds of accounts. Every one of those shares is a separate post, by a separate account, and every one of them matches your search independently. A search that is working perfectly correctly will therefore return the same underlying video several hundred times, from several hundred different accounts, over the course of a day.

Without handling, your feed becomes almost entirely copies of whatever went viral that week, and the posts you actually set the search up for are buried underneath.

The fix is that saved searches have their Retweets toggle off by default. Each of those hundreds of shares is a repost wrapper around the same underlying media, and with the toggle off they are skipped, so you get the original once rather than a wall of near-identical entries.

This is worth knowing rather than just relying on, because the toggle is yours to change. Saved searches deliberately do not force the setting either way, so if you switch Retweets on for a search you take the flooding back with it. That is occasionally what you want, if the thing you are studying is how something spread rather than the thing itself. Most of the time it is not.

Choosing how much history to pull

When you save a search, you are asked how far back the very first check should go, from the last 200 matches up to everything.

This only affects the initial catch-up. Later checks only look for new posts, so the setting is about how much backlog you want up front, not about ongoing behaviour.

The considerations cut both ways. Pulling everything on a long-running term is a large download and can take a while. Pulling only the last 200 on a busy term might cover just a few hours. There is no need to agonise over it, though, because if you decide later that you want more, Deep Sync goes back further whenever you like. Your X Bookmarks feed offers the same choice when you first set it up.

Living with a search feed

A saved search gets the same controls as your creator feeds: check interval, tweet text capture, favourites, notes and Deep Sync. In practice, two of those matter more on a search than they do on a creator.

Check interval is a real decision on a busy search. A term that produces a steady trickle is fine on a long interval. A term attached to a live event needs a short one for the duration and can be relaxed afterwards.

Notes are worth using here specifically because a search feed's name does not always explain itself six months later. Writing down what you were trying to capture, and why you narrowed it the way you did, costs nothing at setup and saves a lot of confusion when you come back to it.

What a search feed will not do

Two honest limits are worth stating.

First, a search feed inherits whatever X's search will actually return. If X does not surface something in search results, a search feed cannot save it. This is the same boundary that applies to any archiver working through a platform's own interfaces, and it is why account feeds and search feeds complement each other rather than one replacing the other.

Second, a search feed is not a substitute for archiving accounts you care about. If there is a specific creator whose work you want preserved, follow them directly. A search that happens to match some of their posts will keep some of their posts, which is not the same thing at all.

The useful mental model is that account feeds preserve people, and search feeds catch subjects. Most libraries want some of each. If you are already running account feeds and finding they stop short of a creator's older material, that is a separate limit with a separate fix, covered in how to reach older tweets past X's media limit.

FAQ

Can I archive X search results instead of a specific account?

Yes. In StreamStash, open Add User, choose Twitter, and switch the box from Account to Search. Type what you are looking for instead of a username and it is saved as a feed that keeps every new matching post, the same way a creator feed keeps that creator's posts.

What search syntax can I use?

Anything you would type into X's own search box. That includes narrowing to a particular account, requiring media on the post, setting a minimum number of likes, or excluding a word entirely. You can also paste a search link straight from X and it will be used as-is.

Will a viral post fill my feed with hundreds of copies?

Not by default. When a post does well it gets shared by hundreds of accounts, and each of those shares is a separate search hit for the same underlying media. Saved searches have their Retweets toggle off by default, which skips those repost wrappers, so you get the original once rather than hundreds of near-identical entries. If you deliberately switch Retweets on for a search, that protection goes with it and a viral post will arrive many times over.

How far back does a saved search go?

You choose when you set it up, from the last 200 matches up to everything. Later checks only look for new posts, so that choice only affects the initial catch-up. If you decide later that you want more, Deep Sync goes back further whenever you like.

Do saved searches count against my feed limit?

Yes. A saved search behaves like any other feed, so it uses a feed slot. The Free tier covers Twitter/X with a limit of 5 monitored feeds; the paid tiers raise that.

Can I still archive individual accounts?

Yes, and most people do both. Saved searches get their own section on the Twitter page, separate from your creator feeds, with the same controls: check interval, tweet text, favourites, notes and Deep Sync.