Does Sizzledraft use real screenshots of my GitHub repo?

Yes. It drives a browser at the repository page and captures the README hero, badges, visible star count and code blocks as rendered. Those captures become source material for the video, so repository details remain recognisable instead of being replaced with generic developer graphics.

How do you keep GitHub code blocks readable in vertical video?

The scene uses tight crops and short excerpts rather than shrinking the full desktop README into a 1080x1920 frame. Choose one install command or compact example that supports the ad's claim. Longer configuration files and multi-step snippets should be split across later videos.

What video formats can I create from a SaaS repository?

Sizzledraft renders vertical video at 1080x1920 or horizontal video at 1920x1080. Both use 30fps H.264 output, and audio is normalised to -14 LUFS. The orientation should match where the ad will run and how much code must stay readable.

Can I use a trending sound with the GitHub repo video?

Yes, but the trending sound is handed over as a link so you can attach it natively on the publishing platform. It is not baked into the H.264 file because baked-in audio does not count as using that platform sound. The rendered audio is still normalised to -14 LUFS.

Show your SaaS repo working in a short video

Sizzledraft turns a SaaS startup's GitHub repo URL into a short video ad built from real repository screenshots. It captures the README hero, badges, star count and code blocks, then renders the scenes at 30fps with normalised audio.

Opening lines that work here

See why developers starred this SaaS repo
It leads with the visible star count, the clearest source of social proof on a GitHub repository.
From git clone to a working SaaS workflow
It connects a familiar installation command to the product result developers want to see.
This README turns into a product demo in seconds
It sets up a visual transition from repository documentation to the SaaS product working on screen.

How do I turn a GitHub repo into a SaaS video ad?

Start with the public repository URL. Sizzledraft drives a browser through the GitHub page and captures the README hero, badges, star count and useful code blocks as they actually appear. It uses the page's own visual details to author a short scene, then renders every frame with scored, synthesised audio. The first video is cut from the repository page alone, so the README structure determines the initial story. Later videos accept a prompt, which can direct attention to installation, an API example or a particular SaaS workflow. The result can be rendered vertically at 1080x1920 or horizontally at 1920x1080, at 30fps in H.264.

What should a GitHub repo video show first?

Show the star count first when it is meaningful, because it is the strongest compact signal available on most SaaS repositories. Keep it beside the repository name so viewers understand what they are seeing without reading the full page. Move next to one short code block, such as the install command or smallest working example, then show the product carrying out the workflow that command enables. Avoid scrolling through the entire README. Badges can establish language, build status or package availability, but they work as supporting details rather than the main claim. A useful sequence is proof, setup and result: star count, readable command, then the SaaS product working on screen.

Can a README provide enough material for a video ad?

A strong README can provide the opening evidence and technical context, but it rarely supplies the whole visual story. Its hero, badges and star count establish the repository, while a concise code example shows how a developer starts. Most of the remaining page is text, which becomes hard to follow at video speed. The ad should therefore isolate one claim from the README and connect it to a visible product action, such as creating a deployment, inspecting an event or completing an API request. Sizzledraft uses real browser captures instead of rebuilding the repository page. Tight framing and deliberate pacing keep commands legible, especially in a 1080x1920 vertical export where a full desktop README would be too small.

What the browser actually gets

Our browser captures the real README hero, repository badges, visible star count and code blocks from the GitHub page. The star count provides a strong visual hook, while the remaining material is mostly text, so code and README excerpts need tight crops and short on-screen sequences.

The common mistake

A common mistake is scrolling through the full README while expecting viewers to read badges, setup notes and code at once. Fix it by opening on the star count, isolating one short command and cutting directly to the SaaS product completing the related workflow.

A GitHub README explains installation and features, but static text does not show prospects how the SaaS product behaves.
The repository star count can earn attention, yet it is easy to bury among badges, setup commands and long documentation.
Code blocks often become unreadable when founders shrink a desktop README into a vertical social video.

Questions

Does Sizzledraft use real screenshots of my GitHub repo?: Yes. It drives a browser at the repository page and captures the README hero, badges, visible star count and code blocks as rendered. Those captures become source material for the video, so repository details remain recognisable instead of being replaced with generic developer graphics.
How do you keep GitHub code blocks readable in vertical video?: The scene uses tight crops and short excerpts rather than shrinking the full desktop README into a 1080x1920 frame. Choose one install command or compact example that supports the ad's claim. Longer configuration files and multi-step snippets should be split across later videos.
What video formats can I create from a SaaS repository?: Sizzledraft renders vertical video at 1080x1920 or horizontal video at 1920x1080. Both use 30fps H.264 output, and audio is normalised to -14 LUFS. The orientation should match where the ad will run and how much code must stay readable.
Can I use a trending sound with the GitHub repo video?: Yes, but the trending sound is handed over as a link so you can attach it natively on the publishing platform. It is not baked into the H.264 file because baked-in audio does not count as using that platform sound. The rendered audio is still normalised to -14 LUFS.

Paste your link and watch one free