Sample a local video at evenly spaced times and download a labeled PNG contact sheet with frame-time JSON.
Your input
Outputs are cleared when the input changes.
Result
Enter your data or use the example, then run the tool.
Worked example
The generated two-second test video sampled four times requests 0.25, 0.75, 1.25 and 1.75 seconds. The PNG labels and JSON use the same order.
Method
For zero-based frame i, request time (i + 0.5) × duration / N. Native browser seeking draws each decoded frame into a 320-pixel-wide thumbnail; the sheet contains the requested timestamp below each thumbnail.
JSON includes requested and player-reported times. These values do not prove frame-accurate codec timestamps. No scene detection or AI analysis is performed.
Limits
The file stays on this device. Supported containers and codecs vary by browser; a filename extension alone does not guarantee decoding.
Up to 24 thumbnails, two hours, 200 MiB, and 40 million pixels per source frame or finished sheet. Very tall thumbnails above 1280 pixels are rejected. This does not promise low memory use on every phone.
Cancel, reset or leaving the page aborts processing, releases the video source and discards unfinished output. Exported sheets contain visible video content and should be shared deliberately.
Your inputs stay on this device. Only optional, consented page visits are measured. Input values, files, filenames and processing logs are not sent to Analytics.
When switching languages, text, settings and selected files are temporarily kept on this device. Transfers are removed after restoring; interrupted transfers are cleaned up on a later visit. Inputs and files are never uploaded.