How to record a coding tutorial that's easy to follow

Coding tutorials are some of the most useful videos online — and some of the hardest to follow. Tiny text, fast typing and jumping between files leave viewers squinting and pausing every few seconds. A good coding tutorial video fixes those problems with a few simple habits.

This guide focuses on recording on Android: coding in a mobile code editor or terminal app, on a phone or tablet. The same principles apply on any device. (Cinematic Recorder for Windows and Mac is planned; today it runs on Android.)

Why coding videos are hard to watch

• Text is small. Code editors are designed for reading up close, not for a video watched on another phone.
• Typing is slow to watch. Watching someone type every character of a long line is boring and invites mistakes.
• Context is hidden. Viewers don't know which file you're in or where the line you're changing sits.
• Errors derail the video. An unexpected bug can turn a five-minute lesson into twenty minutes of debugging.

Every tip below targets one of these problems.

Prepare your coding environment

Make the font big

Increase the editor's font size well beyond what you normally use. A good test: record five seconds, then watch it on a different phone at arm's length. If you can't read a line comfortably, go bigger. Fewer lines on screen is fine.

Choose a high-contrast theme

Pick a theme with clear contrast between background, text and syntax colours. Very low-contrast themes look stylish but become muddy after video compression.

Clean up the screen

• Close unrelated files and tabs.
• Hide sidebars you won't use.
• Turn on Do Not Disturb so messages don't cover your code.
• If you're on a tablet, landscape mode gives more room for longer lines — see screen recording on an Android tablet.

Remove secrets

Plan the code before you record

Live coding feels natural, but unplanned live coding often goes wrong. A middle path works best:

1. Write the final code first and make sure it runs.
2. Break it into steps — each step adds one small, working piece.
3. Prepare snippets for long or boring lines (imports, boilerplate, long strings). Paste them in and explain them, instead of typing every character.
4. Type the important lines live — the ones that teach the concept — so viewers see them being built.

Our guide to writing a screen recording script shows how to add short spoken notes for each step.

Recording settings for code

• Resolution: use the highest resolution your phone handles smoothly. Sharp text matters more than smooth motion in coding videos.
• Frame rate: 30fps is usually enough for code; 60fps helps if you scroll a lot.
• Microphone on, internal audio usually off — you rarely need app sounds.
• Countdown on, so you start with your hands ready.

For details on these choices, see the best screen recording settings for Android.

Pacing a coding tutorial video

Say it, type it, run it

For each step: explain what you're about to write and why, then write it, then run it and show the result. This rhythm keeps viewers oriented.

Name the location

"In main.py, below the imports, we'll add a function." Saying the file and position saves viewers from searching.

Pause on results

When the output appears, stop for two seconds. Let viewers read it before you move on.

Handle bugs calmly

If something breaks, you can pause the recording with the floating controls, fix it, and resume — then cut the detour in editing. Or, if the bug is a common one, keep it and explain the fix. Beginners learn a lot from seeing real errors solved.

Editing: zoom where the code is

This is where a coding video becomes easy to follow.

• Zoom on the active line. Click-based auto zoom moves in smoothly where you tap, so the line you're editing fills more of the frame. Tap near the line you're explaining to guide it.
• Use focus highlight or spotlight to dim the rest of the file and draw eyes to one function. Read more about focus and spotlight effects.
• Cut typing delays and waiting for installs or builds. Speed them up only if the progress itself is useful to see.
• Check readability at the end by watching on a phone.

Edits are non-destructive, so you can adjust zoom and cuts freely without touching the original recording.

Structure: one concept per video

Coding topics grow fast. "Build a full app" is better as a series: setup, first screen, data, saving, publishing. Each video teaches one concept and ends with working code. See why a series of short tutorials works better.

Share the final code in a link or the description, so viewers can compare their work with yours.

FAQ

Can I really code and record on an Android phone?

Yes, with a mobile code editor or terminal app, especially on a tablet or with a keyboard attached. It works well for short lessons and beginner topics.

What font size should I use?

Bigger than feels normal. Test by watching a short clip on another phone. If you need to squint, increase it.

Should I type everything live?

No. Paste boilerplate and long lines, and type only the lines that teach the main idea. Viewers learn more and stay engaged.

How do I avoid leaking API keys?

Use placeholders, keep secret files closed, and check every screen before recording. If a secret ever appears in a published video, revoke and replace it immediately.

Big font, prepared snippets, zoom on the active line, and one concept per video. Get those four right, and your coding tutorials will be far easier to follow than most.