Blur Discord chat before a support ticket
Cover usernames, Discord IDs, and member lists before you paste a Discord snip into Zendesk or a vendor ticket.
Before you paste a Discord chat into a support ticket, black-bar usernames, Discord IDs, and DMs that are not the error — ticket channels often expose bystanders in the member list.
This is the narrow case: one bug or ban report for a vendor or mod team. For memes and full-desktop Discord hygiene, use the full Discord screenshot guide.
How to blur Discord for a support ticket (step by step)
Crop the member list and server rail. Prefer Black bar on Discord IDs, emails in embeds, and gift or invite URLs. Keep the error text or bot reply.
On your phone or computer
iPhone / Android: Capture the ticket channel, then Markup or gallery solid covers on handles and IDs before you upload to Zendesk or email.
Windows: Win + Shift + S → Paint. Filled black rectangles over usernames, IDs, and the bottom-left user panel.
Mac: Preview → Markup with a filled shape over the same chrome, then attach that PNG.
Or finish in a browser (optional)
Want to do it in a tab with no install? BlurThis is one free option. The file stays on your device. Other browser tools work too if they paint on the page and do not upload the image.
- Open the editor in your browser. No account needed for BlurThis.
- Drop the screenshot, tap Upload from PC or Mobile, or paste with Ctrl / ⌘ + V on a computer.
- Pick Box or Draw. Use Black bar for phone numbers, emails, and OTPs. Use Blur for faces when a soft cover is enough.
- Drag over each private spot. Pinch or use + / − to zoom. Leave a little padding so no letter peeks out.
- Tap Download PNG. Send that file. Keep the original out of the chat or ticket.
What to cover when Discord goes into a support ticket
- Reporter and bystander usernames in the thread.
- Discord IDs in bot embeds and audit snippets.
- Member list and role colors in the right rail.
- Server icons that identify a private community.
- Gift links, invites, and payment / Nitro toasts.
- DM previews or notification shade during the capture.
Keep the failing bot message or the UI glitch. Type user IDs into the private ticket field if staff need them. Wider support habits live in redact a customer support screenshot.
Tokens and DevTools in the same snip
Browser Discord plus a network panel is how bot tokens die in help channels. Cover Authorization headers and the address bar. Rotate anything that appeared — details in hide API keys in the URL bar.
FAQ: Are Discord usernames “already public”?
Server-visible is not the same audience as a vendor ticket or Twitter quote. Bar people who are not part of the report.
FAQ: Ticket channel named after the user?
Crop or bar the channel title if the PNG leaves the mod team. The channel name is still a name.