Turn a folder of screenshots into a narrated walkthrough in minutes.
Drop the captures in the order they happen. ngram orders the sequence, places callouts on the buttons you wanted to show, layers voiceover from a written script, and exports landscape, square, and vertical from one render.
Trusted by teams at
How it works
Four steps. A stack of screenshots becomes a walkthrough.
No timeline, no slide template, no separate voiceover session. Drop the sequence, accept the AI-built storyboard, ship the walkthrough.
Drop the screenshot set in
PNG, JPG, JPEG, WebP, or HEIC. A folder, a Drive link, or one image at a time. Filename order is the default sequence; drag to reorder.
ngram reads each capture
Every screenshot is classified — settings panel, dashboard, form, confirmation, code editor — and gets pacing picked to fit: longer holds on dense screens, faster cuts on simple confirmations.
Tune the storyboard
Reorder the captures, write voiceover per scene, drop callouts on the buttons you wanted to highlight, swap the transition. Brand Kit fonts, colors, and intro card apply on the fly.
Export every aspect ratio
One render produces 16:9 for the help center, 1:1 for LinkedIn, and 9:16 for Reels. Callouts and captions reflow per ratio. Download MP4, GIF, or WebM.
Output controls
Smart defaults for stitching a sequence. Real knobs underneath.
Smart zoom on the right UI region
ngram detects buttons, form fields, and headers in every screenshot, then pushes in on the one the step is about. The cursor lands where the script says it lands.
Callouts on the screenshot
Drop an arrow, a highlight box, or a numbered label on any screenshot. Animates in and out timed to the voiceover so it does not block the next step.
Photomotion between captures
Cinematic camera moves — slow push-in, parallax, hold-and-pan — applied per screenshot so the sequence reads as a walkthrough, not a slideshow.
Captions that dodge UI
Auto-captioned from voiceover or script. Caption position routes around detected UI regions so the button you wanted on screen never gets covered by subtitle text.
Voiceover from a written script
Type the narration per step; ngram generates AI voiceover (ElevenLabs or MiniMax) timed to the screenshot transitions. One voice picked once, reused across walkthroughs.
16:9, 1:1, 9:16 in one render
Same screenshot set, three ratios in a single export. Each ratio gets its own reframe and focal-point lock so the UI element each step highlights stays in frame.
Brand Kit applied automatically
Logo, colors, fonts, intro card, and outro card pulled from your Brand Kit. The settings walkthrough and the billing walkthrough look like the same product.
Screenshots gone in 24h
Uploaded captures and rendered walkthroughs auto-delete after 24 hours. Processed in-region, never used to train models. in-region processing.
The rest of ngram
Stitching the screenshots is one node. The product is the workflow around it.
Motion Graphics
Animated arrows, highlight boxes, and numbered labels sit on top of each screenshot, timed to the voiceover. The step's action point is where the eye lands, not where the cursor happens to be.
Learn moreAI Voiceover
Type the script step by step and AI voiceover narrates each screenshot in sync with the cuts. Pick the voice once and the next walkthrough sounds like the same product.
Learn moreCaptions
Burned-in captions for every screenshot. Position routes around detected UI so the 'Save' button never disappears behind a subtitle line on the step that says 'click save'.
Learn moreBrand Kit
Logo, palette, fonts, intro and outro cards applied to every screenshot walkthrough. Ten help-center walkthroughs shipped by ten people still look like the same product.
Learn moreMulti-format Export
Same screenshot project, three ratios out — 16:9 for the docs hero, 1:1 for the launch post, 9:16 for the mobile help center. UI focal points hold in every frame.
Learn moreTranslation
Voiceover, captions, and on-screen labels translated for every locale. The German walkthrough uses the same screenshots and the same callouts as the English one.
Learn moreUse cases
Where a screenshot walkthrough beats a help article.
Replace a 12-screenshot help article with a 60-second video
Support team already has the captures for 'How to enable '. Stitch them, add voiceover, drop callouts on the toggle. The article gets a video that closes tickets without the scroll.
See use caseOnboarding walkthroughs from in-app screenshots
The product team already captured every step of the 'first project' flow for the changelog. Convert that set into a 90-second onboarding video for the welcome email.
See use caseAnnounce a feature before the demo video is shot
PMM has the new-feature screenshots before there is a live recording. Stitch them with callouts on the new button and a voiceover script, and the launch clip ships on day one.
See use caseChangelog walkthroughs from release screenshots
Every release doc already has the screenshot row. Turn that row into a 30-second changelog video for the email send and the in-app banner.
See use caseIntegration walkthroughs from dashboard captures
Code screenshots and dashboard screenshots become a moving integration guide. The dev sees the curl, the response, and the next step in the order the docs already laid out.
See use caseRepro videos from the screenshot trail
QA already captured the steps to reproduce. Stitch the screenshots, drop voiceover explaining each click, and the bug ticket gets a short walkthrough instead of a paragraph.
See use caseSupport replies that show the click
Instead of pasting five screenshots into a ticket, send a 30-second walkthrough with arrows on the right buttons. Customer follows along once, ticket closes.
See use caseWalkthrough videos for cold outbound
Sales has 10 screenshots that show the persona's exact workflow. Convert them into a 45-second branded walkthrough and send it in line one of the prospect email.
See use caseOther converters
Coming from a different source? There's a converter for that.
Screenshots to video is one of 16+ ngram converters. Same engine, same Brand Kit, different input.
If your set is mostly product photos or hero illustrations rather than sequential UI captures, image to video tunes the motion to whole-frame stills instead of step-by-step screens.
Open converterAlready have a Loom or QuickTime capture of the same flow? Start there. Cursor smoothing, dead-air trim, and click emphasis instead of stitching individual screenshots.
Open converterIf the screenshots already live on slides — a kickoff deck or a release deck — start from the PPT. ngram extracts each slide as a scene and keeps the layout intact.
Open converterTools that pair with this converter
Refine the captures. Polish the walkthrough.
Editing further
After the walkthrough render lands
Video Editor
Open the rendered walkthrough on a timeline. Adjust per-screenshot duration, swap one capture for a fresher one, or extend the hold on the dense settings screen.
Open toolAdd Subtitles to Video
Burned-in or.srt subtitles for the walkthrough. Position them clear of the screenshot region each step is meant to highlight.
Open toolVideo Cutter
Trim the walkthrough into shorter cuts — a 15-second teaser for X, a 30-second cut for LinkedIn, a 60-second full walkthrough for the docs.
Open toolAdd Music to Video
Layer licensed background music under the voiceover. Auto-ducks during the narrated steps so the 'click here' instruction stays clear.
Open toolGenerating from scratch
When the screenshot set is missing a frame
AI Image Generator
Generate a missing frame in the same style as your existing screenshots — a hero card for the intro or a context illustration for an abstract step — then drop it into the sequence.
Open toolScreen Recorder
Capture a fresh screenshot or a short screen clip directly in-browser when the existing set is missing the step. Slots straight into the walkthrough.
Open toolAI Avatar Video Generator
Open the walkthrough with a talking head intro from a written script. Same Brand Kit, one render, screenshots roll right after.
Open toolText to Speech Video
Generate a narrated explainer for the parts of the workflow that aren't screenshot-shaped, then splice it before or after the screenshot stretch.
Open toolPolishing the source
Fix the captures before they hit the storyboard
Background Remover
Strip the OS chrome or browser tabs from a screenshot before it enters the walkthrough. The frame focuses on the product, not the user's desktop wallpaper.
Open toolSingle-image motion
Apply photomotion to one hero screenshot as a standalone 6-second clip. Useful for the cover frame of the walkthrough.
Open toolAdd Text to Video
Overlay step numbers, section headers, or instruction text on top of any screenshot. Lives on the rendered walkthrough, not in the source captures.
Open toolVideo Compressor
Compress the final walkthrough down for email embed or in-app help, without softening the small UI text in the screenshots.
Open toolBuilt for teams
Who reaches for screenshots-to-video in your company?
Support Teams
Tickets carry screenshots already. Stitch them into a 30-second walkthrough with arrows on the right buttons and one watch closes the loop.
See workflowsCustomer Success
Onboarding walkthroughs built from the screenshot set the team already captured. Welcome emails get a video instead of a screenshot dump.
See workflowsProduct Marketing
Ship the launch walkthrough from feature screenshots before there's a live demo. Three ratios, one Brand Kit, ready for the email and the in-app banner.
See workflowsProduct Managers
Changelog walkthroughs from the screenshots already attached to the release doc. No need to book recording time with marketing.
See workflowsDeveloper Relations
Integration guides built from dashboard and code screenshots. The dev sees the curl, the response, and the next click in the right order.
See workflowsSales Enablement
Reps need a walkthrough that fits a specific persona. Pick the screenshots the persona cares about, narrate them, and send before the next call.
See workflowsGrowth Marketing
Use-case landing pages get a 30-second screenshot walkthrough above the fold. Same captures repurposed for the LinkedIn and the Reels variant.
See workflowsFounders
Investor and prospect walkthroughs built from screenshots without booking a designer. Voice the script, hit render, send the link.
See workflowsIntegrations
Trigger screenshots-to-video from where the captures already live.
Each integration ships with a working recipe for the screenshot pipeline. Start from one, or wire your own with the REST API and webhooks.
whenA new folder of screenshots lands in Drive
thenRun screenshots-to-video with the team's Brand Kit and post the walkthrough to #help-center
whenAn agent calls the screenshots-to-video tool with a list of capture URLs and a script
thenReturn a rendered walkthrough MP4 and a hosted share link
whenYour S3 bucket gets a fresh screenshot batch from a QA run
thenStitch the captures into a walkthrough video; no asset leaves your VPC
whenA support ticket is tagged 'needs walkthrough' with screenshots attached
thenConvert the screenshots into a 30-second narrated reply and post it back on the ticket
whenYou select a row of screenshots in a Notion or Drive tab
thenSend the set straight to screenshots-to-video and get the walkthrough back in a new tab
whenA screenshots-to-video walkthrough finishes in 1:1
thenSchedule the launch post on the company page with the caption draft already attached
whenA screenshots-to-video walkthrough finishes in 16:9
thenUpload to the channel with title, description, and end card pre-filled from the script
whenA screenshots-to-video walkthrough finishes in 1:1 or 9:16
thenPost the short walkthrough to X with the launch copy attached
How it compares
If you've been using another tool to stitch screenshots.
Canva and Kapwing treat each screenshot as a slide on a timeline. Scribe and Guidde capture the flow but leave you in a doc, not a video. ngram keeps your real screenshots, adds motion and callouts around them, and ships a branded walkthrough.
| Feature | ngram | Canva | Kapwing | Scribe |
|---|---|---|---|---|
| Keeps the original screenshots intact | Yes — motion and callouts layered over the real captures | Yes — placed on slides | Yes — placed on timeline | Yes — in a step-by-step doc |
| Per-screenshot motion choice | AI picks smart zoom on the right UI region per frame | One template motion per slide | Manual keyframes per scene | No motion — static doc |
| Callouts on each capture | Arrow, highlight box, numbered label, timed to voiceover | Manual sticker placement | Manual shape placement | Numbered steps only |
| AI voiceover from a written script | ElevenLabs and MiniMax, multilingual | Limited TTS voices | Limited TTS voices | No voiceover |
| Captions that dodge UI elements | Caption position aware of detected UI regions | Manual placement | Manual placement | No video output |
| Brand Kit applied automatically | Logo, colors, fonts, intro and outro per render | Manual setup per project | Manual setup per project | Limited branding |
| Multi-format export from one project | 16:9, 1:1, 9:16 in one render | Duplicate and re-edit | Resize after | Doc export only |
| Batch a folder of screenshot sets | Parallel renders, one walkthrough per folder | One project at a time | Sequential queue | One capture session at a time |
| API and webhooks | REST, MCP, n8n, Zapier | Limited API | API on enterprise | Embed only |
FAQ
Common questions about screenshots to video
Still curious?
Screenshots → Video
Turn the screenshots you already have into a narrated walkthrough.
Drop the folder, write the script per step, drop callouts on the buttons that matter. ngram ships landscape, square, and vertical in one render.