How to Edit Product Demo Videos with Claude

Editing a product demo means a lot of work. You need to find the take that explains a feature clearly, match it to the close-up that shows the action, and cut between the product and its software. A page can disappear from the frame just as the presenter explains how to feed it. A screen recording can leave the result before viewers have read it. You also need to add labels, time subtitles and balance sound, then keep them aligned through each revision.

Claude can help carry out that work when connected to a compatible video editor through MCP. The connection exposes editing controls, letting Claude search your recordings, arrange cuts, animate graphics, mix audio and export from an editable timeline. Conversation alone does not reliably carry out this editor workflow.

You can choose any editor with a compatible MCP connection. For this guide, we'll be using the free invideo Editor MCP, which gives Claude a professional-grade, frame-accurate multitrack timeline. Its full manual editing suite stays available, so you can choose cut frames, shape a zoom or adjust the mix yourself, then continue with Claude from the updated edit.

Ordinary editing through invideo MCP, including footage analysis, cuts, subtitles and audio cleanup, does not consume invideo credits. Claude’s subscription and usage allowance apply separately. Stock sourcing by the invideo agent uses invideo credits, as does generating new images, video or audio.

We’ll use an illustrative portable document-scanner demo for people who want to digitize paperwork at a small office. Imagine you have presenter takes, close-ups of feeding sample pages, a desktop recording of reviewing and adjusting the scans, and the resulting two-page PDF. The goal is a roughly two-minute, 16:9 video showing the path from paper to a usable file.

Connect Claude to the editing controls

Open invideo’s connection page and select Claude. In Claude on the web or in Claude Desktop, open Customize → Connectors → + Add → Add custom connector. Name it “invideo” and enter the server URL:

https://mcp.invideo.io/mcp

Complete the connection and sign in with your invideo account when prompted. Enable invideo for the editing conversation through the composer’s + menu and Connectors. For Team or Enterprise, an authorized owner or administrator must first add the connector for the organization; Claude’s current custom-connector instructions explain the account-specific route.

The Claude tab shows the MCP server URL and account sign-in step. Keep the Editor open alongside Claude to play and develop the edit.

The MCP overview explains how the assistant operates the Editor. Once connected, give Claude the project to work on and the recordings it should use.

Upload the recordings and give Claude your brief

Create a “Scanner Demo” project and upload the recordings directly to invideo Editor. This works while you use Claude on the web or Desktop. If you want Claude to import local files for you, use Claude Desktop and identify the destination project. For an existing edit, share its project link and timeline name instead.

Include the approved product notes, presenter takes, page-feed close-ups, desktop recording and final PDF. Record with sample paperwork so the demonstration can show the complete page. In this example, its mint header reads “SAMPLE INVOICE.” The desktop recording must show the same document that went through the scanner.

Give Claude the audience and intended result before asking it to edit:

Open [my project link] and read the uploaded material. We’re making a roughly two-minute, 16:9 portable-scanner demo for small-office owners. The recordings show feeding two sample pages, reviewing them in the desktop app, rotating and cropping a page, and saving a two-page PDF. Use “Scanner Demo v1” as the timeline. Use the presenter’s recorded explanation and approved product notes for factual statements. We want viewers to understand the paper-to-file process. Read the footage before making changes.

Illustration based on invideo Editor: the presenter takes, page-feed close-ups, desktop recording, saved-PDF demonstration and product notes are available in the media bin. The source preview shows the selected recording; the timeline remains empty before assembly.

Claude can find moments by spoken content or visual action, so you do not have to supply every source timestamp. Use that search to establish whether the material actually covers the demonstration:

Find the clearest complete take of each action: aligning and feeding a page, the matching scan appearing in the app, rotating and cropping it, saving the two-page PDF and opening the saved file. Return the clip and useful source range for each, plus any missing action. Compare the page header and layout between the physical footage, desktop preview and saved result. Leave the timeline unchanged for now.

Review the selections for the details that matter. A scanner sitting on a desk establishes the product; it does not show how the page enters. A PDF icon does not show whether both scanned pages made it into the file. If a necessary action is missing, record a pickup or adjust what the demo promises to show.

Assemble the paper-to-PDF sequence

Ask Claude to assemble the selected material into a clear action-to-result rough cut, so viewers can follow the demonstration without repeated takes and setup waiting.

Build “Scanner Demo v1” from the reviewed selections. Open briefly with the recorded saved PDF showing both page thumbnails, then return to the beginning: align and feed the pages, show the matching scans in the app, show the recorded rotate and crop adjustments, then save and open the final PDF. Choose complete presenter explanations. Remove false starts, duplicate explanations and idle setup waiting. Keep the page entry, the scan confirmation and the actions needed to understand each adjustment. If shortening a processing wait, make the jump in elapsed time clear. Use presenter dialogue as the main thread and mute the desktop recording’s scratch narration. Leave callouts and music for the next pass. Flag any gap in the recorded sequence.

Illustration: the paper-to-PDF sequence is assembled on V1 with presenter dialogue on A1. Labels, close-up overlays and music are added in later passes.

Play the assembly before adding styling. Check that the invoice header and page order match across the feed shot, app preview and final PDF. Keep the full adjustment visible when it is needed to understand the result. A cut that skips from the sideways page to a corrected page may hide the very control the demonstration is meant to explain.

For a separate product-footage example, Ai Titan’s Editor demonstration at 02:53 shows phone footage arranged as individual cuts on an editable timeline.

The base cut remains yours to shape. You can set the frame where the page reaches the slot, keep a presenter reaction or hold the final PDF longer. Claude reads the updated timeline before continuing. The rough-cut guide develops take selection and assembly in more detail.

Layer close-ups over the matching explanation

Once the sequence works, give the physical details more attention. Claude can find the recorded close-up and place it above the presenter while the explanation continues underneath.

On “Scanner Demo v1,” find our clearest page-feed close-up. Start it as the presenter explains aligning the page, show the hand placing it at the slot and the page beginning to feed, then return to the next demonstration when that action is clear. Put the close-up on a video layer above the presenter. Keep the fingers, page edges and feed slot visible. Preserve the dialogue, base-cut timing and all other selections. Mute the close-up’s source audio for this picture pass.

Illustration based on invideo Editor: the page-feed close-up sits on V2 above the presenter on V1, while the dialogue continues on A1. Labels and music have not been added in this pass.

For a separate layered-footage example, Chris Ajtony’s demonstration at 09:26 shows screen-recording inserts above presenter footage and dialogue in invideo Editor.

In this separate creator example, the screen recording covers the presenter picture while the dialogue remains on its own track.

Use your actual recordings for the feed mechanism and scanned result. Stock can establish a general office setting, while a generated illustration can explain an idea. Neither should stand in for this scanner’s recorded output. The Claude B-roll guide covers source search, stock and generated inserts as separate choices.

Add Zoom ins to keep the controls readable

Claude can create short zoom animations with the Editor’s editable scale and position keyframes. Specify the detail viewers need to read and the context that should stay visible.

In the desktop-review passage of “Scanner Demo v1,” begin with the full app view so viewers can locate the page thumbnails and adjustment controls. Add a smooth zoom-in when the presenter explains Rotate and Crop. Frame the active control and the page edge being adjusted, and hold the closer framing through the recorded adjustments. Return wider for saving the PDF, keeping its two page thumbnails and save confirmation readable. Preserve the recording’s proportions and dialogue timing. Keep the scale and position keyframes editable. Leave the physical demonstration and all other sections unchanged.

Illustration based on invideo Editor: the Program view zooms into the Crop control and adjacent page edge, with the cursor showing where the adjustment begins. The wider Source view preserves the full app context; scale, position and timing remain editable.

Play the screen passage at the size your audience will watch it. Keep the recorded cursor action visible rather than cutting straight to the result. You can use a still from the recording to hold a settled result while its explanation finishes, but keep the rotation, cropping and saving actions as moving footage. If the original text becomes soft when enlarged, record that passage more clearly. The Claude screen-recording guide develops readable framing and narration alignment.

Insert text labels that follow the actions

Use text to name a useful action or result. Claude can build separate text and shape layers, animate their entrance and exit with keyframes, and add dialogue subtitles. The wording, position and motion remain editable.

Add short section labels “Feed pages,” “Review scans” and “Save PDF” at their section openings on “Scanner Demo v1.” Use white text on a dark navy badge with a small mint accent. During the feed close-up, add “Align the page” in the empty upper-right space, clear of the fingers, page and slot. During the final result, add “Two-page PDF” beside the page thumbnails without covering them. Keep each label on its own editable text layer with a short fade in and out. Add readable dialogue subtitles, checking product names against the approved notes and keeping text clear of the app controls. Preserve picture and dialogue timing.

Illustration based on invideo Editor: the feed close-up sits above the presenter, with “Align the page” on a separate text layer. Dialogue, music and recorded feed sound have their own audio tracks.

Make precise revisions as needed

Suppose the physical demonstration now works, but the screen passage cuts away from the crop result too early and “Review scans” covers the Rotate control. Ask Claude to adjust the timing and label placement while preserving the approved sections.

Give Claude the timestamps from the current edit and specify what should change:

On “Scanner Demo v1,” revise only 01:02–01:14, where the presenter explains rotating and cropping the sample invoice. Keep the recorded rotation and crop action as moving footage, then hold the settled page until the explanation ends. Move “Review scans” into empty space outside the adjustment controls. Keep the passage duration and the Save PDF section start unchanged. Preserve the feed sequence, dialogue wording and timing, subtitle style, music and all other labels. If the source cannot show the full action within this range, report that before changing the surrounding timing.

Illustration: this instruction changes the screen hold and label placement while preserving the passage duration, narration and approved sections.

Play from before the adjustment through the start of saving. The page should stay visible through the explanation, the label should clear the controls and the next instruction should still arrive at the right moment. You can choose the exact hold or label position yourself and continue with Claude from that choice.

If the revision instead removes content, say so explicitly:

Remove the duplicate explanation before “Review scans.” Keep the first complete explanation and all demonstrated actions. Close the gap and move the later footage, labels, subtitles and audio cues together, preserving their relative timing and the approved crop treatment. Return the new section times.

After a timing change, use the updated timestamps for further feedback. The video-feedback guide explains how to target revisions across editable layers.

Review the complete demo and export an MP4

Watch the video with picture, text and sound together. Can viewers follow the page from the feed shot into the app and the saved PDF? Are both pages included? Are the recorded adjustments legible? Check every product statement against the supplied notes and footage. A shortened processing wait should not suggest a measured scanning time.

When the edit is ready, name the exact timeline and output for Claude to export:

Export the approved “Scanner Demo v1” timeline as a finished 16:9 H.264 MP4. Preserve the current picture, dialogue, labels, subtitles and sound mix. Keep the editable timeline available for future revisions.

Choose H.264 MP4 for the finished demo. Editable-project export serves a separate handoff to another editor.

You can export manually too. Open the rendered video before sharing it and check the app text, sound, revised passage and ending. To continue in Premiere Pro, Final Cut Pro or DaVinci Resolve, request an editable-project export for that destination separately.

This workflow is useful when you have product recordings and want help with selection, repeated cutting, close-up placement and finishing while keeping creative control over the same timeline. For the broader connection-to-export process, see the complete guide to editing videos with Claude.

Frequently asked questions

Can Claude edit a recorded product demo?

Yes, with a compatible video editor connected through MCP for this timeline workflow. In invideo Editor, Claude can inspect the recordings, assemble cuts, add close-ups and graphics, finish audio and export. The connected editor provides the controls it operates.

Do I need to find every feature shot myself?

No. Describe the action or spoken explanation, and Claude can search the footage in the connected project. Review its selected range to confirm that it contains the useful action and matching result.

Can I use Claude on the web, or do I need Desktop?

You can connect and edit with Claude on the web or Desktop. Upload recordings directly to invideo Editor when using either. If you want Claude to import local files for you, use Claude Desktop.

What if I have no recording of a feature?

You can use invideo’s generation capabilities to create a clearly illustrative explanation grounded in your approved product notes, then ask Claude to add it while preserving the surrounding edit. Actual footage is the stronger choice for the mechanism and observed result, so record a pickup when possible. Generation uses invideo credits.

Does editing the demo use invideo credits?

Ordinary MCP editing, including footage analysis, cuts, subtitles and audio cleanup, does not consume invideo credits. Claude’s subscription and allowance apply separately. Stock sourcing by the invideo agent uses credits, as does generating images, video or audio.

Can I continue editing manually after Claude works on it?

Yes. The full professional editing suite remains available on the same timeline, including cuts, layers, keyframes, color and audio. Claude reads your manual changes before continuing. If you start a new conversation, bring the project link and a handover of the brief, approved choices and next task.