Rate Limits

Rate Limits by Plan#

Plan	POST API (renders/min)	GET API (dynamic URLs/min)
Starter	30	15
Pro	120	60
Business	300	150
Enterprise	1,000	500

How Rate Limiting Works#

Rate limits use a sliding window measured per minute. When you exceed the limit, subsequent requests receive a 429 Too Many Requests response until the window resets.

The response includes headers to help you manage your request rate:

• X-RateLimit-Limit — Your plan rate limit
• X-RateLimit-Remaining — Requests remaining in the current window
• X-RateLimit-Reset — Timestamp when the window resets

Best Practices#

• Use batch rendering (Pro and higher) to process multiple images in a single request instead of making many individual calls
• Implement exponential backoff — When you receive a 429 response, wait before retrying, increasing the delay with each retry
• Cache results — Avoid re-rendering the same image by caching API responses on your end
• Use dynamic image URLs — For images embedded in web pages, GET-based rendering uses the built-in image cache to serve repeated requests efficiently

Need Higher Limits?#

If your use case requires higher rate limits than your current plan provides, consider upgrading to a higher plan or contact us to discuss Enterprise options.