How to Record a Coding Tutorial on Mac: Setup, Recording, and Export

The single biggest mistake in coding tutorials is recording at your normal working setup — small font, dark theme with low contrast, multiple split panes, status bars and sidebars everywhere. What is comfortable for you to work in is often unreadable as a video at 720p with compression artifacts.

Before you record, make these adjustments. Set your editor font size to at least 16pt — 18pt is better. In VS Code, open Settings and set editor.fontSize. In Neovim or terminal editors, increase the terminal font size at the profile level. Zoom in with ⌘+ if you forget. Use a high-contrast dark theme: Dracula, One Dark Pro, or GitHub Dark all read well in recordings. Night Owl and Monokai also work. Avoid themes with muted colors that rely on subtle saturation differences — they compress to mud in video.

In your terminal, do the same: large font, high contrast, minimal prompt. A minimal PS1 or Starship prompt with just the directory and git branch is cleaner than a full powerline prompt that takes two lines. Close any sidebar, drawer, or panel in your editor that is not relevant to what you are teaching. Hide the file tree if you will not navigate it. More screen space on the code means more room for auto-zoom to work with.

Write your tutorial as a numbered sequence of steps before you open Limelight. Not a full script — just the order of operations. What file do you open first? What do you type? What command do you run? What output do you show?

Coding tutorials that drift — where the presenter is thinking on camera, backtracking, or getting distracted by an error they did not plan for — are unwatchable. Rehearse once end-to-end, even informally, so you know the path. Fix any errors you hit in rehearsal so the recording is clean. If a realistic error is part of the lesson, plan for it: know what you will type to debug it and how long it will take.

Also decide in advance where section breaks are. Coding tutorials that run more than five minutes benefit from on-screen text labels at each major section — 'Setting up the database,' 'Writing the route handler,' 'Testing in the browser' — so viewers can scrub to the right section without watching linearly.

Limelight works well for coding content without special configuration — auto-zoom and keystrokes are on by default. A few things to check before recording: make sure you are recording at your editor's native window size, not the full screen. If you are on a large display, consider recording a portion of the screen rather than the full canvas. A 1440×900 or 1280×800 recording region gives auto-zoom more to work with than a full 2560×1440 frame.

If your tutorial involves switching between an editor and a terminal (common for any backend or CLI content), Limelight will auto-zoom into each window as you click into it. This is one of the clearest signals in a coding tutorial — the switch from editor to terminal and back — and having the zoom follow it automatically keeps the viewer oriented.

Hit record and run your planned flow. The most important pacing adjustment for coding recordings: slow down before you type a command or keyboard shortcut. In your normal workflow you might hit ⌘P and type a filename in under a second. In a tutorial, pause, let the viewer see the state of the screen, then type deliberately. The keystroke display in Limelight will show every key you press, so the viewer can read along — but only if you give them enough time.

The same applies to typing code. Type at about 60-70% of your normal speed. Syntax errors from fast typing that you then delete are confusing to watch even if they are normal in real development. Type each line cleanly the first time.

Let auto-zoom do its job. When you click into a function definition or a terminal output line, pause a beat after clicking before you move on. The zoom will land on the element and hold briefly — that is the viewer's window to read what is there. If you click and immediately scroll, the zoom does not have time to be useful.

For keyboard shortcuts, type them and then pause. The keystroke display will show 'Cmd+Shift+P' or whatever you pressed. Give the viewer a moment to read it before the command palette opens and you start typing.

For tutorials with multiple sections, use Limelight's on-screen text feature to drop a label at each section transition. A line like '→ Step 2: Writing the API route' appearing on screen for three seconds tells the viewer exactly where they are without audio narration.

Keep labels short and action-oriented. 'Step 1: Install dependencies' is better than 'Now we are going to install the dependencies for our project.' These labels serve as chapter markers that the viewer can use to scrub back to the right section.

In the Limelight editor, do three things: trim the opening (cut the seconds before your first real action), trim the end (cut after the final command output appears), and speed up any slow sections.

Slow sections in coding tutorials are predictable: npm install or pip install outputs, database migrations, compilation, test suite runs. These can take 10-30 seconds in real time. Speed them up by 3-5x in the editor — the viewer understands that packages are installing, they just do not need to watch it happen at real speed.

Export to mp4 at 16:9 for blog posts, YouTube, and docs. If you plan to share the tutorial on Twitter or LinkedIn, also export at 9:16 — the vertical format means the code takes up the full mobile screen without shrinking. Limelight handles both exports from the same session.

Final check before publishing: watch your exported clip at 720p resolution to verify the code is readable at that size. If it is not, re-record with a larger font size or a smaller recording region.