Mastodon allows you to download an archive of your account data, including posts, media, followers, and lists. However, you cannot request an export every few minutes. The server enforces a cooldown period between export requests to prevent abuse and reduce server load. This article explains the exact frequency limit, how to check your next eligible export time, and what to do if the button appears grayed out.
Understanding the export limit helps you plan bulk data backups or instance migrations. The limit is not adjustable by end users, but knowing the timing lets you avoid frustration when the export button does not respond. This guide covers the default cooldown value, how the server counts requests, and workarounds if you need an export sooner.
Key Takeaways: Mastodon Export Frequency Limit
- Preferences > Import and export > Export: The default cooldown between export requests is 7 days from the last successful export.
- Server-side rate limit variable: Instance administrators can change the cooldown period in the Mastodon configuration file.
- Error message “You have already requested an export recently”: Indicates the cooldown has not expired; wait the remaining time before retrying.
Why Mastodon Limits Export Frequency
Mastodon exports generate a compressed archive containing all your public and private data. Generating this archive consumes CPU time, disk I/O, and database queries. If every user requested an export every hour, the server could slow down or become unresponsive for other activities. The cooldown protects the instance from accidental or intentional denial-of-service conditions.
The default cooldown is 7 days after the last successful export. This value is stored in the Mastodon configuration under the EXPORT_LIMIT environment variable or in the config/settings.yml file. Instance admins can set it to any number of seconds. A typical custom value is 86400 seconds, which equals 24 hours. Some very small instances may set it to 0, effectively disabling the limit.
How the Server Tracks Export Requests
When you click the export button, Mastodon creates a background job that compresses your data. The job writes a timestamp to the database for your user record. The next time you visit the export page, the server compares the current time with that timestamp. If the difference is less than the configured cooldown, the export button appears grayed out or returns an error message.
The limit applies per account, not per IP address. If you have multiple accounts on the same instance, each account has its own independent cooldown timer. Deleting and recreating the account does not reset the timer for the same username because the database record persists until the account is fully removed.
Steps to Check Your Export Eligibility and Request an Export
Follow these steps to verify whether you can request an export and to initiate the process when the cooldown has expired.
- Open Preferences
Click the gear icon in the Mastodon web interface or navigate to Preferences from the user menu in the top-right corner. - Go to Import and export
In the left sidebar, click Import and export. This page shows both import and export options. - Check the export button status
Look for the Export section. If the button says Request your archive and is clickable, the cooldown has expired. If it is grayed out or shows a message like You have already requested an export recently, you must wait. - Click Request your archive
If the button is active, click it. Mastodon schedules the archive generation. You will receive a notification when the archive is ready, usually within a few minutes. - Download the archive
After the notification appears, return to the same Import and export page. A download link for the.tar.gzfile appears. Click it to save the archive to your computer.
What to Do If the Export Button Is Grayed Out
If the export button is inactive, you can estimate when it will become available again. The error message usually does not display the exact remaining time. However, you can check the last export timestamp by viewing the browser developer tools network tab when the page loads, or by contacting your instance admin. In most cases, simply wait 7 days from the last export.
Common Issues and Misunderstandings About Export Limits
Export Button Shows “Request your archive” but Nothing Happens When Clicked
If the button appears active but clicking it does nothing, the browser may have cached a stale page. Refresh the page with Ctrl+F5 on Windows or Cmd+Shift+R on Mac to force a full reload. If the problem persists, clear your browser cache for the Mastodon domain.
Export Limit Resets After an Unsuccessful Attempt
If the archive generation fails due to a server error, the cooldown timer does not reset. You must wait the full period before trying again. Check the server status or contact the admin if failures repeat.
Instance Admin Changed the Limit Without Notice
Some admins reduce the limit to 24 hours or increase it to 30 days. If you believe the cooldown is unusually long, ask the admin directly. They can check the EXPORT_LIMIT value in the server configuration.
Export Archive Contains Old Data After a Recent Post
The export captures a snapshot of your data at the moment the archive job runs. If you posted new content after requesting the export but before downloading, that new content is not included. You must wait for the cooldown to expire and request a new export to get the latest data.
Mastodon Export Limit vs Other Social Platforms
| Item | Mastodon | Twitter / X | |
|---|---|---|---|
| Default cooldown period | 7 days (configurable) | 30 days | No fixed limit; may take hours to generate |
| Data included | Posts, media, followers, lists, bookmarks, account settings | Tweet archive, media, direct messages, account data | Photos, posts, messages, friends list |
| Admin override possible | Yes, via EXPORT_LIMIT variable |
No | No |
| Notification when ready | In-app notification | Email notification | Email notification |
| Format | tar.gz containing CSV and JSON files | ZIP containing HTML and CSV files | ZIP containing HTML and media files |
Mastodon offers more flexibility for instance admins and includes a wider range of data than Twitter. The 7-day default is a reasonable balance between user convenience and server stability.
Conclusion
You now know that Mastodon enforces a 7-day cooldown between export requests by default, and you can check your eligibility on the Preferences > Import and export page. If you need to export data more frequently, ask your instance admin to adjust the EXPORT_LIMIT setting to a lower value such as 86400 seconds for a 24-hour window. For migration planning, consider exporting your data at least one week before the move to avoid timing conflicts with the cooldown.