Everything you need to ship your first demo.

Getting started

Perfect Demo turns one rough screen recording into a finished demo video. The whole flow is four steps, and you only do the first one.

1. 1

   Record

   Walk through your product exactly as you would for a colleague. Mistakes, pauses, and stray clicks are fine — you are not performing, you are showing.

2. 2

   AI analyzes

   Perfect Demo watches the recording, finds the glitches, dead air, and fumbled moments, and works out which parts of the screen actually matter.

3. 3

   Script & voice

   Your walkthrough is transcribed, rewritten for clarity, and narrated in a studio-quality voice — no microphone or quiet room required.

4. 4

   Perfect output

   You get a polished demo video back: clean cuts, smooth cursor paths, zooms on the key actions, ready to share.

Recording your demo

The raw recording is the only input the AI has, so it is worth getting right — but "right" is a lot looser than you would expect.

• Say what you are doing as you do it. The AI rewrites the words, but it needs your intent to work from.

• Do not restart when you slip. A stumble costs you nothing — the cleanup pass removes it.

• Move at a natural pace. There is no need to exaggerate slow, careful mouse movement.

• Keep the walkthrough inside your per-recording limit. Longer flows are better split into a few focused demos.

What the AI does

Every recording runs through the same pipeline. This is the work you would otherwise be doing by hand in an editor.

Reviewing & sharing

When the pipeline finishes you get a polished demo video back. Watch it through, and if something is off, regenerate it rather than reaching for an editor — the point is that the raw recording stays the only thing you ever have to redo.

One recording can produce more than one asset: the same walkthrough backs your product demo, a sales walkthrough, an onboarding guide, or a release note.

Plans & limits

Plans differ on two things: how many recording minutes you get each month, and how long any single recording can be.

Yearly billing takes 20% off every paid plan. See full pricing

API access

The import flow and the entire AI pipeline are available as an authenticated HTTP API — the same one the app itself runs on. There is no single "video in, video out" call; you drive a demo through four steps.

How the flow works

1. 1

   Import a video

   POST /api/demos/import-local

   Upload an MP4 as multipart form data, or register a file already pushed to storage via a presigned PUT. Creates the demo and charges recording minutes at import (1 credit = 1 minute, rounded up). MP4 only, up to 1 GB and 60 minutes.

2. 2

   Run the AI pipeline

   POST /api/demos/:id/process

   Queues the full pipeline: transcription, storyboard, narration, retiming, zooms, render, QA. Checkpointed — re-posting a failed demo resumes from the last completed stage instead of starting over.

3. 3

   Watch progress

   GET /api/demos/:id/progress

   Poll this for a snapshot of the current stage, or hold open /progress/stream for Server-Sent Events — one event per pipeline stage transition.

4. 4

   Fetch the result

   GET /api/demos/:id

   Returns the demo record, including status and finalVideoUrl once the render completes. The video file itself is served through the app's /api/uploads/… paths.

How to authenticate

Every endpoint requires authentication: either the app's session cookie (browser flows) or an Authorization: Bearer <access-token> header — the same mechanism the Chrome extension uses. There is no API-key scheme yet, demos can only be processed by their owner, and the import and process endpoints are strictly rate limited. Recording minutes are charged once at import and reprocessing never re-charges.

Example

# 1. Import a recording (returns demoId)
curl -X POST "$APP_URL/api/demos/import-local" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -F [email protected] \
  -F title="Onboarding demo" \
  -F duration=213

# 2. Run the AI pipeline on it
curl -X POST "$APP_URL/api/demos/$DEMO_ID/process" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

# 3. Follow progress (SSE)
curl -N "$APP_URL/api/demos/$DEMO_ID/progress/stream" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

Supporting endpoints

FAQ