HTTP 200 — OK
HTTP 200
OK
The request worked and the response contains what was asked for.
What 200 actually means
This is the ordinary success response and the one behind nearly every page that loads correctly. What "OK" means depends on the method: for GET it means the body is the requested resource, for POST it means the action was carried out and the body describes the result. A 200 says nothing about whether the content is useful — a page reading "no results found" is still a 200, and so, unhelpfully, is many a broken site's error page.
Common causes
- A normal successful GET, POST, PUT or PATCH
- A cached response revalidated and served in full
If you're just trying to view the page
- Nothing — the request succeeded
- If the page looks wrong despite a 200, the problem is in the page itself, not the HTTP layer
If it's your site
- Do not return 200 for error conditions — "soft 404s" (an error page served with a 200) get pages indexed that should not be, and hide failures from monitoring
- Check that API errors carry a 4xx or 5xx rather than a 200 with an `{"error": …}` body
Reference
- Status code
- 200
- Reason phrase
- OK
- Category
- 2xx — Success
- Cacheable by default
- Yes
- Defined in
- RFC 9110 §15.3.1
Common questions
- What does HTTP 200 mean?
- The request worked and the response contains what was asked for. This is the ordinary success response and the one behind nearly every page that loads correctly. What "OK" means depends on the method: for GET it means the body is the requested resource, for POST it means the action was carried out and the body describes the result.
- How do I fix a 200 error?
- Nothing — the request succeeded
- Is 200 a client error or a server error?
- 200 is in the 2xx range, which means success. It is not an error at all.
Related pages
- 204 No Content The request succeeded and there is deliberately no body to send back.
- 201 Created The request succeeded and a new resource was created as a result.
- 206 Partial Content The server is returning only the requested byte range of a file, not the whole t
- 202 Accepted The request was accepted for processing, but the work has not finished yet.
- 207 Multi-Status A WebDAV response carrying separate status codes for several resources at once.
- 203 Non-Authoritative Information The request succeeded, but an intermediary modified the response on the way.
- 205 Reset Content The request succeeded and the client should clear the form that sent it.
- 208 Already Reported Inside a WebDAV multi-status response, this member was already listed earlier so
- 226 IM Used The server is returning a delta against a copy the client already has, rather th