How to Disable Chat Reporting on a Minecraft Server (26.3)

Published on

enforce-secure-profile=false alone does not stop chat reports. What does on 26.3: FreedomChat on Paper, No Chat Reports on Fabric, and what players then see.

A Minecraft-style server hall with rows of lit server racks

You run a Minecraft server for friends or a community, and you want to handle chat problems yourself instead of through Mojang's reporting system. The usual advice is one line in server.properties. That line still exists in 26.3, the current Java release, but on its own it does less than the advice suggests. This guide shows what chat reporting is, what enforce-secure-profile=false really changes, which mods and plugins disable chat reporting on 26.3 today, and what the Minecraft Wiki says about Bedrock.

Quick answer: To disable chat reporting on a Java server, set enforce-secure-profile=false in server.properties, restart, and add a server-side tool that turns player chat into unsigned messages: FreedomChat on Paper, Purpur or Folia, or No Chat Reports on Fabric, NeoForge or Forge. Both list 26.3 builds on Modrinth as of 3 November 2026. The setting alone only lets players without signed chat join and talk; players on an unmodded client keep signing their messages, and those messages stay reportable. Skin and name reports, Realms and Bedrock are separate, see below.

What Chat Reporting Is

Since Java 1.19, chat messages are cryptographically signed: each player gets a key pair from Mojang when the game starts, and messages carry a signature from it. Since 1.19.1, players can report a message from the Social Interactions screen (press P, or the Player Reporting button in the pause menu). The No Chat Reports page explains why the signature matters: without it there is "no proof that they were actually sent from your account."

Mojang staff review every report by hand. According to the Minecraft Wiki, outcomes range from no action to a temporary or permanent ban from online play.

Three limits to know before you start:

  • Skins and names. Since 1.20.2, players can also report skins and usernames. Those are not chat reports, and none of the tools below claim to block them.
  • Realms. The wiki says Realms has player reporting "fully enabled and functional, with no way to disable it."
  • 26.x. The wiki's change pages for 26.1, 26.2, 26.3 and the seven 26.4 snapshots so far do not mention chat signing or enforce-secure-profile. In the 26.4 snapshots, a new Other Players menu and Player Options screen replace Social Interactions, and reporting moves there.

What enforce-secure-profile=false Changes

As of 26.3, a new server.properties contains enforce-secure-profile=true. The wiki describes it as "Whether to only allow players with a Mojang-signed public key to join the server," and adds that with it off, "all chat messages will be left unsigned and unable to be reported."

The No Chat Reports author's server guide is more careful. Turning it off "doesn't disable chat reporting by itself, but allows users to join without signing their messages." Players on unmodded clients "will still sign the messages," so other players can report them. That is why you need a server-side tool as well.

What the setting does change:

  • Unsigned players can chat. With the setting on, a client that doesn't sign (for example one with No Chat Reports) can join since 1.19.3, but its chat messages and chat commands fail with an error, the wiki's Chat history says. With it off, those players can chat.
  • Bedrock players on Geyser can chat. Geyser's secure chat page says that if the server or proxy requires signing, "Bedrock players will be unable to chat." Our Geyser and Floodgate guide covers the rest of crossplay.
  • Unmodded players see a warning. The wiki: "Clients will get warned about this when connecting to the server." The toast reads "Chat messages can't be verified."

Stop the server, change the line, and start it again, because changes to server.properties only take effect after a restart:

enforce-secure-profile=false

Our server.properties guide explains the other settings in the file.

Disable Chat Reporting on Paper, Purpur and Folia: FreedomChat

The No Chat Reports guide recommends FreedomChat for Paper and its forks. Version 1.7.10 of 17 September 2026 lists 26.3 for Paper and Folia.

  1. Set enforce-secure-profile=false. FreedomChat's README says it rewrites outgoing chat out of the box, but players whose client mods skip signing still need this setting off before they can chat.
  2. Download the build for your exact Minecraft version. The README warns that "Each Minecraft version has its own plugin version."
  3. Put the jar in plugins/ and restart.
  4. Open plugins/FreedomChat/config.yml, check these values, and restart again:
rewrite-chat: true
claim-secure-chat-enforced: false
send-prevents-chat-reports-to-client: true
rewrite-bedrock-only: false

rewrite-chat (on by default) replaces player chat with system messages; its config comment says "This is what makes chat not reportable." send-prevents-chat-reports-to-client is off by default; turn it on so players who use No Chat Reports see your server as safe, as the No Chat Reports guide asks. Leave claim-secure-chat-enforced off: it tries to hide the warning toast, and its own comment says it "may violate Minecraft's usage guidelines." rewrite-bedrock-only fits the opposite case: you keep reporting for Java players but still want Bedrock players on Geyser to chat.

AntiPopup is the other current option. Version 13.3 of 25 October 2026 lists 26.3 for Paper, Purpur, Spigot, Folia and Velocity. It removes reporting at the packet level, and running antipopup setup in the console switches enforce-secure-profile off for you. Its page says it also blocks the warning popup, which is the part Mojang's usage guidelines speak to (more below).

On a Space-Node Minecraft server you pick Paper, Fabric or another loader in the panel and upload the jar with the web file manager or SFTP.

Fabric, NeoForge and Forge: No Chat Reports

No Chat Reports 2.21.0 came out for 26.3 on 30 September 2026, with builds for Fabric, NeoForge and Forge. It works on the server alone, on clients alone, or on both. Installed only on the server, its page says, the server strips signatures before relaying messages, so "chat reporting will not work for any players that join."

  1. Set enforce-secure-profile=false.
  2. Put the 26.3 jar in mods/. On Fabric it also needs Fabric API.
  3. Restart. The server settings are in config/NoChatReports/NCR-Common.json.

In the 26.3 source, convertToGameMessage is on by default: the server turns all player messages into system messages, which "don't have any signatures attached and cannot be reported." demandOnClient is off, so players without the mod can join. Turn it on to require the mod on every client; players without it get the demandOnClientMessage text when the server refuses them.

Velocity and BungeeCord

A proxy checks keys too. In velocity.toml, set force-key-authentication = false (the Velocity docs: "Should the proxy enforce the new public key security standard? By default, this is on."). On BungeeCord and Waterfall, set enforce_secure_profile: false in config.yml. The No Chat Reports guide says to "follow all steps that match," so the backend servers behind the proxy still need the setting and their own plugin or mod. Our Velocity and BungeeCord guide shows the proxy setup itself.

Which Tools Support 26.3

Checked on Modrinth on 3 November 2026:

ToolRuns onBuild for 26.3Note
FreedomChatPaper, Folia (Fabric build too)1.7.10, 17 Sep 2026Rewrites chat to system messages
No Chat ReportsFabric, NeoForge, Forge2.21.0, 30 Sep 2026Server, client or both; Fabric needs Fabric API
AntiPopupPaper, Purpur, Spigot, Folia, Velocity13.3, 25 Oct 2026Also blocks the warning popup
NoChatReports (Spigot/Paper)Paper, Purpur, Spigot, FoliaNone, newest 2.7.8 lists up to 26.2Not made by the No Chat Reports author
Liberated ChatBukkit, Spigot, Paper, PurpurNone, newest 1.2.3 lists up to 1.20.6The Spigot pick in the No Chat Reports guide

The No Chat Reports page warns that many plugins "borrow" its name and icon, and that its author made none of them.

What Players See After the Change

Players on an unmodded client get the "Chat messages can't be verified" toast when they join. The No Chat Reports page says that since 1.20.2 its server side cannot remove that warning, and its guide adds that removing it server-side "may go against" Mojang's usage guidelines. Those guidelines, in the rules for servers that make money, say you may not "hide or alter any of the dialogs or prompts that are part of Minecraft (this includes the End User License Agreement (EULA), warning messages, and error messages)."

Chat that the server rewrote shows a gray bar to the left of each line on unmodded clients. Players who want the toast gone can do it on their own client: No Chat Reports has a hideWarningToast option, and Disable Insecure Chat Toast (Fabric and NeoForge) and Chat Signing Hider (Fabric) both list 26.3. Chat Signing Hider says it "does not remove any signatures or prevent other players from reporting you. It is purely visual."

Once chat can't be reported, moderating it is your job, so write clear rules and give a few trusted players the means to mute and ban.

What About Bedrock?

Geyser's page notes that Bedrock Edition does not support Java's chat reporting mechanism. The Minecraft Wiki describes Bedrock reporting as part of the player's Profile screen, and says "any player can be reported, even players that are not friends or have never been in the same world or server." It lists no server setting that turns this off. Bedrock Dedicated Server has a chat-restriction setting that drops chat or hides the chat box, but the wiki describes it as a chat setting, not a reporting switch.

FAQ

Does enforce-secure-profile=false disable chat reporting? Not by itself. It lets players without signed chat join and talk, and lets Bedrock players on Geyser chat. Players on unmodded clients still sign their messages, so add FreedomChat, AntiPopup or No Chat Reports on the server.

Is the "No Chat Restrictions" mod the same as No Chat Reports? No. They come from the same developer, but No Chat Restrictions is a client mod that "unblocks chat" on accounts where Mojang or Microsoft account flags have turned chat off. It does nothing on a server and does not stop reports. The wiki notes that UK players who haven't verified their age can't chat in multiplayer, and that since 26.2 an Xbox "Friends Only" chat setting limits whose messages a player sees. If a player's chat is off, the account's settings are the place to look.

Can I disable chat reporting on Realms? No. The wiki says Realms has reporting fully enabled "with no way to disable it." You need your own server for the steps above.

Why can't Bedrock players chat on my Java server? With enforce-secure-profile=true, Geyser says Bedrock players can't chat, because Bedrock doesn't support Java's chat reporting mechanism. Set it to false (and force-key-authentication = false on a Velocity proxy), then restart.

Will players still see "Chat messages can't be verified"? Yes, players on an unmodded client will. Hiding it from the server is what Mojang's usage guidelines warn against, but players can hide it on their own client with No Chat Reports, Disable Insecure Chat Toast or Chat Signing Hider.

Can players still report skins and names? Yes. Skin and name reports arrived in 1.20.2 and are separate from chat reports. None of the tools in this guide claim to block them.

Sources

All opened on 3 November 2026: