Rate limits
Throttling headers and quota behavior
By YT2Text Team • Published February 1, 2025 • Updated February 23, 2026
Rate limits
All API requests are subject to rate limits based on the authenticated key and plan.
Response headers
Every throttled endpoint now includes:
- – request cap for the active window
X-RateLimit-Limit
- – requests already consumed in that window
X-RateLimit-Used
- – requests left before throttling
X-RateLimit-Remaining
- – Unix timestamp when the window resets
X-RateLimit-Reset
- – only returned on 429 responses
Retry-After
Exceeding limits
When over quota the API returns:
429 Too Many Requests
- updated limit headers
- indicating when to retry
Retry-After
Do not retry in a tight loop; use backoff with the returned headers.
Plan-aware limits
Current plans for the public API are:
- free
- starter
- pro
Video quotas (daily + monthly)
These quotas apply to video processing (both in the app and via the API):
| Plan | Daily videos | Monthly videos |
|---|---|---|
| free | 3 | 3 |
| starter | 10 | 50 |
| pro | 30 | 200 |
Security note
Rate limits are one layer only. Keep secrets server-side and never rely on throttling as your only abuse-prevention control.