Convert by ngram
Bring the Markdown source your technical team already maintains. Preserve the code, steps, and terminology while turning it into a narrated tutorial or product update for a broader audience.
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 scene-by-scene scripting, no syntax to clean up. Paste the .md, review the plan containing the script, hit render.
Paste your raw Markdown or point at a public README URL, and ngram parses # heading levels, bullet and numbered lists, code fences, and blockquotes. Direct .md file upload is coming soon; paste and public URL work today.
Each ## heading becomes a scene. Numbered steps build as sequence cards. Bullet lists animate in. Code fences render as readable on-screen blocks. The agent writes the voiceover from the prose, not the markup.
Approve, reorder, or rewrite scenes in plain language. Swap a visual, tighten a line, drop a section that reads better as text. Every change is one chat turn.
Export MP4 in 16:9, 1:1, or 9:16. Publish to a hosted /watch page, push to LinkedIn, or drop the link in the repo's release notes.
Output controls
H1, H2, and H3 in the Markdown become real scene boundaries, not arbitrary 7-second chunks. A long section under one heading splits on its natural paragraph beats.
Fenced code blocks and inline snippets render as monospace on-screen cards that hold long enough to read. The voiceover narrates the explanation around the snippet, not the syntax itself.
Keep the file's exact wording for a precise install guide, or let the agent rewrite dense prose for spoken voiceover. Toggle per scene.
Brisk for a changelog, measured for an API reference, warm for a getting-started guide. Pick a brand voice or use a cloned one from /app/settings/voice.
Auto-generated and styled per brand kit. Numbered steps and command names stay readable; blockquotes hold for emphasis when the video plays muted.
Bullet hierarchies animate in. Numbered steps stack as counter cards. Markdown tables render as branded scene cards instead of a flat grid of text.
Render the same README as a German quickstart, a Spanish changelog, or a Portuguese integration guide. Captions, on-screen text, and voiceover all swap together.
Prepare a 9:16 launch-post edit, a 1:1 LinkedIn edit, or a 16:9 hosted-docs edit from the same Markdown. Review each cut separately before exporting one MP4.
The rest of ngram
Turn dense Markdown prose into a spoken script that keeps the file's meaning and heading order. The agent rewrites long code-doc paragraphs for the ear and skips the raw syntax.
Learn moreBullet lists animate in. Numbered install steps build as counter cards. Markdown tables and blockquotes render as branded scene cards, so the structure of your .md carries on screen.
Learn moreNarrate the README or changelog in a voice that fits a developer audience: clear, even-paced, and easy to follow over a code walkthrough. Powered by ElevenLabs and MiniMax.
Learn moreEvery Markdown-to-video render picks up the workspace logo, type, palette, and approved phrases. The docs video, the launch video, and the changelog video all look like the same product.
Learn moreTurn on captions before export. Useful when the docs video autoplays muted at the top of a help article or inside a GitHub README embed.
Learn moreConvert one source .md into localized docs videos and quickstarts. Voiceover, captions, and on-screen text translate together, so global developers get the same walkthrough in their language.
Learn moreUse cases
The release section nobody scrolls becomes a 60-second branded video per ship. Each ### version heading is a scene; re-render straight from the updated Markdown next sprint.
See use casePaste the release-note Markdown and ship a video update instead of another bullet list. Higher feature adoption than a changelog entry that gets skimmed and closed.
See use caseEndpoint headings, request and response blocks, and parameter tables in your API Markdown become a narrated walkthrough developers can watch before they read the full spec.
See use caseThe numbered setup steps in an integration .md become a sequence of scene cards that walk a developer from npm install to the first successful call.
See use caseMarkdown-authored support articles get a short looping video version embedded at the top. Customers see the action instead of re-reading the steps, and tickets drop.
See use caseThe getting-started README becomes a branded video developers can play before cloning. GitHub renders it inline, so the first impression of the repo is motion, not a wall of text.
See use caseAn ops runbook or onboarding SOP kept in Markdown becomes a modular training video. Steps stay numbered on screen; H2 sections become chapter breaks.
See use caseA planning doc written in Markdown opens nobody's inbox. The 3-minute branded video from the same file gets watched in the all-hands and reshared in Slack.
See use caseOther converters
A .md file is one starting point. Word docs, PDFs, slides, and plain text all route through the same agentic storyboard step and the same brand kit, so the output looks identical no matter which source you paste.
When the source is a Google Doc, Word file, or general doc rather than raw Markdown, the docs converter reads the same heading-and-list structure without the .md syntax.
Open converterWhen the docs are a full product-documentation set rather than a single .md, the product-docs converter respects code blocks, endpoints, and cross-references across pages.
Open converterWhen the source is a short brief or a single paragraph instead of a structured Markdown file, drop into text-to-video for a one-prompt render.
Open converterTools that pair with this converter
Generating from scratch
When you only have the Markdown and no footage yet
Paste a single section from the .md and get a standalone short video. Handy for pulling one changelog entry or one install step out of a longer file.
Open toolWrap the README's script in a talking-head presenter instead of motion graphics. Good for a maintainer intro or a getting-started welcome at the top of the docs.
Open toolConvert a Markdown passage into narrated video without a full storyboard pass. Faster and less branded, useful for a quick internal voice note from a runbook.
Open toolSkip the file and prompt the whole video from scratch when the Markdown is still a rough outline rather than finished docs.
Open toolEditing the output further
After the Markdown-to-video render lands
Open the rendered docs video on the timeline. Trim a section that reads better as text, swap the visual on one code scene, or re-cut a 9:16 alt for the launch post.
Open toolLayer extra subtitle tracks for localized versions of the same README (German, French, Japanese) on top of the source render.
Open toolSlice a long docs video into per-heading clips for in-app tooltips, a chaptered help-center embed, or one Slack drop per feature.
Open toolDrop a licensed bed track under the launch or changelog cut, kept low beneath the voiceover so the steps stay easy to follow.
Open toolPolishing the source first
Tighten the Markdown before it becomes video
Run the .md through the script generator to tighten long paragraphs and strip syntax noise before the storyboard step. Better script in, better video out.
Open toolOnce the docs video exists, get title options that match how developers actually search for the feature it covers.
Open toolAuto-write a description that summarizes the README and timestamps each heading-derived chapter for the hosted /watch page.
Open toolTake the finished Markdown-to-video render and republish it in more languages. Captions, voiceover, and on-screen text all swap per locale.
Open toolBuilt for teams
READMEs, integration guides, and API reference Markdown become narrated walkthrough videos for docs pages, GitHub, and developer newsletters, with code fences kept legible on screen.
See workflowsTurn a CHANGELOG.md or a Markdown PRD into a stakeholder video. Re-render straight from the updated file each sprint instead of booking another recording.
See workflowsLaunch briefs and release notes kept in Markdown translate directly into customer-facing launch video, no separate production cycle between the .md and the post.
See workflowsRunbooks, SOPs, and policy docs authored in Markdown ship as branded onboarding and training videos instead of wiki links nobody opens.
See workflowsMarkdown setup guides and feature-education docs become onboarding and renewal videos that lift activation and self-serve completion.
See workflowsHelp articles written in Markdown get a 60-90 second video version embedded at the top of the page. Same wording, fewer how-to tickets.
See workflowsCourse outlines and tutorial scripts drafted in Markdown turn into lesson videos, with headings as chapters and numbered steps as on-screen beats.
See workflowsIntegrations
These recipes start from where your .md already lives: a merged README, a tagged CHANGELOG, a rendered docs page. Wire one up, or hit the REST API and self-managed webhook subscriptions for video.completed or video.failed to build your own.
whenAn approved Markdown is ready for a Studio upload
thenUpload the file in Studio; use Zapier's documented Create Video or Get Status action for this Markdown to Video job, then pass the result to the next step.
whenAn agent has an approved markdown and a video brief
thenUpload the file in Studio; use MCP's documented create and status tools for this Markdown to Video job, then return the status or result to the agent.
whenA webhook fires when a README.md is merged to the main branch
thenUse n8n's documented Create From Text, Create From URL, or Get Status node for this Markdown to Video job, then pass the status or result onward.
whenYou hit 'Convert to video' on a rendered Markdown page in GitHub or a docs site
thenGet a branded walkthrough back in a new tab with the file's headings already chaptered
whenThe video from your markdown is ready for LinkedIn Social Publishing Beta
thenCompose the LinkedIn post for the approved markdown video, then publish it now.
whenThe video from your markdown is ready for YouTube Social Publishing Beta
thenVerify the YouTube destination for the approved markdown video, then publish it now.
How it compares
Slide-based Markdown tools render your .md as static deck frames. Avatar tools narrate the text over a presenter card. ngram reads the file's heading-and-list structure and builds a branded motion-graphic video with voiceover and captions.
| Feature | ngram | Marp + screen recorder | Synthesia | Manual edit (Premiere or DIY) |
|---|---|---|---|---|
| Reads Markdown structure (headings, lists, code fences) | Yes, headings become scenes, lists become sequences, code fences render legibly | Renders .md as static slides, no scene logic | Extracts text; avatar narrates linearly | Manual, depends on the editor |
| Time from .md to first cut | Minutes | Slides fast, then a manual screen-record pass | Tens of minutes (script + render) | Hours to days |
| Re-render when the file changes | Paste the new .md, re-render | Re-export slides, re-record | Re-generate narration | Re-edit from scratch |
| Brand kit across every render | Set up and select your Brand Kit | Theme CSS per deck | Template-level branding | Manual per project |
| Voiceover from the prose | AI voiceover written from the file, captions burned in | None, you record it | Avatar voiceover | Manual VO or none |
| Storyboard preview before render | Full scene plan, editable in chat | Slide preview only | Generate first, edit after | Editor decides |
| Localized variants | Voiceover, captions, on-screen text translate together | Manual per language | Avatar voiceover per language | Manual per language |
| Channel versions | 16:9, 1:1, 9:16 from one file | Slide aspect only | One format per export | Manual reframe per format |
| Best when | You want a branded, scene-based video directly from a Markdown file | You want presentation slides from Markdown | You want a talking-head presenter for the text | You have an editor and time to burn |
Markdown → Video
Paste the README, changelog, or docs .md, review the plan containing the script, and render a branded video people watch instead of bookmark.
Follow a workflow from source material to a video you can review, share and make again.
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
