If FL Studio is crackling, popping or briefly cutting out during playback, the most common cause is an audio underrun. FL Studio has to calculate each block of audio before your interface needs it. If the next buffer is not ready in time, you hear a click, pop or glitch.
The good news is that this usually does not mean your speakers, project or audio files are broken. In most cases you can fix it by changing the buffer, audio driver or CPU-heavy parts of the project.
Quick fix: open Options → Audio settings, increase the buffer size, make sure you are using the correct ASIO/Core Audio driver, then play the project again. If the crackling stops, your project was running out of real-time processing time.
First: is it crackling, clipping or an audio underrun?
These problems can sound similar, but the fixes are different.
| What you hear | Likely cause | What to check first |
|---|---|---|
| Random clicks, pops or short dropouts | Audio underruns / CPU cannot fill the buffer in time | Buffer size and FL Studio CPU meter |
| Harsh distortion only when the mix gets loud | Clipping | Master and mixer levels |
| One plugin crackles while the rest of the project is fine | Plugin compatibility or wrapper issue | Plugin Performance Monitor and wrapper settings |
| Crackling only while recording at a very low buffer | Buffer is too small for the project | Raise buffer or simplify monitoring chain |
| Playback is clean but exported audio is wrong | Render/plugin problem rather than normal real-time underruns | Plugin compatibility, render settings and problem plugin |
FL Studio's CPU meter measures how much of each audio buffer's available time is being used. When it gets close to 100%, the next buffer may not be completed before playback needs it, causing an underrun.
If your master is simply clipping instead, see our Soft Clipper vs Limiter in FL Studio guide. Increasing your audio buffer will not fix a mix that is clipping.
1. Increase the audio buffer size
This is the first setting I would change. A larger buffer gives FL Studio more time to calculate the next block of audio before it has to be played.
Open Options → Audio settings and increase the buffer length. Image-Line recommends around 512 samples as a sensible starting point with an ASIO audio setup.
For mixing, a larger buffer is usually fine because low monitoring latency is not important. For live recording or playing a MIDI keyboard, you may want a smaller buffer, but only as low as your computer can run without underruns.
| Situation | Buffer approach |
|---|---|
| Recording vocals or MIDI live | Use the lowest stable buffer that does not crackle |
| Producing / arranging | Moderate buffer is usually the best compromise |
| Mixing a heavy project | Increase the buffer because latency matters much less |
| Project suddenly crackles after adding plugins | Raise buffer first, then identify the heavy plugin |
Do not chase the smallest possible number. Image-Line notes that CPU load rises quickly as buffer sizes become extremely short.
2. Use the correct audio driver
On Windows, the audio driver matters. If you own an audio interface, use the manufacturer's dedicated ASIO driver when possible. Image-Line recommends the device's own ASIO driver for the best performance with an external interface.
If you do not have a dedicated interface driver, FL Studio ASIO is the normal compatibility option. On macOS, FL Studio uses Core Audio and you should normally select the actual output device you want to use.
To check it, go to Options → Audio settings → Input/output device.
If changing from a generic driver to your interface's proper driver stops the crackling, the project itself may not have been the problem at all.
3. Watch FL Studio's CPU meter — not only Task Manager or Activity Monitor
A common confusing situation is FL Studio crackling while your computer's overall CPU usage looks nowhere near 100%.
That can still happen because real-time audio has to finish specific processing chains before each buffer deadline. One overloaded path or core can cause an underrun even when other CPU cores are not fully used.
Watch the CPU panel in FL Studio. If the meter spikes when you hear the crackle, that is a strong sign the problem is real-time processing load.
4. Find the plugin causing the CPU spike
You do not have to guess which plugin is heavy. Double-click the CPU panel to open FL Studio's Plugin Performance Monitor.
Play the section where the crackling happens and look for plugins using unusually large amounts of processing time.
Then test one change at a time:
Disable the plugin temporarily. If the crackling disappears immediately, you found an important part of the problem.
Reduce expensive settings. Lower oversampling, unison voices, polyphony, quality modes or look-ahead settings where appropriate.
Freeze or render the track to audio. Once a CPU-heavy synth part is finished, printing it to audio can free a large amount of real-time processing power.
5. Enable multithreaded processing
Open Options → Audio settings and check that Multithreaded generator processing and Multithreaded mixer processing are enabled.
These options let FL Studio spread compatible instrument and mixer workloads across multiple CPU cores.
There is one exception: some third-party plugins behave worse with threaded processing. If one specific plugin becomes unstable, Image-Line recommends testing its wrapper setting Allow threaded processing separately rather than disabling multithreading for the entire project.
6. Turn on Smart Disable for inactive plugins
Smart Disable stops compatible plugins from consuming processing time while they are inactive.
Enable Smart Disable in the Audio settings, then use Tools → Macros → Switch smart disable for all plugins to apply it to existing plugins.
This can make a large project noticeably lighter when many instruments and effects are sitting idle.
There is an important caveat: some time-based, envelope-based or long-decay plugins may behave incorrectly with Smart Disable. If a reverb tail gets cut off or a plugin starts late, disable Smart Disable for that specific plugin.
7. Check real-time stretching on Audio Clips
Audio Clips using real-time Stretch or Stretch Pro modes can consume substantially more CPU than simpler playback modes.
If a large project contains many stretched audio clips, check whether every clip actually needs real-time stretching. Image-Line recommends using simpler or offline stretching modes when continuous real-time stretching is unnecessary.
This is especially worth checking in projects with many vocals, loops or stems that have all been left in an expensive stretch mode.
8. Lower unnecessary sample-rate and quality settings
Running a project at an unnecessarily high sample rate means FL Studio and your plugins have to process more samples every second.
For a normal production setup, Image-Line's setup guidance recommends 44.1 kHz or 48 kHz. If you are running a much higher sample rate without a specific reason, switching to a normal production rate can reduce load substantially.
Also check oversampling or “high quality” modes inside individual plugins. You do not always need the maximum real-time quality while writing. Some plugins can use lower settings during playback and higher settings when rendering.
9. If only one plugin crackles, troubleshoot that plugin
If FL Studio runs cleanly until one specific third-party plugin is active, changing the global buffer may only hide the real issue.
Image-Line recommends several plugin-specific tests:
Try a different plugin format. On Windows, test VST3 instead of VST2 or vice versa when both versions exist. On macOS, testing AU versus VST can sometimes reveal a format-specific problem.
Try fixed-size buffers. Open the plugin wrapper's Troubleshooting settings and test Use fixed size buffers.
Test threaded processing. A plugin can occasionally behave worse when multithreading is enabled specifically for that wrapper.
Test Smart Disable. Disable it for the problematic plugin if its timing or audio behaves incorrectly.
If one plugin consistently causes glitches after those tests, update it and check the developer's compatibility notes for your operating system and FL Studio version.
10. Reduce background load and unnecessary project work
FL Studio needs predictable real-time processing. A computer can be powerful and still glitch if other software repeatedly interrupts the workload.
Close unnecessary background applications while troubleshooting, especially anything doing heavy CPU, disk or cloud-sync work. Then play the exact same section again.
Also check FL Studio's autosave setting if the glitch happens intermittently rather than in the same musical section every time. Image-Line notes that very frequent autosaves can cause underruns in larger projects because saving may occur during playback.
Why does FL Studio crackle even when CPU is below 100%?
Because FL Studio's audio task is deadline-based. A project does not only need enough total CPU power; each processing path has to finish before the next audio buffer is required.
A long chain of effects on one mixer track has to be processed in order. That chain cannot always be divided perfectly across every CPU core. One core or one serial processing path can therefore hit its limit while the computer's average CPU usage still looks relatively low.
This is why the Plugin Performance Monitor and FL Studio CPU meter are more useful for diagnosing crackling than only looking at the operating system's overall CPU percentage.
If your main problem is delay rather than crackling, read our guide to reducing latency in FL Studio.
Why does FL Studio crackle only when recording?
Recording usually forces you to use a smaller buffer so monitoring feels responsive. That leaves the CPU less time to calculate each block of audio.
If a large project plays cleanly at 512 or 1024 samples but crackles when you reduce the buffer for recording, you have reached the limit of that project's real-time workload.
Three practical fixes are:
Temporarily disable heavy mix plugins while recording.
Render the instrumental to one audio file and record into a lightweight project.
Use direct monitoring on your audio interface if it supports it, so you do not need to force the FL Studio buffer extremely low just to hear yourself without delay.
Why does FL Studio crackle after adding one plugin?
The plugin may simply require more processing than the remaining buffer time allows, or it may have a compatibility problem.
First open the Plugin Performance Monitor. If that plugin suddenly dominates the processing time, reduce its quality settings or render the track.
If its CPU usage does not look unusually high but the audio still breaks up, test the plugin-specific wrapper fixes above.
Why does the exported file not crackle?
If the project crackles during playback but the exported WAV is clean, that strongly points toward a real-time underrun. Offline rendering is not constrained by the exact same live buffer deadline.
That is also why a CPU-heavy project may export perfectly even though normal playback is struggling.
Why does the export crackle when playback is clean?
That is a different problem. Look for a plugin that behaves differently during offline rendering, a plugin compatibility issue, clipping inside the project or a render setting that changes the processing path.
Export a short section while disabling suspicious plugins one at a time. If the crackle disappears after bypassing one plugin, troubleshoot that plugin rather than increasing the normal playback buffer.
A fast FL Studio crackling checklist
| Order | What to do |
|---|---|
| 1 | Increase the audio buffer |
| 2 | Use your interface's proper ASIO driver or the correct Core Audio device |
| 3 | Watch FL Studio's CPU meter while the glitch happens |
| 4 | Open Plugin Performance Monitor and find the heavy plugin |
| 5 | Enable multithreaded generator and mixer processing |
| 6 | Enable Smart Disable for compatible inactive plugins |
| 7 | Reduce real-time stretching and unnecessary high-quality modes |
| 8 | Freeze or render completed CPU-heavy instruments |
| 9 | Troubleshoot one misbehaving plugin separately |
| 10 | Close unnecessary background work and test again |
Frequently asked questions
What buffer size should I use in FL Studio?
There is no single perfect buffer for every computer. Image-Line recommends around 512 samples as a practical starting point for an ASIO setup. Use a smaller buffer when you need low recording latency and a larger one when mixing a heavy project.
Does increasing buffer size reduce audio quality?
No. The buffer mainly changes how much time FL Studio has to process real-time audio and how much monitoring latency you experience. A larger buffer does not make the rendered audio lower quality.
Why does lowering my buffer make FL Studio crackle?
A smaller buffer gives the CPU less time to finish the next block of audio. Once the project cannot finish within that shorter deadline, underruns begin.
Should I use FL Studio ASIO or ASIO4ALL?
If you own an audio interface with its own ASIO driver, use the manufacturer's driver first. If you do not, FL Studio ASIO is the normal compatibility option. ASIO4ALL can still be useful in specific Windows setups, but it should not automatically be the first choice for every system.
Can a VST plugin cause crackling?
Yes. A plugin can consume too much CPU or have a compatibility issue with its wrapper, plugin format, operating system or multithreading behavior. Use Plugin Performance Monitor to identify suspicious plugins.
Does more RAM fix FL Studio crackling?
Not usually if the issue is a normal CPU/buffer underrun. More RAM helps when a project is running out of memory or constantly reading sample data from disk, but it does not automatically make a CPU-heavy processing chain meet its real-time deadline.
Why does FL Studio crackle on a powerful computer?
Real-time audio depends on buffer deadlines and how processing chains can be distributed across CPU cores. One heavy serial chain can create underruns even when the computer's average CPU usage looks low.
Final fix order
If you want the shortest route to a solution, do this in order: raise the buffer, confirm the audio driver, check the FL Studio CPU meter, open Plugin Performance Monitor, then optimize the plugin or track causing the spike.
Do not start randomly changing every setting in FL Studio. Once you know whether the problem is an underrun, clipping or one misbehaving plugin, the fix is usually much simpler.
Official references
This guide follows Image-Line's current documentation for audio settings, CPU optimization and plugin troubleshooting. See the FL Studio Audio Settings manual, performance optimization guide and plugin troubleshooting guide.
![[background image] image of recording equipment (for a musician & band)](https://cdn.prod.website-files.com/68efa70811edd8e5af30a90d/6acd43b8998701bbde84e11a_Best%20Export%20Settings%20for%20FL%20Studio.png)
![[background image] image of recording equipment (for a musician & band)](https://cdn.prod.website-files.com/68efa70811edd8e5af30a90d/6acd3f9347bd0dd62b202621_ShaperBox%203%20vs%20Infiltrator%202.png)
![[background image] image of recording equipment (for a musician & band)](https://cdn.prod.website-files.com/68efa70811edd8e5af30a90d/6acd3d99fa68785e0f58960e_Kontakt%208%20vs%20Decent%20Sampler.png)