Caching

Pass cache_ttl (seconds, up to 7 days) on any render. The result is stored keyed by a hash of the effective render parameters; any identical request inside the TTL returns the stored bytes immediately.

{ "url": "https://example.com", "full_page": true, "cache_ttl": 3600 }

The two things to know

• Cache hits are free. They don't count toward your monthly renders (you can see them as cached_hits in /v1/usage). The response header x-rasterkit-cache: HIT|MISS tells you what happened.
• The key is exact. Any parameter change (even quality: 81 vs 80) is a different cache entry. cache_ttl itself, async, and webhook_url are excluded from the key.

Patterns

HTTP caching is layered on top: cached-able responses carry Cache-Control: public, max-age=…, so browsers and CDNs can avoid hitting us at all.