Short answer: Every Motion shot now starts from one sentence of intent: the single thing that shot has to say. Motioneed finds the part of your live page that says it, crops the screenshot to that region, frames it for the shot's aspect, and dims everything else. A whole-page screenshot is never a shot. If no region on your site supports the line, the line changes or the shot becomes a fitted type card. Images your site already curated, like a hero or a product photo, are shown as you published them.
Why whole-page screenshots made weak shots
The first version of a URL-to-video pipeline does the obvious thing: capture the page, drop the capture into a frame, add a caption. It looks fine in a thumbnail. In motion it falls apart.
A full landing page squeezed into a 16:9 or 9:16 frame turns every word into a few pixels. The eye has nowhere to land. The caption says "Instant APIs" while the picture shows a nav bar, a hero, a logo strip and a cookie banner all at once. Viewers can't connect the line to the proof, so the shot reads as filler.
Watching our own renders frame by frame, we kept seeing the same failures:
- A full page standing in for a feature.
- A zoomed fragment so tight that the headline was cut at both edges.
- The wrong part of the site: a newsletter form, a sign-in screen, or another company's product embedded in a customer story.
- The same crop used three or four times in one film.
None of those is a taste problem you can fix with a nicer transition. The shot was not deciding what it was for.
One shot, one intent
The storyboard now records one intent per shot: a short line such as "Row Level Security protects every table" or "Deploy previews for every push". That line is the contract for the shot. Everything else, from the picture to the type and the crop, has to support it.
Assets come in two classes, applied on every film rather than patched per site:
| Class | What it is | How Motioneed uses it |
|---|---|---|
| Curated | A hero image, product photo or illustration your site chose to show | Held as-is. No re-cropping into something you didn't publish |
| Screenshot | A capture of your live page | Never the whole page. Matched to the intent, cropped to a focal region, reframed to the shot aspect |
How a screenshot becomes a focal crop
When a shot is a screenshot, the pipeline:
- Matches the intent to a DOM region. The captured page is still structured content, not just pixels, so the line can be matched to a section that actually shares its words.
- Checks that the region can carry a shot. The region has to fill at least 0.42 of the frame once it is reframed, and it has to share words with the intent. A tiny badge stretched to full frame doesn't pass.
- Crops and reframes it to the shot's aspect (16:9 or 9:16).
- Dims the rest so the focal region is what you look at.
If nothing on the page supports the intent, Motioneed doesn't fake it. The intent is changed to match a real region, or the shot takes another asset. If that still fails, the shot is grounded again or swapped for a type card. The rest of the cut stays as it was.
Ranking regions: product first
Not every region that matches a word is a good picture. Since the region ranker shipped, Motioneed prefers a product surface: a dashboard, an editor, a table, a code sample, a pricing grid. It drops:
- forms and newsletter sign-ups
- auth and consent screens, including a feature-labeled crop that contains "Create your account"
- cookie banners
- third-party products that appear inside your page
A precropped region sits in a card the size of its bitmap, so it isn't stretched. Camera scale on a picture stays at or below 1, so a push-in never magnifies a screenshot past its real pixels.
When there's no picture: type that fits
Some lines don't have a picture behind them, and a blurry stretched screenshot is worse than none. Those shots become layout cards, drawn by a layout engine that measures text in the same font the browser will render:
- Lines wrap or shrink inside the safe area instead of running off the edge.
- Wordmarks stay at least 120px.
- Labels in one shot share the size of the longest label and stack in one column.
- Giant type and zoom moves are used only when the whole line measurably fits at the type floor.
- A heading that was split on the source page is joined back into one heading before it is typed.
We also removed the model-painted plates: checkerboards, wedges, tile wipes and stripe covers. A shot shows a validated region, a curated still or a fitted type card, and nothing else.
Templates without repetition
The shot grammar gives the writer a small set of designed shot types and fills each one from validated assets:
- a product push-in on one region
- a split: that region plus a headline
- a feature grid
- kinetic type
- a logo lockup
Two rules keep films from feeling like a slideshow. Kinetic type is used for at most two shots. When enough grounded regions or stills exist, at least 60% of shots show one. Lines and regions are deduplicated, so a film doesn't reuse a crop or repeat a sentence.
What this means for your film
- The pictures are your product, not a stock dashboard and not someone else's app shown on your page.
- Every shot has a reason to be on screen, and you can read it.
- When your site has little to show, Motioneed uses fewer, cleaner type cards instead of padding the cut with whole-page screenshots.
It also means some pages are harder than others. A page that is mostly forms or one long hero image gives the ranker little to work with. That's a real limit, and we'd rather show fewer honest shots than invent proof.
FAQ
Does Motioneed ever show my whole page as a shot?
No. A screenshot shot is always a focal region matched to that shot's intent. A region that is still effectively the whole page doesn't count as a focal crop.
Will it crop my hero image or product photos?
No. Images your site curated are held as you published them. Only page screenshots are cropped and reframed.
What if my homepage embeds another company's product?
Third-party products and nested customer captures are ranked out. Motioneed won't present someone else's UI as yours.
Why did a shot become plain type instead of a screenshot?
No region on the page supported that line well enough, or the line didn't fit as a picture at a readable size. A fitted type card is the honest fallback.
Can I steer which part of my site is shown?
On a paid plan you can revise the film and name the feature you want shown. The new storyboard writes that line as an intent, and the same grounding rules decide whether a real region on your page can carry it.
