
Use OBS Render Delay only when the picture reaches the recording before the matching sound. The filter delays a source image by a specified number of milliseconds. It cannot bring an already late picture forward, and a fixed offset cannot by itself correct synchronization that keeps drifting during a recording.
Key Takeaways
- Establish which signal arrives first in a saved recording.
- Render Delay changes picture timing for the selected source.
- Check a later sync cue as well as the opening cue.
Establish the direction of the mismatch
The OBS Render Delay documentation describes the filter as delaying source-image rendering, including webcam synchronization with microphone audio. Start with that limited purpose rather than adding delay to every source.
Record a private, visible and audible cue, such as a clap, using the intended picture and microphone routes. Open the saved file and identify whether the contact image precedes or follows its sound. Headphone monitoring can introduce a separate listening delay; the Bluetooth monitoring comparison explains why that alone is insufficient evidence.
Delay the source that is early
- Preserve the current scene configuration and record the affected source name.
- Open that picture source's Filters and add Render Delay.
- Note the existing Delay value before making a change.
- Increase the millisecond delay only if the picture is early.
- Record another cue and inspect the saved result using the same playback route.
Choose a value from the observed mismatch, then refine it through comparison. There is no universal delay for every webcam, microphone or computer. Keep other routing and processing stable while testing, otherwise an apparent improvement will not isolate this adjustment.
Distinguish an offset from drift
Imagine a proposed narrator introduction in which a face appears to complete each syllable before the corresponding sound. A consistent offset at the beginning and end makes an image-delay comparison relevant. If the opening aligns but the end does not, adding a larger fixed delay simply moves the point where the recording happens to agree.
Use a second cue later in a representative recording. The separate capture-buffering guide concerns incoming playback stability and latency, not a substitute for an explicit timing correction. Do not change buffering merely because the Delay field exists.
Approve the recorded relationship
Compare the opening cue, later cue and a natural spoken passage. Accept the setting only when the required picture and sound agree throughout the intended interval in the saved candidate. Record the source, delay and remaining limitations with the handoff.
If picture is already late, stop adding image delay and investigate the relevant capture or audio path. If timing drifts, preserve the evidence for a clock or source-timing diagnosis. This procedure proposes a synchronization check; it does not report a tested device configuration.
Related tasks
- Should I Enable OBS Capture-Device Buffering to Fix Stutter?
- Why Is My Dance Out of Sync on Bluetooth Headphones but Fine in the Export?
- I requested 10 seconds in 16:9. How do I check the actual AI video file?
Sources and scope
- OBS Render Delay Filter: Render Delay delays source-image rendering in milliseconds, and is intended for picture/microphone sync.
Documentation-based guidance. No account access, hands-on test, measured speed gain, search volume or AI citation rate is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.