Skip to main content
purge deletes messages from the channel you run it in. On its own it clears a number of recent messages, and with a filter it clears only the ones that match, such as messages from one member or messages containing a link.
Deleted messages are gone. Discord provides no way to recover them, and neither does Bloom. If the messages are evidence, capture them first with a transcript or screenshots.

​
Clearing recent messages

​
Manage Messages
Deletes the most recent messages in the channel. Aliases: clear, delete, c, p.
  • Bloom needs: Manage Messages and Read Message History.
  • Up to 300 messages at a time.
  • !purge 50 clears the last fifty messages and confirms with a message that removes itself a moment later.
Bloom deletes your command as it starts, so the command itself never counts toward the total or survives the clear.
Discord only allows messages under 14 days old to be deleted in bulk. A plain !purge still removes older messages, one at a time, which is noticeably slower. The filters below skip anything older than 14 days instead.

​
Clearing only some messages

Each filter looks at the most recent messages in the channel, up to 100, and deletes the ones that match. The number you give is how many messages Bloom checks, not how many it deletes, so !purge links 100 scans the last hundred messages and may delete only three.
​
Manage Messages
Deletes messages containing a word or phrase. Wrap a phrase in quotes to match it as a whole.
  • !purge contains scam 100 removes messages containing “scam”.
  • !purge contains "free nitro" 200 matches the full phrase.
​
Manage Messages
Deletes one member’s messages from this channel. Takes a mention, an ID, or a name.
  • !purge user @Someone 50 checks the last fifty messages and removes theirs.

​
Clearing a range

​
Manage Messages
Deletes everything between two messages, which is the tool for cleaning up one argument without touching the conversation around it.
  • Takes two message IDs. Order does not matter.
  • Covers up to 1000 messages.
​
Manage Messages
Deletes every message posted after the one you name, up to 5000 messages. Bloom tells you what it is scanning as it works.
  • Message IDs are 17 to 19 digits. Bloom checks the message is in this channel before starting.
To get a message ID, turn on Developer Mode in Discord’s settings under Advanced, then right click a message and choose Copy Message ID.
purge after can remove thousands of messages from a single command, and there is no confirmation step. Check you have the right message ID before running it.

​
Clearing reactions instead of messages

​
Manage Messages
Removes all reactions from recent messages and leaves the messages themselves alone. Checks up to 100 messages.
  • Use it after a reaction spam run, when the messages are fine but the reactions are not.

​
Clearing one member across the server

​
Manage Messages
Deletes a member’s recent messages from every channel Bloom can reach, rather than one channel. Alias: gp.
  • Checks the most recent messages in each text channel and thread, so it is built for a spam run that just happened rather than a full history wipe.
  • Without a time it covers the last 2 weeks, which is also the maximum.
  • !globalpurge @Someone 2h clears their messages from the last two hours everywhere.
  • Channels where Bloom lacks View Channel, Manage Messages, or Read Message History are skipped.
A global purge deletes across every channel at once, including channels you may not have looked at. Prefer !purge user in the affected channel when the mess is contained to one place.

​
Clearing your own messages

​
Manage Messages
Deletes your own recent messages in this channel and nobody else’s. Alias: spurge.
  • Up to 100 at a time.
  • Useful for clearing your own command output without touching the conversation.

​
Troubleshooting

Discord’s bulk deletion only reaches back 14 days. Use a plain !purge <amount>, which falls back to deleting older messages individually, or delete them by hand.
With a filter, the number is how many messages Bloom checks, not how many match. It also skips messages older than 14 days, and stops early if the channel does not have that many messages.
Bloom needs Manage Messages and Read Message History in that specific channel. A channel override can deny either one while the server wide permission looks fine.
purge between and purge after only accept IDs of messages in the channel you are running the command in. Copying an ID from another channel fails this check.
That is deliberate. Bloom removes its own confirmation a few seconds later so the cleared channel stays clear.

Event logging

Log deleted messages so a purge does not erase the record too.

Bans, kicks, and timeouts

Ban commands can clear a member’s recent messages as they go.

Warnings, cases, and staff records

Record why the cleanup happened.

Permissions and hierarchy

Why a command can work in one channel and not another.