To record your screen with OBS Studio, create a scene, add the capture source that fits your computer, check the preview and audio meters, then choose where and how OBS saves the file. Make a short test and play it back before recording a full lesson, demonstration or gameplay session.
For a safer first recording, save to MKV and convert to MP4 afterwards if your editor or upload workflow needs it. The exact capture options and performance depend on your operating system, hardware and the work happening on screen, so a test is more useful than assuming one set of settings will suit every computer.
Install and open OBS Studio
Download OBS Studio from the official OBS website. Choose the installer for your operating system and follow its prompts. OBS's system requirements page lists baseline operating-system and graphics compatibility; it does not mean every compatible computer can record every workload smoothly. That page's stated baseline is dated, so check current OBS documentation if you are installing on an older computer or a recently updated operating system.
When OBS opens, you will see a preview area, a Scenes panel, a Sources panel, an Audio Mixer and recording controls. The panels may be arranged differently in your version, but the basic idea is consistent: a scene is the layout you are recording, and its sources provide the picture and, where configured, sound. If a panel is missing, look in the View or Docks menus rather than assuming OBS has no such control.
Before you start, decide what the recording must show. A narrated software lesson might need one application window and your microphone; a walkthrough involving menus outside that application may need the whole display. A gameplay recording has different capture considerations from a spreadsheet tutorial. This decision affects which source you add and what you should inspect in the preview.
Save your work to a folder you can find again, such as a dedicated folder in Documents or on a drive with sufficient free space. If you are recording a long session, make sure the destination is not nearly full. A short test will also help you catch a mistaken folder before you produce a large file.
Let the wizard make a starting configuration
Open Tools → Auto-Configuration Wizard. The wizard asks about your intended use and considers available hardware resources when proposing an initial configuration. For this task, choose the option for recording rather than streaming if that choice is presented. The wizard is a starting point, not a promise that the resulting picture, file size or performance will match your needs.
Follow the prompts and keep the suggested values unless you already know why you need to change them. If you are recording a presentation, clear desktop demonstration or lesson, you may not need the same output size or frame rate as a fast-moving game. More detail and smoother motion can require more processing and storage. If the wizard offers output choices, treat them as a first proposal to validate in your own short sample.
OBS distinguishes Base (Canvas) Resolution from Output (Scaled) Resolution. The canvas is the space in which sources are arranged; the output resolution is the size of the resulting recording. If these differ, OBS scales the arranged image for the file. You do not need to change them just because there are two labels. Start with a sensible match to your display and recording goal, then inspect the test for legibility and framing.
Frame rate is another trade-off, not a quality switch that should always be set as high as possible. Sixty frames per second can be more demanding than thirty, while a mostly static slide or browser tutorial may not need the extra motion detail. A game or fast cursor movement may benefit from it, provided the computer handles the capture. Check the recording itself rather than relying on a setting name.
The OBS Quick Start Guide covers the initial wizard and setup. After it finishes, you still need to create or select a scene and confirm the capture source. A wizard configuration cannot tell whether you chose the right monitor or whether a required microphone is audible.
Create a scene and add the right capture source
In the Scenes panel, select the existing scene or create one with a descriptive name, for example, “Browser lesson” or “Desktop demo”. Naming scenes is useful when you later add a second layout, such as a window-only lesson and a full-desktop troubleshooting view. For a first recording, keep the scene simple: add only the sources you need.
Use a display source when the entire monitor should appear in the video. Use a window source when you want to limit the image to one application. On Windows and Linux, OBS documentation describes Display Capture and Window Capture; available behaviours may differ by platform and version. On macOS, look for macOS Screen Capture. The precise source list and permissions depend on the system, so use the option available in your installed OBS rather than trying to force a source from another platform's instructions.
To add a source, use the plus button in the Sources panel and choose the appropriate capture type. Give it a recognisable name if prompted, then choose the display or application you intend to record. If the source asks for permissions, follow the operating system prompts. On macOS in particular, screen-recording permissions may need to be granted in system privacy settings before the preview can show the desired content.
A display capture can include notifications, unrelated windows or private information. A window capture narrows what appears, but may not include menus or other windows you need to demonstrate. Close personal material, silence notifications where practical, and consider whether the recording should show the whole desktop before pressing record. This is a content and privacy check, not a setting that OBS can make on your behalf.
For Windows games, OBS also lists Game Capture. It may be appropriate for a game, but no one capture source works on every system or title. If a source produces a blank preview or misses part of the application, try another suitable source and test the result. If your purpose is capturing an external camera or console, a webcam or capture card is a separate, conditional requirement; neither is needed for a basic desktop recording. The distinction between a capture device and ordinary desktop capture is explained in this guide to what an HDMI capture card does.
Inspect the preview before moving on. Confirm that the right display or window is visible, the image is not unexpectedly cropped, and the important controls or text fit within the frame. You can select a source in the preview and adjust its position or size, but take care not to stretch it out of proportion. A tidy preview is only a visual check; the short recording will show whether the saved output is framed as expected.
Check the preview and audio meters
The Audio Mixer helps you see whether OBS is receiving sound. Speak at the volume you expect to use, or play a system sound that should be part of the recording, and look for movement on the relevant meter. A moving meter indicates an input signal is reaching the mixer; it does not confirm the sound is pleasant, correctly balanced or present in the saved file. Playback of a test is still needed.
OBS's Quick Start explains that desktop audio and a microphone may be captured by default, but the selected devices can be wrong or absent. If a meter does not move, or moves for a source you do not want, open Settings → Audio and choose the intended devices manually. The available labels differ between operating systems and hardware. If you use a headset, USB microphone or built-in microphone, identify it by its device name rather than assuming the default input is the one you are speaking into.
For a screen tutorial, decide whether you need microphone narration, computer audio, or both. If you are demonstrating a website with sound, system audio may matter; if you are recording a quiet software walkthrough, it may not. Avoid recording duplicate inputs accidentally, which can make speech sound doubled or echoing. Use the mixer to identify which channel reacts when you speak or play sound, and mute sources that are not part of the intended recording.
A separate USB microphone is optional if you want to improve narration; it is not required to record the screen. Before buying equipment, check whether the microphone you already own gives an intelligible result in the test. Speak at a normal distance and listen for room noise, clipping or an unexpectedly quiet level. If you need practical advice on using the resulting recording in a continuous YouTube format, see the guide to looping pre-recorded videos on YouTube Live with OBS, which is a different workflow from making a local screen recording.
If you record a lesson that is later meant to run continuously as a channel, do not confuse the local capture task with keeping a live broadcast running. StreamNeo can remove the need to leave the recording computer on for that later stage: you upload a finished video and provide your YouTube stream key for a cloud-run 24/7 YouTube broadcast. It is separate from OBS screen recording and is YouTube-only; use it only if your goal changes from making a file to running an always-on channel.
Choose a recording folder, format and quality
Open Settings → Output and locate the recording controls. Set the Recording Path to a folder that you can access and that has enough space for the session. If you use an external drive, confirm that it is connected and mounted before recording. A path on a disconnected drive or a folder with limited space can turn an otherwise correct setup into a failed session.
For the recording format, OBS's Standard Recording Output Guide recommends MKV because an unforeseen interruption is less likely to corrupt the whole file than an ungraceful stop can with MP4. MKV is a good record-first choice when you want to protect the capture from a crash or power interruption. It may not be accepted directly by every editor or upload workflow, which is why OBS provides a conversion step.
If you need an MP4, record to MKV and use File → Remux Recordings after you stop. Select the MKV file and remux it into MP4; remuxing changes the container without the normal process of re-encoding the video. OBS also offers automatic remuxing in its advanced settings. Check the output file afterwards, and keep the original until you know the MP4 opens and contains the expected audio and picture. Do not interpret this as a claim that every MP4 can be made from every recording in every application; use OBS's supported remux workflow and check the result.
Choose quality with the intended edit and available storage in mind. OBS's preset guide distinguishes High Quality, Indistinguishable and Lossless options, among others. Higher-quality choices can increase file size or demand more from the computer, and the outcome depends on the encoder. The OBS Recording Encoder Presets Guide, published in 2023, estimates around 7 GB per minute for Lossless recording and describes it as a very large output. That estimate applies to that Lossless preset guidance, not as a prediction for ordinary recordings. Lossless is not a sensible default for a typical lesson or desktop demonstration.
The Same as stream preset uses stream encoder settings, and OBS notes that recordings cannot be paused with this preset. It is only relevant if you have a reason to match a stream configuration. For a straightforward local recording, start with a quality preset suited to your use and validate it rather than choosing Lossless or the highest-looking option by reflex. The best balance between image detail, file size and resource use varies with content and hardware.
OBS supports software and hardware encoders, with options depending on your operating system, graphics hardware and drivers. Hardware encoding can shift some work away from the CPU, but it is not universally available or necessarily the best-looking option for every machine. Software encoding, resolution, frame rate and a complex scene can each affect the load. If you are unsure, leave the wizard's reasonable starting choice in place and judge a representative test; change one setting at a time if the result needs adjustment.
| Choice | Useful when | Trade-off to check |
|---|---|---|
| Display capture | You need the whole screen, including changes between windows | Notifications or unrelated desktop content can appear |
| Window capture | You want to keep the recording focused on one application | Menus or content outside that window may not be included |
| MKV recording | You want a safer file if recording stops unexpectedly | You may need to remux it for an MP4-only workflow |
| MP4 recording | Your next tool needs MP4 directly | An ungraceful stop can jeopardise the file; confirm your workflow before relying on it |
| Higher quality or frame rate | Fine detail or fast movement matters | Larger output and greater processing demand are possible |
Make and review a short test recording
Before a full session, click Start Recording in the Controls dock and capture a short representative sample. Include the kinds of actions the real recording will contain: open the relevant menus, move the cursor, speak at your normal volume, and play any system sound you intend to include. A static desktop test will not reveal how a fast game or a busy application behaves.
Stop the recording using Stop Recording, then locate the file in the path you chose. Play it in a media player and check four things: is the picture the intended display or window; is the framing correct; can you hear the intended audio; and does playback appear smooth enough for the task? If you plan to edit, open the file in the editor you intend to use. A meter moving in OBS is not a substitute for listening to the saved file.
If the image is blank, cropped, or shows the wrong content, return to the source selection and preview. If the file has no narration, revisit Settings → Audio and confirm the input device and mixer state. If there is no system sound, check the desktop-audio device and test it separately. If the recording stutters, reduce the workload or adjust output demands cautiously, then make another sample. Do not change several unrelated settings at once, because you will not know which change helped.
A useful test should reflect the intended session length and complexity as far as practical, but it cannot prove that every later session will behave identically. An update, a different application, more open windows, a higher-resolution display or a change in drivers can affect capture. Repeat the brief check after a major change to the computer or scene, especially before an important class, client demonstration or scheduled recording.
Once the sample works, use the same scene and settings for the full session. Keep the destination folder in mind, check available disk space, and confirm the recording indicator before you begin. At the end, stop the recording from OBS rather than simply closing the application, then confirm the file is present and plays. If the destination MP4 is needed, remux and inspect it before deleting the original MKV.
If your eventual goal is a live channel rather than an occasional recording, a local OBS session has different failure points from a continuous broadcast. A channel using a looping video needs a plan for continuity and monitoring; the guide to monitoring a YouTube Live playlist stream covers that side of the workflow. For a screen lesson intended as part of an education channel, the cloud setup guide for a 24/7 recorded education channel discusses the separate publishing decision.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Should I record directly to MP4?
You can choose a recording format in OBS, but OBS recommends MKV for recording because an unexpected interruption is less likely to corrupt the whole file. If you need MP4 for an editor or another step, record to MKV and use File → Remux Recordings afterwards. Check that the remuxed file plays before removing the original.
Why is my OBS preview black?
First confirm that you selected a capture source suited to your operating system and the content you want to show. On macOS, check screen-recording permissions; on any system, try another appropriate source if the selected one does not capture the application. Source behaviour varies, so verify the preview and a saved test rather than assuming one option works everywhere.
Why is there no sound in my recording?
Look at the Audio Mixer while you speak or play the sound you expect to capture. If the meter does not move, open Settings → Audio and select the intended microphone or desktop-audio device; if it does move, listen to the saved test to confirm the audio is actually present and at a usable level.
Which OBS quality preset should I choose?
There is no preset that is best for every computer and recording. Higher quality can mean larger files or more processing demand, and the result depends on the encoder and content. Choose a practical starting point, record a representative sample, and adjust only if the playback or file size does not suit your needs.