A shot list from any video.
Drop a clip; get a shot table with timecodes, durations, light, motion and palette — plus a storyboard and two reference frames per shot. Local, free, no account.
The whole job, in one tab.
Drop a clip. The workbench finds the cuts, pulls the frames, measures the light and motion, and writes the prompt sheet. No timeline to learn, no project file, no render queue. Nothing to install, nothing to upload.
Nothing is uploaded. Everything runs here.
The brief
Makes the prompts yoursThe workbench never invents a subject. Measured fields fill camera, light, palette and rhythm; you supply the idea. Changing the brief regenerates all three variants.
Analyze a clip to write the prompt sheet.
What you get
The shot list is not just a list of times. Each row carries the measurements that decide how a shot feels: luma key, contrast, color temperature, saturation, estimated motion and the five dominant colors. The ZIP also includes:
shots.csv— one row per shot, ready for a spreadsheet or a script.storyboard.jpg— every shot in order, with timecodes burned in.frames/shot-XX_first.jpgand_mid.jpg— two references per shot.prompts.md— three prompt variants per shot, built from the same measurements.report.html— a self-contained page you can send to a collaborator.
How cuts are found
The sampler seeks through the clip at 5 fps (3 fps above 60 seconds) and draws each frame to a 160×90 canvas. For every frame it computes an HSV histogram and a pixel difference against the previous sample. A cut is not just “a big difference”: the detector also checks that the three frames before the candidate are similar to each other, the three frames after are similar to each other, and the two groups are different. That persistence gate is what keeps fast motion from being reported as a cut.
If a clip has no cuts, the workbench returns one shot covering the whole duration. If it finds more than 120 shots, it stops and asks you to use the CLI; a long edit is not a browser job.
Accuracy and limits
The practical cut accuracy is about ±0.1 seconds; it is a reference, not a frame-exact conform. The browser limit is 3 minutes, 300 MB and 120 shots. MP4/H.264 and WebM are the safest formats; HEVC support depends on the browser.
Questions
Is the shot list frame-accurate?
It is accurate to about ±0.1 seconds on a typical short clip. The browser samples at 5 fps (3 fps for longer clips) and refines the cut boundary, but it is not a frame-exact conform tool. Use the source timecodes as a reference, not as an edit decision list for a broadcast master.
What is in the CSV?
One row per shot: shot number, in point, out point, duration, mean luma, luma key, contrast, color temperature, saturation, estimated motion, estimated pixels per second, cut confidence and the measured palette.
Can I detect cuts without uploading?
Yes. The video is read with the browser’s File API and a Blob URL. There is no upload endpoint. The only files that leave the tab are the ones you download.
Does it work for vertical or square video?
Yes. The shot list and measurements work for any aspect ratio. The viewer and filmstrip adapt; portrait frames are shown with their own aspect ratio.
What if the video has no cuts?
The workbench returns a single shot covering the whole clip and still extracts the frames, measurements and prompt sheet. A one-take clip is a valid result.
Turn the reference into a shot list.
Timecodes, frames, light and motion — the part a spreadsheet cannot see.