You compose a post in Mastodon, press the publish button, and nothing happens. The post may appear stuck, the button may remain gray, or an error message may flash briefly. This problem usually occurs because of a network issue, a content validation failure, or a server-side limitation. This article explains the most common reasons a Mastodon post fails to send and provides direct fixes for each cause.
Key Takeaways: Why Your Mastodon Post Is Not Sending
- Content warning or sensitive media toggle: Posts with media marked as sensitive require explicit user confirmation before sending.
- Character limit or poll option limit: Mastodon enforces a 500-character default limit and a maximum of four poll options.
- Server rate limiting: Posting too quickly triggers a temporary block from your instance server.
Why a Mastodon Post Fails to Send
Mastodon processes each post through a validation pipeline before it reaches the server. The pipeline checks character count, media file size, content warning flags, and duplicate content. If any check fails, the server returns an error and the post does not send.
The most common root causes fall into three categories: client-side validation, server-side validation, and network interruption. Client-side validation happens in your browser or app before the data leaves your device. Server-side validation happens on the Mastodon instance after the data arrives. Network interruption can occur anywhere between your device and the server.
Understanding which category your problem falls into helps you apply the correct fix quickly. The steps below cover each category with specific troubleshooting actions.
Steps to Diagnose and Fix a Mastodon Post That Will Not Send
- Check the character count
Look at the character counter below the compose box. If the number is red or shows a negative value, the post exceeds your instance limit. Delete text until the counter shows a positive number. The default limit is 500 characters. Some instances allow up to 5000 characters. - Verify content warning and sensitive media settings
If you attached media and toggled the sensitive media switch, Mastodon requires you to also add a content warning. Open the compose box, click the content warning field, and type a short label such as NSFW or Spoiler. Then try sending again. - Remove or reduce media attachments
Mastodon limits the total size of attached media to 8 MB per post on most instances. If you attached a video or high-resolution image, reduce the file size or remove files. Compress images to under 2 MB each using an image editor. Then repost. - Check poll options
If you added a poll, make sure you have at least two options and no more than four options. Each option must have text. Delete empty or duplicate options. Then click publish. - Wait for rate limiting to expire
If you posted several messages in the last few minutes, your instance may temporarily block new posts. Wait 5 to 10 minutes. Then try sending one post. Rate limits vary by instance but typically allow 1 post every 2 to 5 seconds. - Test your internet connection
Open another website in your browser. If it does not load, your internet connection is down. Restart your router or switch to a different network. Then return to Mastodon and try again. - Clear browser cache or restart the app
Outdated cached files can block the compose form from submitting. In a browser, press Ctrl + Shift + Delete, select Cached images and files, and click Clear. In the Mastodon mobile app, force close the app and reopen it. - Try posting without custom emoji
Custom emoji from other instances may not load correctly. Delete any custom emoji from your post and use standard Unicode emoji instead. Then send the post. - Disable browser extensions
Ad blockers and script blockers can interfere with Mastodon’s compose form. Temporarily disable all extensions. Reload the Mastodon page. Try sending the post again. - Use the Mastodon web interface instead of a third-party app
Third-party apps may have bugs that prevent posting. Open the official Mastodon web interface at your instance URL. Compose and send the same post there. If it works, the issue is in your app. Update the app or switch to a different one.
If Mastodon Still Has Issues After the Main Fix
Post Contains a Blocked Domain or URL
Mastodon instances can block specific domains. If your post includes a link to a blocked domain, the server rejects the entire post. Check your instance’s domain blocks by visiting Preferences > Moderation > Domain blocks. Remove the link from your post and try again.
Server Is Under Maintenance or Overloaded
Sometimes the problem is not on your side. The Mastodon instance may be down for maintenance or experiencing high traffic. Check the instance status by visiting status.example.com if your instance provides a status page. Alternatively, ask in the instance’s support channel on Mastodon. Wait until the server is back online.
Account Is Suspended or Limited
If your account was suspended or limited by the instance admin, you cannot send new posts. Check your email for a notification from your instance. If you believe the action was an error, contact the admin using the contact information on your instance’s about page.
Post Contains Duplicate Content
Some instances use anti-spam filters that block posts identical to recent posts from the same account. Change the wording of your post. Add a few unique words. Then try sending again.
Mastodon Post Failures: Browser vs App vs Third-Party Client
| Item | Browser (Web UI) | Official Mobile App | Third-Party Client |
|---|---|---|---|
| Character limit check | Real-time counter | Real-time counter | May not show counter |
| Media size limit | Shows error before sending | Shows error before sending | May fail silently |
| Rate limiting | Shows error message | Shows error message | May show generic error |
| Content warning enforcement | Forces CW field | Forces CW field | May not enforce |
| Blocked domain detection | Server-side only | Server-side only | Server-side only |
Third-party clients often lack real-time validation. When a post fails in a third-party client, switch to the official web interface to confirm the exact error message.
Conclusion
A Mastodon post that will not send usually points to a character limit, content warning requirement, media size issue, or rate limit. By checking the character counter, confirming content warning settings, and reducing media file sizes, you can resolve most failures within a minute. If the problem persists, test your internet connection, clear your browser cache, or switch to the official web interface. For posts that still fail, review your instance’s domain blocks and account status. The official Mastodon web interface at your instance URL provides the most reliable posting experience.