# How render credits and usage work

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

- **URL**: https://orshot.com/help/render-usage-and-credits

---

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

![The billing overview with credits, seats and limits](https://orshot.com/help/account-billing/credits-1-overview.webp)

## 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)

## 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

## At the limit

Configure **Overage Settings** on the billing page to decide what happens past your plan's credits — see [overage renders](https://orshot.com/docs/misc/overage-renders).

## Related