# HTTP status code reference — no upload

> A searchable HTTP status code reference — 2xx, 3xx, 4xx, 5xx — with meanings and when to use each. Runs in your browser, nothing fetched.

Look up any HTTP status code — from 200 OK to 500 Internal Server Error — with its meaning and typical use. It's a built-in reference, so nothing is fetched.

Choosing the right status code makes an API predictable — clients and caches behave based on it. This reference clears up the common confusions (401 vs 403, 301 vs 302, 200 vs 204) so responses say what you mean.

For the headers that accompany those responses, see the HTTP header reference; to test real responses, use the HTTP client.

## How to

1. **Search a code.** Type a number like 404 or a keyword.
2. **Read the meaning.** See what the code signals and its category.
3. **Apply it.** Use the right code in your API responses.

## FAQ

### What's the difference between 401 and 403?

401 Unauthorized means you're not authenticated (log in); 403 Forbidden means you're authenticated but not allowed. The distinction matters for correct API behavior.

### When should I use 301 vs 302?

301 is a permanent redirect (search engines update their index); 302 is temporary. Use 301 for moved pages and 302 for short-lived redirects.

### Is anything fetched?

No. The reference is built in, so it works offline and contacts no server.


## Related tools

- [HTTP headers](https://www.safepaper.app/dev/http-headers)
- [HTTP client](https://www.safepaper.app/dev/http-client)
- [MIME types](https://www.safepaper.app/dev/mime-types)
- [Security headers](https://www.safepaper.app/dev/security-headers)

---

Canonical HTML: https://www.safepaper.app/dev/http-status-codes
Markdown: https://www.safepaper.app/dev/http-status-codes.md

There is no upload endpoint — your files are processed in this browser tab. Open your network tab and check.