Fix the Steam too many requests error by identifying rate limits, shared IPs, VPNs and extensions, plus learn how long to wait before retrying.
Steam says “You’ve made too many requests recently” when its web services temporarily rate-limit your account, browser session or public IP address. Stop refreshing, close Steam web pages, disable scripts or extensions, and wait before trying again. If it persists, remove a VPN or proxy and start a clean browser or client session.
What does Steam’s rate-limit message mean?
It means Steam has refused a burst of requests to protect its Store, Community, Market or authentication services from excessive traffic. The response is commonly associated with the HTTP status 429.
The restriction may apply to one browser session, your Steam account, your public IP address or only the affected service. That is why your Library or game downloads might still work while the Community Market displays the error. It is not normally an account ban, a VAC penalty or proof that somebody has compromised your account.
What triggers “You’ve made too many requests recently”?
Repeated refreshing is the usual cause, but automated tools and shared internet addresses can generate far more requests than the user realises.
| Where it appears | Likely cause | Best first action |
|---|---|---|
| Store or Community pages | Rapid refreshing, duplicate tabs or a browser loop | Close the pages and stop retrying |
| Market or inventory | Searches, inventory scanning, an extension, script or trading tool | Disable automation and wait |
| Steam sign-in | Repeated login attempts or an expired session repeatedly authenticating | Stop signing in and allow the limit to reset |
| Several accounts on one network | A VPN, hotel, campus, workplace or carrier-grade NAT sharing one public IP | Use a normal private connection for one diagnostic test |
| One account on different networks | Account-level activity or an authorised tool making requests | Review account access and connected tools |
How do you fix the Steam too many requests error?
The reliable fix is to stop generating requests, let the restriction expire and then remove whatever caused the burst.
- Stop all retries. Close duplicate Steam Store, Community, profile, inventory and Market tabs. Do not keep refreshing or repeatedly press the sign-in button; a mistake we see constantly is checking every few minutes and extending the same pattern.
- Wait before testing once. For a brief manual burst, leave Steam’s affected page untouched for 30–60 minutes before making one test. If an auto-refresh tool, script or repeated login loop was involved, wait several hours or overnight. Steam does not publish a single cooldown that applies to every service.
- Disable extensions and automation. Turn off browser add-ons that inspect inventories, refresh listings or modify Steam pages. Stop bots, scripts and third-party tools using the account. Simply closing the visible tab may not stop an extension or background process.
- Remove shared network factors. Disconnect any VPN or proxy and retry later through your ordinary connection. A phone hotspot can be used for one diagnostic test: if it works there but not on the original network, the original public IP is probably limited. Restarting a router helps only if it receives a different public IP, and repeatedly cycling VPN exits is not a sensible workaround.
- Start a clean session after the wait. For a browser error, clear site data for
steampowered.comandsteamcommunity.com, restart the browser and sign in once. For an error inside the Steam client, exit Steam fully—including its background or notification-area process—and reopen it. Clearing site data signs you out but does not remove purchases or installed games. - Check account security if the traffic is unexplained. Review authorised devices and connected tools, revoke anything unfamiliar and remove any Steam Web API key you did not create. If there are other signs of unauthorised access, change the password and sign out other devices, then leave the account idle again before testing.
How long does the Steam rate limit last?
Steam does not publish a fixed duration, and separate services can use different limits. A small burst often clears after a period of inactivity, while continual retries, automation or traffic from a heavily shared IP can keep the error present for several hours.
The key is uninterrupted inactivity rather than a particular countdown. If the message remains after an overnight pause, a clean session, disabled extensions and one test on a second normal network, the problem needs closer account or service-level investigation.
Will clearing the cache or reinstalling Steam fix it?
Not by itself, because the active restriction is recorded on Steam’s servers rather than in the installed game files. Verifying game files, clearing the download cache or reinstalling Steam will not remove an account- or IP-based rate limit.
Browser cookies or client web data are worth clearing only after the waiting period, particularly when an expired login session is causing repeated authentication attempts. Doing it immediately and signing in over and over simply creates more requests.
What if the error keeps returning?
Recurring blocks usually reveal their cause through where they occur. An error confined to one browser points to its cookies or extensions; every device failing on one connection suggests a shared public IP; one account failing across separate connections suggests account activity or a connected tool.
If Store, Community and other Steam functions are failing for many users rather than showing only this rate-limit message, use our steps to separate a Steam outage from a local fault. If the client changes to an offline or connection message, follow the Steam network and no-connection checks instead. A sign-in attempt that produces code E87 is a different failure and needs the specific E87 authentication fixes.
If one account still receives the message after an overnight pause on two ordinary connections, with extensions and automation disabled, contact Steam Support. Include the affected page, approximate time, devices and networks tested, but never send a password or authentication code.