Redact a Discord screenshot (tokens love the address bar)

Discord screenshots fail in two boring ways: a username you should not publish, and a developer console you should not have photographed.

The meme is in the middle. The server rail, the member list, the user panel in the bottom left, and a nitro receipt toast are the rest of the frame. Phone captures add a notification shade. Browser Discord adds an address bar. Each of those is a different class of leak.

The social chrome

• Server list icons that identify private communities by shape alone.
• Channel name and category, including ticket-style channel names.
• Member list and role colors; crop that column when it is not the point.
• Username, display name, and clan tags in the message header.
• Friend overlay, pending requests, and DM list if you captured the home tab.
• Nitro, Boost, or payment toasts — treat them like a bank receipt.
• Voice-connected names and the “camera on” tiles in a stage.

Crop to the meme when the meme does not include a handle. If the joke is a DM, bar the handle. Profile banners and custom status text often include an Instagram or a phone number; those are still chrome around the joke. Forum posts add a starter’s name plus tags; bar tags that are just a username. Stickers that reprint a ticket ID get a bar.

The token and URL leak

Browser Discord plus DevTools is how bot tokens die in help channels. The address bar, a network URL, or a copied authorization header can hold a token. Cover the entire bar, not the middle characters. Do not “star out” a token in a screenshot tutorial of your own bot — crop the panel or bar the whole line.

That pattern is the same as any API key in a location field. Walk through it in hide API keys in the URL bar.

Black bar for numbers and receipts

Discord IDs, phone numbers in Moderation, and last-four digits on a nitro invoice are short strings. Blur is the wrong tool. Paint a rectangle. Gift-link URLs are secrets; bar them even if they look like ordinary messages.

Desktop app: cover the user panel (username plus discriminator-style display). Phone app: cover the notification shade. Incoming message previews during a capture are a classic extra leak; the general case is in notifications in screenshots.

Servers, tickets, and mods

Mod screenshots of a report often include the reported user’s ID, the reporter’s ID, and three other cases in a bot embed. Crop to the one embed. Bar IDs if the image will be shown to people who are not mods. Ticket channels named after a user are a name. Rename in the crop.

Audit-log captures include IP-looking fields in some bots. If you did not mean to publish an IP, bar the field. Do not document how to use it. Just cover it.

FAQ: Are usernames public anyway?

Server-visible is not “fine to screenshot into a different server or onto Twitter.” You change the audience. Bar bystanders. If you are quoting a public announcement channel, the channel’s purpose may make the name part of the record — still cover people in the replies.

FAQ: What about spoiler tags?

Spoiler tags hide pixels in the live client. A screenshot of an unspoilered message is ordinary pixels. If you captured through the spoiler, you still hold the image. Bar identity before you reshare.

FAQ: Can I show a ban screen?

Show the reason text if that is the artifact. Bar the user ID, email if present, and any payment line. Do not include a list of other banned accounts from the same modal.

FAQ: Stream overlays and shared screens?

A stream that includes Discord also includes whoever is talking. If you screenshot the stream, bar names in the overlay and in the Discord window under it. Recursive windows are how DMs appear “in the background.”

Open the meme shot in the on-device editor and bar the user panel plus any URL that looks like a token. BlurThis never needs the file uploaded.