Reporting suspected cheating is most useful when it gives moderators a clear, verifiable trail instead of a conclusion they must reconstruct. This guide explains what to collect on PC, console, and game platforms, how to protect your privacy, which details can weaken a report, and how to keep your reporting process current when menus, forms, or evidence requirements change.
Overview
A strong cheat report answers five basic questions: who was involved, what happened, when and where it happened, why the behavior looked suspicious, and where the platform can verify it. The goal is not to prove guilt beyond doubt or identify the exact software being used. Your goal is to submit relevant observations that an appropriate review team can check against server data, replays, anti-cheat signals, or other moderation tools.
Reporting routes vary. A game may offer an in-match report button, a post-match screen, a launcher form, a support website, or a console-level reporting option. Use the route connected to the incident whenever possible. A console account report may address conduct or messages, while the game developer may be the better destination for suspicious gameplay. If several routes are available, avoid sending repetitive reports to every channel. Submit one focused report to the responsible system and keep your own record of what you sent.
Evidence should be factual and proportionate. A short clip showing the relevant moment is usually more useful than a long recording with no explanation. A match ID, round number, timestamp, player name, and platform can help moderators locate the same event. Do not attempt to access another player's account, install questionable tools to investigate them, or publish personal information. Those actions can create safety and moderation problems of their own.
| Platform or route | Useful evidence | Important limitation |
|---|---|---|
| PC game | Gameplay clip, match or lobby ID, in-game name, account identifier, round and timestamp | Do not include unrelated desktop windows, private messages, or personal files |
| Console game | Console capture, game profile name, match details, date and approximate time, relevant voice or text context | Console privacy and sharing settings may limit clips, messages, or voice evidence |
| Game launcher or support form | Concise incident summary, screenshots or clips if accepted, links to the match, and exact player identifiers | Attachment sizes, file types, and retention periods can change |
| Platform-level report | Profile URL or account name, message or conduct evidence, and the specific rule concern | Platform moderation may not investigate game mechanics or make a cheating determination |
What to track
1. Player identifiers and match details
Record the exact in-game name as displayed, including unusual capitalization or characters. If the game shows a profile ID, user ID, friend code, or platform account identifier, include it. Also note the game mode, map or level, region if visible, match or lobby ID, team, and approximate date and time. These details are more reliable than a nickname alone, especially when names can be changed or duplicated.
2. A focused video clip
Capture the smallest section that demonstrates the concern, while leaving enough lead-in and follow-through to show context. A useful clip might show repeated tracking through an obstruction, impossible movement, an unusual input sequence, or behavior that conflicts with the game's normal mechanics. Keep the original file if possible. Avoid editing that changes timing, removes context, adds accusations, or overlays private information. If you share a link, check that it works without exposing your account or unrelated files.
Video is not mandatory in every case, and a clip is not automatically conclusive. Network delay, observer delay, replay reconstruction, audio desynchronization, or a game bug can make legitimate play look strange. If the game provides a replay, killcam, or spectator tool, review it before reporting and note whether the same behavior appears from another viewpoint. For a deeper review process, see how to review suspicious gameplay with replays, killcams, and spectator tools.
3. A neutral incident summary
Describe what you observed rather than asserting an unverified conclusion. For example: “At approximately 18:42 in round three, the player tracked my position through a solid wall for several seconds before the wall opened. The behavior happened again near the objective.” This is stronger than “They were obviously using wallhacks,” because it gives a reviewer something specific to check.
4. Chat, voice, and conduct evidence
Include text or voice details only when they are relevant to the report. Threats, slurs, account-selling offers, boosting arrangements, or links to suspicious downloads may belong in a conduct or safety report as well as a cheating report. Preserve the original context and avoid reposting abusive material publicly. If voice capture is unavailable or restricted, describe what happened and identify the approximate time rather than trying to bypass privacy settings.
5. Privacy and account safety
Before attaching anything, remove phone numbers, email addresses, real names, payment details, private conversations, desktop notifications, and files unrelated to the incident. Do not reveal your own login information or send a supposed “proof” file that requires you to disable security software. Fake cheats and cheat loaders are commonly used as lures for malware or account theft; review how to avoid fake cheats and suspicious loaders if someone directs you to download one.
Copyable report template
Subject: Suspected cheating report — [game], [mode], [date]
Player: [exact display name and available account ID]
Platform: [PC, console, or other]
Match details: [match/lobby ID, map, round, region if visible]
Approximate time: [time zone if known]
Observed behavior: [brief, neutral description of what happened]
Evidence: [clip, replay, screenshot, or profile link]
Relevant timestamps: [00:00, 00:00]
Additional context: [whether it repeated, whether lag or a bug could explain it]
Privacy note: [confirm that unrelated personal information has been removed]
Cadence and checkpoints
Use a simple checklist after each serious incident. First, save the clip or replay before it expires. Next, write down identifiers and timestamps while they are fresh. Then review the footage once without commentary and once with the game's normal mechanics in mind. Finally, submit the report through the current official route and record the date, case number, or confirmation if one is provided.
Because support pages and game interfaces change, check the reporting path monthly or quarterly if you regularly play competitive games. Review it sooner after a major launcher update, a new season, a platform privacy change, or a change to the game's anti-cheat system. Confirm whether the form still accepts your attachment type, whether links require access permissions, and whether the game now separates cheating, harassment, boosting, and account-security reports.
Keep a private incident log rather than a public blacklist. Useful fields include game, platform, date, match ID, report route, evidence saved, and confirmation received. Do not treat a lack of visible follow-up as proof that no action occurred; moderation outcomes may not be disclosed for privacy or security reasons.
How to interpret changes
A changed report form does not necessarily mean the standard of proof has changed. Look for practical differences: a new required identifier, a smaller attachment limit, a dedicated replay upload, or a request to report from inside the match. Adapt your format to the current form while preserving the same core evidence.
If multiple reports concern the same player, avoid submitting identical copies with exaggerated claims. Instead, provide distinct match IDs and explain the repeated pattern briefly. A pattern can be useful when each incident is independently specific, but repetition alone is not proof. Similarly, a ban, leaderboard removal, or matchmaking change seen by the community should not be presented as confirmation unless the responsible provider has clearly stated it.
Before reporting, consider explanations that can undermine an otherwise sincere complaint: packet loss, server correction, sound cues, map knowledge, spectator perspective, replay bugs, aim assistance built into the game, or a mechanic you do not recognize. This does not mean ignoring suspicious play. It means identifying uncertainty so reviewers can test the right possibilities. For a broader comparison of suspicious behavior and possible explanations, see how to spot cheaters and compare evidence with next steps.
When to revisit
Revisit this guide whenever you start a new competitive game, move from PC to console, or use a different launcher. Reporting requirements can differ even when two games use similar menus. Check again after a patch or season update if replay access, killcams, account identifiers, or in-game reporting options have changed.
Make a quarterly checkpoint part of your routine if you report incidents often. Open the game's official support page, confirm the current reporting category, test that your evidence link is private but accessible, and update your personal checklist. Also review your privacy settings and account security. If you suspect that your own account was used for cheating, stop treating the issue as only a player report and follow an account-recovery process; the guide on what to do when an account was used for cheating without permission covers that separate situation.
The practical rule is simple: preserve evidence early, report through the current official channel, describe observations precisely, and avoid public accusations or risky investigations. A calm, complete report gives moderation teams the best chance to verify what happened while protecting your account, privacy, and place in fair play.
