Key takeaways:
- A 400 Bad Request error happens when a server can’t understand the request your browser sent, even though the server is working.
- Most 400 errors are client-side issues caused by things like invalid URLs, corrupted browser data, or browser extensions, not server outages.
- Starting with simple fixes like checking the URL, clearing cache and cookies, or trying another browser often resolves the issue quickly.
A 400 Bad Request error means the server couldn’t understand the request your browser sent. You’ll often see it when a page won’t load, a form won’t submit, or a file upload fails; usually without much explanation.
While it’s frustrating, this is a common client-side error and is often easy to fix without technical expertise. This guide is for everyday website users and small business owners who manage websites, dashboards, or online forms and need clear, fast solutions.
We’ll start with quick fixes you can try right away. If the issue persists, we’ll explain what’s happening behind the scenes and what to check next.
What is a 400 Bad Request error?
A 400 Bad Request error means the server couldn’t understand the request your browser sent.
Every time you visit a page, submit a form, or upload a file, your browser sends a specifically structured request to the website’s server. If something about it is missing, broken, or unexpected (e.g., malformed syntax or unsupported values), the server stops processing it and returns a 400 error instead.
This is usually a client-side issue, meaning the problem lies in the request, not in the website’s server. In many cases, the server is working fine, but can’t make sense of what it received.
You’ll often see 400 errors grouped with other 4xx HTTP status codes, which all point to request-related problems. For example:
- 401 errors relate to authentication or login issues
- 403 errors mean access is blocked
A 400 error is different: the server received your request but couldn’t understand it well enough to proceed.
Common reasons you’re seeing a 400 Bad Request error message
Most 400 Bad Request errors come from a small set of issues. In many cases, the error appears because something about the request doesn’t match what the server expects.
The most common causes include:
- Invalid or malformed URL
- Browser cache or cookies
- Browser extensions
- DNS or network issues
- File upload size or format limits
- Malformed requests in advanced scenarios
Invalid or malformed URL
A small issue in the web address can trigger a 400 error. This includes typos, extra characters, broken query strings, special characters, or outdated links that no longer match the server’s request processing. Even copying and pasting a URL from another source can introduce hidden characters that cause problems.
Browser cache or cookies
Browsers store cached files and cookies to speed things up, but outdated or corrupted data can interfere with new requests. When this happens, the server receives incomplete or conflicting information, which can result in a 400 error.
Browser extensions
Some browser extensions modify web requests before they’re sent. Ad blockers, password managers, and your most recently enabled extension can sometimes block fields, alter headers, or strip data the server needs, causing the request to fail.
DNS or network issues
Your device relies on DNS to translate website names into server addresses. If the DNS cache is outdated or your network connection is unstable, requests may be routed incorrectly or incompletely, leading to a 400 error.
File upload size or format limits
Many websites set server limits on file size, type, or request length. If an upload exceeds those limits (or uses an unsupported format), the server may reject the request and return a 400 error instead of processing it.
Malformed requests (advanced cases)
In more advanced situations, a 400 error can come from improperly structured data. This often affects APIs, embedded forms, or third-party integrations where required fields are missing, incorrectly named, or contain invalid JSON. These cases are less common for everyday browsing, but can affect site owners and form managers.
How to fix a 400 bad request error: Step-by-step
Start with the simplest steps first and work your way down. In many cases, the issue is resolved early, and you won’t need to try every option other than these six steps:
- Double-check the URL
- Clear browser cache and cookies
- Deactivate browser extensions
- Flush DNS or restart your network
- Compress or reduce file size
- Try another browser or device
Step 1: Double-check the URL
Carefully review the web address in your browser. Look for typos, extra characters, or incomplete links. If the link you’re trying to access is a bookmarked or saved link, try manually typing it instead.
Sometimes websites update their pages, which can affect the links on those pages. If you encounter a 400 Bad Request after clicking a link, try going to the site’s homepage and navigating to the correct page from there.
If you’re a website owner, then make sure you apply website navigation best practices.
Step 2: Clear browser cache and cookies
Clear cached files and cookies for the affected site in your browser settings. Then refresh the page or reopen your browser.
For a detailed walkthrough on how to do this for your specific browser, see our guide on clearing browser cache.
Outdated or corrupted stored data can cause your browser to send incorrect information, which the server may reject.
Step 3: Deactivate browser extensions
Temporarily disable browser extensions, especially ad blockers, password managers, and security add-ons. Reload the page to see if the error clears.
Some recently enabled extensions modify requests before they’re sent, potentially interfering with how the server processes them.
Step 4: Flush DNS or restart your network
Restart your router or modem, or refresh your device’s network connection. If you’re comfortable doing so, you can also flush your DNS cache through your operating system’s network settings.
Here’s how you can flush your DNS on different devices:
On Windows 7, 8, 10, and 11
- On the Windows search bar, type cmd to access the Command Prompt.
- Open the Command Prompt.
- Type ipconfig /flushdns in the Command Prompt and press Enter.
- Reload the website.
On macOS 11 Big Sur and later versions
- Use the Spotlight search to look for the Terminal app.
- Open Terminal app.
- On the Terminal app, type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
- Type your administrator password. Note: Your password will not be visible when you type.
For older macOS versions, try the following command:
MacOS version | Command |
|---|---|
MacOS Catalina | sudo killall -HUP mDNSResponder |
Mojave | sudo killall -HUP mDNSResponder |
High Sierra | sudo killall -HUP mDNSResponder |
Sierra | sudo killall -HUP mDNSResponder |
El Capitan | sudo killall -HUP mDNSResponder |
Mavericks | sudo killall -HUP mDNSResponder |
Mountain Lion | sudo killall -HUP mDNSResponder |
Lion | sudo killall -HUP mDNSResponder |
macOS 10.10 Yosemite | sudo discoveryutil mdnsflushcache sudo discoveryutil udnsflushcache |
Network or DNS issues can misroute requests or send outdated information, resulting in a 400 error.
Step 5: Compress or reduce file size
If the error appears during an upload, try reducing the file size or changing the file format. Consider using free online tools, such as compressor.io or Compress a PDF by Adobe, or built-in compression software to reduce the size of your files, making it easier for the server to process them.
Upload one file at a time if possible. Servers often limit upload size and request length. Exceeding those limits can result in the request being rejected.
Step 6: Try another browser or device
Open the page in a different browser or on a different device to see if the error persists.
If the page loads correctly in another browser, incognito mode, or on a different device, the issue is likely tied to settings or data in your original browser.
However, if none of these steps resolve the issue and you manage a website, form, or integration, the problem may be related to how requests are being sent or validated on your site.
What a 400 Bad Request means for website, form, and API owners
This section is optional and only applies if you manage a website, online forms, or system integrations. If you’re just browsing the web and hit a 400 error, the steps above are usually enough.
For site owners, a 400 Bad Request error often means the server received a request but rejected it before processing. Here are some of the most common reasons why the request was rejected:
- Request formatting issues
- Form or data validation problems
- Testing requests with developer tools
- Server-side limits
Request formatting issues
Websites expect submitted data in a specific structure. If required fields are missing, named incorrectly, or sent in the wrong format, the server may return a 400 error because it can’t properly interpret the request.
This often affects custom forms, APIs, and third-party integrations rather than standard web pages.
Form or data validation problems
Many forms and systems check data before accepting it. If a field is empty, contains unexpected characters, or fails validation, the request may be rejected immediately.
In these cases, the server is preventing incomplete or incorrect data from being processed.
Testing requests with developer tools
When troubleshooting more complex issues, developers often use tools like Postman to test requests outside of a browser. These tools help confirm whether the request structure and data are valid before they reach the server.
You don’t need to use these tools yourself, but knowing they exist can help when coordinating with technical support.
Server-side limits
Servers commonly enforce limits on file size, field length, or the number of requests that can be sent in a short period. If those limits are exceeded, the server may respond with a 400 error instead of processing the request.
These limits are especially relevant for file uploads, large forms, and automated integrations.
Is a 400 Bad Request error related to SSL or security issues?
It’s common to associate 400 Bad Request errors with SSL or security issues because these errors often occur during logins, form submissions, or on secure pages. While they can look similar on the surface, they usually point to different issues.
How a 400 Bad Request error differs from SSL or certificate errors
SSL or TLS errors happen when a secure connection between your browser and the website can’t be established.
In simple terms, a 400 error means the request reached the server but didn’t make sense. An SSL error means the connection never became secure enough to begin with. These are different problems, with different causes and different fixes.
When security settings can indirectly cause a 400 error
Security tools don’t typically cause 400 errors on their own. However, they can sometimes change or block parts of a request, which may trigger one.
Examples that affect small business websites include:
- A firewall or security plugin blocking certain form fields
- A web application firewall rejecting specific characters in a submission
- Security rules limiting upload size or request length
These situations are edge cases. In most situations, a 400 error is still caused by the request itself, not a security failure.
Signs you may be dealing with a different type of error
If the error message mentions:
- SSL certificates
- HTTPS warnings
- “Secure connection failed”
…then the issue is likely not a 400 Bad Request error and will require different troubleshooting. In those cases, the problem concerns secure connections rather than the request’s format.
Frequently asked questions
In many cases, yes. A 400 Bad Request error is often caused by temporary issues such as outdated browser cache, a malformed URL, or a failed form submission, and can be resolved quickly with basic troubleshooting.
Repeated 400 errors usually point to a recurring issue, such as corrupted browser cookies, a browser extension interfering with requests, or a form or URL that’s consistently sending incorrect data. If the error keeps appearing on one site or action, it’s a sign that something specific needs attention.
– If you’re seeing a loop or pages refreshing endlessly, you may be dealing with a Too Many Redirects error.
– If your website is timing out rather than rejecting the request, you may instead be seeing an Error 522.
– Server issues such as Error Code 521 indicate the server isn’t responding — unlike 400 errors, which stem from malformed requests.
400 Bad Request usually happens because of outdated cache cookies. To fix this on Google Chrome, open the kebab menu > Settings > Privacy and Security > Delete Browsing data > Clear Data.
Yes, clearing cookies can fix a 400 error in many situations. Cookies store site data, and if that data becomes outdated or corrupted, the server may reject your request.
An HTTP error 400 occurs when the server can’t understand the request it receives. This is usually caused by issues like an invalid URL, corrupted browser data, upload limits, or improperly formatted form or API requests.
You can fix a 400 Bad Request error by ensuring your URL is correct, clearing your browser’s cache and cookies, temporarily disabling your browser extensions, flushing your DNS, and making sure you have a stable internet connection.
You can encounter a 400 Bad Request when there’s a problem with your request. Sometimes, your browser can send an invalid request due to malformed message framing, usually caused by misspellings or missing characters in a URL. This causes the site’s server to refuse to process your request.
Ensure a smooth browsing experience with Network Solutions
A 400 Bad Request error may feel disruptive, but it’s temporary and fixable in most cases. Regardless of the issue’s cause, a few targeted checks are often all it takes to get things moving again.
If you want to understand related HTTP errors or troubleshoot other website issues, our Help Center and error code articles have clear, step-by-step resources that walk you through common scenarios in plain language. They’re there when you need answers without slowing you down.
And if you’re managing a business website, reliable hosting and proactive monitoring can help reduce unexpected errors altogether. Tools like dependable web hosting, SSL certificates, and site security services help keep your site stable for visitors, so you can focus on running your business rather than fixing errors.
