Sign inStart free
Documentation

Cache

The first request fills the cache. Later requests are served from cache until a purge or eviction.

All documentation Open the Dashboard

Currently all the images will be cached and served from cache after first request, unless a "Purge cache" is triggered or cache space is full, thus it'll have the following features:

  • Works like "Always Online", as long as the image cached, it can be normally rendered even if your Origin is offline.
  • You can cache all your images by manually request them through proxy, this is so called "cache pre-heat"
Request pathWebP Cloud sits between the visitor and your origin.

A later request is served from cache. The origin is not contacted.

Visitor
https://xxx.webp.ee/path/to/image.jpgimage/webp · Render through cache
WebP Cloud
Origin

The first request, or a cache pre-heat, fetches the original and stores the result.

Visitor
https://xxx.webp.ee/path/to/image.jpgimage/webp · Optimized response
WebP Cloud
https://some.origin.tld/path/to/image.jpgimage/jpeg · Fetch from origin
Origin

Cache status

From each proxy's detailed page, you can see all the request logs, the Cache Status indicates whether an images is being rendered by WebP Cloud's cache.

  • Hit means rendered by WebP Cloud's cache.
Hit / DynamicSecond request to /path/to/image.jpg

The optimized image is already stored, so WebP Cloud answers without calling the origin.

Visitor
https://xxx.webp.ee/path/to/image.jpgimage/webp · Render through cache
WebP Cloud
Origin
  • Miss means you're using Rapid mode and it's not in WebP Cloud's cache, and WebP Cloud has to fetch that original image to render
Miss / DynamicFirst request to /path/to/image.jpg

Nothing is cached yet, so WebP Cloud requests the original, then returns the rendered image.

Visitor
https://xxx.webp.ee/path/to/image.jpgimage/webp · Rendered response
WebP Cloud
https://some.origin.tld/path/to/image.jpgimage/jpeg · Not in cache, requesting origin
Origin
  • Dynamic means the vistor's device doesn't support WebP/AVIF format so the original image format is being served, for example, the png format image.
    • Here "original image" might both mean cached png image by WebP Cloud (like Hit), or WebP Cloud has fetched image (like Miss)
    • Rendered image will still be EXIF removed to avoid unwanted privacy exposure.
Latest logs
Requested pathRefererCache statusCreated at
/pics/civic-fk7/fk7-g29.jpgDynamic2024-07-03 11:14:52
/pics/xishan-island/30.jpghttps://www.inoreader.com/Hit2024-07-03 09:09:55
/pics/lean-af/fk7.jpghttps://www.inoreader.com/feed/https://fwzyboy.im/feed.xmlHit2024-07-03 08:07:17
/pics/xishan-island/30.jpghttps://www.inoreader.com/feed/https://nova.moe/feedHit2024-07-03 08:07:13
  • Filling means you're using Consistency mode and cache Miss, and original image format is being rendered (while the image is being optimized by WebP Cloud).

You can find cache status in browser's request too, for example, you can take a look at https://1e674d5.webp.li/pics/xishan-island/73.jpg images's response header.

  • x-compression-rate: 0.59
  • X-Firefox-Spdy: h2
  • x-powered-by: WebP Cloud Services (HIO)
  • x-webpcloud-cache: Hit
  • x-webpcloud-cost: 0
  • x-webpcloud-fetch-cost: 0

Cache Limit

All Proxies for free user will have 200MiB of cache, if you go beyond that, we'll use "Least Recently Used" (LRU) algorithm for eviction, that's to say, the least-requested content will be evicted from cache.

For more plan specific information, please refer to Pricing.