OBS Studio · Practical guide

Where Did OBS Save the Recording? Check the Path and Write Access

Locate a finished recording, verify the active recording folder, and test a new destination before trusting it with a long session.

START HERE

Check the Recording Path in the active profile’s Output settings and make a short named test. Confirm that the destination exists, is writable and has room, then open the resulting file from that exact folder.

Locate a finished recording, verify the active recording folder, and test a new destination before trusting it with a long session.

In this guide
Before you start
  • Access to the computer and profile used for the recording.
  • A local folder where you can safely create a short test file.

Start with the active recording settings

A missing file is not automatically a failed recording. You may be looking in the folder used by a different profile, a previous installation or a removable drive that is no longer connected. Write down which OBS setup made the attempt before searching several similarly named Videos folders.

OBS identifies Recording Path under Output settings as the destination for files. Inspect that value in the relevant profile and open the exact folder. Sort by modification time and compare the timestamps with the session you remember, including any automatic file splitting you already configured.

Distinguish a completed file from an output that never started

Recall whether the recording timer actually ran and whether you stopped the output normally. An error at Start Recording needs investigation before file searching will help. Keep any error message verbatim in your notes rather than replacing it with a general statement that the recording disappeared.

If the destination is an external drive or synchronized folder, first confirm it is currently available. Do not rename or delete unfamiliar partial files while diagnosing the issue. Copy a potentially important file before attempting any repair or conversion so the original evidence remains intact.

Prove the destination with a short recording

  1. Check the existing path

    Open Settings → Output and inspect Recording Path for the selected profile. Confirm the drive and folder exist and have sufficient free space.

    Look for: The intended destination is available and not merely remembered from an older setup.

  2. Try a simple local destination

    If the original location is uncertain, choose a new local test folder that your user account can write to. Keep the previous path in your notes. Record a few seconds and stop normally.

    Look for: A new file appears in the known folder or OBS gives a concrete error to investigate.

  3. Open the actual result

    Open the new file from that folder and check picture, sound and duration. Record the filename and full folder path in your session note.

    Look for: The path check proves both file creation and usable playback, not just that a directory was selected.

Plan storage from your own sample

Use a representative sample to estimate storage for the intended session, leaving a margin for content that is harder to encode and for other files on the drive. Avoid promising a fixed hourly size from resolution alone. Encoder, quality settings and the recorded material can all change the resulting file size.

For a long session, check the destination before starting and again during a break if practical. If you move completed recordings elsewhere, verify the copied file before deleting the original. A sensible folder structure helps you distinguish current capture files from exports and compressed review copies.

Use the failure pattern to narrow the cause

If the local test succeeds but the original destination fails, focus on that drive, folder access or availability. If neither destination works, keep the error and session log and inspect the recording configuration. Changing the folder repeatedly will not fix an encoder that never starts.

After restoring the intended location, make one final short recording there. Confirm the active profile and path before a real session, especially after importing settings or switching between recording jobs. The useful outcome is a file you can find and play, not merely a reassuring folder name in Settings.

Still stuck?

A local test saves but an external destination does not.

Check that destination’s availability, free space and write access before changing encoder settings.

Keep troubleshooting

Check the model and connection before trying another change. The device page gathers the related symptoms.

More help with OBS Studio ↗

Sources & references

Based on the linked first-party OBS documentation checked on 4 November 2026. The exercises and acceptance checks are editorial workflows for you to run; no hands-on OBS session or hardware benchmark is claimed.

  1. OBS — Standard Recording Output Guide ↗Checked 2026-11-04

Spotted something out of date? Let Alex know.

How we put our guides together ↗
READ NEXT

A few places to go from here.

All stories

OBS Automatic File Splitting: Cut Long Recordings Safely

Turn on Automatic File Splitting in OBS advanced output, split by time or by size, then check two files side by side so nothing goes missing at the cut.

OBS NVENC Fails to Start Recording: Read the Specific Error

Match the failed codec and GPU capability before reinstalling software.