HTTP error 431 (Request Header Fields Too Large) in Google Chrome means the website server rejected your request because the total size of the HTTP headers sent by your browser exceeded the server’s limit. The fix is usually to clear your browser cookies and site data for that specific site, or to remove problematic extensions that inflate your headers.
What Causes Error 431
Every time your browser requests a webpage, it sends HTTP headers—small pieces of metadata that include cookies, authentication tokens, user-agent strings, and custom headers set by extensions. Most servers cap the total header size at 8 KB or 16 KB. When your headers exceed that limit, the server responds with 431 Request Header Fields Too Large instead of the page you wanted.
The most common culprits are:
- Too many cookies for a single domain, often from years of accumulated tracking and session data.
- A corrupted or oversized cookie—some sites store large JSON objects in cookies that can balloon past the limit.
- Browser extensions that inject custom headers (e.g., ad-blockers, privacy tools, or developer extensions) can add hundreds of bytes per request.
- Malware or adware that modifies browser settings and adds unwanted headers.
- A misconfigured proxy or VPN that adds its own headers to every request.
Quick Fix: Clear Cookies and Site Data
The fastest solution is to clear the cookies and site data for the specific site that’s showing the error. This removes any oversized or corrupted cookies while keeping your other logins intact.
- Click the lock icon (or “Not secure”) in the address bar next to the site URL.
- Select Cookies and site data (or Site settings depending on your Chrome version).
- Click Manage cookies and site data.
- Click the trash icon next to each cookie listed, or click Remove all.
- Reload the page.
If you don’t see the lock icon (e.g., on a browser that hides it), you can also go to Settings > Privacy and security > Cookies and other site data > See all cookies and site data, search for the domain, and delete its entries.
Disable Extensions That Modify Headers
Extensions are a common hidden cause of error 431 because they can add custom headers to every request. To test if an extension is the problem:
- Open Chrome and click the three-dot menu > Extensions > Manage extensions.
- Toggle off all extensions (or at least ad-blockers, privacy tools, and developer tools).
- Reload the page that gave the 431 error.
- If the page loads, turn extensions back on one by one to find the culprit.
If you’re using a privacy extension that blocks tracking, it may be storing a large number of block rules in a cookie. Clearing that extension’s data (via the extension’s options) can also help.
Clear Browser Cache and Reset Settings
Sometimes the issue isn’t a specific cookie but a corrupted cache entry or a browser setting that’s gone wrong. A broader reset can help:
- Clear the cache: Go to Settings > Privacy and security > Clear browsing data, choose “All time,” and check “Cached images and files.” Uncheck cookies if you want to keep logins.
- Reset Chrome settings: Go to Settings > Reset settings > Restore settings to their original defaults. This disables extensions and clears temporary data, but keeps bookmarks and passwords.
- Check for malware: Run Chrome’s cleanup tool at Settings > Reset settings &strong> Clean up computer to remove software that might be altering your browser.
Advanced Fixes: Proxy, VPN, and Developer Tools
If the error persists after clearing cookies and disabling extensions, the problem may be outside Chrome:
- Disable your VPN or proxy temporarily. Some VPN services add large headers for authentication. Try connecting directly to your network.
- Check browser flags. Type
chrome://flagsin the address bar and look for any experimental features that might affect networking. Reset all flags to default by clicking “Reset all.” - Use Incognito mode. If the site loads in Incognito (which blocks extensions by default and uses a fresh session), the issue is likely a cookie or extension.
- Inspect the headers yourself. Press F12 to open Developer Tools, go to the Network tab, reload the page, and click the failed request. Look at the “Request Headers” section—if you see a huge cookie string (often thousands of characters), that’s your smoking gun.
If you’re a developer testing your own site, you can also increase the server’s header limit (e.g., in nginx or Apache), but that’s not something regular Chrome users can do.
Preventing Error 431 in the Future
To reduce the chances of seeing 431 again:
- Regularly clear cookies for sites you don’t use often, especially after a long browsing session.
- Use a reputable ad-blocker that doesn’t store large amounts of data in cookies.
- Keep your extensions minimal. Each extension that adds headers increases your header size.
- Avoid using public Wi-Fi with aggressive captive portals that might inject headers.
- Update Chrome regularly—older versions may have bugs that cause header bloat.
Frequently Asked Questions
Why does error 431 happen only on one website?
Each website has its own server configuration with a specific header size limit. A site with a low limit (e.g., 8 KB) will trigger 431 more easily than one with a higher limit. Also, some sites set many cookies, which can accumulate over time and push you over the limit.
Will clearing cookies log me out of the site?
Yes, clearing cookies for a site will log you out of that site. You’ll need to sign in again, but your bookmarks, history, and passwords (if saved) remain intact.
Can error 431 be caused by a virus?
Yes, malware can modify your browser to add extra headers or create fake cookies that bloat your requests. Running Chrome’s cleanup tool or a reputable antivirus scan is a good idea if the error persists after other fixes.
Does error 431 affect mobile Chrome?
Yes, mobile Chrome can also show 431 if the site sets too many cookies or if a mobile extension (rare) adds headers. The fix is the same: clear site data or disable extensions.
Is error 431 dangerous?
No, it’s a harmless error message—it just means the server refused your request. It doesn’t indicate a security threat, but it can be annoying because you can’t access the site.
What if the error appears on every site?
If you get 431 on every site, the problem is likely a global browser issue—a misbehaving extension, a corrupted profile, or malware. Try resetting Chrome settings first, then reinstall Chrome if needed.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix Text Cursor Turning White in Windows 11
- Force Quit Non-Responding Apps on Mac: 6 Ways
- Chromebook Not Charging? Fix It Fast
- iPhone Won’t Make Calls but Texts Work? Fixes
- Android to iPhone Hotspot: Connect & Fix Issues
- How to Auto-Enable Low Power Mode on iPhone