How to use the exponential backoff calculator
Set the initial wait, number of retries, multiplier, and request time. The schedule lists each delay; the main result adds all retry waits and the duration of the initial request plus every retry.
What counts as a retry?
The first request is attempt 1. The retry count is the number of additional requests after that initial attempt. Six retries therefore means seven total requests and six waits.
Worked example: 1 second, 6 retries, multiplier 2
The waits are 1 + 2 + 4 + 8 + 16 + 32 = 63 seconds. If each request takes 0.5 seconds, seven requests add 3.5 seconds, for 66.5 seconds elapsed under this simple model.
Model limits
This calculator applies the multiplier exactly as entered. It does not cap the maximum delay, add random jitter, apply a server-provided Retry-After value, or decide which errors are safe to retry. Those details vary by service and retry policy. For example, Google Cloud Storage documents configurable maximum retry times and delay values for particular client libraries. Confirm the actual policy in the system you operate.
Sources & assumptions
Verified 2026-10-28. The calculator uses a plain geometric retry schedule without caps or jitter; it is not a substitute for your service's configured policy.
Official reference
- Google Cloud Storage retry strategy (client-specific settings and retry limits)

