HTTP Status Codes
A searchable reference of standard HTTP status codes with their meaning, color-coded by class (1xx-5xx).
| Code | Name | Description |
|---|---|---|
100 | Continue | The server has received the request headers and the client should proceed to send the request body. |
101 | Switching Protocols | The server is switching protocols as requested by the client (e.g. to WebSocket). |
200 | OK | The request succeeded. |
201 | Created | The request succeeded and a new resource was created. |
202 | Accepted | The request was accepted for processing, but processing is not complete. |
204 | No Content | The request succeeded but there is no content to return. |
206 | Partial Content | Only part of the resource is being delivered, as requested via a Range header. |
301 | Moved Permanently | The resource has been permanently moved to a new URL. |
302 | Found | The resource temporarily resides at a different URL. |
304 | Not Modified | The resource has not changed since the last request (used with caching). |
307 | Temporary Redirect | Like 302, but the request method must not change. |
308 | Permanent Redirect | Like 301, but the request method must not change. |
400 | Bad Request | The server cannot process the request due to a client error (malformed syntax, invalid parameters). |
401 | Unauthorized | Authentication is required and has failed or not been provided. |
402 | Payment Required | Reserved for future use, sometimes used for API rate limit / payment issues. |
403 | Forbidden | The server understood the request but refuses to authorize it. |
404 | Not Found | The requested resource could not be found. |
405 | Method Not Allowed | The request method is not supported for the requested resource. |
406 | Not Acceptable | The requested resource cannot generate content matching the Accept headers. |
408 | Request Timeout | The server timed out waiting for the request. |
409 | Conflict | The request conflicts with the current state of the resource. |
410 | Gone | The resource is no longer available and will not be available again. |
411 | Length Required | The request did not specify the length of its content. |
413 | Payload Too Large | The request entity is larger than limits defined by the server. |
414 | URI Too Long | The URI requested by the client is longer than the server is willing to interpret. |
415 | Unsupported Media Type | The media format of the requested data is not supported. |
418 | I'm a teapot | An April Fools' joke from RFC 2324 — the server refuses to brew coffee because it is a teapot. |
422 | Unprocessable Entity | The request was well-formed but contains semantic errors. |
423 | Locked | The resource that is being accessed is locked. |
425 | Too Early | The server is unwilling to process a request that might be replayed. |
426 | Upgrade Required | The client should switch to a different protocol. |
428 | Precondition Required | The origin server requires the request to be conditional. |
429 | Too Many Requests | The user has sent too many requests in a given amount of time (rate limiting). |
431 | Request Header Fields Too Large | The server refuses to process the request because header fields are too large. |
451 | Unavailable For Legal Reasons | The resource is unavailable due to a legal demand. |
500 | Internal Server Error | A generic error message when an unexpected condition was encountered. |
501 | Not Implemented | The server does not support the functionality required to fulfill the request. |
502 | Bad Gateway | The server, acting as a gateway, received an invalid response from an upstream server. |
503 | Service Unavailable | The server is currently unable to handle the request (overloaded or down for maintenance). |
504 | Gateway Timeout | The server, acting as a gateway, did not receive a timely response from an upstream server. |
505 | HTTP Version Not Supported | The server does not support the HTTP protocol version used in the request. |
507 | Insufficient Storage | The server is unable to store the representation needed to complete the request. |
508 | Loop Detected | The server detected an infinite loop while processing the request. |
511 | Network Authentication Required | The client needs to authenticate to gain network access. |
HTTP Status Codes — Free Online Tool
A searchable reference of standard HTTP status codes with their meaning, color-coded by class (1xx-5xx).
How to use the HTTP Status Codes
- Open the tool above — it runs entirely in your browser, so your input never leaves this page.
- Paste or type your input into the field, then press the relevant button (e.g. Encode / Decode, Generate, or Convert).
- Copy the result from the output area with the copy button orCtrl/Cmd + C.
- No signup, no upload, and no tracking — repeat as often as you need.
Frequently asked questions
Is the HTTP Status Codes free to use?
Yes. The HTTP Status Codes is completely free, with no signup, no ads inside the tool, and no hidden limits.
Does the HTTP Status Codes upload my data?
No. The HTTP Status Codes processes everything locally in your browser. Your input is never sent to a server, so it stays private even on shared devices.
Does the HTTP Status Codes work offline?
After the page loads, the HTTP Status Codes runs entirely in your browser, so it keeps working without a network connection.
Free & private — why use this HTTP Status Codes
The HTTP Status Codes runs 100% client-side in your browser. Your data is never uploaded to a server, no account is required, and the tool is completely free. It works offline once the page has loaded and is part of a growing collection of privacy-first developer utilities.