Compute time intervals, frequencies, and execution counts.
Interval Calculator works entirely in the browser tab. Open it, use it, close it. Nothing about the session outlives the page.
The parsing, the maths and the formatting all happen in JavaScript on this page. No request carries your input anywhere, because there is no endpoint for one to reach.
You will find it under Schedules, alongside 7 other tools for the same sort of job.
Shows requests per second, per minute, per hour, and token bucket analysis.
intervalMs: 500 duration: 3600
=== Interval Calculator === Interval: 500ms Duration: 3600s Results: Executions: 7200 Frequency: 2.0000 Hz Conversions: Per second: 2.00 Per minute: 120.00 Per hour: 7200.00 Per day: 172800 Interval as: Milliseconds: 500 Seconds: 0.500 Minutes: 0.0083
Yes. It is JavaScript running in this tab, so once the page has loaded it needs nothing further from the network. Put the machine in flight mode and it carries on. Nothing you do here is sent anywhere, because there is nowhere for it to go.
No. Reload the page and it starts from nothing. There is no account, no saved state and no cookie holding your last session. That is a deliberate trade: it cannot lose your data because it never keeps any.
Timing comes from performance.now(), the high resolution clock the browser provides, rather than from setInterval, which drifts by a few milliseconds every tick and compounds over minutes. What can still shift things is the browser throttling a tab in the background, so leave it visible if the timing matters.
Where a sound makes sense, it is generated with the Web Audio API rather than loaded as a file, so there is nothing to download and nothing to block. Browsers refuse to start audio until you have interacted with the page, which is why the first press is what switches it on.
Yes. The controls are sized for touch and the layout collapses to one column on a narrow screen. Bear in mind that a phone locking its screen will suspend the page, and timing stops with it.