Skip to main content
A Venon Security guide

How do you clear spam on Discord?

Stop the source, clear the channel, penalise with a reason, close it off with automation. Four moves in that order — and evidence in the logs.

6

Configuration steps

5

Final tests

4

Errors solved

~7 min

Reading time

The answer

The short answer

You clear spam on Discord with /clear <count> — and if you want to remove one person's messages, add the user parameter. Cleaning up is only half the work, though: with no response to the author the same run comes back a minute later. The order that works: stop the source first (a timeout or /mute), then clean the channel with /clear, then issue a penalty with a reason, and finally raise the anti-spam thresholds in AutoMod so the bot reacts without you next time. Bear in mind that Discord does not allow bulk deletion of messages older than 14 days.

The content is checked against the bot's configuration — last verified: 2026-11-06.

Context

What the problem is

Spam clutters a channel, generates notifications and effectively kills the conversation. For a single incident one cleanup is enough, but with a repeated flood, deleting by hand turns into a full-time job. On top of that, removing messages without recording the context takes away your evidence when the author appeals against the penalty.

Without an extra bot

What you can do with Discord alone

Before you reach for a bot, get everything out of what Discord gives you out of the box. Some problems are solved here, and the rest of the configuration will run more steadily.
  1. 1

    Give the author a timeout from the member context menu — that stops the spam immediately.

  2. 2

    Delete the messages by hand or, with a large number, use bulk deletion in the channel.

  3. 3

    Turn slowmode on in the channel to limit the pace during the incident.

  4. 4

    Tell the rest of the staff whether this is a one-off or the start of a wider wave.

Venon Security

What Venon Security adds

Only the things Discord's native tools do not handle, or handle without history and automation.
  • The /clear <count> [user] command removes a run of messages, optionally only from the member you point to.

  • AutoMod with the anti-spam detector removes a flood automatically, before anyone has time to react.

  • Warnings with escalation thresholds turn repeated spam into an automatic mute, kick or ban, and all of it goes into the moderation logs.

Configuration

Configuration step by step

Every step says exactly where to perform it and which fields to set. The field names are the same as in the panel, so you can copy them one to one.

0 of 6 steps

0%
  1. Stop the source before you start cleaning

    /mute <user> [time] [reason]

    Cleaning a channel during an ongoing flood makes no sense — new messages arrive faster than you remove the old ones. Mute the author first.

    • /mute grants the mute role; the time parameter accepts values such as 30m or 2h.
    • The silent parameter performs the action without announcing it in the channel.
    • With several accounts at once, go straight to the guide on raid protection — this is no longer ordinary spam.
  2. Clear the channel with /clear

    /clear <count> [user]

    The command removes the number of recent messages you give it. The user parameter narrows the cleanup to one person, so you do not wipe out everyone else's conversation along the way.

    • Always start with a smaller number and check the result before removing more.
    • Discord blocks bulk deletion of messages older than 14 days — older ones have to be removed one at a time.
    • The command requires the Manage Messages permission.
  3. Issue a penalty with a reason

    /warn <user> [reason]

    A penalty without a reason is useless during an appeal — a week later nobody remembers what it was about. The reason is typed once and stays in the case history.

    • /warn adds a warning to the member's history.
    • For a repeated violation use /mute with a longer duration, or /temporary-ban for a temporary ban.
    • The message context menu has shortcuts: Quick warn and Penalty history.
  4. Set up automatic escalation

    Panel → Moderation → Sanctions and warnings → Sanction settings

    Escalation means you do not have to remember how many times somebody has already slipped up. The bot raises the penalty itself once a threshold is crossed.

    • Mute after (warnings), Kick after (warnings), Ban after (warnings): 3 / 5 / 7, for example.
    • Warning expiry (days): 30–90, so the history does not weigh forever.
  5. Close the subject with AutoMod

    Panel → Security → Content protection → Detectors

    If the spam keeps coming back, the AutoMod settings are too loose. After an incident always return to the thresholds instead of counting on somebody reacting in time next round.

    • Anti-spam: on; Spam threshold (messages): 5, Spam window (seconds): 5.
    • The mention limit with the Max. mentions in a message field: 4.
    • Response to a violation: Delete the message plus Log to the moderation log channel.
  6. Limit the pace in the channel if the problem is recurring

    On channels regularly swamped by a flood — announcements, giveaways, the general channel at peak hours — slowmode works better than any filter, because it slows everyone down equally.

    • Set slowmode on the channel in Discord's channel settings.
    • During a raid slowmode can switch on by itself: in Panel → Security → Emergency mode set Venom Shield to limited automation and turn on Automatic slowmode. It takes the rate and duration from the Planned slow mode and Planned slow mode duration fields (Security → Raid protection) and reverts the change on its own afterwards.

The steps you tick are saved in your browser — you can come back and finish later.

Verification

How to check the configuration worked

A green switch in the panel is not proof. Go through the tests below — ideally on a second, ordinary account with no roles.
  1. 1

    After /clear the channel is clean, and the Moderation log category carries an entry with the number of deleted messages and the moderator.

  2. 2

    A muted member genuinely cannot write — if they can, the mute role has no proper overrides (Panel → Moderation → Active mutes, the permission test button).

  3. 3

    The member's penalty history contains a new entry with the reason.

  4. 4

    The anti-spam test: 6 messages in 5 seconds from a test account disappear automatically.

  5. 5

    Once the warning threshold is reached the bot applies a mute itself — check that on a test account before trusting escalation in production.

Diagnostics

When something does not work

The symptom, the cause and a specific fix. Start from the symptom you see — the cause is usually simpler than it seems.

/clear does not remove older messages.

Cause
Discord does not let bots bulk-delete messages older than 14 days.
Fix
Remove older messages by hand, or archive the channel and create a new one. React faster during incidents — after two weeks the bulk option is gone.

The command returns a permission error.

Cause
The bot lacks the Manage Messages permission in that channel, or the moderator role does not have the command in Power Role.
Fix
Check the channel permission overrides for the bot's role, and Panel → Server → Commands and integrations, where you assign commands to roles.

A muted member still writes in some channels.

Cause
The mute role has no override on every channel — especially on those created after it was configured.
Fix
Panel → Moderation → Active mutes: use the channel repair and the permission test, which shows where overrides are missing.

AutoMod does not react to an obvious flood.

Cause
The anti-spam detector is off, or the threshold is higher than the spam rate.
Fix
Panel → Security → Content protection: enable Anti-spam and lower the Spam threshold (messages) to 5 with a 5-second window.

Honestly

What this configuration does not solve

The boundaries matter as much as the capabilities. If you are counting on something from this list, you need a different solution — or simply a person.
  • Discord does not let bots bulk-delete messages older than 14 days — no bot can work around that limit.

  • Deleted messages are gone for good. If they are meant to be evidence, make sure the Deleted messages log category is on before you start cleaning.

  • The anti-spam filter looks at pace and repetition, not at the sense of what is said. A conversation carried on in very short messages can set it off.

  • Venon will not remove spam sent in private messages — it has no access to them.

  • Spam from many accounts at once is already a raid; AutoMod alone is not enough, you need AntiRaid thresholds and an entry gate.

FAQ

FAQ – common questions

Does /clear remove old messages?+

No. Discord blocks bulk deletion of messages older than 14 days, so /clear covers only newer ones. Older ones have to be removed one at a time, which is why it pays to react to incidents straight away.

Can you remove one person's messages?+

Yes. The command takes the form /clear <count> [user] — once you name a member, only their messages from the recent batch are cleared, so everyone else's conversation stays untouched.

Timeout or mute — which should you use?+

A timeout is Discord's native mechanism and applies immediately across the whole server, voice channels included. Venon's mute role gives you more control over exactly where it applies. During ongoing spam a timeout acts faster.

How do you stop spam coming back?+

Combine three things: the anti-spam detector in AutoMod, the warning escalation thresholds in the sanction settings, and slowmode on high-traffic channels. Cleaning the channel alone changes nothing on the author's side.

Ready?

Set this up in your own Venon Security panel

Every screen mentioned in the guide is in the web panel. You save the configuration by hand and see its state before anything takes effect on the server.