Rate Conversion
Throughput Converter
Convert request, event, job, and data throughput across time periods with explicit decimal and binary byte units.
NORMALIZED RATE
Item-rate results
Use the sample values or enter your own average rate.
Body estimates multiply average items per second by the selected average body size. They exclude response bodies, headers, framing, encryption, compression, and retries.
BYTES PER SECOND
Data-rate results
Use the sample value or enter your own data rate.
Long-period totals assume the entered average rate remains constant. They do not predict traffic peaks or provider billing.
READ THE UNITS
Convert the arithmetic without hiding the assumptions.
A converted average is mathematically equivalent to the input rate. It does not describe burstiness, concurrency, queue depth, payload variation, or an API provider's enforcement window.
- 1Normalize time first
Item rates are converted to a per-second value before the minute, hour, day, and 30-day results are calculated.
- 2Keep item meaning
Requests, events, and jobs use the same time arithmetic, but the labels remain distinct so the result keeps its context.
- 3Label decimal and binary units
kB and MB use powers of 1,000. KiB and MiB use powers of 1,024. The converter never labels one as the other.
- 4Separate average from peak
Capacity planning still needs peak rates, safety margin, burst rules, concurrency limits, retries, and representative payload sizes.
Planning estimate: Read How Much API Capacity Does Your Application Need? Use the Payload Size Analyzer to measure representative bodies, then evaluate request capacity with the Rate Limit Calculator. Confirm production throughput from measured traffic and provider documentation.