How to Make a Demo Video for Your Lovable (or Bolt) App
To make a demo video for a Lovable, Bolt, or Replit app: pick the one job your app does best, fill it with realistic demo data, capture five to eight clean screens of that job, write a 30–45 second script that ends on the result, then animate the real screens and export a version for each place you'll post. You don't need to film anything or learn an editor. The hard part is choosing what not to show.
Step 1: Choose one job, not a feature tour
Vibe-coded apps tend to grow sideways fast, so the temptation is to show every screen. Don't. Write one sentence in the form 'You [do X] and get [result Y]', and only show screens that serve it. A habit app's job might be 'log a habit in one tap and see your streak'. Settings, auth, and onboarding usually don't belong in a launch demo. The demo video script guide shows how to structure the arc.
Step 2: Seed realistic demo data
- Replace lorem ipsum and 'test123' with plausible names, numbers, and content. Empty states make a product look unfinished.
- Never use real user data. Create a demo account, or ask your AI builder to generate a seed script with sample records.
- Stage the 'after' state: a filled dashboard, a completed task, a generated output. The result is the most important frame in the video.
- Hide dev artifacts: preview banners, console errors, placeholder images, and debug toggles.
Step 3: Capture clean screens
Open the deployed app (not the editor preview) in a clean browser profile with no extensions in view. For a web app, set the window to a common desktop width such as 1440 px and capture at 2x on a Retina display. For a mobile layout, use your browser's device mode at a phone size. On macOS, Cmd+Shift+4 then Space captures a single window; Cmd+Shift+5 records the screen if you need a live interaction. Capture five to eight states of your one job, in order. The screenshot checklist covers the details that make captures look professional.
Step 4: Write a 30–45 second script
| Beat | Time | What it says |
|---|---|---|
| Hook | 0–3 s | The problem or the payoff, in one line of on-screen type |
| Setup | 3–10 s | Who it's for and the one job |
| Show | 10–30 s | Three to five screens of the job, each with a short caption |
| Result | 30–38 s | The finished state, held long enough to read |
| CTA | 38–45 s | App name and where to try it |
Write captions as on-screen text first. Most feeds autoplay muted, so voiceover is optional. Keep each caption under about eight words so it can be read in the time it's on screen.
Step 5: Animate the real screens
You have two practical routes. Edit a screen recording, trimming dead time and adding zooms and captions. Or build a motion-graphics cut from your screenshots, which looks more designed and doesn't need re-recording when the UI changes. Avoid prompting a text-to-video model for the product shots: it will invent screens that aren't yours, as explained in can AI video show your real app UI. Maybe Labs turns a brief, your brand colors, and your uploaded screenshots into an on-brand motion-graphics video, with revisions in chat.
Step 6: Export per channel
- Landing page hero: 16:9, silent autoplay loop, 15–30 seconds.
- X and LinkedIn: 16:9 or 1:1 with burned-in captions; the first frame doubles as the thumbnail. See product video for LinkedIn.
- Product Hunt: a short gallery video with the result early. See the Product Hunt launch video guide.
- Shorts, Reels, TikTok: 9:16 with the product kept inside the vertical safe area. See the video aspect ratio guide.
Once it's live, the video does the most work where people decide whether to try the app. The first users guide for vibe-coded apps covers where to post it, and vibe coding launch videos covers launch-day formats.
Lovable app demo video FAQ
How long should a demo video for a vibe-coded app be?
30–45 seconds for a launch or landing-page demo. Long enough to show one job end to end, short enough to finish in a scrolling feed.
Should I record the Lovable editor or the deployed app?
The deployed app. Viewers care about what they'll use, not how it was built, and the editor adds clutter. Mention the build story in your post copy if it's part of the hook.
Do I need a voiceover?
No. Most social video autoplays muted, so on-screen captions carry the message. Add voiceover only if you'll post where sound is on, like YouTube.
Can AI generate the whole demo from a prompt?
A prompt-only video generator can't show your real screens. Use your own screenshots or recording as the source, then use AI for scripting, captions, and motion design.
Make your next launch in motion
Bring a brief, brand assets, and product captures. Review the story, visuals, and exported video before publishing. Request free private-beta access.
Get early access →