FL Studio Pro
Troubleshooting

FL Studio Export Has No Sound: Fix a Silent Render

By Eric Norris Published Sep 17, 2026 9 min read

Quick answer

A silent FL Studio export means the signal never reached the Master track during the render, or the player can't read the file. Check the file, the render range, Master routing, mutes and plugins, use 44100 or 48000 Hz for MP3, and record hardware to audio before export.

Producer diagnosing a silent FL Studio export with render and Master-routing checks

A silent FL Studio export means the signal never reached the Master track during the render, or the file is fine and the player can't read it. FL Studio renders the Master Mixer track offline, so check the file first, then the render range, Master routing, mutes and plugins. Bit depth and interpolation can't bring back missing audio. I render a short WAV after each change, because a short file tells you at once whether the fix worked.

Work through the checks below in order: the file itself, the render mode and range, Master routing, mute and solo states, plugins that change behavior during a render, and sound from external hardware. Each check rules out one stage of the signal path before you touch the next.

Use this check order

Silent-export checks in order
CheckWhat it revealsNext action
Open the new WAV and view its waveformThe file is silent, very quiet, or silent only in one playerOpen it in a second player and export a 16-bit test file
Confirm Song or Pattern mode, Length and Total TimeThe wrong pattern or an empty timeline selection was renderedSelect the intended range and render again
Watch the Master meter during playbackThe project signal does not reach MasterRestore the route to Master or record the monitored source
Clear mute and solo statesThe Master or a required Mixer track is muted and left outRestore normal track states, including automation
Render a short WAV with suspect plugins bypassedA plugin behaves differently during renderingCheck the Plugin Wrapper render options
Export WAV, then MP3Only the MP3 fails, at a project sample rate MP3 does not supportSet 44100 or 48000 Hz and render again
Look at the start and end of the fileSilence at the start from MP3 or PDC, or a long silent end from a time markerUse WAV with Trim PDC silence on, and move the marker
Identify external MIDI or hardware soundFL Studio sends notes but holds no returning audioRecord the hardware output as audio before export

Prove that the exported file is silent

Export twenty seconds to WAV, open that exact file in a second player or audio editor, and look for a waveform. That test separates a silent render from a playback problem caused by the player, the operating-system output, an unsupported format, or a file opened from the wrong folder.

Format support is the other half of that test. FL Studio's mix engine runs in 32-bit float, and not every player or device reads 32-bit float WAV files. I keep a 16-bit WAV as the test format, because Image-Line calls 16-bit integer the highest-quality WAV compatible with a wide range of playback devices. If the 16-bit file plays and the 32-bit file stays silent, the render is fine and the player is the limit. 24-bit is the fallback for devices and apps without 32-bit float support.

If the WAV plays and only the MP3 fails, look at the project sample rate. The MP3 standard supports three rates, 32000, 44100 and 48000 Hz, and Image-Line says any other FL Studio sample rate results in MP3 rendering errors. Set the rate in Options > Audio Settings, as the audio settings guide shows, and render again. I export WAV first and MP3 second, because a working WAV proves the mix and leaves only the MP3 settings to check.

A waveform that is there but tiny points to level and routing, not total silence. Check the Master peak level, automation, any limiter or gain plugin, and whether the file came from the project version you expected. The FL Studio no-sound guide is the better path when the project is silent during playback too.

Silence only at the start of the file has two sources. MP3 conversion adds a short silence at the start of the file, which is why Image-Line points loop makers to WAV. In WAV files, Trim PDC silence, on by default, removes the delay that plugin delay compensation added to the Master or split tracks. With the option off, that delay stays in the file as a short silence equal to the PDC setting of the source Mixer track.

Check Song mode, Pattern mode and the render range

The Image-Line export documentation says the render covers the whole Song or the selected Pattern. FL Studio sets the render length in a fixed order: any timeline selection first, then the last time marker beyond the last bar with data, then the end of the last bar with data, plus the Tail setting. An empty or wrong selection produces a file with no useful material, and a time marker far past the music adds silence at the end.

I read Length and Total Time before every render, because a wrong selection shows there before the file exists. To export the arrangement, choose Song and clear an accidental timeline selection, or select a range that contains Playlist material. To export a pattern, make sure the active pattern has notes and its channels reach the Mixer. The FL Studio markers guide covers adding and naming time markers.

The Tail setting decides how the end of the render is handled. Leave remainder is the default and extends the render to capture decaying sound. Cut remainder stops the render at the end of the last bar, selection or time marker, which can cut a reverb or delay tail short. If Leave remainder still misses the tail, place a Playlist Repeat marker after the last clip, and FL Studio renders up to that marker.

Project type Mode set to Pattern, with a reminder to select Song for the Playlist arrangement and check the export range.
This example shows Pattern mode. Choose Song for the Playlist arrangement, since Pattern exports the active pattern. Check Length, Total Time and the selected Playlist range before Start. Open the full-size view to inspect the controls.

Follow the signal to the Master track

By default, FL Studio renders the Master Mixer track, and Image-Line states that any Mixer track not routed to Master, directly or through other tracks, is left out of the render. A channel can look active elsewhere in the project while its final Mixer route is disconnected. Rendering is a non-realtime process, so the audio device you play through has no part in it.

Play the failing section and watch the Master meter. If the source track moves but Master doesn't, look at the routing cable or send switch from that track and any buses between it and Master. I restore the one broken route instead of connecting every track to Master, because a track that only feeds a sidechain becomes audible in the mix once it reaches Master.

The stem-export guide covers buses, returns and Split mixer tracks. Use it when individual stems are missing while the full Master export still works.

Clear mute, solo and automation exclusions

Image-Line notes that muted Mixer tracks, the Master included, are not exported. Check the Master, the source track, intermediate buses and effect returns. A forgotten solo leaves the track you want outside the audible path, and a mute automation clip can flip state inside the selected render range.

Put the project back in its normal mix state and play the same range again. If automation controls a mute, volume, send level or plugin bypass, check its value at the start of the selection. I set those states at or before the render start, because a render from mid-song begins after earlier automation events.

Test plugins that behave differently during rendering

Some plugins behave differently during rendering than during live playback. The Plugin Wrapper manual describes Notify about rendering mode: FL Studio tells the plugin a render is running so it can switch to higher-quality output, and Image-Line's advice is to deselect the option when a plugin does not render correctly. Use fixed size buffers helps with rendering errors such as glitches and timing problems, and Smart disable, which stops processing a plugin while it is inactive, can interfere with time-based, envelope-based and long-decaying effects.

Save a copy of the project, then bypass one suspect plugin at a time and render the same short WAV. I start with the plugins on the Master and shared buses, because one failure there silences the whole file. When bypassing a plugin brings the audio back, the plugins behaving badly page gives the order: open the wrapper Troubleshooting tab and select Use fixed size buffers, then deselect Smart disable in the plugin menu. Don't make up for a silent output by raising gain.

If the wrapper settings don't help, update or reinstall the plugin with its latest installer, then run a fresh Verify plugins scan with Verify previously scanned plugins selected. Swapping formats is the next test: VST and AU on a Mac, VST2 and VST3 on Windows. An FL Studio update can reset some Plugin Wrapper settings, so check them again after each update.

Once the signal is back, use the FL Studio export-settings guide for quality choices. Bit depth, interpolation and dither change format or fidelity, but none of them creates missing audio. For silence, sample rate matters only in an MP3 export, as covered above.

Handle realtime-dependent instruments and controllers

A generator that relies on live input, a controller script, a network stream or another realtime event can play while you interact with the project and then fail in a non-realtime render. Capture the part into the Playlist as audio, then export that recorded clip with the rest of the song.

The same goes for a plugin that streams content from a drive or service that isn't available during the render. Make sure the source files load without warnings and the instrument plays the section without manual input. Freeze or record only after you've kept an editable copy of the project.

Record external MIDI instruments and audio hardware first

MIDI notes are instructions, not recorded sound. If FL Studio drives an external synthesizer, drum machine or sampler, the offline render can't include that device unless its audio output is recorded back into the project. Image-Line's export manual lays out the chain: connect MIDI and audio, record the hardware while FL Studio plays it, put the recording in the Playlist, then render.

Check that the recorded clip reaches Master. Direct monitoring on an audio interface routes a copy of the input straight to its outputs and headphone jack, so you hear the synth even when nothing is recorded inside FL Studio. Once the sound is a Playlist Audio Clip, it follows the same render path as the rest of the project. The audio recording guide covers the recording setup.

Separate a silent full mix from missing stems

A silent Master file and one missing stem are two different failures. With Split mixer tracks, FL Studio writes one file per Mixer track and can include the Master and Current stems. Image-Line lists three rules for split renders: Master effects appear only on the Master track export, split export does not write FLAC, MP3 or OGG, and Mixer tracks fed by a multi-output plugin render only after you rename them from the default Insert N name.

First render a normal stereo WAV with Split mixer tracks off. If that file works, the fault lies in stem selection, naming, routing or where you're opening the files. If the stereo WAV is silent too, go back to the Master route, mute state and plugin checks above.

Skip fixes that do not match a silent render

  • Do not reinstall FL Studio first. Playback already proves that much of the audio system is working.
  • Do not raise bit depth or Sinc quality. Those settings cannot recover a missing Master signal.
  • Do not normalize a flat file. Normalization cannot create audio from digital silence.
  • Do not change the audio driver. The render runs offline from the Master track, so the playback device is not part of it.
  • Do not overwrite the project while troubleshooting. Save a copy before changing routing or plugins.
  • Do not open an older file by mistake. Turn on Show file(s) when complete in the export dialog to open the folder of the new render, and check its filename and modification time.

Verify the corrected render

  1. Export a 20-second WAV from a section with audible parts.
  2. Open that exact file in another player or editor.
  3. Check for a visible waveform and the expected duration.
  4. Listen for the main instruments, buses, returns and external recordings.
  5. Render the full song only after the short test file carries the right signal.
  6. Keep the diagnostic project copy until the final file passes these checks.

Frequently asked questions

Why does my FL Studio export have no sound?

The signal never reached the Master track during the render, or the player can't read the file. FL Studio renders the Master Mixer track, so a track that isn't routed to Master, a muted Master or source track, or an empty timeline selection all produce a silent file.

Do audio drivers affect a silent export?

Not for the project's own sounds. Rendering is a non-realtime process from the Master track, so the driver changes what you hear, not what the file contains. External hardware is the exception: its sound has to be recorded through the audio device before export.

Why is only my MP3 export silent or failing?

The MP3 standard supports only 32000, 44100 and 48000 Hz. Image-Line says other FL Studio sample rates result in MP3 rendering errors, so set one of those rates in Audio Settings and export again.

Why won't my 32-bit WAV export play?

32-bit float is the native format of FL Studio's mix engine, and not every player or device supports it. Export a 16-bit WAV, which Image-Line calls compatible with a wide range of playback devices, or 24-bit when the device lacks 32-bit float support.

Why is there silence at the start of my export?

MP3 conversion adds a short silence at the start of the file. In WAV exports, Trim PDC silence removes the delay that plugin delay compensation adds; with the option off, that delay stays as a short silence at the start.

Why are some stems missing from a split export?

Mixer tracks fed by a multi-output plugin render only after you rename them from the default Insert N name, muted tracks are skipped, and split export does not write FLAC, MP3 or OGG. Master effects appear only on the Master track export.

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