How render credits and usage work

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

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.

What doesn't#

• 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

Voice usage#

AI voiceovers use a separate voice-minute allowance instead of render credits. The allowance is shared across all workspaces on the account and resets with the billing period.

Generating new spoken narration uses voice time. Rendering a template with narration that has already been generated does not use it again. Dynamic narration uses voice time when new spoken copy needs to be generated.

Your plan controls the included minutes, available voice models, and maximum script length. Open Voiceover in Studio to see current usage, or compare plans on the pricing page.

At the limit#

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

Related#