How to Make a Product Demo Video From a Website: A Practical Guide

We made a 47-second launch film from our website and four app screens. That example shows why a short product story can use both public pages and real product evidence—and why the method matters when a workflow is behind a login (our recording guide).

To make a product demo video from a website, choose whether you need a branded video based on public pages, an AI agent to navigate a live workflow, or a recording of real product screens. Pick one audience and outcome, prepare the pages or test account, capture only the steps that prove the outcome, then add a clear call to action and frame the export for its destination.

The right choice affects more than the footage: it determines whether viewers see a visual interpretation of your site or evidence of the actual product. It also affects cost. A 30-second Vuela demo uses 235 credits, while our product videos cost no credits on any plan; those are different workflows, so compare what each output actually shows.

Choose the right way to turn a website into a demo video

A product demo video maker can create a branded piece from a URL, but a URL-based video is not automatically a recording of someone completing a task in your app. Decide whether the video needs to introduce the product, show a live workflow, or prove a precise screen state before choosing a tool.

Kario AI sits between URL input and editable visual output: it says it reads and screenshots a site, animates real layers, and can rebuild uploaded app screenshots as animated layers. Its pricing page does not state whether website capture navigates live pages or how it handles login-gated flows. That distinction matters if the proof depends on a live interaction rather than an animated representation.

Start with one audience, problem, and product outcome

A SaaS product demo video should make one result easy to recognize, not show every menu. Write a one-line brief: “For [audience], [problem] gets in the way of [job]; the product helps them [visible outcome].” Then confirm that the outcome appears on screen, rather than relying on a claim such as “work faster.”

For example, a support platform might show an agent opening a customer issue, assigning it to a teammate, and ending on the updated owner and status. That is a short, observable result; a full tour of reporting, settings, and account administration would compete with it. Storyship’s guidance also emphasizes choosing one user outcome and preparing demo data before capture.

Use the same brief whether you make a product demo video from a website URL, ask an agent to navigate, or record manually. Include the intended viewer and the final screen in the instruction. “Show how a support agent assigns an issue and confirms the new owner” is more actionable than “make a video about our support platform.”

Prepare the website, product flow, and demo account

Open the URL in a private browser window and test the exact pages you plan to use. Check that the product page loads, cookie banners do not cover important content, and the relevant screens are available. If the core feature sits behind a login, prepare a test account or screenshots rather than assuming a URL-only tool can reach it.

Use realistic sample data that supports the story: a sample issue with a clear status, for instance, rather than an empty workspace. Avoid exposing actual customer records, private messages, billing information, or admin controls. A dedicated test account also reduces the chance that notifications or unrelated production data appear in a recording.

Agent-led capture has its own failure points. CAPTCHA, two-factor authentication, or automation blocks can interrupt a route, so test the exact sequence before planning the final cut. For screenshots that are not on a public page, Vuela says users can upload app screenshots and describe what to show; its product demo page does not say that the maker supports login-gated flows. The same page does not specify caption support or direct editing controls, so plan those needs around the features it does publish.

Write a short demo script that shows the result

Build the script around a hook, three to five product actions, the visible result, and a call to action. Keep the actions in the order a viewer would perform them. For a task-assignment demo, that might be: show an unassigned issue, open its owner field, select a teammate, save, then hold on the issue with its new owner visible.

Use a format-specific duration rather than treating 30–60 seconds as a universal rule. We list a walkthrough at about 30 seconds, a launch film at about 35 seconds, a vertical teaser at about 25 seconds, and a square ad at about 18 seconds (Velos formats). Vuela’s credit example is a 30-second demo; that is a pricing reference, not a requirement for every product story.

Close with one CTA that matches the placement: “Explore the workflow” on a landing page, or “Try the feature” in a social post. Keep it specific enough for viewers to know what to do next. If the video is for a landing page, the CTA can lead to a trial or product page; for a social media product demo video, it can point to one next step rather than a list of links.

Create the video from a URL or capture real screens

For URL-based generation, enter the public page and describe the intended story: which audience, product action, and result should appear. Vuela’s published workflow is to paste a URL and brief, choose a look and format, optionally select a narrator, then download an MP4. We take a website or product-page link, read the screens and brand elements, and create a first cut with music and a voice. Our homepage says the first cut takes about four minutes (Velos).

When the proof depends on a particular in-product sequence, capture the real workflow. Start from the first screen, follow the shortest route to the result, and pause after a meaningful change so viewers can read it. A Chrome Extension or another screen recorder can work for this; keep the cursor deliberate and remove unrelated clicks during editing.

Our 47-second launch film used the website and four app screens, a useful example of combining public context with real product evidence rather than expecting a single URL to tell the entire story. We also let users sign in or upload screenshots to show screens behind a login. That is one option for supplying the missing product evidence, not a reason to assume every URL-based maker can access private flows.

Frame the demo for its destination

Choose the aspect ratio around where people will watch. Use 9:16 for Reels, TikTok, Shorts, and Stories; 16:9 for a landing-page embed or YouTube; and 1:1 for a square feed placement. We also support 4:5, alongside 16:9, 9:16, and 1:1, from one video (Velos formats).

A vertical crop can make a dense desktop interface unreadable. If the proof sits in a wide table or several side-by-side panels, frame one panel or action for 9:16 instead of shrinking the whole interface. Keep the text and result large enough to read on a phone, then watch the exported file in the placement where it will appear.

Add branding, narration, captions, and music

Use the logo, colours, and type consistently, but keep them away from controls and product text that carry the proof. We read a website’s colours, fonts, and logo for branding; our product videos include a voice and music, and music can be composed for the video or chosen from four moods (Velos).

Narration should explain why an action matters while the relevant screen is visible. Captions help when social viewers watch without sound, but position them so they do not cover a button, chart, or final state. We offer six voice options and word-by-word captions. Vuela’s product demo page does not specify captions or an editing interface, so teams that require those controls should account for that in their choice.

Compare the cost of a website demo workflow

Compare the priced output and how you will use it, not just the headline amount. Velos lists product videos at no credit cost on every plan; its credits apply to other outputs such as director’s cuts, UGC ads, and product photo sets. A director’s cut costs 20 credits, a UGC ad 150 credits, and a product photo set 5 credits (Velos pricing).

Vuela says a 30-second demo uses 235 credits, about €4 on the Lite plan; voiceover adds 15 credits. Kario also offers Creator at $39 / month with 230 credits and about 2 finished videos a month, revisions included. Its Studio page describes a brand-specific pipeline, finished videos in 48 hours, and unlimited changes, but gives no price. These are different credit systems and output types, so the monthly totals do not represent identical deliverables.

Review, revise, and export the finished demo

Check the export against the actual product before publishing. Confirm that the right control is clicked, the resulting screen is accurate, the action stays visible long enough to understand, and the CTA is readable. Watch the final file at phone size for a vertical post and at its real landing-page size for a website demo video.

Use this checklist:

• Screen accuracy: Does each screen show the product state the script promises?
• Crop and legibility: Can viewers read the key label and see the result in the intended ratio?
• Pacing and audio: Are actions clear, narration understandable, and music appropriate to the voice?
• Captions and CTA: Are captions timed and positioned correctly, and does the final instruction fit the destination?
• Privacy: Are sample records used, with customer details and internal controls out of frame?

When a line or scene misses, make the revision precise. We let people request edits in plain language or click a word to rewrite it; that can help fix a line such as “Show pricing” without rebuilding the whole story. Export the intended ratio and review that file, not just the editor preview.

Choose a workflow that matches your product and launch goal

Choose public-URL generation when the public site already explains the value and speed matters. Choose agent-led navigation for a workflow the agent can reach and complete. Record real screens when the exact authenticated interface or result is the evidence viewers need. That distinction makes the choice more useful than selecting a tool by the word “AI” alone.

For a landing page, a 16:9 launch film can establish the product story; a vertical teaser or square ad can serve social placements. We also make UGC ads from a product link using a creator’s script, voice, and real product imagery. For ongoing social publishing, Autopilot plans a week of posts from a website, creates videos and photos, and publishes them; each post requires approval until the account allows autonomous posting.

If you are comparing costs for recurring output, a team producing two Vuela demos can plan around 2 × 235 = 470 credits, while a three-demo month is 3 × 235 = 705 credits. With Velos, the product videos themselves use no credits across plans, while the plan price and credit allowance matter for add-ons such as director’s cuts and UGC ads. Choose based on the product evidence you need, the number of assets you plan to make, and where viewers will see them.

Frequently asked questions

How do you make a product demo video from a website URL?

Enter a public product page, give the tool a focused outcome and audience, select a format, and review the result against the real product. If a key workflow is not shown publicly, use a supported method such as uploaded screenshots or a recording of the actual screen rather than assuming the URL reveals it.

What should a product demo video show?

Show one audience, one problem, the shortest set of actions that proves the product outcome, and a clear CTA. A focused task such as assigning an issue and showing its updated owner gives viewers more evidence than a tour of unrelated menus.

Can an AI tool record a product demo behind a login?

It depends on the tool and its stated workflow. We support signing in or uploading screenshots to show login-gated screens. Vuela’s product demo page describes public website screenshots and uploaded app screenshots but does not say the maker supports login-gated flows; Kario’s pricing page does not state how its URL capture handles them.

How long should a SaaS product demo video be?

Use the time needed to make the result clear, then cut anything that does not support it. Our listed examples range from an approximately 18-second square ad and 25-second vertical teaser to a 30-second walkthrough and 35-second launch film.

Which video format should I use for social media versus a landing page?

Use 9:16 for vertical social placements such as Reels and TikTok, and 16:9 for a landing-page video or YouTube. Square 1:1 and portrait 4:5 can suit feed placements; reframe dense desktop screens so the important interface remains readable.