How to Fix Latency in Logic Pro

I was mid-vocal session when a singer stopped and said, "I keep hearing myself late." The track had 47 plugins across 19 channels, and my I/O buffer was set to 512. That's the problem in one sentence. Here's how to fix it.

Latency is a delay between a sound entering your audio interface and you hearing it back through your headphones or monitors. It shows up in two main ways: input monitoring latency when you're recording, and playback sync issues caused by plugins. Both are solvable. Some take 30 seconds. One requires understanding how Logic's plugin delay compensation (PDC) actually works. If you still search for this as Logic Pro X latency, the same settings apply in current Logic Pro versions.

Quick fix for Logic Pro latency:

• Use wired headphones, not Bluetooth.
• Go to Logic Pro > Settings > Audio > Devices.
• Set I/O Buffer Size to 64 or 128 samples.
• Turn on Low Latency Monitoring Mode from the control bar or Logic Pro > Settings > Audio > General.
• Remove linear-phase EQs, look-ahead limiters, oversampling plugins, and convolution reverbs from the Stereo Out while recording.
• Use direct monitoring on your audio interface if you need the fastest dry headphone signal.

How to Fix Latency in Logic Pro: Start With Buffer Size

The I/O buffer size is the first thing to adjust. Go to Logic Pro > Settings > Audio > Devices and look for the I/O Buffer Size pop-up menu. Depending on your audio device, the options usually range from 32 or 64 up to 1024 samples.

Lower buffer sizes mean lower latency. At 44.1 kHz, the buffer itself represents about 1.5 ms at 64 samples or 11.6 ms at 512 samples. Your real roundtrip latency will be higher because the audio interface and driver add their own delay on top of that. Logic shows you the actual roundtrip figure below the buffer size menu, and that number is the one to watch.

When recording, set this to 64 or 128 samples. That's usually enough to make monitoring comfortable without hitting CPU overloads. The catch: smaller buffers demand more from your processor. If you're running a dense mix with a lot of software instruments and effects, 64 samples might cause audio dropouts or system overload alerts. When that happens, you have two options: bounce plugins to audio to free up CPU, or use Low Latency Mode instead.

For mixing sessions where you're not recording live input, set the buffer to 512 or 1024 samples. It gives Logic more processing headroom and you won't feel any monitoring delay because there's nothing to monitor.

Keep PDC set to All for normal playback alignment. If a software instrument still feels late while you're playing it live, the real fix is usually a lower I/O buffer, Low Latency Mode, or removing high-latency plug-ins from the monitored signal path. PDC handles playback sync; it doesn't reduce the monitoring delay you feel when playing in real time.

Certain plugins add latency by design. Look-ahead compressors, linear-phase EQs, and heavy convolution reverbs like Space Designer all need extra processing time. A single look-ahead compressor on your master bus can add 20 or more milliseconds of delay to the signal you're monitoring while you record.

Low Latency Mode temporarily bypasses latency-inducing plug-ins and may also affect sends on record-enabled or input-monitored tracks if those sends contribute to latency above the Limit setting. Turn it on from the Low Latency Monitoring Mode button in the control bar, or go to Logic Pro > Settings > Audio > General and enable Low Latency Monitoring Mode.

You set the threshold in Logic Pro > Settings > Audio > General, under Plug-In Latency > Limit. The default is 15 ms. I keep mine at 11 ms, which is tight enough to feel responsive but forgiving enough to leave most channel-level plugins active.

One thing most tutorials get wrong about Low Latency Mode: it doesn't delete the plug-ins from your session or permanently change your mix. It only changes what Logic lets you monitor while recording. Normal playback uses your full plug-in chain again once you stop tracking. You're not sacrificing your mix to fix your monitoring.

Plugin Delay Compensation: Fix Playback Sync Problems

Plugin delay compensation is different from input monitoring latency. PDC affects playback sync across your entire project, not just what you hear in your headphones while tracking.

Every plugin adds some amount of delay to the signal passing through it. Apple's Logic Pro documentation describes how Logic automatically detects the channel strip with the highest plugin-induced latency and delays all other channels to match, keeping everything in sync during playback.

You configure this at Logic Pro > Settings > Audio > General > Plug-In Latency > Compensation. The useful options are:

• Off: Turns plugin delay compensation off entirely. Avoid this unless you're troubleshooting a specific issue.
• Audio and Software Instrument Tracks: Logic shifts regions on individual tracks to compensate. Use this when your latency-inducing plugins are only on audio or instrument tracks.
• All: Logic delays the audio stream on every channel strip individually, including aux channels and the output. Use this when you have latency-causing plugins on bus channels or your master output.

If you have compressors or limiters sitting on sub-groups or your stereo output, "All" is the setting you want. Switching from "Audio and Software Instrument Tracks" to "All" fixed a 50 ms timing gap in one project I'd been chasing for two days.

Audio Interface Latency and Direct Monitoring

Some latency is fixed and can't be reduced inside Logic. The analog-to-digital and digital-to-analog conversion in your audio interface adds a delay that Logic has no control over. Two interfaces at the same 64-sample buffer can report very different roundtrip latency because their drivers, converters, and internal safety buffers are different. Check Logic's roundtrip readout for your specific setup rather than relying on any published figure.

If you're monitoring through your interface's direct monitoring feature, you bypass Logic's software monitoring path, I/O buffer, and plug-in processing. You still have the interface's own conversion path, but the monitoring delay is usually low enough to feel effectively real-time. Direct monitoring sends your input signal straight to your headphones through the interface before Logic's software monitoring path gets involved. There's no plugin processing on that signal, but if you're recording dry vocals or guitar to process later, it's the fastest practical option.

Most audio interfaces have a direct monitoring option in their companion software or via a hardware switch. Check your interface manual if you're not sure where to find it.

Bluetooth headphones are a completely different problem. Apple recommends using Bluetooth devices with Logic Pro for mixing or listening only, not tracking. Bluetooth audio adds delay that makes real-time monitoring uncomfortable at best. Use wired headphones for any recording session.

Sample Rate and Latency: 44.1 kHz, 48 kHz, or 96 kHz?

Higher sample rates produce less input monitoring latency. A project running at 96 kHz will have lower input latency than the same buffer size at 44.1 kHz, because each buffer represents a shorter duration of audio at the higher rate.

The tradeoff is real. Projects at 96 kHz produce larger audio files and put more load on your CPU and disk. Plugins also run harder at higher rates. On Apple Silicon Macs, this is less of a concern than it used to be, but it's still a factor on large sessions. For most recording work, 44.1 kHz or 48 kHz with a 64 or 128 sample buffer is the practical range.

Set your sample rate at the start of a project in File > Project Settings > Audio. Changing it mid-project requires converting all your recorded audio, which takes time and can introduce issues with Flex Time edits already made in the session.

Troubleshooting Latency When the Usual Fixes Don't Work

Sometimes you've set a low buffer, turned on Low Latency Mode, and there's still a noticeable delay. A few less-obvious culprits:

Third-party plugins with unreported latency. Most well-built plugins report their processing delay to Logic, which lets PDC account for it correctly. Some older or poorly coded third-party Audio Units don't report their latency at all. Logic can't compensate for what it doesn't know about. If you suspect a specific plugin, remove it temporarily and see if the timing improves.

Plugins on bypassed channels still introducing delay. In some sessions, bypassed plug-ins on auxes or the Stereo Out can still keep the project in a high-latency compensation state. I ran into this directly: removing all plugins from a drum bus and master channel dropped recorded-signal delay from 50 ms to 0 ms in one session, even though those plugins were bypassed. If you're fighting unexplained timing drift during tracking, removing plugins from unused aux channels and bus sends is worth trying.

Process Buffer Range. If low I/O buffer settings cause overloads, check Process Buffer Range in Logic Pro > Settings > Audio > Devices. Smaller settings can feel more responsive, while larger settings give Logic more processing headroom during heavy sessions. This doesn't replace I/O buffer size adjustment, but it can help on sessions that hover near overload.

Recording Delay slider. Also in Logic Pro > Settings > Audio > Devices, the Recording Delay slider lets you manually offset the timing of your recorded audio in samples. It won't fix real-time monitoring latency, but it can correct timing drift on recorded takes if PDC isn't fully solving it.

Rosetta 2 mode on Apple Silicon. If you're running Logic under Rosetta 2 to support older third-party plugins, latency behavior can differ from native Apple Silicon mode. Running natively is usually the cleaner first troubleshooting state. Check Finder > Applications > Logic Pro > Get Info to see if "Open in Rosetta" is checked.

Low Latency Mode vs. Direct Monitoring

Low Latency Mode keeps you inside Logic's signal chain. You hear your plugins (those that fall under your latency threshold), you hear the click track, and the resulting recording lands correctly in your project. It's the right choice for most overdub sessions.

Direct monitoring through your audio interface is faster and simpler. Zero plugin coloring on your headphone signal, but you also hear nothing that Logic is processing. No reverb, no compression, no click track blended from Logic's output. Good for quickly punching in a dry take; not ideal if the performer needs to hear the full mix to play along.

Many producers run both: direct monitoring at the interface level for real-time feel, plus Low Latency Mode active in Logic so session playback stays tight. The interface handles the zero-latency headphone feed, and Logic handles the mix the performer hears in their phones from the control room return.

Frequently Asked Questions About Latency in Logic Pro

What causes latency in Logic Pro?

The main causes are I/O buffer size, analog-to-digital conversion in your audio interface, and plugin processing delay. Higher buffer sizes and more latency-inducing plugins both push latency up. Bluetooth headphones add their own layer on top of all of that.

What is the best I/O buffer size for recording in Logic Pro?

64 or 128 samples covers most recording sessions. At 44.1 kHz, 128 samples gives you around 3 ms of output latency, which is comfortable for most singers and players. Go lower if you're on a fast M-series Mac with a clean session. Go higher if you're mixing a dense project and just need to print a few final takes.

What does Low Latency Mode do in Logic Pro?

It temporarily bypasses latency-inducing plugins and may also affect sends on record-enabled or input-monitored tracks if those sends contribute to latency above your Limit setting. It doesn't delete those plugins or change your mix. Normal playback uses your full plugin chain again after you stop recording.

Why is my Logic Pro project still out of sync even after fixing latency?

Plugin delay compensation may not be set correctly. Go to Logic Pro > Settings > Audio > General and confirm that Compensation is set to "All" if you have plugins on bus channels or your master output. Also check for third-party plugins that don't report their own latency to Logic.

Can I use Bluetooth headphones to record in Logic Pro?

Apple recommends Bluetooth devices for mixing or listening only, not tracking. Bluetooth audio delay makes real-time monitoring uncomfortable. Use wired headphones for recording sessions.

Does Apple Silicon reduce latency in Logic Pro?

Apple Silicon lets Logic run lower buffer sizes without the CPU overloads that hit Intel Macs at the same settings. M-series Macs tend to handle 64-sample buffers on larger sessions where an Intel machine would need 256 or higher. Running Logic natively rather than under Rosetta produces the most consistent results.

Related guides: Why your mic is quiet in Logic Pro, Logic Pro Stem Splitter, Export Logic Pro as MP3

Sources: Logic Pro User Guide — Apple Support · Logic Pro — Apple