Bytescale · Rate Limits

Bytescale Rate Limits

Bytescale governs usage primarily through monthly plan quotas - storage, download bandwidth, upload requests, and processing (CPU hours) - rather than fixed per-second request rates. There are no daily limits; restrictions are monthly quotas only. Exceeding a quota results in overage billing (on pay-as-you-go) or throttling/blocking depending on account configuration. Per-second request throttles and max upload sizes apply per plan. Specific per-endpoint request-rate values are not reconciled in this artifact.

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

It captures 5 rate-limit definitions, measuring gigabytes, requests, cpu_hours, and bytes.

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

Tagged areas include File Upload, Storage, Image Processing, CDN, and Media.

5 Limits Throttle: 429
File UploadStorageImage ProcessingCDNMediaRate LimitingQuotasThrottling

Limits

Storage Quota account
gigabytes
per plan (Basic 10 GB / Plus 50 GB / Advanced 300 GB)
Total storage used at any point in time; overage billed per GB.
Download Bandwidth Quota account
gigabytes
per plan (Basic 10 GB / Plus 50 GB / Advanced 300 GB)
Monthly egress data transfer; overage billed per GB.
Upload Requests Quota account
requests
per plan (Basic 20,000 / Plus 100,000 / Advanced 500,000)
Monthly count of files created or overwritten; overage billed per upload.
Processing Quota (CPU Hours) account
cpu_hours
per plan (Basic 1x / Plus 5x / Advanced 30x)
Monthly transformation processing time; overage billed per CPU hour.
Max Upload Size request
bytes
per plan (Basic 500 MB / Plus 5 GB / Advanced 100 GB)
Maximum size of a single uploaded file.

Policies

Monthly Quotas Only
No daily limits apply; all restrictions are enforced as monthly quotas.
Overage Billing
On pay-as-you-go, usage beyond bundled quotas is billed per GB / per CPU hour / per upload rather than hard-blocked.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources