LaunchReel AI / GitHub to video
GitHub to video: paste a repo, get a launch video
Paste a public repo URL from GitHub, GitLab, Codeberg or Bitbucket. LaunchReel AI reads the repository page and its README, writes a brief (what the project is, who it is for, three to six points worth showing) and a shot-by-shot storyboard, and once you confirm both it renders a 16:9 launch video with captions. The brief and the storyboard are free and need no email.
No email and no card to start. You see the brief and the storyboard first; we ask for an email only when you want the preview rendered.
What is free, what costs credits
- Free, no email: the brief and the storyboard, written from what you paste. One storyboard rewrite is free too.
- Free once per verified email: a watermarked 720p preview of the film (and a few per network per day).
- Credits from one-time packs, from $9: 1 to change a shot, 10 for a clean 1080p export, 20 for 4K, 5 to start another product. See pricing.
What the film is today
- 16:9 only, 1920×1080 or 4K. A 9:16 vertical cut is not available yet.
- Silent: captions are burned in and you also get an .srt file. No voiceover or music yet.
- MP4 files. No GIF export.
What happens after you paste the repo
We read the repository page as the code host renders it, which includes the README, plus up to three pages linked from it, such as a guide or docs. From that we draft the brief. You correct it: the one-line description, the audience, the selling points, which screens to use and the brand colour.
Then we write the storyboard: seven shots for a 30-second film, each with its words, its timing and the motion it uses. You can change a line, swap a screen, move or remove a shot, and nothing renders until you confirm. On the run shown below, the brief took about a minute and the storyboard about four more. One desk writes every brief and storyboard in turn, so a queue can add a few minutes.
What a README gives the film
A README is already a launch script. The table on README to video shows, line by line, how one README became a brief and then shots.
- The title line and description become the opening shot
- The feature list becomes the middle shots: panels, cards and short title lines
- Numbers the README states (such as “20 MCP tools”) are quoted as written, never invented
- Commands and code are set as real type, so they stay exact
Check these on the brief before you confirm
A bare repository has no brand of its own, and today the reader can pick up the code host's own icon, its blue, or pages and images from the host's marketing site as screen candidates. On the brief, clear or replace the logo, set your colour, and untick any screen that is not yours. This is a known gap in the reader; the brief step exists so that you catch it before anything renders.
Where it fits
Post the MP4 with the release, put it on your docs site, or attach it to a Show HN or X post. For a video about one release rather than the whole project, use the changelog video maker. If the project ships as a browser add-on, see Chrome extension demo videos.
Storyboard
- 01 · 0:00–0:04Big-word shot: “Automate” with the repository page as the screen.“State-aware GUI automation for AI coding agents.”
- 02 · 0:04–0:07Tagline tracks in on the dark stage.“Pure Swift. Zero deps.”
- 03 · 0:07–0:11Dashboard kit: one KPI panel titled “Automation Toolkit”.“MCP Tools · 20”
- 04 · 0:11–0:15.5Glass-trio kit: three cards, one per technique the README names.“Accessibility API · Vision OCR · CGEvent Synthesis”
- 05 · 0:15.5–0:19.5Big-word shot: “Bridge” over the README's How It Works section.“For agents like Claude Code and Cursor”
- 06 · 0:19.5–0:23Two title lines, the second in the accent colour.“One proxy. Full macOS control.”
- 07 · 0:23–0:30End card: initials “MB”, product name and a line under it.“MacAutoBridge · GUI automation for AI agents”
Written by LaunchReel AI on 27 September 2026 from the public repo RuoqiJin/mac-auto-bridge, an open-source project of ours. Before confirming the brief we removed two things the reader had picked up from GitHub itself (GitHub's logo and a github.com/features page); the storyboard is otherwise unedited. The brief took about a minute and the storyboard about four more. It has not been rendered to a film yet.
Questions
Can it read a private repository?
No. The reader only fetches public pages and never asks for access to your account. For a private project, attach a .zip with the README (up to 50 MB) or describe the product in a sentence; the box takes both.
What if my README has no screenshots?
The film still works: kinetic type and motion kits (panels, cards, title lines) are drawn from the README's words, and the repository page itself is a screen candidate. A screenshot of the tool running gives the middle of the film something concrete, so if you have one, add it to the README before you paste the link.
Can I edit each shot?
Yes. On the storyboard you can change any line, swap the screen, move or remove a shot, free, before anything renders. After the preview, changing one shot costs 1 credit and only that shot re-renders.
Try it on your own project
Paste your link. The brief and the storyboard come back in a few minutes, for you to correct before anything renders. See pricing.