Why a display name is not enough for a report
Display names and usernames change. A person can rename themselves mid-conversation, and two accounts can share the same visible name. Support teams need a durable identifier that points to one account or one message, not a label that may be different by the time the report is read. That is why copying a Discord user ID or a message link is more useful than typing a name into a report form.
A user ID is a long numeric string tied to the account. A message link is a URL that points to a specific message in a specific channel. Neither is a substitute for describing what happened, but both remove ambiguity about who and what you are reporting. This guide covers how to capture them, when each is appropriate, and what not to include in a public report.
Step 1: Turn on Developer Mode
Developer Mode is the setting that exposes copy-ID options in the Discord interface. It is off by default, so you will not see those options until you enable it.
Discord Developer Mode is enabled in Settings, Advanced before copying IDs. Source
Once Developer Mode is on, right-click or long-press a user or message to see the additional copy options. If you are on mobile, the same options appear in the context menu after the setting is enabled. The exact menu layout can differ between desktop and mobile clients, so look for the copy actions rather than memorizing a fixed position.
Step 2: Copy the user ID
To capture a user ID, open the user’s profile or the member list entry and use the copy option. This gives you the numeric identifier for that account, which remains stable even if the person changes their display name.
The user menu offers Copy User ID, and message menus offer Copy Message Link. Source
Paste the ID into a plain text file or a notes app immediately. Do not rely on your clipboard surviving a restart or being overwritten by another copy action. Label it with the date and the context in which you saw the account, because a bare number is hard to interpret later.
Step 3: Copy the message link
When the problem is a specific message rather than an account, use the message menu to copy its link. This is useful for reports about harassment, spam, or a misleading post in a channel you can access.
A message link does not grant access to a conversation that the recipient lacks permission to view. Source
That limitation matters for reports. If you send a message link to a support agent or a moderator who cannot see the channel, the link will not open for them. In that case, describe the channel and the message content in your report instead of assuming the link is enough. Do not paste private message contents into a public thread to compensate; keep sensitive material out of public view.
Decision table: which identifier to save
| Situation | Save this | Why |
|---|---|---|
| Reporting an account that changed its display name | User ID | The numeric ID stays tied to the account |
| Reporting one specific message in a channel | Message link | Points to the exact message |
| Reporting behavior across several messages | User ID plus a written summary | A single link may not capture the pattern |
| Reporting to someone who cannot see the channel | Written description, not the link | The link will not open without permission |
| Comparing accounts with similar names | User ID for each | Display names can collide |
Common mistakes
- Copying the display name instead of the ID. A name is easy to mistype and easy for the account holder to change. Use the copy action, not manual transcription.
- Sending a message link to someone without access. A message link does not grant access. If the recipient cannot view the channel, the link is useless to them.
- Pasting private message contents into a public report. Support reports should identify the account or message without exposing private conversation. Keep the report factual and minimal.
- Leaving Developer Mode off and guessing. If you cannot find the copy options, check whether Developer Mode is enabled before assuming the feature is missing.
- Losing the ID before you write the report. Copy and save it first; write the narrative second.
- Treating a username match as proof of ownership. A matching handle on another platform is a lead, not confirmation that the same person owns both accounts.
Protecting your own footprint
If you are the one being reported, or if you are auditing your own exposure, the same mechanics apply in reverse. Your user ID is not secret, but it is durable, and it can be used to correlate reports about your account. Review which accounts are connected to your profile and what those connections reveal. Our guide to the Discord connections and profile privacy checklist walks through the settings that control what others can see.
When you want to see how a known public handle appears across other platforms, a username lookup can help you spot reuse. TraceSeek checks 3,000+ platforms and returns public matches in 20-30 seconds, with a free first scan. It does not change Discord settings, does not expose private records, and does not prove that two accounts belong to the same person. Treat every match as a lead to verify. You can read more about the approach on the Discord lookup page.
Key facts
- Discord Developer Mode is enabled in Settings, Advanced before copying IDs.
- The user menu offers Copy User ID, and message menus offer Copy Message Link.
- A message link does not grant access to a conversation that the recipient lacks permission to view.
- TraceSeek checks 3,000+ platforms and returns public matches in 20-30 seconds, with a free first scan.
- Public username matches are leads, not proof of ownership.