Skip to main content
The Blueprint answers: how is this video built, visually? videngineer samples frames across the whole runtime and aggregates them into a production-style breakdown: shot types, camera angles, animation intensity, text overlays, color, and pacing. Open this layer when you want to know what the edit is doing, not what the script is saying.
Blueprint tiles showing scenes per minute, static frames, distinct scenes, text-overlay frequency, plus shot mix and angle mix

The Blueprint on a live teardown - Coinbase 'Break The Cycle' (80 scenes at 79.8/minute).

Live example: Coinbase - “Break The Cycle” teardown, Blueprint tab.

​
How it is sampled

Frame sampling adapts to the video’s length, so fast-cut teasers and long-form videos both get sensible coverage: When the system detects montage-grade cut density, it samples denser still, so a 20-second teaser cutting every half-second does not lose half its shots.

​
What each frame carries

​
The blueprint fields

​
What to do with it

  • Treat the shot mix as evidence. If the reference runs 60% tight talking-head and 30% product screen, write your scenes into those slots.
  • Read scenes_per_minute against your own edit. A 3x pacing gap often explains a retention gap better than the script does.
  • Use text_overlay_frequency to decide your caption strategy. At 30% or higher, text is structural, not decorative.
  • Hand color_mood_board to whoever grades or generates your visuals. It keeps your new work in a related visual family without borrowing the original footage.

The Cuts

The blueprint’s scenes as real, playable shots.

Script analysis

The narrative skeleton the visuals are carrying.

Scorecard

How well this build executes for its format.

Recipe & Cut Blueprint

Turn the blueprint into scene prompts and cut-level direction.