You want to share a message with only people on your home instance, but standard Mastodon posts always reach the wider fediverse. Mastodon Glitch Edition includes a local-only posting feature that keeps your toot visible only to users on the same server. This article shows you how to enable and use local-only posts on any Glitch Edition instance.
Key Takeaways: Enabling Local-Only Posts in Glitch Edition
- Compose window visibility dropdown: Select the Local-Only option to restrict a post to your instance only.
- Instance admin feature flag: Your server admin must enable the
local_onlyfeature in the Glitch Edition settings. - No federation indicator: Local-only posts show a lock icon with a globe crossed out; they never reach other instances.
What Is a Local-Only Post in Glitch Edition
Standard Mastodon posts are public by default and federate to other servers. Glitch Edition adds a visibility level called Local-Only. When you select this option, the post is stored only on your home instance. Other instances cannot fetch or display it. This is useful for instance announcements, community polls, or casual chat that should not leave the server.
The feature is not available in upstream Mastodon. It is a Glitch Edition fork enhancement. The setting is controlled by the instance administrator. If your admin has not enabled the local_only feature flag, you will not see the Local-Only option in the compose box.
A local-only post behaves like a public post within your instance. It appears in the local timeline, public timeline, and profile page of the author. Users on other instances cannot see it at all. The post does not generate any federation activity. It is effectively invisible to the rest of the fediverse.
How to Enable and Use Local-Only Posts
Before you start, confirm that your instance runs Glitch Edition. Check the server footer or About page for the software version. If it says Mastodon Glitch Edition, you are on the right fork. If you see only Mastodon, you need to ask your admin to switch to Glitch Edition or enable the feature.
- Open the compose window
Click the compose button or press N on your keyboard. The compose box appears at the top of your home timeline. - Locate the visibility dropdown
Next to the post button, you see a small globe icon or text showing the current visibility. Options include Public, Unlisted, Followers-Only, and Direct. - Select Local-Only from the dropdown
Click the visibility button. A menu opens. Choose Local-Only. The icon changes to a lock with a globe crossed out. The post button now reads Local-Only. - Write your post and send it
Type your message. Add media, polls, or content warnings as needed. Click the post button. The post appears only in your instance. No other server receives it. - Verify the post visibility
Open the post on your profile. Look for the Local-Only badge next to the timestamp. If you log out or view the post from a different instance, you cannot see it.
If you do not see the Local-Only option, the admin has not enabled it. Contact your instance admin and ask them to check the Glitch Edition feature settings. They need to set the local_only feature to enabled in the admin dashboard.
Common Issues and Limitations of Local-Only Posts
Local-Only Option Missing in Compose Box
This is the most frequent issue. The option is hidden because the admin has not flipped the feature flag. Log in as an admin and go to Administration > Server Settings > Features. Toggle the Local-Only Posts option to on. The setting takes effect immediately. No restart is needed.
Local-Only Posts Still Federating
This should not happen if the feature is correctly enabled. Check that you selected Local-Only from the dropdown, not Public or Unlisted. If the post already federated, delete it and repost with the correct visibility. If the problem persists, the instance may have a custom patch that overrides the feature. Contact the admin.
Third-Party Apps Do Not Show Local-Only Option
Most third-party Mastodon clients do not support Glitch Edition extensions. Use the official Glitch Edition web interface or a compatible app like Tusky or FediLab. If you must use a third-party app, compose the post in the web interface first, then switch to the app for reading.
Local-Only Posts Cannot Be Boosted or Favorited by Remote Users
This is by design. Since the post never leaves your instance, remote users cannot interact with it. Only users on your home instance can boost, favorite, or reply. This limitation is not a bug. It is the core purpose of the feature.
Local-Only Posts vs Standard Mastodon Visibility Levels
| Item | Local-Only (Glitch Edition) | Public (Standard) |
|---|---|---|
| Visibility on home instance | Visible in local timeline and profile | Visible in local timeline and profile |
| Visibility on other instances | Not visible at all | Visible if federated |
| Federation behavior | No federation activity | Post is sent to all connected servers |
| Boost and favorite by remote users | Not possible | Possible |
| Admin feature flag required | Yes | No |
Local-Only posts fill a gap that standard Mastodon does not address. They give instance communities a private space without requiring a separate server or group account.
You can now create posts that stay within your Mastodon instance using the Local-Only visibility option in Glitch Edition. Ask your admin to enable the feature if it is missing. For your next community poll or internal announcement, choose Local-Only from the compose dropdown instead of Public. This keeps the conversation contained and reduces unnecessary federation traffic.