What can the video editor actually do to my recording?

Give the team a raw recording and it produces a clean, tightened cut without you touching a timeline. It cuts the ums, filler words and false starts, picks the best take when you said a line more than once, closes the dead air, and adds gentle zoom-ins so it never feels static. It does the same for screen recordings and camera talking-heads. You ask for it in plain words, or record with automatic editing on, and the finished cut appears in Versions.

What it removes and tightens

• Ums and filler. The "um", "uh", "you know", "like", "so" and "basically" that pepper natural speech.
• False starts. The half-sentence you abandoned and began again.
• Stutters and repeats. A stumbled or doubled phrase, kept once and cleanly.
• The best take. When you recorded a line several times to get it right, it keeps the best one and drops the rest. You do not have to mark which was which.
• Dead air. The long pauses and silences between sentences, tightened so the video moves without sounding rushed.

It works from a word-accurate transcript of what you actually said, so it cuts between words and never chops a word in half. It does not rewrite you or put words in your mouth.

What it adds, sparingly

• Punch-ins. Gentle zoom-ins on a cut, which hide the join and keep the eye moving. These are always on.
• Graphics. Titles, lower-thirds and simple charts, but only where one genuinely helps. A plain talking-head often gets very few, by design.
• B-roll and photos. A supporting clip or image to illustrate a point, credited to its source.
• Music and sound. A bed or the odd effect where it suits, with the credit line you need to paste when you publish.

How much of this you get depends on the edit scope you picked. A quick edit is the clean cut and nothing else. The full treatment brings in the extras. See How do I record footage for a video? for choosing the scope.

Screen recordings work too

If your footage is a screen recording or a demo, the team edits it the same hands-off way, with a few things tuned for screens: it trims your narration without making the cursor jump, holds the picture steady across a cut in the audio, and punches in on the part of the screen you are talking about. Record with screen or window as the source and, if you like, add a camera bubble of yourself. See How do I record footage for a video?.

Where you can see its decisions

Open the Cut tab on a project. It is a read-only view of what the team decided, and it fills in as the team works.

• Mistake map. Every stumble it found, with a timestamp, a type (retake, stutter, filler, false start), what was said, and whether it cut it or kept it.
• Keep-ranges. The exact stretches of your recording that made the final cut.
• Transcript. The full word-accurate transcript it worked from.

How do I ask for it?

Two ways, and you can mix them.

• Record with automatic editing on, and the cut happens the moment you stop. See How do I record footage for a video?.
• Open the project and click Run team, optionally with a note like "keep it under 60 seconds" or "no music". See How do I run the video team?.

How do I know it worked?

A render appears in the Versions tab with a quality-check pass, and the Cut tab shows the mistake map and keep-ranges the team used to make it.

Common problems

"It kept an um I wanted gone, or cut something I wanted kept." Tell it. Run the team again with a note in the Run team box, for example "there is still an um around the 20 second mark". The Cut tab shows you what it decided so you can be specific.

"I wanted graphics and there are none." On a quick edit scope the team makes no graphics at all. Choose Standard or Full, or ask for them. Even then, it only adds graphics that earn their place.

"It feels too fast, or too slow." Say so in the Run team note or the Brief style field, and run it again.