Your Mastodon server is more than just a place to post. It is a community you are responsible for. Every day, your moderation policies decide what kind of content flows through your local feed and how your members interact with the wider Fediverse. Get the policies right, and you build a space where people feel safe to share. Get them wrong, and your server can become a magnet for spam, harassment, or worse. This guide walks you through the practical side of building and enforcing Mastodon server moderation policies that actually work in 2026.

Start with a Clear Code of Conduct

Before you write a single moderation action, you need a code of conduct. This is your server’s constitution. It tells new users what you expect and gives your moderation team a clear standard to enforce.

A good code of conduct covers these areas:

• Harassment and hate speech. Define what counts. Do not leave room for interpretation.
• Content warnings. Require them for sensitive topics like politics, violence, or adult content.
• Spam and self-promotion. Set limits on how often members can post links to their own projects.
• Bot behavior. Decide if automated accounts are allowed and under what rules.
• Appeals process. Tell users how to challenge a moderation decision.

Your code of conduct should be pinned in your server’s sidebar and linked in your welcome message. Make it impossible to miss.

“A server without a written code of conduct is a server where the loudest voices make the rules. Write it down, or someone else will write it for you.” – Fediverse moderation community, 2026

Build Your Moderation Stack

Your moderation policies are only as good as the tools you use to enforce them. In 2026, Mastodon offers several built-in features plus third-party tools that can help you manage your feed.

1. Server-level filters and word blocks

Set up automatic moderation for common problem terms. Mastodon lets you add server-wide word filters that hide or flag posts containing specific phrases. This catches the obvious stuff before your team has to review it.

2. Report queues and escalation paths

Assign different levels of moderation permissions. Some volunteers can handle spam reports. Others handle harassment. A small team handles appeals. This keeps your workflow organized and prevents burnout.

3. Federation management tools

Use the “limit” and “suspend” features for remote servers that refuse to moderate their own content. If a server consistently sends harassment your way, you can defederate from them entirely.

4. Third-party moderation bots

Bots like fedi-block or custom Ruby scripts can watch for patterns your human moderators might miss. Just make sure any bot you use follows your own code of conduct.

Common Moderation Mistakes (and How to Avoid Them)

Even experienced admins slip up. Here are the most frequent errors and how to steer clear of them.

Mistake	Why It Happens	How to Fix It
Overly broad bans	Admins ban entire servers for one bad user	Use individual user bans first. Only defederate from a server if its admins refuse to act.
No public policy	Rules exist only in the admin’s head	Write everything down. Share it publicly. Update it yearly.
Inconsistent enforcement	Different mods apply different standards	Create a shared decision tree. Hold regular team syncs.
Ignoring appeals	Users feel unheard and leave	Set up a dedicated email or form. Respond within 48 hours.
Too many automated blocks	Word filters catch harmless posts	Review your filter logs weekly. Adjust terms that generate false positives.

A Practical 5-Step Moderation Workflow

Here is a numbered workflow you can implement today. It works for servers of any size.

1. Receive a report. A user flags a post or profile. Your system logs the timestamp and the reporting user (anonymously if desired).

2. Triage the report. A moderator checks if the report violates your code of conduct. If it does not, the report is closed with a note to the reporter explaining why.

3. Apply an action. If it violates policy, the moderator chooses from a tiered set of actions: a warning, a temporary mute, a 24-hour suspension, or a permanent ban. The action matches the severity of the infraction.

4. Document the decision. Log the action, the reason, and the moderator’s name. This creates an audit trail for appeals.

5. Handle appeals. If the user appeals, a different moderator (or a senior admin) reviews the case. They can uphold, reduce, or reverse the original action.

This workflow keeps your team consistent and your community informed.

Handling Cross-Instance Issues

One of the biggest challenges in 2026 is dealing with content that originates on another server. Your moderation policies stop at your server’s border, but the content can still reach your users through federation.

When you see harmful content from another instance, you have two options:

• Report it to the remote server’s admin. Most admins are reasonable and will act on valid reports. Keep a list of contact addresses for servers you federate with regularly.
• Limit or silence the remote server. If the other admin ignores your reports, you can stop their content from appearing in your local feed without fully defederating. This is a middle ground that many servers use.

Remember that your moderation policies can include rules about how your users interact with problematic remote servers. For example, you might require a content warning on any post that boosts content from a server known for low moderation standards.

The Future of Server Moderation in 2026

The Fediverse is growing, and moderation is becoming more collaborative. Many servers now share blocklists and moderation signals with trusted partners. This helps smaller instances benefit from the experience of larger ones.

At the same time, the demand for transparency is rising. Users want to see how moderation decisions are made. Some servers publish regular transparency reports showing how many reports they received, how many actions they took, and how many appeals they granted. This builds trust and sets a standard for the whole network.

If you are just getting started, consider reading how decentralized moderation is reshaping trust on Mastodon in 2026. It covers the collaborative side of this work in more detail.

Build a Safer Feed, One Policy at a Time

Your moderation policies are not a set-it-and-forget-it task. They need regular review, honest feedback from your community, and a willingness to adapt. Start with a clear code of conduct. Build a consistent workflow. Learn from the mistakes other admins have made. And never stop treating your server as the community it is.

The safer your feed, the more your members will trust you. And trust is the only currency that matters in the Fediverse.