You log in one morning and your favorite Mastodon instance is gone. The page won’t load. Your timeline is silent. Panic sets in as you realize all those posts, replies, and conversations might be lost forever. This scenario is more common than most people think. Small instances run by volunteers can disappear overnight due to costs, burnout, or technical failures. Understanding what happens to your data during a Mastodon instance data shutdown is the first step to protecting your digital life.

How Mastodon Data Storage Works

Mastodon is decentralized. Your data lives on the server where you signed up, not on a central platform like Facebook or Twitter. When you post a toot, follow someone, or send a direct message, that information is stored in a PostgreSQL database on your home instance. The server also holds media files like images and videos.

Other instances in the fediverse only cache pieces of your content. They store copies of your public posts so their users can see them in their federated timeline. But the master copy always stays on your home server. If that server goes down, the cached copies on other instances might remain for a while, but they are not reliable.

Your account is like a library card tied to one specific library. If that library closes, your card is no longer valid anywhere else. You cannot simply walk into another instance and claim your old identity.

What Actually Vanishes During a Shutdown

When a Mastodon instance data shutdown happens, several things disappear immediately. Your profile page becomes unreachable. Your username, display name, bio, and avatar are gone. All your toots, including public, unlisted, and private posts, vanish from the internet. Direct messages you sent or received are lost unless the recipient already saved them.

Your follower and following lists are stored in the database. When the server goes offline, those connections break. Other instances will eventually remove references to your account from their databases. Your followers on other servers will see a broken link where your profile used to be.

Any media you uploaded, like profile pictures or post attachments, is also gone. If you linked to those images from outside the fediverse, those links will return 404 errors.

What Survives (and for How Long)

Some pieces of your data can survive a shutdown, but only temporarily. Other instances that followed your account may keep cached copies of your public toots for a few days or weeks. The exact duration depends on how each instance handles cache cleanup.

Your account may appear in search results on other instances for a short time. But without a live server to confirm your identity, those results become stale references.

If you ever exported your data archive before the shutdown, you still have your posts, media, and account metadata. That export is a JSON file containing everything you created. It does not include other people’s replies to you or your direct messages from others.

The Three Stages of an Instance Shutdown

Not all shutdowns happen instantly. Understanding the stages can help you act in time.

1. The warning stage. The admin announces the instance will close. This is your window to export your data. You can download your archive from the preferences menu. You can also update your profile with a redirect to a new account.

2. The offline stage. The server stops responding. Your data is still on the hard drive, but nobody can access it. If the admin has not deleted the database, there is a chance they could restore it later.

3. The deletion stage. The admin wipes the server or lets the hosting lapse. The database is destroyed. Your data is gone permanently.

The best time to act is during stage one. If you miss that window, your options become very limited.

How to Save Your Data Before It Is Too Late

If your instance is still running, take these steps right now. Do not wait for a shutdown announcement.

• Go to your preferences and select “Import and export.”
• Click “Export data.” This creates a downloadable archive of your toots, media, and account details.
• Download the archive to your computer. Store it in a safe place, like an external drive or cloud storage.
• Export your following list. This is a separate CSV file that lists every account you follow.
• Export your lists. If you use lists to organize your timeline, save those too.
• Take screenshots of your profile and any important conversations.

If your instance is already offline, check if the admin has set up a read-only mode or a data recovery page. Some admins provide a temporary download link for user data before pulling the plug.

Migrating to a New Instance

Once you have your data, you need a new home. Mastodon includes a migration feature that lets you move your followers to a new account. This process requires both your old and new accounts to be active at the same time.

Here is how migration works in practice:

1. Create a new account on a different instance.
2. On your old account, go to preferences and select “Move to a different account.”
3. Enter the handle of your new account.
4. On your new account, confirm the migration request.
5. Your old followers will see a notice that you moved. They can choose to follow your new account automatically.

The migration only transfers your followers. Your posts, media, and account history stay on the old instance. That is why exporting your archive is still important.

If your old instance is already down, you cannot use this migration feature. You will need to rebuild your follower list manually. That is why you should export your following list as a CSV file. You can use that list to find and refollow people on your new instance.

What Admins Should Do Before Shutting Down

If you run a Mastodon instance and need to close it, you have a responsibility to your users. A responsible shutdown protects the community’s data.

1. Announce the closure at least two weeks in advance. Give users time to export their data and migrate.
2. Enable the data export feature for all users. Some instances disable it to save resources. Turn it back on.
3. Provide a way for users to download their archives after the shutdown. A simple static page with download links is enough.
4. Share a copy of the database with any user who requests it. The database contains their personal data, and they have a right to it.
5. Delete the server data only after a reasonable grace period. Thirty days is a common standard.

Admin Action	User Benefit	Risk if Skipped
Announce closure	Time to export	Users lose all data
Enable exports	Personal archive	No way to recover toots
Provide post-shutdown downloads	Grace period for late users	Permanent data loss
Share database copy	Full account recovery	Legal exposure
Wait before deletion	Last chance to save	Unrecoverable loss

“The difference between a good shutdown and a bad one is communication. Tell your users what is happening, give them time, and let them take their data. That is the ethical path.” — Mastodon server admin community guideline

Common Mistakes Users Make

Many people assume their data is safe because the fediverse is decentralized. That is not true. Decentralization means your data is spread across many servers, but the master copy is still on one server. If that server dies, the network cannot rebuild it.

Another mistake is relying on other instances to cache your content. Cached data is temporary. It is not a backup. You cannot control when other admins clear their caches.

Some users think their account can be transferred to a new instance automatically. It cannot. Your account is tied to the domain name of your home server. You cannot take your username with you. You have to create a new account and tell people where you moved.

The Tools That Help You Stay Safe

Several tools and practices can reduce the risk of data loss. Use them before a crisis happens.

• Mastodon’s built-in export. Run this monthly. It takes seconds.
• Third-party backup tools. Some developers have created scripts that back up your account data automatically. Check the fediverse for community-maintained tools.
• Cross-instance following. You can follow accounts from multiple instances using a client that supports multiple accounts. This way, if one instance goes down, you still have access to your network through another account.
• Personal media hosting. Store your images and videos on your own server or a reliable cloud service. Link to them from Mastodon instead of uploading directly. If your instance shuts down, your media stays online.

For a broader look at how the platform works, check out our guide on mastering mastodon essential tips for new users navigating the decentralized social platform. It covers the basics of instance choice and account management.

Why Some Instances Shut Down Without Warning

Instances run on donations and volunteer time. The admin might lose interest, face unexpected hosting bills, or deal with personal issues. Some instances are targeted by malicious actors who overload the server with traffic. Others simply cannot keep up with the technical demands of running Mastodon at scale.

Small instances are especially vulnerable. A single admin can burn out quickly. If that person walks away without handing over the keys, the instance dies with them. Larger instances with multiple admins and funding are more stable, but they are not immune.

Understanding these risks helps you choose your instance wisely. A large, well-funded instance with a transparent team is safer than a one-person operation. But even the safest instance can fail. Always keep a backup.

What to Do If Your Instance Is Already Down

If you are reading this because your instance just disappeared, do not panic. There are still steps you can take.

First, check if the domain still resolves. Sometimes the server is just overloaded, not dead. Wait a few hours and try again.

Second, search for the admin on other platforms. They might have posted an update on Twitter, Reddit, or a fediverse forum. Look for any announcement about the shutdown.

Third, contact the admin directly if you have their email. Ask if they can provide a database dump or an export of your account.

Fourth, use the Wayback Machine to see if your profile page was archived. This is a long shot, but it sometimes works.

Finally, start rebuilding. Create a new account on a stable instance. Use your exported following list to find your old connections. Post a toot announcing your new handle and ask your followers to find you again.

For more context on why instance choice matters, read our article on why your mastodon instance choice defines your social experience. It explains the factors that make an instance trustworthy.

The Hard Truth About Data Ownership

You do not own your Mastodon account. You rent space on someone else’s server. That is true for every social platform, centralized or decentralized. The difference is that Mastodon gives you tools to take your data with you when you leave. But those tools only work if you use them before the server goes dark.

Think of your Mastodon instance as a landlord. If the landlord sells the building, you have to move out. You can take your furniture and your belongings, but you cannot take the apartment itself. Your data is your furniture. Export it often.

A Practical Backup Schedule

Set a reminder on your phone to export your Mastodon data on the first day of every month. This takes less than five minutes. Store the archive in a folder on your computer or a cloud drive. If you are a power user with lots of posts, consider exporting weekly.

Keep a copy of your following list in a safe place. That list is the key to rebuilding your network. Without it, you have to remember every account you followed.

If you run an instance, back up your database daily. Use automated scripts to create snapshots of your PostgreSQL database. Store those backups offsite. A simple cron job can save you and your users from a disaster.

What the Future Holds

The fediverse is still young. Tools for data portability are improving. Some projects are working on standards that let you move your entire identity between instances without losing your followers or posts. But those tools are not ready yet.

Until they arrive, the responsibility for data safety falls on you. The fediverse gives you freedom, but freedom comes with homework. Export your data. Choose your instance carefully. Stay informed.

For a look at the broader landscape, check out our piece on the future of social media with mastodon and decentralized networks. It discusses where the technology is heading and what that means for your data.

Protecting Your Digital Life in a Decentralized World

A Mastodon instance data shutdown does not have to mean the end of your social media presence. With a little preparation, you can walk away with everything that matters. Your words, your connections, and your identity can survive the closure of any single server.

Start today. Open your preferences and export your archive. Save your following list. Pick a backup instance where you can land if your main one goes dark. These small actions cost almost nothing, but they protect months or years of your online life.

The decentralized web is powerful because it puts control back in your hands. Use that control. Take ownership of your data before someone else decides to turn off the lights.