How to crop a screen recording to vertical and keep the text readable

Last updated 2026-08-30 · 7 min read

What is the short version?

A screen recording is mostly interface, and the part worth showing is usually a narrow column of text inside it. Cropping to vertical is an opportunity rather than a compromise, provided the crop is chosen from what is actually legible.

1. Go to Vizard Agent and upload the recording.
2. Say to crop to vertical and keep the on-screen text readable.
3. Say whether the silent or slow parts should be trimmed.

What do you need before you start?

The recording and a sense of what actually matters in it. Vizard Agent works out the crop from the frames themselves, but knowing whether the point is the document, the sidebar or the cursor changes which region it protects and which it is free to discard.

• The recording. As captured.
• The subject. Which part of the screen matters.
• The trimming. Whether pauses should go.
• The frame. Vertical, usually 1080 by 1920.
• The audio. Whether there is any worth keeping.

What do you type into Vizard Agent?

Say the crop and the legibility requirement together. Vizard Agent otherwise centres the crop, which is the reasonable default and is usually wrong for a screen recording, because the content people care about rarely sits in the middle of a desktop.

Prompt

Variants worth knowing:

• Chrome excluded. Dropping the browser bars so the content is bigger.
• A left-weighted crop. So lines of text start complete.
• Slow parts trimmed. Scrolling compressed, reading held.

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real screen recording. The decision at the seventeenth step is the useful one: it tested a crop that cut out the browser toolbar and the taskbar entirely, which let the document fill more of the frame.

1. Checks the duration and extracts overview frames of the source.
2. Looks at those frames to work out the composition and where the text sits.
3. Checks how to locate the pauses and slow stretches precisely.
4. Identifies the speech and the long pauses in the audio.
5. Looks closely at the key scrolling and screen-change moments.
6. Reviews detailed frames to choose a safe vertical region, then refines where the page sits in the original frame.
7. Checks whether there is any useful audio so the track is not left empty.
8. Compares where the text moves during scrolling before fixing the focal area, and tests a wider left-weighted crop so lines begin complete.
9. Tests a crop that excludes the browser chrome and the taskbar for a larger document, assembles the vertical version with the pauses shortened, then corrects the output to exactly 1080 by 1920 and rebuilds.

Step 8 is the one that catches the common failure. A crop chosen on a single frame looks fine until the page scrolls and the text shifts sideways out of the region, and comparing several moments during the scroll is what finds that before the render.

What does the result look like?

The recording this was built from measures 1920x1080 at about 24fps and runs 31.55 seconds. From it comes a vertical version at exactly 1080 by 1920 in which the document fills the frame, the browser furniture is gone, the lines of text begin at their left edge, and the slow stretches are shortened.

The text is larger in the vertical version than in the original. That sounds impossible and is simply what happens when you throw away the parts of a desktop nobody needed to see.

When does this not work well?

Cropping a wide screen down to a narrow one discards most of the width, and some interfaces genuinely need all of it to make sense. These are the cases where Vizard Agent runs into the recording rather than into the brief.

• Wide layouts do not fit. A spreadsheet or a timeline needs its width.
• Small text stays small. Cropping helps; it does not add resolution.
• Moving content escapes a fixed crop. Scrolling sideways breaks a static region.
• The cursor may leave the frame. If the pointer matters, say so.
• Recording vertically is better. A capture made at the target shape needs no crop.

How do you fix a result that came back wrong?

Point at the moment where it goes wrong. Vizard Agent keeps the overview frames, all the tested crops, the scroll comparisons and the pause analysis, so the focal region can be moved without redoing any of the trimming.

• "The lines are cut off on the left." Shifted to the wider left-weighted crop.
• "It loses the sidebar." The region is widened to include it.
• "It trimmed too much." The pause threshold is relaxed and rebuilt.

How does Vizard Agent compare to doing it yourself?

By hand this means choosing a crop on one frame, rendering, watching, discovering the text scrolls out of it, and going back. The idea of cropping out the browser chrome to make the content bigger is the thing almost nobody thinks to try.

Common questions

Will the text be legible after cropping? That is the constraint Vizard Agent works to, and it tests several crops rather than assuming one.

Can it drop the browser bars? Yes, and it usually should. Vizard Agent tested exactly that on this run.

What if the page scrolls sideways? A fixed region will fail there. Vizard Agent compares scroll positions and reports the problem.

Does it trim the slow parts? If you ask. Vizard Agent locates the pauses in the audio rather than guessing at them.

What about the cursor? Say if it matters. Otherwise the crop is chosen around the content, not the pointer.

Why is the text bigger after cropping? Because a desktop recording spends most of its width on interface nobody needs to read. Removing that lets the part that matters occupy the whole vertical frame.

Can it handle a recording with no audio? Yes. Vizard Agent checks first so it does not leave a silent track where none was needed.

Will the output be exactly 1080 by 1920? Yes. Vizard Agent corrects the output dimensions rather than leaving them roughly right.

Should I just record vertically instead? If you can, yes. Cropping is a rescue rather than a plan.

Can I keep a widescreen version too? Yes. Vizard Agent works from the original recording rather than replacing it, so a trimmed widescreen cut and a vertical crop can both come out of the same pass over the footage.

Does this suit a software demo? Very well. Vizard Agent crops to the part of the interface the demo is about, which usually makes a feature legible on a phone for the first time.

Does Vizard Agent check the result? Yes. It reviews the cropped frames for legibility before delivery.