Loading tutorials…
Loading tutorials…
Loom records screens fast but edits poorly. Premiere edits beautifully but records nothing. Descript does both — screen record, edit by transcript, polish, ship. Here's the full screen-recording workflow for tutorials, demos, and course modules.
Who this is forCourse creators, founders recording demos, support teams building tutorial libraries, sales engineers producing technical walkthroughs. If you record 5+ screen videos a month and they need to look more polished than a raw Loom, this is the workflow.
What you'll need
Step 1
Don't wing it. Write a 5-10 bullet outline. Put it in a second window. Glance, speak, move on. Saves 50% of editing time.
The biggest time sink in screen recordings: rambling, getting lost, restarting sections. Outlines fix this.
Before recording, write a 5-10 bullet outline:
— Hook (15 sec): what will the viewer learn
— Core (45-90 sec per section, 3-5 sections): the actual content
— Recap (10 sec): the one thing to remember
— CTA (10 sec): what to do next
Put the outline in a second monitor or a small floating window. Glance, speak naturally, move on.
Don't read scripts verbatim — sounds robotic. Use the outline as guardrails, speak conversationally inside them.
Cue cards for specific phrases: a sticky note with brand-specific terminology or numbers you need to get exactly right. Avoids stumbling on key details.
Step 2
New Project → Record → Screen + Camera. Choose: full screen, specific window, or specific area. Webcam bubble bottom-right is the standard.
Descript → New Project → Record → Screen Recording.
Choose source: Full Screen (good for app walkthroughs), Specific Window (good for browser tutorials, avoids distracting other UI), or Specific Area (good for tight crops).
Camera: bubble in bottom-right at ~240px. Adds presence; don't skip unless the content is entirely visual.
Audio: select your real mic, not 'System Default.' Verify input level is around -6 to -3 dB peaks.
System audio: enable if you're demoing something with sound (UI clicks, alerts, video playback). Disable if it's a silent app walkthrough.
Resolution: 1080p is standard. 4K only when the content has fine detail (code editors, design tools).
Before pressing Record: do a 30-second test, watch it back, fix any issues (mic too quiet, cursor too small, system notifications visible). 5 min upfront saves 20 min in post.
Step 3
Record each outline section separately, pausing between. Easier to edit, easier to re-record one bad section without redoing everything.
Two recording styles: continuous (one long take) vs section-by-section (multiple takes per outline bullet).
Section-by-section wins for screen recordings: easier to re-record one bad section, easier to edit, fewer wasted takes.
After each section, hit Pause (not Stop). Take a breath, glance at outline, hit Record again.
Descript merges paused sections into one project automatically.
If a section goes badly, stop, scroll back in the script, delete that section's transcript+audio, and re-record just that section. Continuous-take editing in Premiere = 30+ min; section-by-section in Descript = 3-5 min.
Mistakes during recording: keep going. Note the mistake mentally, complete the section, and either re-record or trim in post. Stopping mid-section to restart costs more total time than fixing in post.
Step 4
After recording, transcript generates. Run Filler Word Removal. Delete mistake-takes. Tighten pacing by removing pauses + restarts.
When recording stops, Descript auto-transcribes (2-5 min for typical screen recording length).
First pass: Tools → Filler Word Removal. Remove obvious 'um/uh/er.'
Second pass: read transcript, delete mistake-takes. If you said 'Wait, let me restart that' anywhere, delete from the restart back to the start of the bad take.
Third pass: pacing. Tighten by removing long pauses, dead air, false starts. Aim for 'just slow enough that viewers can follow' — too fast loses people, too slow loses people too.
Target final length: 30-60% of raw recording length. A 10-min raw recording becomes a 4-6 min polished video. The 50-70% removed is filler + mistakes + over-explanation.
Step 5
Zoom into important UI moments. Add red arrow/circle callouts on key buttons. Lower-third for your name + title. Brand intro/outro stinger.
Polish is what separates a Descript tutorial from a Loom recording.
Zoom-ins: select a section of the timeline → Effects → Zoom → drag the zoom area to the part of the screen you want to highlight. Descript animates the zoom. Use on: code, fine UI details, small text.
Callouts: Insert → Shape → Arrow or Circle. Position over the button/element you're describing. Time it to appear when you mention it.
Lower-third (first 5 sec): name + role + (optional) episode title. Bottom-left, brand color.
Brand intro stinger: 3-5 sec animated logo at the start. Built once in the workspace, reused per video.
Outro card: 5 sec at end with CTA (subscribe, book demo, see related videos). Brand-aligned.
Don't over-polish: 1 zoom per 30 sec is plenty. Too many zooms = motion sickness for viewers.
Step 6
Tools → Captions → auto-generate from transcript. Review for accuracy. Chapter markers at major section breaks for YouTube + Descript playback.
Tools → Captions → Generate. Descript uses the transcript to create burned-in or soft-subtitle captions.
Burned-in: captions are part of the video file (always visible). Good for social/mobile.
Soft-subtitle (SRT/VTT): separate caption file uploaded to YouTube. Viewer toggleable.
Review captions for accuracy. Common issues: punctuation missing, name capitalization, technical terms (re-add to vocabulary).
Chapter markers: Tools → Chapter Markers. Add at major section breaks (typically your outline sections). YouTube uses chapters in the player.
Chapter titles: short, clear, action-oriented. 'Setting up the project' beats 'Section 1.'
Step 7
Publish → Export → MP4 1080p. Or use direct publish to YouTube via integration. Drop captions file alongside. Move project to right folder.
Export options: MP4 1080p H.264 (standard), MP4 4K (for fine-detail content like code), MP4 with burned-in captions (social), separate caption file (YouTube SRT).
Bitrate: 8-12 Mbps for 1080p, 35-50 Mbps for 4K. Higher = better quality + larger files.
Publish directly: Descript can publish to YouTube via integration. Saves the export-then-upload step. Configure in Settings → Publishing → YouTube.
Course platforms (Teachable, Thinkific, Kajabi, Podia): export MP4, upload manually. Most don't have native Descript integration.
Help center / docs site: upload to a video host (YouTube unlisted, Vimeo, Mux) and embed.
Move project to the correct library folder (don't leave in Recents).
Tag with #published and the publish date for future reference.
Common mistakes
Recording without an outline
What goes wrong: 30-min recordings produce 8-min usable video. Endless rambling, dead ends, restarts. Editor (you) spends 90 min cleaning up a 5-min final video.
How to avoid: 5-10 bullet outline ALWAYS before recording. Even rough is better than none. Cuts editing time by 50%.
Continuous take instead of section-by-section
What goes wrong: One mistake in minute 8 of a 15-min take means either re-recording everything or doing complex multi-cut editing. Time wasted.
How to avoid: Pause between outline sections. Re-record one bad section instead of restarting the whole video.
No zooms or callouts
What goes wrong: Viewers can't see what you're pointing at on a 1920×1080 screen. Especially bad on mobile/tablet viewing. Tutorial fails to teach.
How to avoid: At least 1 zoom or callout per 30 sec of UI walkthrough. Highlights the action, makes mobile viewing feasible.
No captions
What goes wrong: 40-60% of viewers watch with sound off. No captions = no comprehension. YouTube SEO suffers. Accessibility compliance fails.
How to avoid: Auto-generate captions from transcript. Review for accuracy. Burn in for social, soft-subtitle for YouTube.
Over-polishing on internal videos
What goes wrong: Internal training videos get 4-hour treatments because the editor goes overboard on intros, transitions, and effects. ROI on time is terrible.
How to avoid: Match polish to audience. External (customer-facing, course modules): high polish. Internal (team training): light polish, ship fast.
Exporting before final transcript review
What goes wrong: Captions ship with mistakes — wrong names, typos, missing punctuation. Looks unprofessional. SEO suffers (YouTube uses caption text for ranking).
How to avoid: Mandatory transcript review pass before export. 5-10 min per video. Catches 90% of caption errors before they ship.
Recap
Done — what's next
How to set up a Descript account for podcast + video editing
Read the next tutorial
Hand it off
Mastering the workflow takes 90 min. Producing 8-15 polished tutorial videos per month with consistent quality is ongoing work. A vetted video editor on EverestX runs screen-recording production from $14-16/hr — typically $600-1,200/mo for a steady tutorial / course / demo cadence.
See video editor rates
Descript wins for content needing polish: tutorials, demos, course modules. Loom wins for speed: async messages, customer support replies, quick walkthroughs. Use Loom for messages you'd otherwise text, Descript for content that needs to feel professional. Many teams use both.
5-min final video: ~90 min total (5-10 min outline, 10-15 min recording with section-by-section, 30-45 min editing + polish, 5-10 min captions + export). 15-min final video: 3-4 hours. Bigger ratio of polish-to-record on shorter videos.
No — Descript needs Screen Recording, Microphone, and (for webcam) Camera permissions on macOS. Settings → Privacy & Security → grant all three for Descript. Without them, recording fails silently or produces empty files.
Two approaches: (1) Descript → Recording Settings → enable 'Highlight cursor.' Adds a yellow circle around the cursor during recording, (2) post-record: add a custom cursor effect in the timeline. Both help on small screens. Larger system-level cursor (System Settings → Accessibility → Display) also helps.
Technical fact: Descript records whatever's on your screen. Legal/practical: copyrighted content (movies, games, copyrighted software UIs) shown in tutorials usually falls under fair use for educational purposes BUT YouTube/platform algorithms may flag it. Use brief clips, add commentary, and consult counsel for high-risk use cases.
Descript
Descript is the editor that thinks like a doc — but the install is misleadingly simple. Skip the workspace + project + storage configuration and you get untitled files everywhere and editors fighting over which version is current. Here's the proper setup.
Descript
Descript's killer feature: edit your video by editing the transcript. Delete a word in the doc, the audio/video deletes too. This walks the full workflow — Filler Word Removal, Word Find & Replace, Strikethrough, and Studio Sound — that makes Descript 5-10x faster than traditional editors.
Descript
Editing is half the job. Publishing, sharing review links, gathering feedback, and shipping cleanly is the other half. Descript has solid publishing + collaboration features — here's how to use them so projects don't get stuck in 'waiting for feedback' purgatory.
Descript
Most content creators hit the DIY Descript ceiling at 10-20 episodes. Editing eats 6-12 hours/week per episode. Quality plateaus. Cadence slips. Here's the honest framework for when to bring in a podcast or video editor.
Loom
Half your support tickets get answered with a 4-paragraph email that takes 12 minutes. A 90-second Loom answers the same ticket in 3 minutes and the customer actually understands the answer. Here's the support-specific setup.