FL Studio Audio Crackling: Fix Clicks and Pops

A crackle during playback does not automatically mean your mix is clipping, your interface is broken or FL Studio needs reinstalling. Most cases fall into one of four buckets: the real-time audio buffer runs dry, a driver or sample-rate chain is unstable, one plugin misses its processing deadline, or the click is already part of an audio edit or rendered signal.

The useful first move is not “set the buffer to 2048.” It is to find out when the noise happens. This guide gives you a short diagnostic path, then the fix that fits the result. Make one change at a time and replay the same difficult section. Otherwise a clean pass can look like a cure when the crackle was only intermittent.

First, identify which kind of crackle you have

Open the project, loop the section that fails most reliably and run these four checks before touching a setting:

1. Play the section in FL Studio and listen for the crackle.
2. Render that same range to WAV and listen outside FL Studio.
3. Open a new empty project and play one stock instrument.
4. Play audio from another app through the same headphones or speakers.

A clean offline render is a strong clue. Image-Line’s current Audio Settings manual, checked September 4, 2026, says buffer underruns matter during live playback; an exported glitch is not created by the same real-time buffer shortage. Treat those as different faults instead of applying the same buffer fix to both.

Watch the underrun counter and FL Studio CPU meter

Open Options > Audio settings, reset or note the Underruns count, then replay the troublesome section. If the count climbs at the same moment you hear clicks, pops or stuttering, the audio buffer is running out before FL Studio finishes the next block of sound.

Also watch FL Studio’s CPU panel at the top. It does not mean the same thing as the percentage in Windows Task Manager or macOS Activity Monitor. The official CPU panel explanation says FL Studio measures how much of each short audio-buffer deadline was used. Your operating system measures overall processor capacity across a much longer interval. A project can therefore crackle while the system meter still looks comfortable.

Do not diagnose by the number alone:

• An underrun added while a project or plugin loads is not a fault if you hear no glitch.
• A live click can still be driver-related even when the counter does not increase; some driver paths bypass that counter.
• A red or near-full FL Studio CPU meter points to a missed real-time deadline, not necessarily a weak computer.

Select the right audio driver before raising the buffer

On Windows, choose the native ASIO driver supplied by your audio interface manufacturer when one is available. Image-Line currently recommends that route ahead of generic alternatives because it communicates directly with the hardware and usually offers the best stable latency. Update it from the interface maker, never from a third-party driver-download site.

If you do not own an interface, FL Studio ASIO is the practical starting point for a built-in sound device. ASIO4ALL can combine or expose devices that other routes cannot, but its extra device panel also makes it easy to activate an input or output you do not need. On macOS, select the intended Core Audio device and install the manufacturer’s control software when the interface provides it.

After switching drivers, confirm the actual input and output. “The crackling stopped” is not a win if FL Studio silently moved from your interface to laptop speakers. Our FL Studio audio settings guide covers the full device and latency setup; this page stays focused on crackle diagnosis.

Increase buffer length in controlled steps

A longer buffer gives FL Studio more time to build each block of audio, but it also increases the delay you feel while recording or playing a MIDI keyboard. The goal is the smallest value that plays the current project cleanly, not the smallest number the panel accepts or a universal number copied from a video.

1. Loop the failing section.
2. Open Audio Settings; on Windows, use Show ASIO panel if the driver owns the buffer control.
3. Write down the current buffer value.
4. Move up one available step, apply it and replay the loop.
5. Stop when the underrun count stays still and the section sounds clean.

Processor architecture matters. Image-Line’s performance guidance recommends at least about 10 ms for Intel and AMD systems, then testing upward. Apple Silicon behaves differently: Image-Line recommends starting at 128 samples and stepping through 192, 256, 512 and 1024 only as needed, because an unnecessarily long buffer can keep a light project on efficiency cores. That is why “always make the buffer bigger” is poor advice for every Mac.

Save two working values if you record and mix on the same machine: a low stable value for tracking, and a more forgiving one for a dense mix. Do not turn on Triple buffer as a permanent reflex; the manual notes that it doubles latency and helps only with some drivers near overload. Test it, and turn it back off if it changes nothing.

Match sample rates across FL Studio, the driver and the OS

A sample-rate mismatch can force resampling, prevent a device from opening correctly or produce unstable audio when two applications fight over the same hardware. Check the rate in FL Studio, the interface control panel and the operating system’s input and output device settings.

Use one rate throughout the chain. Image-Line recommends 44.1 kHz by default, or 48 kHz when that is the supported choice, and warns that 96 or 192 kHz adds substantial CPU work. A higher number is not a free quality upgrade. If a session was created for a specific delivery rate, keep that rate. Make every device agree before looking for a more exotic cause.

When the interface uses an external digital clock, confirm that exactly one device is the clock master. Clock faults tend to sound like irregular ticks rather than a crackle that rises with project complexity. If you use only an analog or USB interface with its default internal clock, leave the clock source alone.

Find the plugin that misses the deadline

If a blank project is clean but one production crackles, do not disable twenty plugins at random. Double-click FL Studio’s CPU panel or open View > Plugin performance monitor. Sort by the recent percentage or peak, loop the difficult section and look for a plugin that jumps when the noise appears. The official monitor reference explains that its percentage is the share of the audio buffer a plugin needs.

Bypass the suspected plugin and replay the loop. A lower CPU reading is not enough; the crackle must disappear at the same point. Then try, in order:

• Update the plugin and FL Studio.
• Reduce oversampling, voices or high-quality real-time modes inside that plugin.
• Close its interface and other open plugin windows.
• Consolidate the instrument or effect-heavy track to audio when the sound is settled.
• Test the plugin maker’s alternative format, such as VST3 versus VST2 on Windows or VST versus AU on macOS.

Use wrapper options such as fixed-size buffers only for the plugin that needs them. Image-Line’s Plugin Wrapper manual treats those settings as targeted compatibility tests, not switches that every plugin should receive. If the culprit sits inside a large modular chain, the FL Studio Patcher guide will help you trace and simplify that route.

Keep recording latency low without recording crackle

Recording creates the hardest compromise: you want a short buffer so the monitored voice or instrument feels immediate, but a short buffer gives the project less time to process. Start a recording session from a light version of the project rather than forcing a mastered arrangement to behave like a tracking template.

• Use the interface manufacturer’s native driver and connect the interface directly, without a USB hub while diagnosing.
• Temporarily bypass look-ahead limiters, linear-phase processors and oversampled effects on the monitored path.
• Consolidate finished virtual instruments or disable their heavy processing while tracking.
• Use direct monitoring on the interface when available; then mute the duplicate software-monitored return.
• Raise the buffer one step if the recorded take still contains gaps or ticks.

If only the input crackles, make a short recording with plugins bypassed. A damaged cable, overloaded preamp, unstable USB connection or mismatched clock can be printed into the file; no playback buffer setting can remove noise that was recorded at the source. For Mixer input routing and monitoring, follow the FL Studio Mixer tutorial.

Reduce project load without wrecking the arrangement

Once the driver, buffer and sample rate are stable, reduce only the work the project does in real time. Start with reversible moves:

1. Close plugin windows with Alt/Option+F12.
2. Lower real-time oversampling or “high quality” modes that are meant for export.
3. Consolidate the heaviest settled instrument or Mixer track.
4. Shorten needless synth release tails and reduce unused polyphony.
5. Keep independent heavy instruments on independent Mixer paths where possible.
6. Close screen recorders, video calls and other applications that interrupt real-time audio.

Smart Disable can save CPU by sleeping silent plugins, but time-based or long-decay effects can misbehave when it is enabled. Test the global macro, then disable Smart Disable for any plugin that cuts tails, starts late or loses sync. Do not lower the project PPQ as a first response: it changes timing resolution, and Image-Line only flags unusually high settings above 192 PPQ as a meaningful CPU concern. The normal 96 PPQ default is not usually the villain.

This is the stopping point for crackle repair. A separate High CPU guide will own sustained project optimization, multicore routing and heavy-plugin strategy so this page does not compete for that broader search intent.

If the FL Studio CPU panel remains close to its deadline after the driver, buffer and sample rate are stable, continue with the high-CPU workflow. That guide owns plugin scheduling, Smart Disable, rendering and project-load decisions; this page stays focused on proving where the clicks enter the signal path.

Check the system when the counter stays still

If the Underruns count does not move and every application crackles, step outside FL Studio. Play a known clean file, then test another output device. Wired headphones direct from the computer are a useful comparison against an interface or Bluetooth path.

On Windows, also disable optional Audio Enhancements on the monitoring device while mixing; the Audio Settings manual notes that FL Studio ASIO sits on top of the Windows audio stack and can be affected by them. Do not install “driver booster” utilities or change ten power settings from an old forum post. Confirm one system-level cause with an A/B test.

Fix clicks that appear in the export

An offline export is not constrained by the live audio buffer, so raising buffer length is not the fix for a click that is rendered into the file. First import the WAV back into an empty FL Studio project and find the exact sample where the click occurs.

If it lands on an Audio Clip cut, add a tiny fade or use FL Studio’s declicking options. The Audio Clip manual explains that zero-crossing edits and short fades prevent a sudden waveform jump at a slice boundary.

If the click repeats at a plugin, bypass that plugin and render again; then update it or test its wrapper’s fixed-size buffer option. If the Master meter is driven hard and the waveform is visibly flattened, reduce the level before the final output. The official mixing guidance warns that sustained output clipping can render distortion and crackle.

Do not run a declicker across the full master until you know the fault is actually printed noise. It can soften legitimate drum transients while leaving a misbehaving plugin untouched. Our FL Studio mastering guide covers final level, limiting and export checks after the click itself is gone.

Use this five-minute repair order

1. Compare live playback with an offline WAV render.
2. Watch the Underruns counter and FL Studio CPU panel on the same loop.
3. Select the correct native ASIO or Core Audio device and confirm its outputs.
4. Increase the buffer one supported step at a time; follow the Apple Silicon exception.
5. Match the sample rate across FL Studio, the interface and the operating system.
6. Use Plugin Performance Monitor and bypass one suspect plugin.
7. Test a dry recording input or a known-clean wired output.
8. For export-only clicks, inspect clip boundaries, plugin behavior and Master clipping.

If none of those tests changes the symptom, save a diagnostic copy of the project and remove half the channels, then half again, until the fault disappears. That binary search finds a bad route or plugin faster than deleting channels one by one. Keep the original project untouched.

When the problem also occurs in a blank project with the correct driver and a known-clean output, capture the FL Studio version, operating system, interface model, driver version, sample rate and buffer setting before contacting Image-Line or the interface manufacturer.

Frequently asked questions

Why is my audio crackling in FL Studio?

During live playback, the most common cause is a buffer underrun: FL Studio or the audio driver did not finish the next block of sound in time. A mismatched sample rate, unstable driver, heavy plugin, recording-chain fault, clipped signal or Audio Clip boundary can produce similar noise, so compare live playback with an offline render first.

How do I stop crackling in FL Studio?

Loop the failing section, watch the Underruns counter, select the correct audio driver and raise the buffer one step at a time. If the counter stays still, match sample rates and use Plugin Performance Monitor to bypass the plugin whose peak matches the crackle.

What buffer size should I use to prevent crackling?

Use the smallest supported setting that plays your project without audible glitches or a rising underrun count. Image-Line recommends starting around 10 ms for Intel and AMD systems; on Apple Silicon, start at 128 samples and step through the supported values only as needed.

Why does FL Studio crackle when the CPU is low?

FL Studio’s CPU meter tracks each short audio-buffer deadline, while the operating system reports overall processor use across cores and a longer time window. One processing chain or system interruption can miss its deadline even when total CPU utilization looks low.

Why does FL Studio crackle only while recording?

Recording often uses a shorter buffer and adds a live input path. Test the dry input with plugins bypassed, use the interface’s native driver and direct monitoring when available, connect it without a USB hub and raise the buffer one step if gaps are printed into the take.

Why is the underrun count increasing but I hear no crackle?

FL Studio can count underruns while loading a project or plugin. Image-Line says the total is only important when it rises with audible glitches during live playback, so reproduce the same section before treating the number as a fault.

Why does the exported WAV crackle when live playback is fine?

An offline render is not a live buffer underrun. Inspect the exact click for an abrupt Audio Clip cut, a plugin rendering fault or Master clipping. Add a short clip fade, test the suspect plugin by bypassing it, and lower an overloaded output before rendering again.

Does increasing buffer size reduce audio quality?

No. Buffer length changes real-time latency and how much time FL Studio has to process audio; it does not lower the sound quality of the project. A larger buffer can feel delayed while playing or monitoring, which is why tracking and mixing may use different stable settings.

Eric Norris Nashville-based FL Studio producer and editor focused on practical workflow, mixer routing, troubleshooting, sampling and native Image-Line tools.