A wide screen in a narrow frame

Screen shares are the hardest source for vertical video, because everything that matters is small, wide, and spread across the whole picture.

01

How much of a shared screen survives 9:16?

Roughly the middle third, which for most applications is not where the important part sits. That is why screen shares are one of the few cases where a wider shape genuinely beats the standard vertical one, even though it occupies less of a phone display.

02

How much of a shared screen each shape keeps

Enlarging the interface before recording does more than any shape choice afterwards, because nothing recovers detail that was never captured.

ShapeWidth keptReadable?
16:9All of itYes, and small on a phone
1:1Around halfUsually, if the interface was enlarged
4:5Under halfOnly with a large interface
9:16About a thirdRarely, unless one panel is the subject
Blur fillAll of it, smallerYes, at reduced size

03

Preparing the screen before recording

Zoom the interface in, enlarge the font in code editors and documents, and close panels you do not need. The more space the important content takes up on the screen, the more of it survives any crop. Presenters are often surprised how much larger text needs to be for a phone, and a quick test recording shows it immediately.

Hide notifications, bookmarks and personal tabs. They distract viewers and occasionally reveal information you did not mean to share.

04

Guiding the viewer's eye

Move the cursor slowly and deliberately, and pause it on what you are talking about. Fast, restless cursor movement is hard to follow even on a large screen, and on a phone it is almost impossible. Some presenters enable cursor highlighting so the pointer is easier to spot.

Say where to look as you go: top left, the second line, the red button. Verbal cues help viewers who are watching a smaller version of the screen find the right spot quickly.

05

Choosing moments that work small

The best screen-share clips show a single clear result: a before and after, a surprising number, a quick trick that saves time. Long walkthroughs with many steps belong in the full video, where viewers can pause and follow along.

If a clip needs detail, consider showing the result first, then how it was done. Viewers who see the payoff early are more willing to follow the steps.

06

Adding the presenter back in

A small view of the presenter's face, if you recorded one, adds warmth to a screen-heavy clip. Keep it small and in a corner that does not cover the content. Viewers connect with a person more easily than with a screen alone.

If there was no camera, a clear, friendly voice and good captions carry the same connection surprisingly well.

07

Keep the part that has to be read

  • Choose 4:5 or 1:1 over 9:16. Both keep substantially more of the width, and both are on every plan.
  • Zoom in before you record. A larger interface in the original survives cropping. Nothing recovers text that was small to begin with.
  • Clip one step at a time. A single action fits a small frame. A whole workflow does not.

Send a screen recording and compare the shapes. Nothing to pay for the first.

Questions people ask

Can I keep the whole screen?
In 16:9, yes, and that shape is available on every plan. It shows less large on a phone, which is the trade you are making.
What if the presenter is also on camera?
Split screen on paid plans holds both the face and the screen, which suits a walkthrough better than either alone.
Why does my screen recording look blurry?
Usually because the interface was small when recorded. Increasing the display size before recording is the fix, and it has to happen beforehand.
Is a code editor clippable?
Only when the type is large. Default editor sizes are unreadable once cropped and shown on a phone.
Where do captions go over a screen?
Somewhere with fewer competing elements, and a shape behind the line helps because interfaces are visually busy.
Why does my screen recording look soft?
Usually because the interface was small when recorded. Increasing the display size beforehand is the only fix, and it has to happen before.

Read next

01Source with text already in itGuide02Hands on demonstrationsGuide03Framing a whiteboardGuide