Blog/Craft

Tutorial videos developers finish

Set the screen up for the viewer, keep the real error, and give every tutorial chapters and a link to the code.

Kevin Blanco··6 min read·Activation

The short answer

A tutorial developers finish is set up for the viewer's screen, not yours. Code is large enough to read on a phone, the cursor is visible, the real error stays in, and the video has chapters and a link to the code. Five to ten minutes is typical for one task. Measure completion and where people leave.

01

Set up the screen

Most tutorials are recorded on a large monitor and watched on a laptop or a phone. If the code is readable on your screen and unreadable on theirs, the viewer is guessing.

Fix that before you record anything.

FigureThe same code, two sizes. Check it on a phone before you record the rest.
  • Font size

    Phone-size

    Large enough to read on a small screen without zooming.

  • Zoom

    Per line

    Zoom in on the line that matters while you talk about it.

  • Cursor

    Visible

    A cursor people can follow shows where to click and type.

02

A structure that works

The shape of a six-minute tutorial

0:00  The finished result, on screen
0:20  What you need before you start
1:00  Step one to three, with the code visible
3:30  The error most people hit, and the fix
5:00  The result again, working
5:40  The next step, with the link

The timings are an example. The order is the point: result first, error in the middle, result again at the end.

03

Keep the real error

Don't edit out the moment it fails. The error is the part a viewer will hit themselves, and watching someone fix it is why they came.

Cut the dead time around it: the typing, the waiting, the scrolling. Keep the failure and the fix.

04

Make it easy to come back to

  • Under the video

    • Chapters that name the steps
    • A link to the repo or snippet
    • The versions you used
  • On the screen

    • Command text large enough to copy
    • Steps named as you go
    • The result visible at the end
  • In the audio

    • A clean microphone
    • No music under the voice
    • The name of each step, said aloud

05

Check before you publish

The test

Will they finish it?

Tick every question you can answer yes to.

Not yet

0 / 5

Pick one task and set up the screen first. Everything else depends on those.

FAQ

Questions people ask

How long should a developer tutorial video be?

Five to ten minutes is typical for one task. If the task takes longer, split it into two videos or add chapters.

What font size should I use for code in a video?

One that's readable on a phone. Record a few seconds, watch it on an actual phone, and increase the size until you don't have to squint.

Should I edit out mistakes in a tutorial?

Keep the real error that most people will hit, and the fix. Cut the dead time around it.

What should go in the video description?

Chapters that name each step, a link to the repo or code, and the versions of the tools you used.

How do I know if a tutorial works?

Look at how many viewers reach the last step and where the audience leaves. Fix the minute where they leave first.

DevReel

How we do it at DevReel

We record tutorials on a screen set up for a phone, keep the real error in, and ship each one with chapters and a link to the code. Where viewers leave tells us which minute to fix.

Cloudinary's videos usually average around 400 views. Ours passed 9,000 in the first week. For ngrok, watch hours tripled and subscribers went from about 450 to over 800 in the first week.

Cloudinary views

9,000+

in the first week, against a usual ~400

ngrok watch hours

3×

subscribers from ~450 to 800+ in the first week

A free 5-minute teardown

Send us a tutorial you're unsure about and we'll tell you where a viewer would leave.

Kevin Blanco founded DevReel. He has made 500+ developer-tool videos and spoken at 80+ developer conferences.

Keep reading