Tutorials
How to animate a product screenshot for a landing page hero
Turn a product screenshot into an animated landing-page hero with Animate Image: Story motion roles, entrances, hero timing, export and reduced motion.
Most landing pages open with a product screenshot. It is the most honest picture of what you sell, and also the most static. A hero that builds itself up piece by piece, the window first, then the main panel, then the small details, tells visitors where to look and gives the page a little life without a video.
This tutorial uses Animate Image to turn one product screenshot into that kind of hero. It focuses on the choices that matter for a hero: roles, entrances and timing. For the basics of the editor, see how to animate a static image.
Prepare the screenshot
A little preparation makes the split cleaner and the result calmer.
- Crop to what matters. Browser chrome and empty margins become parts that animate for no reason.
- Use clean data. Realistic but tidy numbers and names. The animation draws attention to every detail.
- Keep clear separation between panels, cards and the background. Distinct shapes are easier to cut out as distinct parts.
- Export as PNG, JPG or WebP. Those are the formats Animate Image accepts.
Load it into Animate Image
- Open Animate Image and drop the screenshot, or click Choose an image.
- Sign in if asked. Reading the text and cutting out figures runs on the Capture Motion backend, so the editor asks you to sign in, then carries on with the same image. Free accounts get a few free images; plans add credits. See pricing.
- Choose how to split it. Shapes or Sharp cut-outs. For a UI screenshot, try both and keep the one whose parts line up with real panels and cards. If a split gives you odd fragments, switch to the other one and Rebuild.
Story motion: give each part a role
Story motion gives each part a role so the image plays like a short story: the background first, the hero next, details after, then the closing. For a product screenshot, the roles map neatly onto a typical interface.
| Role | In a product screenshot | Why it plays here |
|---|---|---|
| Stage | The app window, background, sidebar frame | Sets the scene so nothing appears floating in space |
| Hero | The main chart, editor or panel you are selling | The thing visitors should look at first |
| Support | Secondary cards, lists, table rows | Fills in context once the hero is in place |
| Accent | Badges, avatars, a cursor, a notification dot | Small touches that make the screen feel alive |
| Closing | A success toast, a button, a final number | Ends the story on the outcome |
Check the roles in the Layers panel. Filter by a role to see which parts it holds, or by Any part to see everything. If the sidebar landed in Hero, it will compete with the real hero. Try the other split and Rebuild, or filter to it and use Skip shown so it stays still.
Entrance choices per role
The entrance is set per part, so it is easiest to think about it role by role. Auto picks a move per part, which is a good first pass. For a hero, a few deliberate choices usually look better.
| Role | Good entrances | Avoid |
|---|---|---|
| Stage | Fade (fades in, no movement) | Pop or slides. A bouncing window looks unstable. |
| Hero | Fade up (rises a little as it fades in), Scale in (grows slightly into place) | Anything slower or bigger than the rest. It should be clear, not loud. |
| Support | Fade up, Slide from left or Slide from right, matching their side of the layout | Mixing directions on the same side. |
| Accent | Pop (lands with a small bounce), Scale in | Pop on large parts. Keep the bounce for small things. |
| Closing | Pop or Fade up | Rise (moves up, no fade) on text, which can look abrupt. |
One rule covers most of it: the larger the part, the quieter the entrance.
Timing for heroes
Animate Image has two timing controls: Duration (default 400ms) and Gap between parts (default 80ms). The defaults are a sensible start for a hero.
- Count your parts. Twelve parts means eleven gaps. A gap that feels tiny on its own adds up quickly, and a hero that takes too long to settle makes visitors wait to read your headline.
- Cut parts before you cut time. In the Layers panel, filter to a role and use Skip shown to leave those parts still. Fewer moving parts reads as more confident than the same parts moving faster.
- Use Animate shown to test one role. Filter to Accent, animate only those, and check the small touches work on their own.
- Watch it with Replay, then Loop. The time readout shows how long the whole sequence runs. Loop it a few times; if it starts to annoy you, shorten the gap.
When you are happy, click Save to keep it in My Gallery. A second save updates the same copy, so you can keep tuning without creating duplicates.
Export to your stack
Click Export. Each format has a Copy button.
| Your site | Export |
|---|---|
| Static HTML, a site builder that takes custom code | HTML, or CSS for your own markup |
| Plain JavaScript | Web Animations |
| Already uses GSAP | GSAP |
| React or Next.js | Motion (React) |
| Your own tooling | JSON |
Animate Image export code goes through what each format contains. If you are new to the browser's built-in API, the Web Animations API guide is a good primer.
Respect reduced motion
A hero plays to every visitor, including people who have asked their system for less motion. Do not delete the animation for them; reduce it. Keep the fades and drop the movement, or show the finished screenshot straight away.
A minimal CSS pattern, for illustration, that shows the final state when reduced motion is on:
@media (prefers-reduced-motion: reduce) {
.hero-shot * {
animation: none !important;
transition: none !important;
opacity: 1 !important;
transform: none !important;
}
}
Adapt the selector to your export's markup. If your export uses JavaScript (Web Animations, GSAP or Motion), check the setting in code instead. The prefers-reduced-motion guide has patterns for each.
Beyond the hero: social posts and slides
The same screenshot works in other places with small changes.
- Social posts. An animated post needs to make its point quickly, so lean on Hero and Closing and skip most Support parts. Animate Image exports code, not video files, so use it where HTML or JavaScript can run, or record it yourself for platforms that only accept video.
- Slides. If your slides are built on the web, drop in the HTML export. One build per slide is plenty; use Change to load the next screenshot rather than packing several features into one image.
- Onboarding. An onboarding illustration can run slower than a hero, because the user has chosen to be there. Try a longer duration with the same gap.
Start with one screenshot and the defaults, play it a few times, then change one thing at a time.
Questions
What image formats can I use?
PNG, JPG or WebP. Drop the image on the Animate Image page or click Choose an image.
Do I need an account?
Yes. Reading the text and cutting out the parts runs on the Capture Motion backend, so the editor asks you to sign in when you drop an image, then carries on with that same image. Free accounts get a few free images, and plans add credits.
What are the Story motion roles?
Stage, Hero, Support, Accent and Closing. Each part of the image gets one, so it plays like a short story: the background first, the hero next, the details after, then the closing.
Which export should I use for a landing page?
Match your stack. HTML and CSS for a static site, Web Animations for plain JavaScript, GSAP if the site already uses it, Motion (React) for a React app, and JSON if you want the raw data.
