Prompts real ngram users wrote to make walkthrough videos — cleaned up, copy-ready. Pick the shape closest to your brief and generate.
Trusted by teams at
A walkthrough video shows how something works, step by step — narrated over the real UI, a script, or both. People make them to onboard users, explain a product, and create how-to content. The examples below are real prompts from ngram users, cleaned up and ready to copy.
30s
Typical length
~93%
Attach a URL or file
Step-by-step
Structure
Copy one, swap the bracketed parts for your product or topic, and generate.
The most common shape: drop in a URL and get a guided video that tours the site's key sections.
Create a 30-second tutorial walkthrough video from [URL]. Tour the main sections of the site, highlight what makes it useful, and narrate each step clearly. Keep the pacing steady and end with a brief closing line.
Pair a written script with supporting screenshots to build a step-by-step walkthrough without any recording.
Create a walkthrough video using the attached script and screenshots. Follow the script order exactly, use each screenshot as the visual for its matching step, and narrate in a clear, professional tone.
Upload a rough tutorial and clean it up — better pacing, tighter narration, cleaner presentation.
Take the uploaded tutorial video and improve it. Tighten the pacing, clean up any dead air, add clear step labels, and make the narration more direct. Keep all the original content — just make it sharper.
When you have a full script with scene descriptions and images, ngram assembles each shot in order.
Create a 9:16 marketing walkthrough video from the full script below. Each scene description includes the image to use and the timing. Assemble them in order, add voiceover from the script text, and include brief on-screen labels per scene.
What strong walkthrough prompts share in common.
Create a 30-second tutorial walkthrough video from [URL]. Tour the main sections of the site, highlight what makes it useful, and narrate each step clearly. Keep the pacing steady and end with a brief closing line.
Input
One URL. No recording, no screenshots — the system fetches the page and pulls what it needs.
Structure
Implicit tour order: sections in sequence, highlight the value at each stop, end on a closing line. Simple and repeatable.
Tone
"Clear, professional" — lets the content carry the video rather than overselling it.
Guardrail
No invented UI: the prompt points to the real URL so every screen in the video matches the actual product.
Why it works
It gives the model one source of truth (the URL), a clear order (tour the main sections), and a single tone directive. There's nothing to invent because the real page is the script.
Ninety-three percent of walkthrough prompts include a URL or file. The real source keeps every screen accurate and removes the need to describe what the product looks like.
Say what the viewer does at each point, not what the feature is called. "Select a data source" lands better than "the data-source picker."
Thirty seconds covers one task well. Trying to cover three turns every step into a blur.
One tone directive — "clear and professional" or "warm and casual" — is enough. Conflicting tone instructions produce awkward voiceover.
Close with a single action or result, then the CTA. A laundry list at the end undoes a tight walkthrough.
When the shot sequence matters — training, onboarding, compliance — pair a written script with screenshots. It locks the order so nothing gets rearranged.
URL walkthrough, script-and-screenshots, polish an existing clip, or scene-by-scene? Choose the example closest to your brief.
30s
Swap the bracketed parts for your product, topic, or URL. Attach your source file if you have one.
1 min
ngram drafts the walkthrough. Adjust pacing, step labels, voice, and music before you ship.
5 min
Prefilled prompts you can copy, edit, and generate.
The jobs people hire walkthrough videos for.
Teams that ship walkthroughs with ngram.
The ngram capabilities a walkthrough leans on.
Wire walkthrough creation into the tools your team already uses.
whena walkthrough finishes rendering
thenpublish it straight to your channel
whenyou approve a how-to walkthrough
thenpost it captioned to your feed
whena new feature ships
thenauto-render a walkthrough and notify the team
whena support ticket recurs
thenkick off a walkthrough render in a scenario
whena webhook fires from your CMS
thengenerate a walkthrough in a self-hosted flow
whenyou capture a screen recording
thenstart a walkthrough from the browser
Quick utilities for the pieces of a walkthrough.
Drop in what you already have.
Paste a URL or drop in a script and ngram builds the walkthrough. Edit pacing, captions, and voice before you ship.