Code tool

Debounce/Throttle Visualizer

Enter event timings and a window to compare two common timing policies.

In-browser processingNo account requiredPrivacy details ↗

A QUICK WALKTHROUGH

How to use this tool

  1. Enter sorted or unsorted event times in milliseconds.
  2. Set the timing window.
  3. Compare trailing debounce with leading-plus-trailing throttle.

Deterministic timing policy

Enter event timestamps in milliseconds. Debounce uses trailing behavior and fires once at the last event in each burst plus the window. Throttle uses leading plus trailing behavior at the stated fixed window.

Visualization only

This tool replays timing data; it does not attach listeners or run actual debounce/throttle code. Results depend on the stated policy and should be adapted to your implementation.

Local processing

Timing data is processed in your browser and is not uploaded.

GOOD TO KNOW

Common questions

What is debounce?

It waits for a quiet window and emits after the final event in a burst.

What is throttle?

It emits at most once per window; this visualizer uses leading plus trailing output.

Does it capture real events?

No. Enter deterministic timestamps manually.