Shotstack · Rate Limits

Shotstack Rate Limits

Shotstack constrains usage through API request rate limits and render concurrency rather than token quotas. Renders are queued asynchronously and processed against a per-account concurrency allowance that scales with plan tier (Subscription and High Volume plans offer thousands of concurrent renders). Individual renders are capped at a 3-hour maximum length. Credit balance (1 credit = 1 rendered minute or 10 images) acts as the primary usage ceiling. Specific per-endpoint RPS values are not reconciled in this artifact.

Shotstack Rate Limits is the machine-readable rate-limit profile for Shotstack on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, concurrent_renders, minutes, and credits.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Video, Video Editing, Media, Rendering, and Generative AI.

4 Limits Throttle: 429
VideoVideo EditingMediaRenderingGenerative AIRate LimitingQuotasThrottling

Limits

API Requests account
requests
see provider documentation
Per-account request rate across Edit, Ingest, Serve, and Create APIs.
Render Concurrency account
concurrent_renders
thousands of concurrent renders (tier-dependent)
Concurrent renders scale with the plan tier; queued renders process as capacity frees.
Maximum Render Length render
minutes
180
A single render is capped at 3 hours of output duration.
Credit Balance account
credits
plan-dependent
1 credit = 1 rendered minute or 10 images; depletion blocks new renders.

Policies

Tiered Limits
Concurrency, priority, and resolution caps raise from Sandbox to PAYG to Subscription to High Volume / Enterprise.
Asynchronous Queueing
Renders are queued and processed asynchronously; poll the render status endpoint or use a webhook callback rather than blocking.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor Retry-After.

Sources