---
title: "200 OK — what it means and how to fix it"
description: "The request worked and the response contains what was asked for. What causes an HTTP 200, what to try as a visitor, and what to check if it is your own site."
url: https://atoneplace.net/error/200/
site: "At One Place"
---

# 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

1. Nothing — the request succeeded
2. If the page looks wrong despite a 200, the problem is in the page itself, not the HTTP layer

## If it's your site

1. 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
2. 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](https://atoneplace.net/error/204/)
- [201 Created](https://atoneplace.net/error/201/)
- [206 Partial Content](https://atoneplace.net/error/206/)
- [202 Accepted](https://atoneplace.net/error/202/)
- [207 Multi-Status](https://atoneplace.net/error/207/)
- [203 Non-Authoritative Information](https://atoneplace.net/error/203/)
- [205 Reset Content](https://atoneplace.net/error/205/)
- [208 Already Reported](https://atoneplace.net/error/208/)
- [226 IM Used](https://atoneplace.net/error/226/)

## Sources

- Hypertext Transfer Protocol (HTTP) Status Code Registry — IANA (https://www.iana.org/assignments/http-status-codes/)
- RFC 9110: HTTP Semantics — IETF (https://www.rfc-editor.org/rfc/rfc9110.html)