http.cat No paid content found

What is HTTP Cats?

HTTP Cats is a simple image service that maps HTTP status codes to cat photos. Instead of a plain "404 Not Found" page, you can show a cat picture that corresponds to that exact error code.

How it works

The usage pattern from the site is a URL with the status code appended:

https://http.cat/[status_code]

So a 404 page would use https://http.cat/404. Adding .jpg at the end returns the image file directly, which is convenient when you want to embed it in an <img> tag or set it as a background image.

What it covers

The service supports a wide range of codes, not just the common ones:

• Success and informational: 100, 101, 200, 201, 204, 206, and others
• Redirects: 301, 302, 304, 307, 308
• Client errors: 400, 401, 403, 404, 418, 429, and many more
• Server errors: 500, 502, 503, 504, plus variants like 521, 522, and 599
• Non-standard codes: 419, 420, 444, 495–499, 530

Who it is for

• Developers building custom error pages who want something friendlier than default server output
• Teams running demos, internal tools, or side projects where a light tone fits
• Anyone teaching HTTP status codes who wants a visual mnemonic

Trade-offs to consider

A cat image is memorable and disarming, but it may not suit every context. On a banking, healthcare, or enterprise login page, a joke image can undermine trust or look unprofessional. It also adds an external dependency: if the service is unavailable, your error page loses its image. For production use, download the image you need and serve it yourself rather than hotlinking.

Next step

Pick the status codes your application actually returns, fetch those images once, and store them locally. Then wire them into your error templates so the page still works if the external service goes down.

How do I use HTTP Cats to display cat images for HTTP status codes?

Point an <img> tag at https://http.cat/[status_code], replacing [status_code] with the numeric code you want — for example, https://http.cat/404 returns the cat image for "Not Found." Add .jpg if you need a file extension. That single URL pattern is the whole API; there are no keys, headers or query parameters to configure.

Common uses

• Error pages: Show /404 on a not-found page, /500 on a server error, or /403 when access is denied, so a dead end still feels human.
• Status dashboards: Map a monitored service's response code to the matching cat, giving an at-a-glance visual for non-engineers.
• Testing and demos: Use a specific code to verify your error-handling path renders an image correctly.
• Slack or chat bots: Post the relevant cat when a deploy or health check fails.

Picking the right code

The site covers the standard ranges plus many unofficial ones. Match the code your server or upstream actually returns rather than the closest-sounding one:

Practical notes

• Hotlinking: You are loading images from someone else's server, so availability and speed depend on them. For anything customer-facing or high-traffic, download the images you need and serve them yourself.
• Accessibility: Always set a meaningful alt attribute (e.g. alt="404 Not Found"). A decorative cat with no text leaves screen-reader users without the status information.
• Fallbacks: Add a local fallback image or a plain text message in case the remote image fails to load.
• Caching: Since the images rarely change, set long cache lifetimes on your own copies to avoid repeat requests.

A simple example for a 404 page:

<img src="https://http.cat/404" alt="404 Not Found">

Next step: decide whether you are prototyping or shipping. For a quick demo, hotlink directly. For production, download the handful of codes your app actually returns, host them locally, and wire them into your error templates.

Can I get a JPG version of an HTTP Cat image by adding an extension?

Yes. Append .jpg to the status-code URL and you get a JPG version of that cat image.

The base pattern is https://http.cat/[status_code], and adding .jpg gives the extension variant. So a 404 cat becomes https://http.cat/404.jpg, and a 500 cat becomes https://http.cat/500.jpg.

Why the extension matters

• Some tools, CMS fields, and social preview systems expect a file extension to recognise an image.
• If you are embedding the image in HTML, the extensionless URL usually works fine in an <img> tag.
• If you are downloading the file to a local folder or passing it to software that guesses type from the filename, the .jpg form avoids ambiguity.

Quick decision guide

A practical example: for a custom 404 page, point an image tag at https://http.cat/404.jpg. For a 503 maintenance page, use https://http.cat/503.jpg. The status codes listed on the site range from informational responses like 100 through client and server errors up to 599, so you can match the cat to the actual response your server returns.

Next step: pick the exact status code your page or API emits, then test both the bare URL and the .jpg version in your target tool before shipping. If you want a broader set of status-code illustrations to compare, HTTP Cats is the source here; other well-known alternatives exist, but verify their official domains before using them.

Which HTTP status codes are supported by HTTP Cats?

HTTP Cats supports a broad set of standard, extended, and vendor-specific status codes. The core pattern is https://http.cat/[status_code], and you can append .jpg to get an image file directly.

H3. Standard codes (most commonly used)

• 1xx: 100, 101, 102, 103
• 2xx: 200, 201, 202, 203, 204, 205, 206, 207, 208, 214, 226
• 3xx: 300, 301, 302, 303, 304, 305, 307, 308
• 4xx: 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 418, 419, 420, 421, 422, 423, 424, 425, 426, 428, 429, 431, 444, 450, 451
• 5xx: 500, 501, 502, 503, 504, 506, 507, 508, 509, 510, 511

H3. Non-standard and server-specific codes

• 495 SSL Certificate Error
• 496 SSL Certificate Required
• 497 HTTP Request Sent to HTTPS Port
• 498 Token expired/invalid
• 499 Client Closed Request
• 521 Web Server Is Down
• 522 Connection Timed Out
• 523 Origin Is Unreachable
• 525 SSL Handshake Failed
• 530 Site Frozen
• 599 Network Connect Timeout Error

H3. Practical notes

The list includes playful or unofficial codes such as 418 "I'm a teapot" and 420 "Enhance Your Calm," which are useful for humor or Easter eggs. Codes like 444, 495–499, 521–525, and 599 are typically tied to specific servers or proxies rather than the HTTP standard, so they may not be meaningful in every stack.

A useful next step is to test the exact code you plan to use, since not every listed code necessarily maps to an image. You can also compare coverage with HTTP Statuses or MDN Web Docs if you need authoritative definitions alongside the cat images.

Is HTTP Cats free to use, or do I need to upgrade?

HTTP Cats is free to use. The site presents itself as an API you can call directly from your own website to display cat images for HTTP status codes, and the published usage pattern is simply a URL with the status code appended, with an optional .jpg extension. There is no stated requirement to create an account, pay, or upgrade in order to use it.

The only pricing-adjacent signal on the page is the word "upgrade," but it appears as part of the standard HTTP status code 426 Upgrade Required in the status list, not as a paid plan or checkout option. In other words, it describes an HTTP response, not a product tier. No pricing links or payment platforms are listed either.

How to use it in practice

• Direct image embedding: Point an <img> tag at the status-code URL for the error you want to illustrate, for example a 404 page or a 500 page.
• Fallback handling: Because the image is fetched over the network, decide what your page should show if the request fails or is slow. A local placeholder or a plain text message is a sensible backup.
• Status coverage: The page lists a wide range of codes, from informational ones like 100 and 103 through client errors like 400, 401, 403, 404, 418 and 429, to server errors like 500, 502, 503 and 504, plus some non-standard or vendor-specific ones such as 419, 420, 444, 450 and 521–530. That makes it easy to match most error pages.
• Audience fit: It suits developer tools, internal dashboards, hobby projects and documentation where a lighthearted error state is appropriate. For customer-facing banking, healthcare or enterprise applications, a funny cat image may undercut the seriousness of a failed payment or outage, so consider whether the tone matches your brand.

What to check before relying on it

The page does not state uptime guarantees, rate limits, caching headers, licensing terms for the images, or whether hotlinking is officially permitted. Those are the practical trade-offs of depending on a third-party image host: you get zero setup and instant variety, but you inherit whatever availability and terms the operator applies. If your error pages are business-critical, download or self-host the images you need, or keep a text-only fallback.

A useful next step: open the URL for the specific code you care about, confirm the image loads and looks right at the size you need, then wire it into your error template with a fallback in place.

How do I integrate HTTP Cats into my website for error pages?

Point an <img> tag at https://http.cat/[status_code], swapping [status_code] for the numeric code you want to illustrate — for example, https://http.cat/404 for a not-found page. HTTP Cats is a straightforward image endpoint rather than a JavaScript library, so integration is mostly about choosing where the image appears and how it degrades.

Common integration patterns

The dynamic approach is usually worth it: instead of maintaining one template per code, keep a single error view that builds the URL from the status code it receives. That way a 429 rate-limit page and a 503 maintenance page both get an appropriate image without extra work.

Practical details to handle

• File extension: the base URL works as-is; append .jpg if a tool or platform needs an explicit extension.
• Alt text: write something meaningful like "404 Not Found" rather than leaving alt empty — screen readers and search engines both benefit.
• Sizing: constrain the image with CSS (max-width: 100%) so it doesn't dominate the page or cause layout shift.
• Caching and availability: the image is served from a third party. If it fails to load, your page should still communicate the error in text. Consider self-hosting a copy of the images you actually use if uptime matters.
• Tone: a cat picture suits consumer-facing, informal products. For banking, healthcare or enterprise admin tools, a playful image on a 500 page can read as flippant — keep a plain-text fallback or reserve the cats for low-stakes codes like 404.

A concrete next step

Decide which status codes your site can actually return, then build one error template that accepts a code and renders both a short human explanation and the corresponding image. Test it by deliberately triggering a 404 and, if you can, a 500. If you want a different visual style for the same idea, HTTP Status Dogs follows an equivalent pattern with dogs.