HTTP Status Codes
Lookup HTTP status codes by number, name, or keyword. With plain-English explanations.
- 100
Continue
Server received request headers; client should send the body.
- 101
Switching Protocols
Server is switching protocols as requested by the client (e.g., to WebSocket).
- 200
OK
Standard success response. The most common status code.
- 201
Created
Request succeeded and a new resource was created. Common for POST that creates an entity.
- 202
Accepted
Request accepted but not yet processed. Used for async operations.
- 204
No Content
Success, but no body returned. Common for DELETE.
- 206
Partial Content
Server delivered a partial range as requested. Used for resumable downloads.
- 301
Moved Permanently
Resource has permanently moved. Browsers cache this aggressively — use carefully.
- 302
Found
Temporary redirect. Method may change to GET on follow.
- 303
See Other
Tells the client to GET another URL after a non-GET request (POST/Redirect/GET pattern).
- 304
Not Modified
Cached version is still valid. Used with conditional GETs (If-None-Match / If-Modified-Since).
- 307
Temporary Redirect
Like 302 but the method must NOT change (POST stays POST).
- 308
Permanent Redirect
Like 301 but the method must NOT change.
- 400
Bad Request
Generic client error. The request was malformed or invalid.
- 401
Unauthorized
Authentication required. Despite the name, it's about authentication, not authorization.
- 402
Payment Required
Reserved. Some APIs (Stripe) use it for billing-related errors.
- 403
Forbidden
The server understood you, but you're not allowed to do this. About authorization.
- 404
Not Found
Resource doesn't exist.
- 405
Method Not Allowed
The HTTP method (GET/POST/etc) isn't supported on this resource.
- 406
Not Acceptable
Server can't produce a response matching the Accept-* headers.
- 409
Conflict
The request conflicts with current state (e.g., duplicate key, edit conflict).
- 410
Gone
Resource has been permanently removed and won't return.
- 413
Payload Too Large
Request body is bigger than the server is willing to handle.
- 415
Unsupported Media Type
Body's Content-Type isn't supported.
- 418
I'm a teapot
April Fools' joke from RFC 2324. Some APIs use it for rate limiting humor.
- 422
Unprocessable Content
Request was well-formed but had semantic errors. Common for validation failures.
- 429
Too Many Requests
Rate limited. Check Retry-After header for guidance.
- 500
Internal Server Error
Generic server failure. The server hit an unexpected condition.
- 501
Not Implemented
Server doesn't support the functionality required.
- 502
Bad Gateway
Server was acting as a gateway and got an invalid response from upstream.
- 503
Service Unavailable
Server is temporarily down (overloaded or under maintenance).
- 504
Gateway Timeout
Server was acting as a gateway and didn't get a timely response from upstream.
Files processed in your browser
Your files never leave your device. No upload, no servers.