← Back to status codes
HTTP Status Code
204 No Content
SuccessThe request was successful, but the server returned no response body.
HTTP status code reference, response example, common causes, fixes, and related status codes.
What does HTTP 204 No Content mean?
HTTP 204 No Content is a status code sent by a server to indicate the result of an HTTP request.
Status codes help browsers, APIs, apps, and backend systems understand whether a request succeeded, failed, was redirected, or needs additional action.
In practice, HTTP 204 No Content usually appears when a server responds under specific request, validation, permission, or infrastructure conditions.
Response example
HTTP/1.1 204 No Content
HTTP example
HTTP/1.1 204 No Content
Common causes
- Successful delete operation
- Successful update with no response payload
- Request completed without returning content
Common mistakes
- Assuming the status code alone explains the full backend issue
- Ignoring related response headers that add important context
- Treating temporary errors as permanent failures
- Retrying too aggressively without checking the cause
- Debugging the frontend only when the problem is server-side
How browsers and APIs use it
Browsers, APIs, and backend services use HTTP status codes to understand the outcome of a request. Depending on the status code, an application may render content, retry a request, redirect the user, show an error, or trigger a different flow in the client or server.
Developer note
Do not try to parse JSON from a 204 response. There is no response body to read.
Client-side example
const response = await fetch("/api/item/123", {
method: "DELETE",
});
if (response.status === 204) {
console.log("Item deleted");
}