Last updated: 2026-01-12

For most people, the fastest way to fix screen recording audio delays is to run a simple checklist in a browser-based studio like StreamYard: match your audio sample rate, simplify your setup, and test a short recording before you hit record for real. If you need frame-level offsets on individual sources (for example, gameplay via a capture card), tools like OBS can add precise sync delays once your base setup is stable.

Summary

• Start with the basics: sample rate, browser choice, CPU load, and extensions are the most common causes of audio lag.
• Use a browser-based studio such as StreamYard for clear, presenter-led recordings without complex local setup or tuning. (StreamYard)
• Only reach for per-source sync offsets in OBS when you have a consistent, measurable delay.
• For quick async clips, lighter tools like Loom can work, but their limits and device load can still cause audio drift. (Loom)

Why is my screen recording audio delayed?

Audio delay (or "lag") usually comes from three things working together:

• Mismatched sample rates between your operating system, mic, and recording tool.
• System overload from too many apps, browser tabs, or high-resolution recording on a modest laptop.
• Extra processing like virtual audio devices, noise filters, or capture cards buffering the signal.

At StreamYard, we optimize for a 48 kHz sample rate and explicitly show how to set your mic and system to 48,000 Hz in your OS audio settings so that your browser studio and hardware are in sync. (StreamYard Help Center) When those fundamentals are aligned, most casual delays disappear without touching any “advanced” menus.

What’s the fastest checklist to fix audio delays?

Use this quick playbook before your next recording session, regardless of tool.

1. Match your sample rate to 48 kHz

   • On both Windows and macOS, set your input device (mic, interface, webcam mic) to 48,000 Hz.
   • StreamYard is built around 48 kHz audio, and our help article walks through where to change this in your OS. (StreamYard Help Center)

2. Close background apps and browser tabs

   • CPU spikes are a classic cause of audio/video drift.
   • Even Loom recommends shutting down unused tabs and apps when you see lag, because freeing RAM and CPU often clears the issue. (Loom Support)

3. Use a modern browser and disable extensions

   • If you record in the browser, test Chrome or Edge, and temporarily disable extensions that intercept audio or video.
   • Our guidance at StreamYard explicitly calls out browser and extension conflicts as a common root cause of audio issues. (StreamYard Help Center)

4. Lower your recording load if needed

   • Drop resolution or frame rate if your laptop fans are roaring.
   • Loom’s support team points out that reducing resolution or FPS can noticeably reduce lag when your machine is under strain. (Loom Support)

5. Record a 20–30 second test clip

   • In StreamYard, you can open a studio, share your screen, speak for 30 seconds, and watch the cloud or local recording back before your real take.
   • If lips and audio match here, your core pipeline is solid; any remaining issues are usually app-specific.

For most US creators using typical laptops, this checklist fixes the vast majority of audio delay problems without any deep technical work.

How does StreamYard help avoid audio delays in the first place?

If your main goal is clear, presenter-led screen recordings—think tutorials, walkthroughs, or live-style demos—StreamYard is designed to keep you out of the weeds.

Here’s what that looks like in practice:

• Browser studio, no heavy install
  You join from your browser, bring in your screen, camera, and guests, and start recording. That alone sidesteps a lot of driver-level complexity that desktop apps introduce. (StreamYard)

• Presenter-visible layouts and audio controls
  You can see exactly how your screen and camera are framed while independently controlling screen audio and mic audio. That visual feedback makes it obvious if something is muted or doubled.

• Local multi-track recordings for cleanup
  On all plans, StreamYard supports local recordings, and on paid plans those local tracks are unlimited, subject to your device and storage. (StreamYard Help Center) If a guest’s audio is a few frames off, you can nudge it into place later in your editor without re-recording the entire session.

• Stable studio defaults
  Because we tune the studio around 48 kHz audio and sensible quality settings, many people never need to touch advanced menus. You focus on your story, not your encoder.

Add in support for portrait and landscape outputs, branded overlays and logos, presenter notes only you can see, and multi-participant screen sharing, and you get a workflow that stays predictable even as your productions grow.

When should you use OBS to fix audio delays?

OBS is powerful desktop software used for screen capture and streaming, especially when you need fine-grained control over every input. (OBS) It also gives you tools to fix stubborn, consistent audio delays.

Use OBS when:

• You have a capture card (for example, HDMI gameplay) that’s always delayed by the same amount.
• You need to apply per-source audio offsets in milliseconds.
• You’re comfortable digging into audio and encoder settings.

Two key tools inside OBS:

1. Global sample rate
   In OBS settings, you can set the audio sample rate (often to 48 kHz) so it matches your devices and reduces drift over long recordings. OBS forum guidance specifically points to matching sample rates to prevent video/audio drift. (OBS Forums)

2. Sync Offset in Advanced Audio Properties
   OBS exposes a Sync Offset field per audio source, which lets you delay that audio by a set number of milliseconds to match the video. (Volume Support)

A common scenario: your capture card manual says its average delay is 1450 ms. You can plug that number into OBS as a sync offset so your commentary lines up with the gameplay feed. Some device vendors, like Elgato, provide these measured delays in their documentation. (Elgato Help)

That level of control is powerful, but it also means more chances to misconfigure something. Many teams find it easier to do their main recording work in a simpler studio like StreamYard, then reserve OBS for situations where device-specific offsets are truly necessary.

Where does Loom fit if I’m just doing quick screen recordings?

If your primary use case is quick async feedback—like a 3-minute bug report or a status update—Loom is a familiar option. It focuses on simple screen + camera bubble recordings and fast link sharing.

But even here, the same sources of audio delay show up: system load, resolution, and outdated apps. Loom’s own guidance suggests closing unused apps and tabs and lowering resolution or frame rate when you see lag, because that reduces pressure on your CPU and GPU. (Loom Support)

For many teams that also run live events or multi-participant demos, it’s more efficient to:

• Use StreamYard as the primary studio for polished, reusable recordings and live shows.
• Export those recordings and reuse them wherever you like, instead of maintaining separate tooling and troubleshooting paths.

Because StreamYard pricing is per workspace instead of per user, growing a team around a shared studio often ends up more economical than scaling individual-per-seat tools for every creator. (Loom Pricing)

What OS audio settings and hardware habits reduce delay long term?

Once you’ve cleared up the immediate issue, it helps to lock in a few habits so audio delays stay rare:

• Standardize on 48 kHz across your mics, interfaces, and recording tools.
• Use wired headphones and mics when possible; Bluetooth introduces its own latency that can confuse monitoring.
• Avoid stacking virtual devices (multiple virtual cables, filters, and mixers) unless you truly need them.
• Restart your recording app if you change audio hardware mid-session; cached buffers can cause drift.

In StreamYard, the workflow is intentionally straightforward: pick your mic and camera in the studio, confirm levels, do a short test recording, and you’re ready. By keeping the pipeline clean, we help you spend more time presenting and less time chasing sync gremlins.

What we recommend

• Default path: Use StreamYard’s browser-based studio for most screen recordings, set everything to 48 kHz, and run a 30-second test clip before important sessions. (StreamYard Help Center)
• For stubborn device delays: When you have consistent, measured lag (especially from capture cards), configure matching sample rates and—if needed—per-source sync offsets in OBS.
• For quick async clips: Lightweight tools like Loom can handle short updates, but the same CPU and resolution rules apply, so keep your system load under control. (Loom Support)
• For teams and recurring content: Build your recording workflow around a studio that balances reliability, quality, and simplicity—StreamYard is designed to be that default for most creators and small teams in the US. (StreamYard)