The quality of your raw recording directly affects the quality of the finished video -- whether you edit manually or use AI tools. These tips cover the screen setup, recording habits, and environment adjustments that produce the best raw footage for developer tutorials.

Editor Setup

Font Size

This is the single most impactful setting. Bump your editor font to at minimum 16px. 18px is better. Yes, it feels ridiculous on your monitor. It looks correct on a YouTube viewer's laptop or phone.

// VS Code settings.json
{
  "editor.fontSize": 18,
  "terminal.integrated.fontSize": 16,
  "editor.lineHeight": 28
}

If you use VidNo or any AI tool, larger font size also improves OCR accuracy, which directly improves script quality.

Theme

Use a dark theme with high contrast. YouTube compresses dark backgrounds well, and most developer viewers prefer dark themes. Avoid:

Stop editing. Start shipping.

VidNo turns your coding sessions into YouTube videos — scripted, edited, thumbnailed, and uploaded. Shorts included. One command.

Try VidNo Free
  • Light themes (glare, poor compression, looks washed out on most monitors)
  • Extremely low contrast themes (grayed-out text is unreadable at 720p)
  • Themes with very saturated colors (red on dark blue is hard to read when compressed)

Recommended: One Dark Pro, GitHub Dark, Dracula, or Tokyo Night. These have been empirically validated to look good after YouTube's compression.

Window Layout

Use a single monitor for recording. If you have dual monitors, record only one.

  • Full-screen editor: Best for code-heavy tutorials. No distractions.
  • Split view (editor + terminal): Good for build-and-test workflows. Use a 70/30 split, editor on the left.
  • Editor + browser side by side: Good for API testing or frontend development. 50/50 split.

Avoid window overlap. If one window partially covers another, the AI has to work harder to understand what is on screen.

Recording Settings

Resolution

Record at 1920x1080 (1080p). Higher resolutions like 4K offer no benefit for screen recordings -- YouTube compresses code to the point where 4K and 1080p look identical. Recording at 4K just makes files larger and processing slower.

Frame Rate

30 fps is sufficient for screen recordings. 60 fps doubles file size with no visible benefit for code content (unlike gaming or animation). VidNo samples at 1 fps for analysis anyway, so higher recording frame rates do not improve AI output.

Bitrate

For 1080p at 30fps, target 6-8 Mbps for screen recordings. This is lower than typical video bitrate recommendations because screen content (mostly static text) compresses much better than camera footage. A 30-minute recording at 8 Mbps is roughly 1.8 GB.

Audio

Record system audio and microphone on separate tracks if your recording software supports it. This lets AI tools distinguish between your narration and system sounds. If you only get one track, prioritize the microphone.

Use a USB microphone if you have one. Laptop mics work but produce more room noise, which can affect voice cloning quality. See the OBS settings guide for detailed audio configuration.

Coding Habits During Recording

Commit Frequently

This is the highest-impact habit for AI-assisted workflows. VidNo uses git diffs to understand what you changed. More commits = more granular understanding = better scripts.

# Instead of one big commit at the end:
git add . && git commit -m "implement user authentication"

# Commit at each logical step:
git commit -m "add user model schema"
git commit -m "implement password hashing"
git commit -m "add login route"
git commit -m "add auth middleware"
git commit -m "add protected route example"

Use Clear File Names and Variable Names

AI tools read your code. userAuthMiddleware.ts gives the AI more context than middleware.ts. validateEmail() is more informative than validate(). This is good practice anyway, but it directly impacts AI script quality.

Pause Between Steps

When you finish one logical step (created a file, ran a test, installed a dependency) and are about to start the next, pause for 3-5 seconds. This gives AI scene detection clean boundaries and makes cuts look natural.

Keep It Under 45 Minutes

Longer recordings produce diminishing returns. If a coding session runs long, split it into two recordings. VidNo handles 45-minute recordings well but starts losing script coherence above 60 minutes.

Environment

  • Notifications: Turn off all system notifications. A Slack message popup in the middle of a recording is unprofessional and gives AI tools noise to filter.
  • Browser: Close unnecessary tabs. If you need to look something up, use a fresh browser window.
  • Desktop: Clean wallpaper, no personal files visible. This matters less for AI tools but matters for professionalism.

For OBS-specific configuration, see best OBS settings for coding tutorials.