HTTP 404 Not Found
What a 404 Not Found response means, why it happens, and the fastest ways to fix it.
The server can't find anything at the requested URL. It says nothing about whether the resource ever existed or will exist.
- Typo in the URL or route not registered.
- Resource deleted or ID wrong in an API call.
- SPA routes without a server-side fallback to index.html.
- Trailing-slash or case-sensitivity mismatches.
- Check the exact path against the server's route table.
- For SPAs, configure a rewrite of unknown paths to index.html.
- Return 410 instead if the resource is gone permanently, and set up 301s for moved content.
Notes
HTTP status codes are defined in RFC 9110 (which replaced RFC 7231). The first digit is the class: 1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error.
Same class: 400 · 401 · 403 · 405 · 408 · 409 · 410 · 412 · 413 · 415 · 418 · 422 · 425 · 429 · 431 · 451
All codes: HTTP status code reference
Frequently asked questions
What does HTTP 404 mean?
HTTP 404 Not Found: The server can't find anything at the requested URL. It says nothing about whether the resource ever existed or will exist.
How do I fix a 404 error?
Check the exact path against the server's route table. For SPAs, configure a rewrite of unknown paths to index.html. Return 410 instead if the resource is gone permanently, and set up 301s for moved content.
Is a 404 my fault or the server's?
404 is a client error — the request itself needs to change, though server misconfiguration can also trigger it.