A Claude Workflow for Editing Screen Recordings into Tutorials

October 12, 2026

Illustration of a Claude-directed screen tutorial with readable pivot settings and editable screen, title and narration layers

Claude can edit screen recordings into tutorials when connected to a compatible video editor through MCP. This guide uses the free invideo Editor MCP connection to show you how to assemble the steps, make interface details readable, add editable callouts and align the demonstration with narration. Refine the same timeline through feedback or the full manual editing suite, then export the tutorial.

A screen recording can contain the right demonstration and still take a lot of editing to become a useful tutorial. That means cutting repeated explanations and waiting, framing small controls clearly, and timing the demonstration to the narration. When the narration changes, the close-up, callout and subtitle may all need new timing.

Claude can help with the editing, but it needs a video editor to make changes to your footage. Connecting a compatible editor through MCP gives Claude access to its controls, so it can find the relevant screen actions, build the sequence, adjust framing and time graphics and audio from your instructions.

You can use any editor that supports a compatible MCP connection. For this tutorial, we'll be using the free invideo Editor: its MCP connection lets Claude work on a professional-grade, frame-accurate multitrack timeline, while its full manual editing suite gives you control over every cut, layer, animation and audio adjustment. You can make changes yourself and continue with Claude from the updated edit.

Ordinary editing through invideo MCP does not consume invideo credits. Claude’s subscription and usage allowance apply separately. Generating new images, video or audio uses invideo credits.

Today, we’ll use an illustrative Google Sheets tutorial for a small shop’s operations assistant as an example: The source is an eleven-minute screen recording with a wrong aggregation choice, a repeated filter demonstration and some waiting. A separate finished voiceover explains the successful procedure in about four minutes. The desired video shows the source range, the pivot-table setup, the Paid filter and the resulting totals. The prompts below use this worked example; adapt them to your own recordings.

Connect Claude to the editing controls

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

Complete the connection, sign in with your invideo account when prompted and enable invideo in the conversation you will use for editing. An organization owner must add the connector first for Team or Enterprise accounts. Claude’s custom-connector guide covers the current account-specific route.

Current Claude setup instructions on invideo’s connection page

The Claude tab shows the custom-connector route, server URL and invideo sign-in step.

Keep the Editor open beside Claude so you can play the timeline and make manual adjustments as the edit develops. The MCP overview explains how the external assistant operates the Editor.

Bring in the screen capture and establish the lesson

Create an “Orders Summary Tutorial” project in invideo Editor. Upload your screen recording and finished voiceover directly to the Editor, then give Claude the project link. You can do this while using Claude on the web or Desktop. If you want Claude to import local files for you, use Claude Desktop and identify the destination project.

Illustrated Claude Desktop import prompt with two attached tutorial files

Illustration: the two files go into the named project. Importing them is separate from asking Claude to edit them.

Before execution, explain what viewers should learn and which audio to use:

Read the project at [my project link]. We’re making a roughly four-minute, 16:9 Google Sheets tutorial for a shop assistant learning pivot tables. “Orders walkthrough.mp4” is an eleven-minute screen recording; “Final narration.wav” is the finished explanation and our timing reference. The lesson is to select the Orders data with its headers, create a pivot table on a new sheet, use Product for Rows and Revenue for Values summarized by SUM, then filter Status to Paid and read the totals. Use “Orders Summary v1” as the editing timeline. Use the recorded interface and results, and mute the screen capture’s scratch narration. Read the material before making changes.

Use sample orders when recording, so the tutorial can show the complete table without exposing customer details. Google’s pivot-table instructions and filtering guide are useful checks for the software procedure. A sheet filter and a pivot-table filter serve different purposes: this example selects Paid inside the pivot editor’s Status filter.

Assemble the base cut

Claude can find the relevant actions in your screen recording with the Editor’s footage search and arrange them into a base cut. Give it the steps to include, the repetition and waits to remove, and the voiceover to follow:

Create a first cut of “Orders Summary v1” using the screen recording and finished voiceover. Show the tutorial steps in order: select the data, create the pivot table, set Product as Rows and Revenue as SUM, filter for Paid orders, then show the totals. Remove mistakes, repeated demonstrations and long pauses. Keep the clicks and menu selections viewers need to follow each step. Use the voiceover to guide the sequence and keep its wording and speed unchanged.

Claude can assemble the recorded steps into a first cut. Review it before adding zoom-ins or callouts, checking that each action and its result are included.

Davinci tutorial clips on an editable invideo Editor timeline

In Davinci’s demonstration at 5:32, screen-recording selections are arranged on an editable tutorial timeline.

Play the base cut and check that the steps appear in order, the menus are easy to follow and the result stays visible long enough to read. Ask Claude to restore a missing action or adjust a cut where needed. For more on trimming repetition, see our guide to removing retakes and pauses.

You can also trim clips or adjust their timing directly in the Editor, then continue with Claude from the updated timeline.

Add zoom-ins on interface details

Claude can build zoom animations using the Editor’s position and scale keyframes. Ask it to zoom in when a small control needs attention, hold the close-up during the explanation, then return to the wider view. You can adjust the framing, timing and animation manually or ask Claude to refine them.

In the pivot-configuration passage on “Orders Summary v1,” begin wide enough to show the new sheet and pivot editor. Move closer when Revenue is added to Values, keeping its field name and “Summarize by: SUM” readable. Hold that view through the explanation, then return to a framing that shows the product rows and their totals. In the Status-filter passage, keep the selected Paid value and confirmation visible before returning to the updated summary. Preserve proportions, narration and the rest of the edit. Use restrained position and scale keyframes rather than chasing the cursor.

Check the preview at the size viewers will actually watch. If the letters are soft, use a clearer recording of that action. Enlarging a screen capture cannot restore detail the original did not capture.

Insert animated text callouts that explain the choice

Claude can build editable text and shapes and time their entrance and exit through the Editor’s keyframe animation controls. For this tutorial, the most useful callout explains the aggregation: the viewer wants revenue totals, so SUM matters.

In the Revenue setup passage, add a “Sum revenue” callout in empty space beside the pivot editor, with a thin outline around the recorded SUM control. Fade both in as the narrator explains aggregation and remove them before the filter step. Add short section labels “Choose data,” “Build summary” and “Show paid orders” at their respective openings. Keep text and outlines on separate editable layers. Preserve the screen and narration timing, and leave the menu text, dropdowns and table unobstructed.

Reference-based invideo Editor illustration with source and preview viewers, animated Sum revenue text on V3, SUM outline on V2, screen clips on V1 and narration on A1

Reference-based illustration: “Sum revenue” and its outline have their own layers above the screen recording. The recorded SUM setting remains visible; the graphic points to it.

Make the first callout work before applying the same treatment elsewhere. You can refine its position, readable hold or keyframes yourself, then ask Claude to carry that styling into the Status callout while keeping each element’s wording and individual timing.

Align the screen recording with the voiceover

Align the screen recording with your finished voiceover. Ask it to keep each control and result visible while the narrator explains it, adjusting the screen clips without changing the narration.

On “Orders Summary v1,” match the screen clips to the finished voiceover. Show the SUM selection as it is explained, then keep that setting visible until the sentence ends. Do the same for the Paid filter and its result. If a completed screen needs more time, use a still from our recording to hold it. Keep clicks, typing and menu selections as moving footage. Preserve the narration’s wording and speed.

Use still holds after an action is complete. Keep the selection itself as moving footage so viewers can follow the procedure. Play the sequence to check that the next screen appears with the next instruction.

Screen selections and a snapshot above a separate narration track

Screen clips and still holds sit above a separate narration track in Make it Simple’s tutorial example.

Give feedback on a specific moment

Give precise instructions to revise one moment without affecting other aspects of the edit.

For example, the screen might leave the SUM setting before its explanation ends, while the callout overlaps the next control. Ask Claude to adjust that passage’s timing and label placement. Use the timestamps from your current edit; the range in this illustration is an example:

Complete illustrative Claude feedback targeting the SUM passage

Illustration: the feedback targets the SUM passage at 01:36–01:48 while preserving the narration, other tutorial steps and later section starts.

Play the revised passage with a few seconds before and after it. Check that the setting stays visible through its explanation, the callout clears the controls and the following step starts at the right point.

You can choose the exact hold length or label position manually, then continue with Claude from the updated timeline. For more examples, see giving video feedback to Claude or ChatGPT.

Review and export the finished tutorial

Play the tutorial from start to finish. Check that viewers can follow each step, read the controls and see the result while it is explained. Listen for doubled narration or abrupt audio joins, and check that callouts do not cover the actions.

Before exporting, ask Claude to add readable subtitles clear of the pivot panel and totals, checking Product, Revenue, SUM and Paid against your script. It can also balance the narration and reduce distracting room noise while preserving the screen timing. Review the text and sound together in playback.

If the tutorial is for YouTube, ask Claude to add chapter markers and return a matching timestamped list. Use the final timeline so the chapter times match the finished edit.

Once you’re happy with the edit, ask Claude to export the finished tutorial as an H.264 MP4:

Export “Orders Summary v1” as a finished 16:9 H.264 MP4. Keep the current screen edit, voiceover, subtitles and callouts.

invideo Editor H.264 MP4 video export settings with entire timeline, resolution, frame rate, quality and loudness controls

Choose H.264 MP4 for the finished tutorial. The editable-project options serve a separate handoff to another editor.

You can also export manually. To continue in Premiere Pro, Final Cut Pro or DaVinci Resolve, request an editable-project export separately. Open the rendered video before sharing it and check the interface text, sound, revised passages and ending.

This workflow helps tutorial creators delegate the repeated cutting, framing and timing work while directing how the lesson is taught. For the broader process, see editing videos with Claude.

Frequently asked questions

Can Claude turn my screen recording into a tutorial?

Claude needs a compatible video editor connected through MCP to turn your screen recording into a tutorial. The conversation provides the instructions; the connected editor provides the tools for cuts, framing, layers, audio and export.

Is editing videos with Claude free?

Yes. invideo Editor’s editing tools are free to use through MCP. Your requests count toward your Claude usage allowance, and any Claude subscription costs are separate. Generating images, video or audio uses invideo credits.

Can I use narration recorded separately from the screen capture?

Yes. Upload both files, identify the finished narration as the timing reference and ask Claude to arrange the screen actions around it. Use still holds on settled screens when the explanation needs more time, then check the alignment in playback.

Do I need to provide timestamps for every tutorial step?

No. Describe the steps you want to include, and Claude can search your recording for the matching actions. When revising a specific moment, give a timestamp from the current edit and describe what should change.

Can I keep editing manually after Claude makes the cut?

Yes. Clips, graphics, keyframes, subtitles and audio remain editable on the same timeline. You can adjust them manually and continue directing Claude from the updated project. Ask for an alternate timeline first if you want to compare a different treatment while preserving the current version.

Generate AI summary
Share