A screen recording can look sharp on your monitor and still be difficult to follow on YouTube. Menu labels become tiny, the cursor moves before viewers understand the instruction, and important settings disappear during a fast scroll.
Increasing recording quality will not solve every one of these problems. A useful tutorial needs both a readable picture and a sequence of actions that viewers can follow.
This guide explains how to prepare and record a software tutorial in OBS Studio on Windows. The example setup targets a horizontal 1080p video showing a browser or desktop application, with spoken instructions.
The settings below are a starting point for testing, rather than a guarantee that every computer or application will behave identically.
1. Plan the Smallest Useful Demonstration
Before opening OBS, write down what the viewer should be able to do after watching.
For example:
Add an image to a WordPress article, adjust its display size, and check the result.
That outcome is narrow enough to demonstrate clearly. It also gives you a reason to leave unrelated settings out of the recording.
Build a short sequence:
- Show the starting state.
- Explain the first action.
- Perform it.
- Show the result.
- Continue to the next action.
- Confirm the finished outcome.
Prepare the demonstration materials in advance. For a WordPress tutorial, that could mean a draft article, a sample image, and a test site.
Use sample content where possible. Close unrelated tabs, hide personal bookmarks, and pause notifications before recording. This also makes the screen less distracting.
Rehearse the sequence once without recording. Notice where you hesitate, search for a file, or open the wrong menu. Fix those interruptions before they become editing work.
2. Make the Interface Readable Before Capturing It
The viewer does not see your monitor at its physical size. They may watch the tutorial in a small browser player or on a phone.
Start by enlarging the application’s text or interface where the software allows it. For a browser-based tutorial, try a moderate browser zoom increase, then check that the required controls still fit.
There is no universal zoom percentage. A dense settings page and a simple text editor need different framing.
For example, suppose a WordPress sidebar is difficult to read in a test recording. Try increasing browser zoom, closing an unnecessary panel, and recording the relevant section again. Compare the result at the size viewers are likely to use.
Avoid zooming so far that a desktop layout changes into a different interface halfway through the lesson. Rehearse after adjusting the zoom.
Also distinguish between two problems:
- Text is sharp but too small: Enlarge the interface or show a smaller area.
- Text is large enough but looks smeared: Investigate scaling, recording quality, or export settings.
This distinction prevents you from spending time increasing file size when the real problem is composition.
3. Build a Simple OBS Scene
Open OBS and run Tools → Auto-Configuration Wizard. Choose the option intended for recording rather than streaming.
The wizard evaluates your intended use and available hardware. OBS describes it in the official Quick Start Guide.
Create a scene with a descriptive name, such as Browser Tutorial.
For a lesson that stays inside one application:
- Select the + button in the Sources panel.
- Add Window Capture.
- Choose the application window.
- Check that the correct content appears.
- Leave cursor capture enabled if viewers need to follow your clicks.
Window Capture targets a selected window rather than the entire desktop. OBS documents its behavior and options in the Window Capture guide.
If the lesson moves between several applications, Display Capture may be more practical. Check everything visible on that display before recording.
Test any dropdown menus, file dialogs, or separate application windows used in the lesson. Do not assume that a source capturing the main window will show every secondary window you open.
Keep the scene simple initially. Add a webcam only if seeing you helps the explanation, and position it away from menus or settings that the viewer must read.
4. Set the Canvas and Output Deliberately
In Settings → Video, OBS separates the working canvas from the output resolution.
The Base (Canvas) Resolution defines the space where sources are arranged. The Output (Scaled) Resolution controls the resulting video dimensions in this simple recording workflow.
For a 1920 × 1080 display and a horizontal tutorial, a straightforward starting point is:
| Setting | Starting value |
|---|---|
| Base canvas | 1920 × 1080 |
| Output resolution | 1920 × 1080 |
| Frame rate | 30 fps |
OBS explains these controls in its Studio Overview Guide.
Matching these two resolutions avoids a separate canvas-to-output resize. However, the captured window can still be scaled within the canvas.
If you use a higher-resolution monitor, decide whether to record at its native resolution or compose a readable 1080p frame. Fitting an entire dense desktop into a smaller output can make interface text difficult to read.
For a typical browser walkthrough, try 30 fps first. Consider 60 fps when smooth motion is important to the subject and your computer can record it reliably. A settings tutorial rarely needs the same motion treatment as a fast-moving game.
When fitting the source, preserve its proportions. Do not stretch a narrow window across a wide canvas.
On Windows, OBS allows source cropping by holding Alt while dragging an edge in the preview. Crop unused space carefully, then check that controls needed later in the lesson remain visible.
Cropping and enlarging an existing image does not create new detail. If the source text is already tiny, enlarge it in the application before capture.
5. Choose a Recording Quality You Can Test
Open Settings → Output and use Simple output mode for this initial setup.
Choose a recording folder with sufficient free space. Then select a recording quality preset.
Start with High Quality. If text shows compression damage in the saved recording, compare a short sample using Indistinguishable, provided the computer can handle it.
OBS describes High Quality as a balance between quality and file size. Indistinguishable produces larger files and can have a greater performance cost. See the Recording Encoder Presets Guide.
Use an available H.264 encoder for a broadly compatible starting workflow. Hardware options depend on your computer; keep the wizard’s recommendation initially and verify it with a recording.
For the recording container, MKV is a practical choice because an interrupted recording is generally more recoverable than a traditional MP4 that requires finalization. OBS also supports other resilient containers, including Hybrid MP4. Its Audio/Video Formats Guide explains the differences.
If your editor does not accept MKV, use File → Remux Recordings to create an MP4 version. Remuxing changes the container without re-encoding the video; it does not sharpen the recording or repair missing detail. The workflow is documented in the Standard Recording Output Guide.
Test that your editor can import the sample before recording the full lesson.
6. Confirm the Audio You Are Actually Recording
Speak a few sentences while watching the OBS Audio Mixer. Confirm that the intended microphone responds.
If the tutorial does not need application audio, mute the unused desktop audio source. If it does, test the balance between the application and your voice.
Check for duplicate microphone capture. For example, the same microphone may be active through a global audio device and a separate source. That can produce doubled or echoing speech.
Record and listen back. Moving meters confirm that a signal exists, but they do not establish that the voice sounds clear.
Listen for distortion, excessive room echo, and unexpected notification sounds. OBS explains its level indicators and controls in the Audio Mixer Guide.
If you make a speaking mistake, pause briefly and repeat the complete sentence. That usually gives you a cleaner editing point than restarting halfway through a word.
7. Run a Short Test That Resembles the Real Lesson
A static ten-second recording does not test scrolling, menu behavior, or the workload of the actual application.
Record a sample of roughly one to two minutes containing the actions you will demonstrate:
- Open the smallest menu viewers need to read.
- Scroll through a typical section.
- Move the cursor to a control and click it.
- Type a short example.
- Speak at your normal teaching volume.
- Open any secondary dialog used in the lesson.
Stop the recording and play the saved file outside OBS.
Check it at a normal viewing size, not only enlarged across your entire monitor.
Use this review table:
| What you notice | First adjustment to try |
|---|---|
| Labels look sharp but tiny | Enlarge the application interface or tighten the framing |
| Letters break up during scrolling | Compare a higher-quality recording preset |
| The picture stutters | Reduce competing workload and check OBS performance |
| A menu or dialog is missing | Review the capture source and repeat that action |
| Voice sounds doubled | Check for duplicate audio capture |
| Part of the interface is cut off | Reposition or resize the source without stretching it |
If OBS reports encoding overload, simplify the scene and close unnecessary resource-heavy applications. Lowering frame rate or output resolution can also reduce the workload, but recheck text readability afterward. OBS provides an encoding performance troubleshooting guide.
Change one thing at a time, then repeat the relevant part of the test. This helps you identify which adjustment solved the problem.
8. Record Actions at a Pace Viewers Can Follow
A clear tutorial gives the viewer time to connect the spoken instruction with the visible action.
Use a simple rhythm:
Name the control → move to it → click → show what changed.
For example:
Open the image settings in the right sidebar.
Move the cursor to the control, click it, and pause while the settings appear.
Then explain the next choice.
Avoid continuously circling the cursor while talking. If you are explaining a result, leave the pointer somewhere that does not cover important text.
Scroll in deliberate steps. Stop when the relevant section is visible, explain it, then continue. Long scrolling movements make it harder for someone to identify where an instruction applies.
Record the lesson in manageable sections. You might separate opening the editor, inserting an image, changing its settings, and checking the final page.
At the beginning and end of each section, leave a brief pause. These pauses provide editing space.
When repeating a section, return to the same starting state. If the earlier take ended with a menu closed, the replacement should not unexpectedly begin with a different panel open.
Keep the intermediate steps that a beginner needs. A shorter edit is not automatically a clearer explanation.
9. Edit Without Losing the Screen’s Detail
Create an editing project that matches the intended output resolution and frame rate.
Watch for accidental changes such as placing a 1080p recording into a 720p timeline or stretching a source to fill the frame.
Remove false starts, unnecessary waiting, and repeated explanations. Keep enough time after important actions for viewers to see the result.
Use zooms sparingly. A close-up can help identify a small control, but enlarging a low-detail recording cannot reconstruct sharp text.
If an essential setting remains unreadable, rerecord that section with a larger interface. This is often more useful than adding several arrows around a blurred label.
For a conventional 1080p SDR upload, an MP4 export with H.264 video and AAC audio is a practical starting point. YouTube recommends keeping the recorded frame rate and lists 8 Mbps as its reference video bitrate for 1080p at standard frame rates such as 30 fps. That is upload guidance, not a requirement to record the original footage at 8 Mbps. See YouTube’s recommended upload settings.
Play the exported file before uploading. Check the smallest necessary text and a section containing movement. If the recording is clear but the export is not, investigate the timeline and export settings.
10. Check the Processed YouTube Version
Upload the video privately while you review it.
YouTube initially processes lower-quality versions, and higher resolutions can take longer to become available. A newly uploaded video that temporarily looks soft may still be processing. YouTube explains this in its video quality guidance.
Once the intended resolution appears in the player’s quality menu, select it and inspect the tutorial again.
Check three stages separately:
- Original recording: Was the interface readable when captured?
- Exported file: Did editing or compression reduce that readability?
- Processed upload: Is the intended playback quality available and selected?
Also watch on a phone. Ask whether a viewer can identify the control you are discussing without repeatedly pausing and magnifying the picture.
If the answer is no, improve the framing or interface size in the next recording. More pixels alone do not replace a clear demonstration.
A successful screen tutorial lets someone see the relevant control, understand the instruction, and recognize the result. Use those three checks throughout preparation, recording, and review.