Steam Client WebHelper (steamwebhelper.exe) using high CPU

Valve fixed a specific case of steamwebhelper high CPU triggered by events shown in the library tab, and shipped it as a re-release of the 1 September client rather than as a new update entry.

Applies to: Steam on Windows 10, Steam on Windows 11

1. In Steam, open the Steam menu in the top-left and choose "Check for Steam Client Updates". Let it download and restart.
2. Open the Steam menu again and choose "About Steam". Check that the build date shown is 6 September 2026 or later.
3. Use Steam normally for a few minutes and re-check Task Manager. If the client was already on that build or later, this was not your cause — carry on to the next step.

Confirmed by the vendor.

Source: Valve

steamwebhelper renders the client's web UI, so the load usually follows one particular page. Knowing which one tells you whether any of the settings below are worth changing at all.

Applies to: Steam on Windows 10, Steam on Windows 11

1. Open Task Manager with Ctrl+Shift+Esc, expand the Steam entry, and keep the "Steam Client WebHelper" rows visible while you use Steam.
2. Put Steam on the Library home screen and note the CPU figure. This is the screen carrying the What's New panel, the view most often reported to drive this.
3. Switch to a different tab — Store, Community, or a single game's page — and wait about thirty seconds. If CPU drops, the Library home screen is your trigger and you can simply avoid starting Steam there.
4. Repeat on a store page that auto-plays video, and again with a game running and the overlay enabled, so you know which of the two fixes below is the one to try.

Confirmed by the vendor.

Source: Valve, Steam Community, Steam Community

These hand the client's web views to the GPU. Valve exposes them as troubleshooting toggles, so turning them off changes how the same content is rendered. Reports are mixed — at least one user found it made no difference for them.

Applies to: Steam on Windows 10, Steam on Windows 11

1. In Steam, open Settings and select Interface.
2. Turn off "Enable GPU accelerated rendering in web views".
3. Turn off "Enable hardware video decoding, if supported".
4. Restart Steam, then re-check CPU on the view you identified in the previous step.
5. If nothing changed, turn both back on. They exist to make the client cheaper to render, not more expensive, and leaving them off for no benefit only costs you.

Reported to work by 2 users; not confirmed by the vendor. 1 report it did not help.

Source: Steam Community, Steam Community

Animated avatars and frames are video the client keeps decoding, and the overlay runs another web view on top of the game. Reports here are genuinely split: one user measured the overlay change taking WebHelper from about 15 per cent to nothing, another saw little change.

Applies to: Steam on Windows 10, Steam on Windows 11

1. In Steam, open Settings and select Friends & Chat, then turn off animated avatars and animated avatar frames.
2. To test the overlay for one game only, right-click the game in your Library, choose Properties, and turn off the Steam Overlay under General. Prefer this over the global setting if you use the overlay elsewhere.
3. To turn it off everywhere, open Settings, select In Game, and turn off "Enable the Steam Overlay while in-game".
4. Be aware of what this costs: with the overlay off you lose the in-game Steam browser, in-game screenshots via Steam, and in some games the Steam Input configuration UI.

Reported to work by 2 users; not confirmed by the vendor. 1 report it did not help.

Source: Steam Community