Set OBS filename formatting in Advanced settings using the variables listed by the installed version. Keep a sortable date and time, add a short project label, and test two consecutive recordings before relying on the pattern.
Choose a useful recording filename pattern, keep timestamps unique, and verify the resulting names with consecutive test recordings.
In this guide
Before you start
- A known recording folder and a profile used for one defined project.
- A note of the current filename format before editing it.
Design the name for the moment you need to find the file
Imagine opening the recording folder two weeks later. A useful name should tell you which project the file belongs to and when it was made without opening every video. Keep the project label short enough to read in a normal file list and leave detailed session notes in a separate log.
OBS exposes recording filename formatting in Advanced settings. The field’s help lists the variables supported by the installed version. Use that list instead of copying a long pattern from an old tutorial whose placeholders may not match your build.
Keep the parts that make separate takes identifiable
Use a consistent order: project, date and time is easy for people scanning by project, while date first helps a chronological archive. Include enough time detail to distinguish nearby takes. A name that only contains a date becomes ambiguous when you start and stop several times in one session.
Avoid putting private client names, account identifiers or sensitive topics into a filename that may later appear in a screenshot or shared link. Use a short internal project code if needed. Also keep the naming pattern separate from your decision about where files are stored.
Apply and test the naming rule
Inspect the supported variables
Open the filename-format field in Advanced settings and read its available-variable help. Copy the current value into your notes before editing.
Look for: You know which date and time tokens your installed OBS supports and can restore the starting pattern.
Add the smallest useful label
Combine a short project label with supported date and time variables. If your workflow needs filenames without spaces, inspect the recording option for generating names without spaces.
Look for: The pattern describes the project while retaining clear timestamps.
Make two consecutive recordings
Record a few seconds, stop, then record another take. Open the recording folder and compare both names and playback durations.
Look for: Two separate files have understandable, distinct names and neither take is mistaken for the other.
Check the other files your workflow creates
If you split recordings or remux them after capture, inspect the resulting group of files too. Make sure you can tell an original capture from a container-converted copy and from a later edited export. The best name is one that remains understandable through the whole handoff.
For an editor, provide the actual file list and a brief note about the sequence. Do not rely on a filename to communicate which audio track contains the microphone or whether a take is approved. Names help navigation; they cannot replace a clear handoff when the content has multiple versions.
Keep the naming convention small enough to sustain
Once the pattern works, save a sample name in the project notes. After changing profiles or importing a configuration, make another short test instead of assuming the same pattern is active. If a token appears literally in the filename, return to the installed field’s help and correct the pattern there.
Resist adding every imaginable detail to the name. A long string of settings becomes hard to scan and can become inaccurate after an encoder change. Preserve a stable project label and timestamp, then record technical settings alongside the session when they are actually needed.
Still stuck?
A formatting token appears literally in the filename.
Check the supported-variable help for your installed OBS version and repeat the two-file test after correcting the token.
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.
- OBS — Standard Recording Output Guide ↗Checked 2026-11-04
Spotted something out of date? Let Alex know.
How we put our guides together ↗