A 404 Not Found is an HTTP response telling you that a website’s server received a request but could not find a current resource at that URL. The resource might be a web page, image, download, API object, or another file. It is a client-error response, not proof that the entire website is offline and not proof that the page was permanently deleted.
What a 404 error means
When you enter a URL, your browser asks a web server for the resource identified by that address. If the server can locate a current representation, it returns the content with a successful status. If it cannot locate the requested resource, it can return HTTP status 404 Not Found.
As an Amazon Associate I earn from qualifying purchases.
In standards terms, HTTP 404 means that the origin server did not find a current representation for the target resource, or is not willing to disclose that one exists. In ordinary language: the request reached a web server, but the server could not provide the page, file, record, or other item named by the URL.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →The status code belongs to HTTP’s 4xx client-error class. “Client” here refers to the request and its target, not necessarily to a mistake by the person using the browser. A site can return 404 because its content moved, its routing is wrong, or it intentionally hides whether a restricted resource exists.
#1 Best Overall
What can return 404?
- A normal HTML page such as
/news/article-123. - An image, stylesheet, JavaScript file, PDF, or other download.
- An API endpoint’s specific object, such as a user, order, or product ID that does not exist.
- A route generated by a content-management system or application that has no current representation.
A 404 is therefore about one requested resource. It does not automatically mean that the domain, server, or every page on the site is unavailable.
Why websites return 404
The address is incorrect
A single wrong character can identify a different path. Common examples include a misspelling, an omitted or added hyphen, incorrect capitalization on a case-sensitive system, misplaced punctuation, or an extra character copied into the address. A stale bookmark or a link broken by line wrapping can have the same effect.
The content moved
A site owner may have changed a page’s URL during a redesign, category change, or migration. If the old address does not redirect to the new one, requests for the old address can produce 404. Internal links, search results, social posts, and bookmarks can continue sending visitors to that old location.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →The content was removed
A page or file may have been deleted while references to it remained. However, a 404 alone does not prove deletion or permanence. The owner might restore the resource, correct a routing problem, or add a redirect later.
An API object does not exist
An API endpoint can be valid while the particular record requested is absent. For example, a request to an existing endpoint with an ID for a deleted or never-created object may return 404. The endpoint itself may still work for other IDs.
The application has no route for the path
Web applications map URL paths to pages or actions. A deployment error, an incorrect route, or a missing rewrite rule can leave a path with no current representation even though the site and its code are running.
The site is deliberately withholding information
The HTTP specification allows a server to use 404 when it is not willing to disclose that a restricted resource exists. In that situation, the response does not tell an observer whether the resource is absent or intentionally concealed.
Recommended Free Tools
Does a 404 mean the page was permanently deleted?
No. HTTP 404 leaves permanence unspecified. It can describe a temporary absence, an incorrect URL, a moved page without a redirect, or a resource that is gone for good.
When an origin knows that a resource has been permanently removed and will not return, the HTTP standard identifies 410 Gone as the more appropriate status. A visitor should not infer 410 merely because a site displays 404, and a site owner should not use 404 as a declaration of permanent deletion unless that is the site’s deliberate policy.
Is 404 a server error?
A server sends the 404 response, but 404 is not in the 5xx server-error class. It is an HTTP response that says the requested target could not be found or disclosed. Calling it a “server not found” error is misleading because it can be confused with a failure to locate or connect to the server itself.
| Message or status | What failed | What it usually suggests |
|---|---|---|
| 400 Bad Request | The request is malformed or cannot be understood. | Correct the request syntax, parameters, or formatting. |
| 403 Forbidden | The server understood the request but refuses access. | Authentication, authorization, or access policy may be involved. |
| 404 Not Found | No current representation was found for the requested target, or its existence is being withheld. | Check the URL, routing, redirect, or requested record. |
| 410 Gone | The resource is known to be permanently removed. | Use the replacement URL, if one exists, or remove the reference. |
| DNS or connection failure | The browser could not resolve the domain or establish an HTTP connection. | No HTTP status may have been received at all; check the network, DNS, domain, or server availability. |
How to fix a 404 as a visitor
These steps are appropriate when one page, file, or API resource fails while you are trying to use a site.
- Inspect the complete address. Check spelling, punctuation, capitalization, slashes, file extensions, and any extra characters at the beginning or end. If you pasted the URL, remove accidental spaces or copied punctuation.
- Try the site’s home page. Open the domain without the failing path, then use the site’s navigation. This can reveal a renamed section or a replacement page.
- Use the site’s search. Search for the page title, product name, article headline, or file name rather than repeating the broken link.
- Remove stale path segments only when the structure makes that sensible. For example, going from a deeply nested article address to its visible category can help you find the current location. Do not randomly delete characters from a URL that contains an API version, identifier, or required file name.
- Try the corrected or replacement address. If a link came from an email, bookmark, search result, or another site, look for a newer link from the same publisher or organization.
- Retry later when a move may be temporary. A site owner can restore a resource or repair routing. A later attempt may therefore produce different results, but repeated retries cannot fix a permanently wrong address.
- Contact the site owner when the link should work. Include the exact URL, the page where you found it, and the approximate time. This gives the owner enough information to repair a broken internal link or add a redirect.
If only one download or image is missing
Reload the page after confirming the address of the individual file. If the surrounding page loads, the site is reachable and the missing item may have been moved or removed independently. Use the page’s current download control instead of relying on an old direct-file link.
If an API request returns 404
Verify the base URL, API version or path, spelling, capitalization, and resource identifier. Confirm that the record still exists and that you are requesting the intended environment. A valid endpoint can still return 404 for one nonexistent object, so test only with an identifier you know should be present and follow the service’s own documentation for the correct address.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to fix 404s as a site owner or developer
Confirm what the server is receiving
Start with the exact failing URL, including its path and capitalization. Check whether the request reaches the intended site, application, virtual host, or deployment. Compare a failing address with a known-good address in the same section to identify a spelling, routing, or rewrite difference.
Repair internal links
Update menus, related-content links, navigation elements, sitemaps, feeds, and templates that still point to the old path. A custom 404 page can help visitors recover, but removing the broken reference prevents the error from recurring.
Rank #4
Add a redirect when content has moved
Map the old URL to the current, equivalent resource when a replacement exists. Preserve the useful destination rather than redirecting every missing path to the home page; a precise redirect gives visitors and automated clients a meaningful result.
Handle permanent removals deliberately
If the origin knows that a resource will not return, decide whether the correct response is 410 or a redirect to a genuinely equivalent replacement. Do not label every temporary routing problem as permanently gone.
Check application routes and records
For dynamic pages and APIs, verify that the route is registered, the deployment contains the expected files or handlers, and the requested identifier maps to a current record. A route can be present while one record is absent, so diagnose the path and the underlying object separately.
Provide a useful custom 404 page
A clear custom page should state that the requested resource was not found and offer working navigation or search. Keep the page itself available at a stable address. The goal is to minimize broken links and help the visitor reach valid content, not to disguise the status.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsOn Apache, MDN documents this configuration pattern for assigning a custom page:
ErrorDocument 404 /notfound.htmlThe path in that example must match a real page on the site, and the exact configuration location depends on the server’s setup. After changing routing or redirects, test the old URL, the new URL, nearby paths, and the custom error page so that a fix does not create another chain of missing resources.
What a 404 page can tell you—and what it cannot
- It confirms that an HTTP response was returned for the request.
- It identifies a missing or undisclosed representation for that target at the time of the request.
- It does not establish that the entire website is down.
- It does not establish that the page was deleted permanently.
- It does not by itself indicate malware, a virus, or a problem with your computer.
- It does not prove that the visitor caused the problem; site links and routing are frequent causes.
As an optional shortcut after you have checked the address and site, Outbyte PC Repair can look for certain common Windows issues, including broken system elements, invalid redirects, shared DLL problems, and crash-related issues; it also offers cleanup and diagnostic features. It complements antivirus software rather than replacing it, results vary, and no tool repairs every website or application failure. It runs on Windows 11, 10, 8, and 7, with a free trial by category of at least two days followed by a paid subscription.
The practical interpretation is simple: a 404 means the server answered but could not provide the resource named by that URL. Visitors should verify the address and find the site’s current navigation; owners should repair links, routes, records, redirects, and the custom error experience. Only the site’s owner can determine whether the absence is temporary, intentional, or permanent.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
