Short answer: to download product walkthrough videos from SaaS websites, save software tutorial videos for offline reference, or keep an AI generated explainer video from a website, treat it as citation work: play the video, capture the media the page requested, and store the file with its page URL, product version and date. These clips are usually plain MP4 or simple HLS on a documentation CDN, which makes them technically easy — and they are usually removed without notice, which makes them urgent.
Where this video usually lives
| Placement | Typical delivery | Note |
|---|---|---|
| Marketing hero video on a product page | Muted, autoplaying <video> with a direct MP4 or WebM | Frequently the easiest fetch on the whole site |
| Interactive product tour | Short clips per step, or a single walkthrough file | Each step may be its own asset; walk the tour before analysing |
| In-app dashboard preview | Token-gated media behind login | Capture from your own session — login-required downloads |
| Documentation embed | CDN file, or an unlabelled background video without controls | Right-click may be absent; the network log still shows it |
| AI-generated explainer or overview | Generated asset served to a preview player, sometimes blob-backed | Use the tool’s own download if present — AI output workflow |
| Launch or webinar-style recording | Platform embed or a simple HLS setup | Check the licence: marketing footage is owned footage |
The workflow
Get the video to play, then look at what was fetched
Open the Network panel filtered to media, and trigger the real video rather than its poster: click play, advance the tour, or expand the docs embed. Generated explainers sometimes need the tool to finish rendering before the asset URL exists.
Take the highest version that is offered
Docs clips are often delivered at one rung; product pages occasionally offer a smaller autoplay plus a higher-resolution file. Choose deliberately (quality rules).
Record what the clip is, while you still know
Store alongside the file: page URL, product name and version, the page title, retrieval date, and one line on why you kept it. Six months later “demo-v3.mp4” tells nobody anything; “Acme analytics 2.4 onboarding walkthrough, captured 2026-10, internal evaluation” is a usable record.
If the clip is inside an AI tool, settle rights first
Generated explainers and overviews are your output under the tool’s terms — check whether your plan permits the reuse you intend. Where the tool has a download button, use it: the exported file is the intended artefact, with correct audio and no preview cap.
Three cases people ask about specifically
“Download NotebookLM video overview.” Tools in this family generate a media artefact inside a web app and expose it through a preview player. From our network today we could not open the product to verify its current export options, so treat this as the general AI-output case: check for a download or share control in the product, and if the only surface is a player, capture the media your session requested (blob case). If a service offers no file to you, that is its decision.
“Save a video embedded in an AI tool documentation page.” Usually the simplest job here: docs hosts put clips on a CDN as plain files. If the element is a background loop, it may have no context menu — the request log does.
“Download public demo videos from an AI startup website.” Also straightforward technically. “Public” describes access, not licence: launch films, customer demos and marketing edits are owned work, and keeping a copy for evaluation differs from republishing them.
Why these clips vanish
Documentation and marketing video is the least protected content on most sites. It has no retention promise, it is not in the product’s data export, and rebrands and redesigns delete assets silently. So if a clip is evidence for something — a comparison you are preparing, a feature you are documenting, a claim a vendor made — capture it at the moment it matters, with the page URL and date. This is the same discipline as research video references, applied to commercial pages.
For teams: a small convention beats a tool
- One shared folder per evaluated product, with dated subfolders.
- Filename pattern:
product-version-topic-YYYY-MM.mp4. - A sidecar or index row with URL, retrieval date, and the purpose (evaluation, regression evidence, training).
- An agreed line on use: internal reference by default, publication only with permission.
That is enough structure that the archive is still legible when the person who captured it has moved on — which is the actual failure mode of team video libraries.
FAQ
How do I save an AI-generated explainer video from a website?
Use the tool’s download or export control where it exists; otherwise capture the media your own session requested. Rights depend on your plan’s terms, not on the capture method.
Can I download product walkthrough videos from SaaS sites?
Usually yes — they are plain files or simple HLS on a docs CDN. Keep the page URL and product version with the clip.
The demo video has no right-click option. Now what?
It is likely a background loop without controls; the file still appears in the network log while playing.
Is a public demo clip free to reuse?
No. Public means viewable. Launch films and customer demos are owned footage; keep internal and ask before publishing.
Where do I find a NotebookLM-style generated video?
In the product’s own download or share control if it has one. We could not verify that product's options from our network today, so check in-app rather than trusting an article.
How should a team store these clips?
Dated folders, a product-version-topic filename, and an index row with URL and purpose — structure is what keeps it usable.