Complete reference for all standard HTTP status codes. Search by code number or keyword, filter by category, and click any code to see its description, common use cases, and example response. Everything runs client-side -- your data never leaves your browser.
Type any status code number or keyword to instantly find the code you need. The search matches against code numbers, names, and descriptions for fast discovery.
Status codes are organized by category with distinct colors: gray for 1xx Informational, green for 2xx Success, blue for 3xx Redirection, orange for 4xx Client Error, and red for 5xx Server Error.
Click any status code to expand its details including a full description, common real-world use cases, and an example HTTP response showing typical headers and body.
Copy any status line (e.g., "200 OK" or "404 Not Found") to your clipboard with a single click. Useful when writing documentation, tests, or API specifications.
HTTP status codes are standardized three-digit numbers that a web server returns in response to every HTTP request. Defined in RFC 9110 and related specifications, these codes tell the client whether the request was successful, needs further action, or encountered an error. Understanding status codes is essential for web developers, API designers, and system administrators.
HTTP status codes are grouped into five classes based on their first digit:
Proper use of HTTP status codes is a cornerstone of RESTful API design. Using the correct status code helps API consumers understand exactly what happened without parsing the response body. For example, returning 201 Created (with a Location header) after creating a resource, 204 No Content after a successful deletion, or 422 Unprocessable Entity for validation errors communicates intent clearly and enables better error handling on the client side.
A frequent mistake is returning 200 OK for every response and encoding the actual status in the response body (e.g., {"status": "error"}). This defeats the purpose of HTTP status codes and makes it harder for clients, proxies, and monitoring tools to handle responses correctly. Another common error is confusing 401 (not authenticated) with 403 (authenticated but not authorized), or using 302 when 307 or 308 would be more appropriate to preserve the request method.
Check out our other free developer tools. Decode JWTs, format JSON, parse cron expressions, and more -- all from your browser with no sign-up required.
JSON Formatter →