Start with the technical source your team actually maintains. Turn the setup, workflow, or API concept into a precise tutorial, then keep it editable when the product or documentation 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 screen recording, no second pass to clean up code. Paste the page, accept the scene plan, render the walkthrough.
Paste markdown, link a public docs URL, or drop a README. ngram preserves code fences, API method names, parameter tables, and step-numbered prerequisites.
Each H2 becomes a scene. Each fenced code block becomes a syntax-highlighted scene card. Parameter tables become callouts. Curl commands and JSON payloads stay readable on the frame.
Reorder scenes, rewrite the voiceover line for a specific endpoint, or regenerate one code card without touching the rest. Visual chat handles the per-scene tweaks.
Review the product docs 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.
Output controls
Code fences render with the right language theme: TypeScript, Python, Go, curl, JSON, GraphQL. The voiceover narrates the line being highlighted, not just the block.
HTTP method, path, and required parameters get pulled into framed callouts. Optional parameters stay smaller so the eye lands on what matters first.
Numbered prerequisites become a numbered scene track: install the SDK, set the API key, hit the first endpoint. Each step earns its own frame with a progress indicator.
Captions handle camelCase, snake_case, package names, and acronyms without autocorrect mishaps. A domain pass keeps function names intact.
Translate the script and burned-in captions to any of the supported voiceover languages. Code blocks stay in source. Useful for SDK launches in multiple markets.
Set the intended channel and aspect ratio for the product docs video, then review the crop, caption placement, and CTA before exporting one MP4. Prepare another channel version as a separate edit.
Paste the diff or the new version, and ngram rebuilds the affected scenes without touching the rest. Keeps a 90-second quickstart in sync with the latest SDK release.
Working with pre-release SDK docs or private endpoints? Talk to sales about security, access controls, and data handling for your team.
The rest of ngram
Reads the docs page and writes a script that opens with the use case, then walks each code block. Keeps method names intact and skips the boilerplate the reference page already covers.
Learn morePronounces SDK names, camelCase identifiers, and acronyms the way your team says them, not the way TTS guesses. Per-team voices available for branded developer channels.
Learn moreBurned-in captions that preserve code identifiers, parameter names, and HTTP verbs. Critical when half your viewers watch muted on the docs page.
Learn moreDeveloper-facing videos still represent the product. Logo and color applied per export so the API walkthrough matches your docs site. Choose saved intro or outro slides for each video that needs them.
Learn moreAnimated callouts, parameter pop-ups, and method highlights generated per scene. Turns a static code block into a frame that holds attention long enough to read.
Learn moreFinish the product docs video in Studio and download one MP4. When a site, player, or handoff requires MOV, WebM, or MKV, convert that file separately in Video Converter, one input and one output per job.
Learn moreUse cases
Embed a 90-second walkthrough above the curl example. Watch-completes correlate with developers reaching the second endpoint without filing a ticket.
See use caseShip the SDK and the walkthrough video on the same day. Re-render from the new docs page when 1.x ships, no studio re-shoot, no scheduling.
See use caseEach partner integration deserves its own video. Convert the integration guide once per partner; embed on the partner page and in the launch post.
See use casePair the GitHub release with a 60-second walkthrough that shows the new endpoint in action. Posts in Discord and developer Slack instead of getting buried.
See use caseTake the “How auth works” page and render an explainer with the actual method signatures. Stays accurate when the auth flow changes.
See use caseSupport articles that include code snippets get a video version that walks through the snippet. Cuts the back-and-forth tickets that follow copy-paste mistakes.
See use caseConvert the announcement page, not the marketing brief, into the launch video. Keeps the demo on the real method names and lets PMM publish without a re-shoot.
See use caseTurn the implementation guide into a video that the CSM hands to a new account’s engineering team during kickoff. Fewer “where do I start” emails.
See use caseOther converters
Product docs to video shares the parser, brand kit, and render stack with the rest of the converters. Pick the input you actually have.
Internal handbooks, PRDs, SOPs, and Google Docs. The non-technical sibling: no code blocks, no method tables, broader prose.
Open converterPair an API quickstart walkthrough with the changelog video that ships alongside it. Same brand kit, different framing.
Open converterCustomer-facing help articles, often a mix of UI screenshots and short snippets. Sits next to product docs in most teams’ stacks.
Open converterTools that pair with this converter
Generating from the docs
Different entry points to the same parser
Point at a public Mintlify, ReadMe, or Docusaurus page. ngram fetches it, preserves code blocks, and renders the walkthrough.
Open toolPaste raw markdown when the docs page isn’t public yet. Same parser, no fetch.
Open toolWhen the docs page doesn’t exist yet, prompt the generator with the endpoint behavior and let it draft the walkthrough.
Open toolPaste a snippet of the docs page, pick a voice, get a narrated explainer in one pass.
Open toolEditing the walkthrough further
After the first render lands
Trim a 4-minute walkthrough into a 90-second quickstart. Replace the intro card. Re-record one scene’s voiceover.
Open toolHand-tune captions where the AI got a SDK name wrong, or burn captions onto a rendered walkthrough from an external source.
Open toolTrim by transcript: pick the endpoint demo out of a longer walkthrough to embed in the API reference.
Open toolTranslate the voiceover and captions into a target market’s language while leaving code identifiers untouched.
Open toolPolishing the source first
Before you convert
Capture the real terminal output to drop into the rendered walkthrough as a B-roll segment between code scenes.
Open toolGenerate architecture diagrams or auth-flow visuals to use as scene backgrounds where the docs page has none.
Open toolIf you record a developer doing the walkthrough first, fix the gaze before the doc pages become scene cards around them.
Open toolBuilt for teams
Quickstart walkthroughs that ship with each SDK release. The video is one paste from the docs page, not a Friday calendar block in the studio.
See workflowsLaunch videos for technical features that use the real method names instead of marketing paraphrase. Prepare and review each channel edit separately before exporting one MP4.
See workflowsConvert the implementation guide into a 90-second video for the engineering kickoff. Stakeholders watch instead of skimming.
See workflowsOnboarding videos for technical accounts. Convert the integration guide once per partner, hand to the customer engineering lead.
See workflowsHelp articles with code snippets get a paired video walkthrough. Reduces “my curl returns 401” tickets that have an answer on the auth page.
See workflowsInternal documentation behind SSO can still feed branded walkthroughs. Talk to sales about security, access controls, and data handling for your team.
See workflowsIntegrations
Every integration ships with a working recipe. Or build the same flow with the REST API and self-managed webhook subscriptions for video.completed or video.failed.
whenA new docs page is published in Mintlify or ReadMe
thenUse Zapier's documented Create Video or Get Status action for this Product Docs to Video job with its supported input, then pass the result to the next step.
whenClaude or ChatGPT is handed an API docs URL during a developer workflow
thenUse MCP's documented create and status tools for this Product Docs to Video job with its supported input, then return the status or result to the agent.
whenA self-hosted CI step opens a PR with updated docs
thenUse n8n's documented Create From Text, Create From URL, or Get Status node for this Product Docs to Video job, then pass the status or result onward.
whenYou’re on a public docs page in the browser
thenHit “Convert to walkthrough” and get the MP4 back in a new tab
whenThe video from your product docs is ready for YouTube Social Publishing Beta
thenVerify the YouTube destination for the approved product docs walkthrough, then publish it now.
How it compares
Guidde records and edits a desktop capture. Scribe builds a step guide from clicks. Loom hands you the raw recording and a trim bar. ngram reads the docs page itself, code blocks, headings, parameters, and ships a branded walkthrough without a screen recording.
| Feature | ngram | Guidde | Scribe | Loom |
|---|---|---|---|---|
| Source material | Reads the actual docs page (markdown, MDX, HTML) | Screen recording | Browser click capture | Screen recording |
| Code block treatment | Language-aware syntax-highlighted scene cards | Whatever is on screen | Static screenshot | Whatever is on screen |
| Re-render on docs update | Paste the diff, regenerate affected scenes | Re-record the desktop | Re-record the click flow | Re-record the desktop |
| Storyboard before render | Scene-by-scene preview with editable script | Post-record edit | Step list editor | Trim bar |
| Channel-specific editing workflow | One reviewed MP4 per channel-specific edit | 16:9 only | Doc/PDF format | 16:9 only |
| Voiceover that pronounces SDK names | Domain pass for identifiers and acronyms | Your own voice | Text steps | Your own voice |
| Localized voiceover and captions | Translate script and burned-in captions; keep code | Manual re-record | Manual translation | Manual re-record |
| API for the docs pipeline | REST API with self-service API keys; MCP, Zapier, and n8n for documented workflows | Limited API | Limited API | Limited API |
| Source handling | Used only to generate your video | Retained | Retained | Retained |
Product Docs → Video
Paste the page, accept the scene plan, render the branded walkthrough. Roughly the time it takes to write the launch announcement.
Follow a workflow from source material to a video you can review, share and make again.
Each distinct buyer question or updated approved answer
Give Claude the buyer question and approved product evidence. Review ngram’s answer and visuals, then create a focused video with one practical next step.
One buyer question and current approved product evidenceA concise answer video grounded in the approved source
Ways to run: Claude
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 product listing or approved update
Give Claude your product facts and real photos. Review ngram’s plan, then create a short listing video that keeps the product’s appearance and attributes accurate.
Current product facts and approved photosA source-faithful product-page video
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 product question or revised answer
Give Claude the questions, approved answers and speaking roles. Review ngram’s Conversation plan, then create an exchange with distinct presenters and voices.
Approved questions and answers, speaker roles and supporting product factsA two-speaker product explanation in Conversation style
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 audience, positioning update or new product explanation
Give Claude the audience, approved positioning and supported product facts. Review ngram’s plan, then create a concise explanation of how the product’s main concepts fit together.
An approved positioning brief and current product sourcesA source-backed software explanation with clear labeled visuals
Ways to run: Claude
Each product release
Give Claude the shipped changes. Use ngram to create a narrated update, review its plan and bring the finished video back to the conversation.
Release notes and real product screenshotsA narrated customer update
Ways to run: Claude
Every release
Give customers a short explanation of what shipped, who it helps and where to find it. Use your release notes to make a repeatable video update, then check the result against the shipped product.
Published release notesRelease roundup video
Ways to run: In ngram
