The Steam Deck compositor overlay can get stuck; use the steps below to clear it, reset overlays, or reboot safely.
What’s Happening When The Overlay Sticks
On the Deck, Gamescope acts as the session compositor that frames your games and swaps buffers. When its stats window or a game session refuses to close, it can look like inputs do nothing. The root cause is usually a lingering process, a game that didn’t exit cleanly, a shortcut that toggled the meter back on, or the Steam client’s performance monitor stacking with the Deck HUD.
You can clear this with a short checklist. Start with the least disruptive steps. Move to resets only if the overlay still refuses to disappear.
Gamescope Overlay On Steam Deck Stuck — Quick Causes And Cures
Use this map of symptoms and fast actions. Work from top to bottom before trying deeper fixes.
| Symptom | Likely Cause | Quick Action |
|---|---|---|
| FPS/CPU/GPU box lingers after quitting | Deck HUD level toggled or Steam overlay monitor active | Open Quick Access (three dots) → Battery icon → set Performance Overlay Level to 0 |
| Game closes but a black frame stays | Child window ended; compositor session still up | Steam button → Power → Exit game; if stuck, use Steam + B (long press) to close the foreground window |
| Controls respond slowly, overlay flickers | Runaway process or high load | Quick Access → Performance → toggle Frame Limiter; if still jittery, use Restart from the Power menu |
| Nothing reacts at all | Session hang | Hold Power 4 seconds (7 on OLED) for soft restart; if needed, hold 10 seconds (16 on OLED) for forced shutdown |
| Overlay returns every launch | Setting persists or extra monitor enabled | Set Deck HUD to 0 in-game and in Desktop Mode; disable other performance monitors |
Step-By-Step Fixes That Work
1) Toggle The Deck HUD Off
Press the three-dot button to open Quick Access. Move to the battery icon. Set Performance Overlay Level to 0. If the slider looks frozen, nudge it up one level and back down. Return to the game and check the corner of the screen.
2) Check The Steam Overlay Performance Monitor
Recent client builds add a PC-style performance monitor inside the Steam overlay. If you turned that on, it can stack with the Deck HUD. Open the Steam overlay in-game, head to Settings → In-Game, and turn off the monitor there. That stops two overlays from competing.
3) Close The Current Game Session Cleanly
Tap the Steam button, pick Power, and choose Exit Game. If the session ignores that, press Steam + B for a few seconds to send a close request to the active window. Give it a moment to release control. If a black frame lingers, move on.
4) Restart The Steam Client Shell
Open the Power menu again and select Restart. This refreshes SteamOS services and flushes the session the compositor is managing. After the restart, launch a small title to confirm the meter is gone.
5) Use A Safe Forced Reboot
When inputs stop responding, reach for the hardware buttons. Hold Power for 4 seconds (7 on OLED) to trigger a soft restart. If nothing happens, hold for 10 seconds (16 on OLED) to force a shutdown. Wait a second, then power on. Valve documents these timings in its Deck guide under basic use & troubleshooting.
6) Reset Conflicting Monitors In Desktop Mode
Switch to Desktop Mode. Open Steam’s Settings → In-Game and disable the PC performance monitor. If you run MangoHud or similar tools, turn them off for a test. Launch a game from Desktop Mode, confirm no stats layer appears, then return to Gaming Mode.
7) Update SteamOS And The Client
Install pending updates. Deck updates ship fixes for HUD accuracy and timing. After updating, reboot once, then test with a known stable title.
Why The Meter Hangs At All
Gamescope is a micro-compositor Valve uses to present games in a controlled surface. It can run nested or as the session itself. On the Deck, it forms the glue between a game and the display stack, which is why a stuck session can make the device look frozen. Sometimes a game window exits but the session still expects a child surface; sometimes a performance monitor remains active after a game quits. Clearing the setting or restarting the shell resolves both patterns in most cases.
If you’d like a plain technical overview of what this compositor does, the ArchWiki page on Gamescope covers goals, features, and common flags without extra fluff.
Safe Modes, Buttons, And Recovery
Soft Restart Versus Full Shutdown
A short press on Power opens the menu. A timed hold sends a hardware signal. Use the menu when the UI still moves. Use the timed hold when inputs stop responding. Match the hold length to your model: 4 or 10 seconds on LCD, 7 or 16 seconds on OLED (as linked above).
Boot To BIOS When Needed
If crashes repeat at startup, power down completely. Hold Volume Up and tap Power, keep holding Volume Up until the chime, then enter the BIOS menu. From there you can back out to a normal boot or enter storage mode. You rarely need this for a stuck HUD, but it helps when a plugin wrecks the session.
Settings To Review After You’re Back In
Deck HUD Level
Set the Performance Overlay Level to 0 for daily play. Levels 1–4 add extra detail when you’re testing. The higher the level, the more screen space the readout uses. Keep it off unless you’re tuning a game.
Steam Overlay Performance Monitor
On the latest client, the monitor lives under Settings → In-Game. Pick one metrics layer: either the Deck HUD or that monitor. Running both makes troubleshooting harder and can keep a box on-screen when you don’t expect it.
Frame Limiter, V-Sync, And VRR
In Quick Access → Performance, set a frame cap that matches your refresh rate. Matching caps cut jitter and keep overlays stable. If the counter looks weird after a crash, toggle the cap and V-Sync once to resync the session.
Common Scenarios And Exact Fixes
The Box Reappears Every Launch
Toggle the HUD to 0 inside a game. Then repeat that in Desktop Mode. If the Steam overlay monitor is on, switch it off. Launch a small title to confirm the corner stays clear.
Black Screen After Exit
Send a close request with Steam + B, wait a moment, then open the Power menu and choose Restart. After the restart, test with a different title to rule out a single-game quirk.
Overlay Flickers Or Misreports
Lower the level to 1, toggle the frame limiter once, then raise the level again if you need detail. Install updates and reboot. Flicker usually points to timing changes that a restart cleans up.
Advanced Checks For Power Users
Desktop Mode Process Sweep
Open the system monitor in Desktop Mode and look for a hanging game binary. End it. Return to Gaming Mode and launch a small app to confirm a clean session. Reboot once if the HUD appears at login.
Launch Options And Extra Tools
Clear custom launch flags that spawn a compositor instance or inject a third-party overlay. If you added extra arguments in the past, remove them for a clean test. Keep only one stats layer active while troubleshooting.
Recreate The Issue Safely
Pick a small title and toggle the HUD while closing the game different ways: Power menu, Steam + B, then a full Restart. This reveals the step that fixes your setup fastest next time.
Authoritative References For Context
Valve documents restart holds and recovery paths here: basic use & troubleshooting. For background on the compositor that frames Deck sessions, see the Gamescope overview.
Docked Setups And External Displays
When docked, a stuck session can leave the TV on a black frame. Unplug the HDMI/USB-C video path, then plug it back after a Restart. If the overlay box returns only while docked, drop the HUD to 0, set a frame cap that matches the external display, and test again. Keep only one metrics layer active.
Plugin And Mod Notes
Tools installed in Desktop Mode can add their own overlays. If you’ve tried shader mod managers, power tools, or custom HUDs, disable them one by one for a test. The goal is a clean game launch with no overlays. Add tools back only if the issue stays gone.
| Check | What You’re Looking For | Action To Take |
|---|---|---|
| Overlay level in Quick Access | Not set to 0 when you don’t need stats | Move slider to 0; restart the game |
| Steam In-Game performance monitor | Enabled while Deck HUD also on | Disable one of them to avoid duplicates |
| Hanging game process | Game binary still present after exit | End task in Desktop Mode; reboot if needed |
| Out-of-date client or OS | Pending updates listed | Apply updates; retest with a light game |
| Hardware-level freeze | No input response at all | Use the timed Power hold for restart |
When To Seek Help
If a clean boot with the HUD at 0 still drops a stats box into every title, gather details: model (LCD or OLED), current SteamOS version, client channel, display used (built-in or external), and any overlay tools installed in Desktop Mode. Open a ticket with Valve support from a browser and attach your notes and a photo. Try a known stable game to show that the behavior isn’t tied to one title.
Keep Your Deck Calm
Stick to a simple routine: keep overlays off unless you’re testing, apply updates, match your frame cap to the display refresh, and use the Power menu before any hard hold. If a game locks the screen, Steam + B to close the window, then Restart. With that flow, the compositor and its HUD stay out of the way when you just want to play.