What Happens to Your Mastodon Bookmarks When an Instance Shuts Down (and Why the Archive Survives)

An instance called mstdn.social has about 900,000 accounts on it. A smaller one, say a 200-person Mastodon server run by one guy on a Hetzner box, can disappear whenever that guy stops paying the bill or gets tired of moderating it. Both things count as "an instance," and the fediverse treats them the same way: no guarantee either one stays up.

That's the tradeoff nobody explains clearly when they tell you to try Mastodon. On X, your bookmarks live on X's servers. On Mastodon, your bookmarks live on whatever instance you signed up with, and if that instance shuts down, defederates, or the admin just walks away, your bookmarked posts go with it. Not "become harder to find." Gone.

An author can also delete a post outright. Or an instance can defederate from part of the network, which quietly breaks every reply thread and quote that crossed that boundary. Or an account can migrate to a new instance and the old posts don't necessarily come along. None of this is a bug in Mastodon. It's what running on a federated network of independently operated servers actually means.

Birdfeeder's answer is to stop treating the bookmark as a pointer and start treating it as a copy. As soon as you bookmark a post, Birdfeeder stores its full text and media in your own archive. That happens quietly in the background from your home instance, so every save gets captured without you doing anything extra. On signup we also pull your entire back catalogue in one pass, so your history is backed up from day one, not just going forward.

Practically: if the instance that hosted a post you bookmarked shuts down tomorrow, your copy in Birdfeeder doesn't care. The text is already sitting in your archive, full-text searchable alongside everything else you've saved. You're not relying on the fediverse to keep serving you a URL that a server operator you've never met has to keep paying for.

Mastodon bookmarks are private by default, and Birdfeeder keeps that: your archive stays yours unless you choose to publish individual posts to a public Birdfeeder profile. That's a separate, deliberate action, not something that happens because a post became public on the fediverse.

One account in Birdfeeder can also hold your X, Bluesky, and Mastodon identities at once, so if you're bookmarking across two or three networks you get one search across all of it instead of three separate histories that each depend on their own platform staying online. There's a weekly summary email if you want a digest instead of digging through search, and on the yearly plan you can export the whole archive to CSV, TSV, JSON, or Excel if you want your own copy of the copy.

None of this stops instances from shutting down. People run these servers as a hobby or a side project, and some of them will stop. The point of Birdfeeder isn't to prevent that. It's that when it happens, the post you cared about enough to bookmark is already somewhere else, in a place that isn't going anywhere because one person decided to turn off a VPS.