The CPU meter sits in the red. Audio crackles, notes drop out, and playback stutters halfway through the drop.
Almost none of this is about your computer being too slow. It is nearly always settings, and 3 of them do most of the damage.
Key takeaways
- Buffer size is the single biggest lever. Raise it to 512 samples for mixing.
- On Windows, FL Studio needs an ASIO driver. Primary Sound Driver will crackle no matter what else you fix.
- The CPU meter in FL Studio is not your actual CPU load. Check both.
- 1 reverb on a send beats 6 separate instances, and the saving is large.
- Windows power plans throttle laptops silently. This catches people out constantly.
Quick answer
Open Options, then Audio settings. Set the device to an ASIO driver, then raise the buffer length to 512 samples. That fixes most crackling on its own. If it persists, freeze your heaviest channels and move reverb onto a send track instead of running it on every channel.
Check what is causing high CPU usage in FL Studio
FL Studio shows a CPU percentage in the top panel. That number is not your system CPU load, and confusing the two sends people down the wrong path.
Open Task Manager on Windows, or Activity Monitor on macOS, and watch both at once. A high FL Studio meter with low system usage points at your buffer or a single greedy plugin.
Both high together means you genuinely have too much running. That needs freezing and rendering rather than a settings tweak.
Fix 1: raise your buffer size
A small buffer forces your CPU to deliver audio in tiny, urgent chunks. Miss one deadline and you hear a click.
Go to Options, then Audio settings, and find the buffer length slider. Set it to 512 samples and play the project again.
The trade is latency. A large buffer adds a delay you notice when playing a MIDI keyboard, so track at 128 and mix at 512. On my machine that swap alone cut the meter close to half.
Pro tip
Treat buffer size as a setting you change twice per session, not once per install. Low while recording, high while mixing. Most people pick one value, leave it forever, and then either fight latency all day or fight crackles all day.
Fix 2: use an ASIO driver on Windows
Windows audio was not built for music production. The default Primary Sound Driver adds latency and handles multiple streams badly.
In Audio settings, open the device dropdown. Pick your interface’s own ASIO driver if it has one, or FL Studio ASIO if you have no interface.
ASIO4ALL is the fallback for onboard sound, though a real interface driver beats it every time. If you are shopping, our guide to audio interfaces under $200 covers what to look for.
Fix 3: freeze and render heavy channels
Some plugins are simply expensive. Orchestral libraries, convolution reverbs and analogue emulations cost real processing power on every playback.
Right click a channel and choose Render to audio. FL Studio replaces the live plugin with an audio clip, and the CPU cost drops to almost nothing.
Keep the original channel muted rather than deleting it. You can unmute and edit later if the part needs changing.
Fix 4: share effects on send tracks
Putting the same reverb on 8 separate channels means running 8 reverbs. Each one costs the same as the first.
Load 1 reverb on a spare mixer track instead. Route the channels to it and control how much each sends.
I noticed this made more difference than any other single change on a busy project. It also sounds better, because shared reverb glues a mix together. Our roundups of the best reverb plugins and delay versus reverb explain when to use each.
Fix 5: turn on smart disable and multithreading
Smart disable switches off plugins that are not currently producing sound. It is a free saving that many people never enable.
Find it under Options, then General settings. Tick smart disable for both the mixer and the generators.
While you are there, check multithreaded processing is on for both generators and effects. Modern processors have many cores, and FL Studio will not use them all unless you say so. This belongs on the list of DAW settings worth changing the day you install.
Fix 6: stop Windows throttling your laptop
Laptops default to a balanced power plan. That deliberately slows the processor to save battery, and it wrecks audio performance.
Open Windows power settings and pick High performance or Best performance. Stay plugged in while you work.
I chased a crackle for an hour once before spotting Windows had quietly dropped to power saving on battery. Nothing in FL Studio hinted at it. Mac users get a milder version of this, covered in running FL Studio on a MacBook Air.
Fix 7: drop your sample rate to 44.1 kHz
Running at 96 kHz roughly doubles the work for every plugin. Very few home projects need it.
Set the sample rate to 44,100 Hz in Audio settings unless a client asked for higher. Streaming platforms deliver well below that anyway.
Check your interface control panel matches. A mismatch between the two causes crackling that looks exactly like a CPU problem.
Pro tip
Change 1 setting at a time and play the same 8 bars after each. Change 4 things at once and you never learn which one mattered. Keep the winner, undo the rest, and you build a mental model of your own machine instead of guessing next time.
What to do when only 1 plugin is the problem
Sometimes the project is fine and a single plugin eats everything. Finding it is quicker than optimising the whole session.
Open the mixer and bypass channels one at a time while the project plays. Watch the CPU meter after each. The one that drops the meter sharply is your culprit.
Once you know, you have 3 options. Render that channel to audio, replace the plugin with a lighter alternative, or lower its internal quality setting.
Most synths and reverbs have a quality or oversampling control tucked in their settings. Dropping it from high to medium during writing costs almost nothing you can hear. Put it back before you export.
If it still crackles
Work down this list. Each item rules out a different cause.
- Close your browser. Chrome with 30 tabs open competes for the same cores.
- Disable Wi-Fi adapters temporarily. Their drivers are a well known source of audio dropouts.
- Update your interface driver from the manufacturer site, not Windows Update.
- Bypass plugins one at a time to find a single badly behaved one.
- Increase the underrun and priority settings in Audio settings if your interface allows it.
Crackling that survives all of that usually means a faulty cable or a failing interface. Test with headphones straight into the computer to rule the hardware in or out. Persistent buzzing is a separate problem, covered in why studio monitors buzz.
Frequently asked questions
Why is my FL Studio CPU usage so high?
Usually a buffer size set too low, a non ASIO audio driver, or too many separate plugin instances. Raise the buffer to 512 samples and switch to ASIO first.
What buffer size should I use in FL Studio?
Use 128 samples while recording so latency stays low. Switch to 512 samples or higher while mixing, when latency no longer matters and CPU headroom does.
Does the FL Studio CPU meter show real CPU usage?
No. It shows how close the audio engine is to missing its deadline. Check Task Manager or Activity Monitor alongside it to see genuine system load.
Will more RAM fix FL Studio crackling?
Rarely. Crackling is a timing problem, not a memory one. RAM only helps if you run large sample libraries and see memory usage near maximum.
Should I use 44.1 kHz or 48 kHz?
Use 44,100 Hz for music unless a client specifies otherwise. Use 48,000 Hz for video work. Higher rates cost processing power for very little audible gain.
Does freezing a track lose quality?
No. Rendering to audio captures exactly what the plugin produced. Keep the original channel muted so you can go back and change the part later.
Where to go next
If FL Studio closes entirely rather than crackling, that is a different fault. See FL Studio crashing when loading plugins. For plugins that never appear at all, read a VST not showing up in FL Studio or the Serum specific missing Serum guide.
Lighter plugins help more than hardware upgrades. Browse the best free VST plugins, plugin bundles worth buying, the EQ plugins pros use and compressors for transparent mixing. Avoiding the usual DAW mixing mistakes keeps projects lean too.
Thinking about switching? Compare FL Studio against Ableton Live and DAWs on Windows versus Mac. Set your buffer and driver correctly, and FL Studio CPU usage too high stops being the thing that ends your sessions.
