Documentation
Everything Demofy does, in the order you are likely to meet it. Start at the top if you have never made a demo; jump anywhere if you have.
Start here
What Demofy is, and what it is not
Demofy films a live web app into a narrated demo video from a URL and one line of intent, and can shoot the same demo again when the product changes.
Your first demo
Paste a URL, write one line about what to show, and press the button. No account, no card, nothing to install.
Reading the build log
Every phase of a render writes a line you can read while it happens — what each phase is doing and what its messages mean.
What you get back
A finished MP4, a poster frame, a caption track, a transcript and a written guide — which files exist, and when each one does not.
Making demos
The URL and the intent line
What Demofy does with the address you give it and the sentence beside it, and how the refiner rewrites a rough intent into a tight one.
Quality tiers
Standard, High and Ultra decide the resolution a demo is captured at. Standard is free and is the full pipeline.
Desktop and mobile capture
A demo can be recorded at a phone viewport and delivered as a portrait video. What changes, and what deliberately does not.
Recording behind a login
Save a browser session once and record demos of the signed-in product — either from a hosted browser or from a session file you export yourself.
Intros, outros and audio
Attach a stinger to either end of a demo, pick what happens at the seam, or replace the whole soundtrack with a track of your own.
The media library
One place for the stingers, audio tracks and logos you reuse across demos. Uploaded once, attached anywhere.
The kinds of job
A demo, a re-render, a refresh, an edit, an import and a scripted job each walk their own line through the same phases.
Editing and shipping
The step editor
Retype a beat’s narration, cut a beat out of the video, move the camera, mask a region, lay audio under a beat — then render a new version.
The look and the brand kit
The backdrop, framing and cursor a video is composited with, and the workspace defaults every new demo starts from.
Sharing and embedding
One link per demo, revocable in a click, and an iframe snippet that dies with it. What the link is, and what it is not.
Captions, transcripts and the written guide
Every narrated demo ships a caption track, a transcript in two formats and a Markdown walkthrough of the flow it filmed.
Version history
Every re-shoot, re-render and edit is a new video beside the old one. Nothing is overwritten and no shared link stops working.
Audience analytics
How far people got in a shared demo, and which beat was on screen when they stopped — counted in aggregate, with no viewer recorded at all.
Accounts and limits
Guests, accounts and signing up
There is no login wall anywhere. What a guest gets, what signing up adds, and why nothing you made as a guest is lost.
Daily limits and the in-flight cap
Two different bounds with two different jobs: how many demos a day, and how many at once. What counts, and what does not.
Workspaces and members
A video belongs to the workspace it was made in. Inviting people, what each role may do, and where your personal workspace fits.
Pro, and what a lapse takes
What Pro adds, why it is priced per workspace rather than per seat, and exactly what happens to your videos if you cancel.
How a saved login is stored
The highest-sensitivity thing Demofy ever holds, and the four mechanisms that hold it: sealed in the web process, never presigned, never plaintext in storage, destroyed after capture.
Deleting a video, a library or an account
Three destructive controls with three different blast radii, what each one really removes, and the one record that deliberately survives.
When a demo fails
The failures with a name — no usable flow, a changed element, a rejected login — what each one means, and what to do about it.