LaunchReel AI

LaunchReel AI / GitHub to video

GitHub to video: turn your README into a launch video

A good README already contains a launch script: a one-line description, a quick start, and a list of what the project does. LaunchReel AI reads your repository and your project site, pulls out the selling points, and turns them into a short video you can post with your release, pin to your repo, or share on Hacker News and X.

How README to video works

Give us the repo URL, and your docs or landing page if you have one. We write back a brief for you to confirm: what the project is, who it is for, three to six points worth showing, and which assets to use. Then you review a storyboard before anything renders.

If you only send a repo, the README does most of the work. Projects without a website are common, and a clear README with a short description, an install command and one example output is enough material for a 30-second video. A screenshot of the tool running, or a diagram you already use in your docs, gives the video a stronger middle.

  • The tagline from your README header
  • Install and usage commands shown as readable terminal frames
  • Benchmarks or examples you already publish, quoted as written
  • Your logo and project colors, if you have them

Code people can actually read

Terminal output and code snippets are set as real text in motion graphics, not generated pixels, so commands stay legible and correct. If a flag changes before release, you edit that line and only that shot re-renders.

Where it fits in a release

Use the 16:9 cut in the README or on your docs site, and the 9:16 cut for short-form posts. Both come with captions and commercially licensed music. If the project also has a hosted product, see the SaaS explainer video page; if it ships as a browser add-on, see Chrome extension demo videos. The product launch video template shows the shot structure we start from.

Example storyboard

Example: 30 s GitHub to video for a CLI tool30 s
  1. 01 · 0:00–0:03A terminal window fills with a slow, failing build log.Number taken from the project's own README.“Your CI takes 14 minutes. Why?”
  2. 02 · 0:03–0:06Project logo and name slide in over the repo's accent color.“buildscope”
  3. 03 · 0:06–0:10Install command types out in a clean terminal frame.“One command to install”
  4. 04 · 0:10–0:15Flame-graph screenshot from the README animates in, slowest step highlighted.“See exactly which step is slow”
  5. 05 · 0:15–0:20Config snippet appears with one line highlighted.“Cache it with one line of config”
  6. 06 · 0:20–0:25Supported CI providers listed as a simple grid of names.“Works with the CI you already use”
  7. 07 · 0:25–0:30End card: repo path, license badge and star button graphic.“Open source · github.com/example/buildscope”

An illustrative storyboard. Yours is written from your own site and confirmed by you before rendering.

Questions

Do you need access to a private repository?

No. We read public repositories and pages. For a private project, send screenshots and a short description after checkout on your order page.

Will the code in the video be accurate?

Code and commands are typeset from your README, not generated as images, and you check them in the storyboard before rendering.

Can I embed the video in my README?

Yes. You receive MP4 files you can upload to GitHub, your docs site or any social platform, with full commercial usage rights.

Get your github to video

Paste your URL. We send the brief back for you to confirm, then storyboard and a free watermarked preview. See pricing.