Arrange real screenshots around the workflow the audience needs to understand. Add movement, callouts, and narration, then keep the project ready to update when the interface changes.
Video generation uses credits. Review your estimate in ngram. MP4 downloads require Basic or higher.
How credits workTrusted by teams at
How it works
No timeline, no slide template, no separate voiceover session. Drop the sequence, accept the AI-built storyboard, ship the walkthrough.
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.
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.
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.
Review the screenshots video for its intended channel, including the crop and caption placement, then export one MP4 from Studio. Prepare and review another aspect ratio as a separate edit. If another file type is required, run that MP4 through a separate one-file, one-output Video Converter job for MOV, WebM, or MKV, or use Video to GIF for a GIF.
Output controls
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.
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.
Cinematic camera moves (slow push-in, parallax, hold-and-pan) applied per screenshot so the sequence reads as a walkthrough, not a slideshow.
Turn on captions generated from voiceover or script and select your saved Brand Kit for styling. Review caption position against each screenshot before export.
Type the narration per step; ngram generates AI voiceover (ElevenLabs or MiniMax) timed to the screenshot transitions. One voice picked once, reused across walkthroughs.
Set the intended channel and aspect ratio for the screenshots video, then review the crop, caption placement, and CTA before exporting one MP4. Prepare another channel version as a separate edit.
Logo, colors and fonts pulled from your Brand Kit. Choose saved intro or outro slides for each video that needs them. The settings walkthrough and the billing walkthrough look like the same product.
Need details on data handling, access controls, or retention for your team? Talk to sales and we will walk you through how ngram handles your captures and renders.
The rest of ngram
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 moreType 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 moreBurned-in captions for every screenshot. Set and review their position so controls such as the Save button remain visible.
Learn moreLogo, palette and fonts applied to every screenshot walkthrough. Ten help-center walkthroughs shipped by ten people still look like the same product.
Learn moreThe screenshot walkthrough leaves Studio as a single MP4. Use Video Converter afterward to make one MOV, WebM, or MKV file; it is a separate one-file, one-output step.
Learn moreVoiceover, 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
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 caseThe 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 casePMM 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 caseEvery 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 caseCode 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 caseQA 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 caseInstead 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 caseSales 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
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 converterUse the kickoff or release deck as source material when your screenshots already live on slides. Review how ngram proposes to use them in the video plan.
Open converterTools that pair with this converter
Editing further
After the walkthrough render lands
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 toolBurned-in or.srt subtitles for the walkthrough. Position them clear of the screenshot region each step is meant to highlight.
Open toolTrim 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 toolLayer licensed background music under the voiceover so the 'click here' instruction stays clear during the narrated steps.
Open toolGenerating from scratch
When the screenshot set is missing a frame
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 toolCapture 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 toolOpen the walkthrough with a talking head intro from a written script. Same Brand Kit, one render, screenshots roll right after.
Open toolGenerate 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
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 toolApply photomotion to one hero screenshot as a standalone 6-second clip. Useful for the cover frame of the walkthrough.
Open toolOverlay step numbers, section headers, or instruction text on top of any screenshot. Lives on the rendered walkthrough, not in the source captures.
Open toolCompress the final walkthrough down for email embed or in-app help, without softening the small UI text in the screenshots.
Open toolBuilt for 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 workflowsOnboarding walkthroughs built from the screenshot set the team already captured. Welcome emails get a video instead of a screenshot dump.
See workflowsShip the launch walkthrough from feature screenshots before there's a live demo. Prepare and review each channel edit separately before exporting one MP4.
See workflowsChangelog walkthroughs from the screenshots already attached to the release doc. No need to book recording time with marketing.
See workflowsIntegration guides built from dashboard and code screenshots. The dev sees the curl, the response, and the next click in the right order.
See workflowsReps need a walkthrough that fits a specific persona. Pick the screenshots the persona cares about, narrate them, and send before the next call.
See workflowsUse-case landing pages get a 30-second screenshot walkthrough above the fold. Same captures repurposed for the LinkedIn and the Reels variant.
See workflowsInvestor and prospect walkthroughs built from screenshots without booking a designer. Voice the script, hit render, send the link.
See workflowsIntegrations
Each integration ships with a working recipe for the screenshot pipeline. Start from one, or wire your own with the REST API and self-managed webhook subscriptions for video.completed or video.failed.
whenAn approved screenshot set is ready for a Studio upload
thenUpload the file in Studio; use Zapier's documented Create Video or Get Status action for this Screenshots to Video job, then pass the result to the next step.
whenAn agent calls the screenshots-to-video tool with a list of capture URLs and a script
thenUse MCP's documented create and status tools for this Screenshots to Video job with its supported input, then return the status or result to the agent.
whenYour workflow has an approved screenshots ready for Studio
thenUpload the file in Studio; use n8n's documented Create From Text, Create From URL, or Get Status node for this Screenshots to Video job, then pass the result onward.
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
whenThe video from your screenshots is ready for LinkedIn Social Publishing Beta
thenCompose the LinkedIn post for the approved screenshots video, then publish it now.
whenThe video from your screenshots is ready for YouTube Social Publishing Beta
thenVerify the YouTube destination for the approved screenshots video, then publish it now.
whenThe video from your screenshots is ready for X Social Publishing Beta
thenCompose the X post for the approved screenshots video, then publish it now.
How it compares
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 |
| Branded burned-in captions | Auto-generated, styled, and editable before export | Manual placement | Manual placement | No video output |
| Select your Brand Kit | Logo, colors and fonts per render. Choose a compatible intro or outro separately. | Manual setup per project | Manual setup per project | Limited branding |
| Channel-specific editing workflow | One reviewed MP4 per channel-specific edit | Duplicate and re-edit | Resize after | Doc export only |
| Repeat a screenshot-set workflow | One walkthrough per request | One project at a time | Sequential queue | One capture session at a time |
| API and webhooks | REST API with self-service API keys; webhook subscriptions for video.completed or video.failed; MCP, Zapier, and n8n for documented workflows | Limited API | API on enterprise | Embed only |
Screenshots → Video
Drop the folder, write the script per step, drop callouts on the buttons that matter. Prepare and review each channel edit separately before exporting one MP4.
Follow a workflow from source material to a video you can review, share and make again.
Each onboarding path or product change
Give Claude your setup guide and current product screens. Review ngram’s plan, then create a walkthrough that helps a new customer finish one useful task.
A verified setup guide and real product screensA first-workflow video with clear next steps
Ways to run: Claude
Each buyer role, product workflow or interface update
Give Claude the buyer’s task, current interface screenshots and approved narration. Review ngram’s plan, then create a product demonstration that shows the workflow this role needs to understand.
Genuine interface screenshots, a verified product path and approved narrationA focused SaaS demonstration using the supplied interface material
Ways to run: Claude
Each recurring onboarding question or approved process update
Give Claude the approved customer instructions for one onboarding step. Review ngram’s explanation, then create a video that tells customers what to prepare and what to do next.
Approved onboarding instructions and demonstration assetsA focused customer instruction video
Ways to run: Claude
Each reusable support answer
Give Claude your help article and the question customers keep asking. Review ngram’s plan, check the troubleshooting steps and add the finished video to your support answer.
A documented symptom, checks and resolutionA reusable troubleshooting video
Ways to run: Claude
Each approved client story
Give Claude the customer story, approved quotation and reported results. Review ngram’s narration and scene plan, then create a video that leads prospects to the full story.
A consented customer story and attributed resultsA source-backed case-study video
Ways to run: Claude
Each buyer demonstration or evaluation follow-up
Give Claude the buyer’s priorities, demonstrated screens and open questions. Review ngram’s plan, then create a concise recap that keeps the product facts and proposed next step clear.
Reviewed demo notes, genuine demonstrated screens and outstanding questionsA buyer-specific recap with a clear evaluation step
Ways to run: Claude
