How to Fix Mastodon Error ‘This Post Has Been Removed’ on Reply

You tap Reply on a Mastodon post and see the error message “This post has been removed.” The post still appears in your timeline, but you cannot reply to it. This usually happens because the original post was deleted or its visibility changed after it was fetched by your instance. This article explains the exact cause of this error and gives you step-by-step fixes to resolve it on both the web interface and mobile apps.

Why Mastodon Shows “This Post Has Been Removed” When You Reply

Mastodon is a federated network. Your home instance fetches and caches posts from other servers. When you see a post in your timeline, your instance holds a local copy. If the original author deletes the post, or if they change its visibility from public to followers-only or direct, your cached copy becomes invalid. When you try to reply, your instance checks the original post’s status. If the post no longer exists on the author’s server or is no longer visible to you, Mastodon returns the “This post has been removed” error.

Another common cause is a moderation action. The author’s instance moderator may have deleted the post for policy violations. In that case, the post disappears from the author’s server, but your instance may still display it until the next cache refresh. Your reply attempt fails because the source post is gone.

A third scenario involves deleted or suspended accounts. If the author deletes their account, all their posts vanish from the network. Your instance keeps a cached copy until the deletion propagates across the federation. Replying during this window triggers the error.

Steps to Fix the “This Post Has Been Removed” Error

1. Refresh your timeline
   Press F5 on the web interface or pull down to refresh in the official Mastodon app for Android or iOS. This forces your instance to re-fetch the timeline and remove stale cached posts.
2. Open the post directly on the author’s instance
   Click the timestamp of the post to open its permalink. If the URL takes you to your own instance, copy the post URL and change the domain to the author’s instance. If the post loads on the author’s instance, you can reply from there. If it shows a 404 or “This post has been removed,” the post is genuinely gone.
3. Use a third-party Mastodon client
   Apps like Tusky, Fedilab, or Moshidon sometimes cache posts differently and may allow replying even when the official web interface blocks it. Install one of these clients, log in, find the post, and try replying.
4. Clear the browser cache for your Mastodon instance
   In your browser settings, clear cached images and files for your instance’s domain. On Chrome, go to Settings > Privacy and security > Clear browsing data, select “Cached images and files,” set the time range to “All time,” and clear data. Reload Mastodon and try again.
5. Try replying from a different device or browser
   Use a private browsing window or a different browser. This avoids any cached data that may be interfering with the reply action.
6. Use the Mastodon API directly
   Advanced users can send a POST request to /api/v1/statuses with the in_reply_to_id parameter set to the post’s ID. If the post is truly deleted, the API returns a 404 error. If the API succeeds, the reply is created despite the web interface error.

If Mastodon Still Shows the Error After the Main Fixes

The post was deleted by the author or moderator

If the post is truly gone, you cannot reply to it. The only workaround is to compose a new post that quotes or references the original, but you cannot attach a direct reply chain. Use the “Copy link to post” option to preserve the original post’s URL for context.

The post’s visibility changed to followers-only or direct

If the author changed the post’s visibility after you saw it, you may no longer have permission to view or reply to it. Follow the author on their instance and ask them to change the visibility back to public if they want you to reply.

The author’s instance is blocking your instance

Some instances block or limit federation with others. In that case, your instance cannot verify the post’s existence. The error appears even if the post is still public. You cannot reply from your instance. Use the author’s instance URL to reply directly, or ask the author to boost your reply from their account.

Mastodon Web Interface vs Third-Party Client: Error Handling Comparison

Item	Official Web Interface	Third-Party Client (Tusky, Fedilab)
Cache handling	Heavy caching of remote posts	Lighter caching, more frequent refresh
Error message on reply	“This post has been removed”	May show “Post not found” or allow reply
Ability to reply to deleted post	Blocks reply completely	Sometimes succeeds if post still exists on author’s instance
Workaround options	Refresh, clear cache, use permalink	Direct API access, alternate cache

You now know why Mastodon shows the “This post has been removed” error when you try to reply. The most reliable fix is to open the post on the author’s instance and reply from there. If the post is genuinely deleted, compose a new post with context instead of forcing a reply chain. For advanced users, the Mastodon API provides a direct way to post replies that bypass the web interface’s caching layer.