Is WingHUD anti-cheat safe?
Last updated 6 August 2026WingHUD is not a cheating software, and using it is not cheating. It cannot see anything you couldn't already see yourself, and it never acts in the game on your behalf. All it actually does is let you talk to an AI coach and share a screenshot of your own screen with it — the same thing you already do with a build guide, a wiki, or a knowledgeable friend on Discord, just faster and without alt-tabbing out of the game.
Short answer: WingHUD does not inject code into games, does not hook DirectX, and does not read game memory. It runs as an ordinary Windows application in its own process and only ever sees the pixels already on your screen.
That is the honest technical answer, and this page explains exactly what that means — including the parts we cannot promise. If you have ever searched "will this overlay get me banned", you already know the category has a trust problem. We would rather over-explain than ask you to take our word for it.
Tested in practice: we have run WingHUD across multiple real sessions in League of Legends and Valorant (both on Riot Vanguard), Call of Duty (Activision Ricochet), World of Warcraft (Blizzard Warden), and Dota 2 (Valve VAC) — playing real matches with the overlay, screenshot capture, and voice features actively in use throughout. No detections and no warnings in any of them. We have also put substantial time on WingHUD in Baldur's Gate 3 and Minecraft without issue, though we are not counting those as anti-cheat tests: BG3 has no anti-cheat system at all (it is single-player/co-op), and Minecraft has no single anti-cheat to test against — where one exists it is a third-party plugin running on that specific server, not a unified system like the four above. That is not a guarantee — see what we cannot promise below — but it is what we have actually observed rather than merely reasoned about.
Why overlays get flagged in the first place
Anti-cheat systems like Easy Anti-Cheat (EAC), BattlEye, and Riot Vanguard are not looking for "overlays". They look for a specific set of behaviours that cheats rely on:
- DLL injection — loading foreign code into the game's own process.
- API hooking — intercepting DirectX, DXGI, OpenGL, or Vulkan calls to draw inside the game's render pipeline.
- Memory access — reading or writing the game's memory to extract player positions or alter state.
- Input simulation — synthesising mouse or keyboard input to aim or act on the player's behalf.
Many popular overlays legitimately do the first two, because drawing inside the game is the only way to appear over exclusive fullscreen and to read structured game events. That is a reasonable engineering trade-off, but it is also why those tools sit in a grey zone and why players ask about bans.
What WingHUD does and does not do
| Behaviour | Typical injected overlay | WingHUD |
|---|---|---|
| Injects a DLL into the game process | Often yes | No |
| Hooks DirectX / DXGI / Vulkan | Often yes | No |
| Reads or writes game memory | Sometimes | No |
| Simulates mouse or keyboard input | Sometimes | No |
| Draws over exclusive fullscreen | Yes | No — borderless / windowed only |
| Captures the screen image | Varies | Yes — standard Windows screen capture |
| Reads the running-process list | Varies | Yes — to detect which game is open |
How the overlay is actually drawn
WingHUD is a standard always-on-top Windows desktop window. It sits above the game the same way Discord's window, Steam's friends list, or Windows' own notifications do — composited by the operating system, not by the game. Nothing is added to the game's render pipeline.
How WingHUD sees your screen
Screenshot, Area Capture, and Last Scene all use the same ordinary Windows screen-capture call that any screenshot utility uses. WingHUD receives a flat image — the identical pixels you are looking at. It has no access to anything the game did not already draw on screen.
This is worth dwelling on, because capturing and analysing gameplay is the part players most often assume must be risky. It is actually the safest thing WingHUD does. Reading the composited desktop image is a completely different operation from reading a game's memory: one looks at pixels the graphics card has already drawn for you, the other reaches inside the game process. Anti-cheat systems care enormously about the second and not at all about the first.
The simplest proof: this is the same screen-capture mechanism behind OBS, NVIDIA ShadowPlay, AMD ReLive, Discord screen share and the Xbox Game Bar. Streamers record and broadcast ranked matches on the strictest anti-cheats in the world, every day, without bans. If capturing your own screen were detectable behaviour, streaming as a profession could not exist.
The one thing worth being clear about is what happens next: when you send a screenshot or trigger Last Scene, that image is uploaded to WingHUD's servers so the AI can actually read it. That is a privacy consideration, and we cover exactly what is sent and retained in the Privacy Policy — but it carries no anti-cheat implication. What you do with an image of your own screen is outside anti-cheat's scope entirely.
How WingHUD knows which game you are playing
WingHUD checks the list of running processes against a lookup table of known game executables. Reading the process list is a routine, unprivileged Windows operation — it is what Task Manager does. WingHUD does not open, attach to, or inspect the inside of those processes.
Why WingHUD needs Borderless Windowed mode
This limitation is direct evidence of the architecture above. WingHUD cannot draw over a game running in true exclusive fullscreen, because in that mode the game takes direct control of the display output and the only way to appear on top is to hook into its rendering — exactly the technique WingHUD refuses to use.
So WingHUD asks you to run games in Borderless Windowed (also called "Windowed Fullscreen" or "Fullscreen Windowed"), which is already the default in most modern PC games and what most players use anyway because it alt-tabs instantly. If the overlay does not appear over your game, that setting is almost always the reason.
A trade-off, stated plainly: supporting exclusive fullscreen would mean adding the hooking behaviour this entire page explains we avoid. We would rather have the narrower compatibility and the cleaner risk profile.
What we cannot promise
No third-party tool can guarantee you will never be flagged, and you should be sceptical of any that claims otherwise. Anti-cheat vendors do not publish their heuristics, they change them without notice, and false positives genuinely happen across the industry.
Specifically, please understand:
- WingHUD is not on any anti-cheat vendor's allow-list. Formal whitelisting requires registering with vendors such as Epic (EAC) and BattlEye, which is a step for a later stage of the product, not something that has happened today.
- Each game's terms of service still apply to you. Some publishers restrict any third-party assistance, and some tournament and league rulesets are stricter still. If you compete under a specific ruleset, check it.
- WingHUD is in closed beta. It has not yet been exercised across every anti-cheat and every title at scale. If you are worried about a specific competitive account, use your judgement.
Does WingHUD count as cheating?
WingHUD can only see what you can already see. It cannot reveal enemy positions through walls, expose hidden information, or act in the game on your behalf. It has no aim assistance and does not send input to the game.
Functionally, asking WingHUD "what should I build against this lineup?" is closer to asking a knowledgeable friend on the couch next to you than to running a cheat — the same category of help as a wiki, a build site, or a Discord full of teammates, just without the alt-tab. That said, "is it allowed" is a rules question, not a technical one, and rulesets differ. We have given you the technical facts so you can answer it for your own situation.