Quick answer: "Always on top" utilities (PowerToys Always On Top, DevToys, Win+ tools, a custom AHK WinSet, AlwaysOnTop) fail over an exclusive-fullscreen game because the game owns the entire display — a "topmost" flag is just a hint to the desktop window manager, and an exclusive-fullscreen game has taken that manager out of the loop, so your pinned window either gets covered or forces the game to flip into a slower windowed mode. The reliable fix is not a topmost hack at all: run the game on its own virtual display at native fullscreen, and place the other window in a zone beside it on your physical monitor. The window is genuinely on-screen and clickable, the game keeps native fullscreen, and there is no borderless FPS penalty.
It is one of the most-repeated PC complaints there is: "I pinned the window always on top, but the second I launch the game fullscreen it disappears." You want a timer, a guide, a chat window, or a dashboard to sit on top of a fullscreen game — and every "always on top" trick lets you down. Here is exactly why, and how to actually keep a window over the game.
Why "always on top" doesn't work over a fullscreen game
"Always on top" is a z-order hint. When you pin a window with PowerToys Always On Top, DevToys, or an AutoHotkey AlwaysOnTop command, all you have done is ask the Windows desktop window manager to keep that window above its siblings in the stacking order. That works great over normal windows and even over borderless games, because those all live inside the same composited desktop.
An exclusive-fullscreen game breaks the premise. It takes direct control of the whole display and bypasses the desktop compositor — so the stacking order your topmost flag lives in no longer governs what is on the screen. From there, one of two things happens:
- Your pinned window gets covered. The game is painting the entire display directly; the compositor's "keep this on top" instruction has nothing to enforce it against, so the window is simply not visible.
- The game gets kicked out of exclusive fullscreen. To show your topmost window at all, Windows has to drag the game back into a composited (borderless-like) mode — which is exactly the slower path you were trying to avoid, costing you FPS and adding input latency.
So "always on top not working in game" is not a bug in your utility. It is a structural mismatch: a topmost flag is a request to a compositor that an exclusive-fullscreen game has deliberately stepped around. No topmost hack can pin a window over true exclusive fullscreen without pulling the game out of it.
The fixes, ranked
Here is how the common approaches stack up when you actually want a window over a fullscreen game.
| Approach | Stays visible over TRUE fullscreen? | Game keeps native FPS? | Window clickable? | One screen? |
|---|---|---|---|---|
| PowerToys / AHK "always on top" | No — covered or forces game out of exclusive fullscreen | Only if it flips the game to windowed (then no) | Yes | Yes |
| Borderless windowed + topmost | Not "true" fullscreen — game is already windowed | No — pays the compositor FPS/latency cost | Yes | Yes |
| Second monitor | N/A — window is on the other screen, not over the game | Yes | Yes | No — needs extra hardware |
| Staged (own virtual display + zone) | Yes — window sits beside the game, genuinely on-screen | Yes — native fullscreen, no borderless penalty | Yes | Yes |
1. PowerToys Always On Top / AHK (works over windows, loses to exclusive fullscreen)
PowerToys Always On Top, DevToys, and a one-line AutoHotkey script all pin a window's z-order. Over normal apps and borderless games they are excellent — instant and free-of-charge with your existing tools.
- Pros: lightweight, works over borderless games and desktop apps.
- Cons: over an exclusive-fullscreen game the pinned window is either covered or only appears by forcing the game out of exclusive fullscreen (the slower mode). It is a compositor-level hint, and exclusive fullscreen sits outside the compositor.
2. Borderless windowed + topmost (visible, but you pay the FPS tax)
Switch the game to Borderless Windowed and then pin your other window on top. Now everything lives in the composited desktop, so the topmost flag works and your window stays visible.
- Pros: the pinned window genuinely stays over the game; works in most modern titles.
- Cons: you have given up exclusive fullscreen for the desktop compositor, which adds a small FPS and input-latency cost. And to be precise, you are no longer keeping a window over true fullscreen — you changed the game to windowed to make it work. Competitive players tend to dislike the latency tax.
3. Run the game on its own virtual display and dock the window beside it (native fullscreen, no hack)
Instead of fighting the z-order, sidestep it. Run the game on a separate virtual display at native fullscreen, and place the other window in a zone next to it on your physical monitor. Windows treats the virtual display as a real monitor, so the game keeps true native fullscreen and never has to leave exclusive mode — while your other window is composited into a zone right beside it, fully on-screen and clickable. This is what Staged does: it runs the game on a virtual display and composites it into a zone on your physical screen, with your other apps in zones around it.
- Pros: native-fullscreen performance (no borderless penalty); the other window is genuinely visible and clickable beside the game — not a topmost hack that can be covered; and it works on a single monitor, no extra hardware, laptop included.
- Honest note: the window sits beside the game in its own zone rather than literally floating on top of a full-screen game — which is the whole point, because "on top of true exclusive fullscreen" is not something a topmost flag can honestly deliver. Staged is also a dedicated tool rather than a built-in Windows toggle.
Pinned "on top" vs. genuinely visible beside the game
It is worth being precise about what you actually want, because the fixes differ:
- If you only need the window over borderless games or desktop apps, PowerToys Always On Top or an AHK script is perfect — pin it and you are done.
- If you need the window visible while the game stays in true exclusive fullscreen, no topmost flag can do it without dragging the game into windowed mode. Give the game its own virtual display and dock the window in a zone beside it instead — genuinely on-screen, and the game never leaves native fullscreen.
Knowing which one you have saves you from chasing a topmost hack that exclusive fullscreen was always going to ignore.
Frequently asked questions
Why doesn't Always on Top work over my fullscreen game?
Because "always on top" is a z-order hint to the Windows desktop compositor, and an exclusive-fullscreen game bypasses that compositor to paint the whole display directly. With nothing for the topmost flag to enforce against, your pinned window is either covered or only shows up by forcing the game out of exclusive fullscreen into a slower windowed mode. It is a structural mismatch, not a bug in your utility.
Does PowerToys Always On Top work in games?
Over borderless games and desktop apps, yes — PowerToys Always On Top pins the window fine. Over a game in exclusive fullscreen, no: the game owns the display outside the compositor, so the pinned window gets covered or kicks the game into windowed mode. The same goes for DevToys and custom AutoHotkey AlwaysOnTop scripts.
How do I pin a window over a fullscreen game?
The honest answer is you do not pin it over true exclusive fullscreen — you place it beside the game instead. Run the game on its own virtual display at native fullscreen and dock the other window in a zone next to it on the same monitor. It is genuinely on-screen and clickable, and the game never has to leave exclusive fullscreen. That is what Staged does on a single monitor.
Will borderless windowed fix it (and what does it cost)?
Yes, in the sense that once the game is Borderless Windowed everything lives in the composited desktop, so a topmost flag will keep your window visible. The cost is that you have traded exclusive fullscreen for the desktop compositor, which adds a small FPS and input-latency cost — and you are no longer keeping a window over true fullscreen, because you changed the game to windowed. A virtual display avoids that trade-off.
Does it work on one monitor?
Yes. Running the game on a virtual display and docking the window in a zone beside it happens entirely on the one screen you already have — no second monitor, no extra hardware, and it works on a laptop. The game stays full-size in its zone while the other window stays live next to it.
Will it lower my FPS?
Borderless windowed lowers FPS slightly because it routes the game through the desktop compositor instead of exclusive fullscreen. Forcing a topmost window over a fullscreen game can trigger the same compositor path. Running the game on its own virtual display keeps native-fullscreen performance with no borderless penalty and zero frame lag — you also choose the render resolution.
Keep the window visible without the topmost hack
Staged runs your game on a virtual display at native fullscreen and docks your other window in a zone beside it — genuinely on-screen and clickable, no topmost flag to be covered, no borderless FPS penalty, all on one monitor. It is coming to Steam; wishlist it to be first to play.
Related reading: