How render credits and usage work

What counts as a credit, where to track your balance, and what happens at the limit

Published Jun 7, 2026

Open Billing & Usage from your workspace sidebar to see where you stand:

The billing overview with credits, seats and limits

What uses credits#

Image and PDF renders — every render request (API, Playground, or integrations), including repeat requests served from cache
Video renders — these scale with length (roughly 1 credit per second of video), so a 10-second MP4 costs more than an image
MP4 downloads from Orshot Studio (same per-second rule)
Smart Resize sizes — each size in a render counts on its own: response.size is one render at the new size, and every entry in response.extraSizes adds another. Saving sizes in Studio is free — you're only charged when you render them.

Editing and saving templates in Orshot Studio
Image downloads of the current canvas (PNG, PDF, etc.)
Serving an existing render URL — once rendered, the output URL is a hosted file; embedding or sharing it costs nothing

For high-traffic visuals like OG images, render once and reuse the output URL — serving the file again never triggers a new render.

Configure Overage Settings on the billing page to decide what happens past your plan's credits — see overage renders.

The precise accounting rules

Manage your plan anytime