Latency and Drivers

WASAPI vs ASIO: Which Windows Driver Gives Lower Latency?

WASAPI vs ASIO on Windows: ASIO usually gives lower, steadier latency with a dedicated interface, while WASAPI suits onboard audio and headsets.

On this page
  1. What WASAPI is
  2. Shared mode
  3. Exclusive mode
  4. ASIO
  5. Side by side
  6. Why a dedicated interface usually wins
  7. When WASAPI is the right choice
  8. What driver changes won’t fix
  9. How to test on your system

ASIO usually gives the lowest and most consistent latency on Windows, especially with a dedicated audio interface that has its own ASIO driver. WASAPI exclusive mode can get close to ASIO. WASAPI shared mode has historically added more delay, though it works well for onboard audio and headsets. The driver and buffer setting matter more than the name, so measure your own round trip before you decide.

What WASAPI is

WASAPI stands for Windows Audio Session API. Microsoft introduced it with Windows Vista. It offers two modes, shared and exclusive, which use the Windows audio engine in very different ways.

Shared mode

In shared mode, audio passes through the Windows audio engine. The engine mixes sound from every running app and converts it to the device’s format. The default engine period is about 10 ms per direction, and that adds up. Newer Windows versions can use smaller periods, around 2 to 3 ms at 128 samples and 48 kHz, but only when the driver supports it, and support varies.

Shared mode also forces the device’s Windows sample rate and format. If your DAW project uses a different rate, the audio is resampled, which adds processing work. Set the same sample rate in Windows and in your DAW to avoid this. If you’re unsure which rate to use, see is 44.1 kHz or 48 kHz better for music.

Exclusive mode

Exclusive mode lets one app take sole control of the device and bypass the mixer. Latency can approach ASIO levels. The trade-offs are that other apps lose the device while it is in use, and not every app offers this mode.

ASIO

ASIO is Steinberg’s protocol for a direct path to the interface’s driver. With a native manufacturer driver, it usually gives the lowest and most stable latency. Buffer size still matters, though. A large buffer or a poor driver can cancel out ASIO’s advantage. For an explanation of the protocol, see What Is ASIO?.

Wrappers such as ASIO4ALL and FlexASIO give ASIO-style access to devices that lack an ASIO driver. Their results are similar to WASAPI or slightly better, but they don’t match a native driver.

Side by side

Option Common use Latency Watch for
ASIO with a native driver Tracking with a dedicated interface Lowest and most consistent One device at a time in most DAWs
WASAPI exclusive Interfaces without ASIO drivers; some DAWs Can approach ASIO Silences other apps on that device
WASAPI shared Onboard audio, USB headsets, general use Higher; depends on Windows and the driver Forces the Windows sample rate and format
ASIO4ALL or FlexASIO Devices without an ASIO driver Similar to WASAPI or slightly better Not as good as a native driver

Why a dedicated interface usually wins

A dedicated interface comes with a driver built for its hardware. That driver provides a short, direct path and handles multi-channel input and output well. At the same buffer size, a dedicated interface with its own ASIO driver usually beats WASAPI, especially on round-trip latency.

When WASAPI is the right choice

  • Onboard audio and USB headsets often lack ASIO drivers, so WASAPI is a practical option for them.
  • Some DAWs offer WASAPI as a driver mode. Reaper, Ableton Live, FL Studio, Studio One, and Bitwig all do, so you can compare the modes on your own hardware. The FL Studio audio settings guide walks through the driver choices in one of them.
  • Cubase and Pro Tools rely mainly on ASIO on Windows, so WASAPI is less central to those DAWs.

What driver changes won’t fix

Switching drivers won’t fix crackles caused by CPU or plugin load. If you hear crackles, reduce the load first or raise the buffer, then test the driver again. ASIO is also not automatically low latency. A poor driver or a large buffer can cancel out its advantage.

How to test on your system

  1. In your DAW, choose a driver mode, such as ASIO or WASAPI exclusive.
  2. Set the buffer to 128 samples, or 64 if your system handles it.
  3. Patch an output to an input and run a loopback test, then measure the round-trip delay. The audio latency and buffer size guide explains the method.
  4. Repeat for each driver mode, and note any dropouts.
  5. Keep the combination with the lowest stable round trip.

The complete guide to latency and drivers

Audio Latency and Buffer Size: How to Reduce Delay When Recording
Read the guide

Keep exploring

Guides from other topics

All topics →