-
Load your footage
Open local video…, paste a direct video URL, or click a clip in the playlist. Files are read in
place; nothing is uploaded. Remote links must point at the video file itself (an .mp4/.webm
URL), not a page that plays it.
-
Read the frame-rate badge
The badge comes from the file's own timing table: “30 fps · CFR”. Clips whose frame spacing varies
show a range instead, e.g. “23.98 fps · VFR 23.9–60.1”, and frame steps then follow the file's real
frames rather than a fixed 1/fps.
If the badge says fps unknown, the container could not be parsed (typical for cross-origin links).
Play for a second and the measured rate appears, or type the rate into fps fallback.
-
Move through the footage
Space plays at normal speed. ← / → jump 5 seconds back or forward, paused or
playing. The 1 s buttons either side of the frame buttons jump a single second, , /
. step exactly one frame, and the slider seeks anywhere. The clip's audio plays
too — M or the speaker button mutes it, and the slider beside it sets the volume.
-
Log your marks
Park on the first frame you want and press L (Log start). Step to later frames and press
A for each point. Every row carries the frame number, the exact frame time, and the distance from the
start. Loading another video asks before clearing the log.
-
Take the numbers
Copy TSV pastes straight into Excel, LibreOffice or Google Sheets; CSV downloads a
file. Δ time ÷ Δ frame time gives your droplet velocity — the tool deliberately does not do the physics.
Frame numbers are 0-based, so they line up with burned-in counters and ffmpeg. Logged times are the file's exact frame
timestamps when the file can be read; otherwise they are frame ÷ fps. On a variable-frame-rate clip the timestamps are
what make Δt trustworthy.
Remote videos must allow HTTP range requests, otherwise the browser cannot seek and frame stepping does nothing.
If that happens, download the file and open it locally.