Constant frame rate
Usually produces predictable neighboring frames for a known time.
Paste one or several timecodes and capture the corresponding decoded frames. This workflow is designed for edit notes, bug reports, evidence, and repeatable review tasks.
A timestamp list makes a frame request reproducible. Teammates can keep the timecode with the exported filename and return to the same area of the video later.
Browser seeking is time based rather than frame-number based. The tool requests the specified time, then captures the frame that the browser decoder presents at that point.


Times can be separated by commas, spaces, semicolons, or new lines.
Confirm that the browser can decode and seek the local source.
Open the timestamp field instead of interval or count mode.
Use values such as 12.5, 00:12.500, or 01:03:12.250.
Export images whose filenames include their requested time.
Container indexes, keyframes, and variable frame rate can affect the exact decoded result.
Usually produces predictable neighboring frames for a known time.
A timeline time may not correspond to a simple fixed frame number.
The decoder may seek from a nearby keyframe before presenting the target area.
Professional editors may use source timecode metadata the browser does not expose.
Use decimal seconds when whole-second capture is too coarse.
For fast action, add times a few hundredths of a second apart.
Lossless output protects small text and fine edges.
Timestamp repeatability depends on using the same video file.
The web video API exposes playback time, so the tool cannot promise an editor-specific source frame number.
Use seconds, mm:ss, or hh:mm:ss.ms, including decimal fractions.
Yes. Separate them with commas, spaces, semicolons, or lines.
The requested time is precise, but the decoder returns the frame available at that point.
Yes. Use Capture current after scrubbing.
Yes. Each exported filename includes a safe timestamp.