FL Studio 
Your mix is ready to send, and then the export window hits you with three WAV depths, several interpolation methods and a checkbox promising HQ for all plugins. The best FL Studio export settings depend on what happens to the file next. For a broad production handoff, 24-bit WAV at the established project sample rate is a sensible starting point. Use 32-bit float when the receiving application accepts it for further processing.
Check the recipient’s specification before you pick a preset. For a required final 16-bit file, decide where the final dither will be applied. Pushing every number higher won’t fix a clipped recording, an unwanted effect or a mix that’s out of balance.
Using the standard Trial? You can save projects and export audio, but cannot reopen saved projects until you purchase and unlock FL Studio. The edition and plugins you own must cover the project. Keep needed work open until its exports are finished, and verify files in another application without replacing that session. Image-Line explains the Trial limitation.
Choose FL Studio export settings by destination
| Destination | Starting point | Confirm before delivery |
|---|---|---|
| Further mixing or editing | 32-bit float WAV at the project rate | The receiving application supports float |
| Mastering or broad production exchange | 24-bit integer WAV at the project rate | The engineer’s format, level and processing requirements |
| Video editor | WAV at the requested depth; often 48 kHz | The picture project’s actual specification |
| Standard audio CD preparation | 44.1 kHz, 16-bit WAV | Final bit-depth reduction and one intended dither stage |
| Listening or review copy | 320 kbps MP3, with a lossless master retained | The recipient needs convenient listening, not sample-accurate alignment |
| Smaller lossless delivery | 16- or 24-bit FLAC | The recipient accepts FLAC and that depth |
Treat these as examples, not universal platform requirements. A mastering engineer may want float, and a distributor may list a different accepted format. Follow that brief instead of quietly converting an established 44.1 kHz project to 48, 96 or 192 kHz.
If you need the actual render procedure, use the full-song export guide. For separate instruments, buses and returns, the stem-export workflow explains which files belong together. This page focuses on format and processing choices.
Where do you set sample rate and WAV bit depth?
Set the project’s output sample rate in Options > Audio Settings. Choose the file’s WAV bit depth after opening File > Export > Wave file. They are separate controls: the export dialog’s bit-depth menu does not set the project sample rate. The current export reference describes both locations.
Sample rate: 44.1 kHz, 48 kHz or a required alternative
Sample rate counts samples per second and limits the frequency range a file can represent. Image-Line recommends the default 44.1 kHz where possible and notes that video often uses 48 kHz. A file recorded at a lower rate won’t gain missing detail just because you export it at a higher one.
Keep the rate you approved the mix at unless the delivery needs a change. If you do change it, audition the relevant passages again, because some older plugins behave differently at other rates. The Audio Settings documentation separates project rate, live processing and hardware options; the Audio Settings guide helps if the device or driver is the problem.
File depth is not the audio device’s bit depth
The 16- or 24-bit setting in an operating-system or interface control panel is about device input and output. It isn’t the WAV export selector. FL Studio’s main render choices are 16-bit integer, 24-bit integer and 32-bit float WAV. A sample-loading reference that lists other supported WAV types doesn’t add those types to this export menu.
With integer audio, more bits give finer level steps and a lower quantization noise floor. Float uses a different numeric representation that suits a compatible processing workflow. Don’t read “32-bit float” as a uniformly finer 32-bit integer grid, and don’t confuse it with the 32/64-bit architecture of a plugin.
Should you use 16-bit, 24-bit or 32-bit float WAV?
16-bit integer for a required final format
A standard audio-CD preparation file uses 44.1 kHz, 16-bit WAV. FL Studio creates that audio file; burning the CD is a separate job. Use 16-bit when the final brief asks for it, and apply your chosen dither once at the final reduction instead of repeatedly along the production chain.
24-bit integer for broad production compatibility
24-bit WAV is a practical handoff when the engineer or receiving system hasn’t asked for float. Check the file’s peaks: unlike the floating-point processing inside FL Studio, fixed-depth output can clip, and turning playback down later won’t recover samples that already clipped in that file.
32-bit float for compatible continued processing
FL Studio’s mix engine runs in 32-bit floating point. Exporting a float WAV keeps a suitable intermediate for further mixing or editing in an application that supports it. Floating-point headroom is useful, but it can’t undo distortion already printed by a recording, a clipping plugin or another earlier process.
A float file isn’t automatically the right upload for every phone, distributor or collaborator. Ask whether it’s accepted. If the next tool can’t use float, choose the requested integer depth and check the levels before delivery.
Choose WAV, FLAC or a lossy review copy
FL Studio’s WAV export produces uncompressed, lossless audio. It’s a good production default when the receiver accepts the chosen depth and channel layout. A stereo WAV has left and right channels; Mono (merged) combines them, while the left-only and right-only options save just that side. Don’t collapse a stereo mix just because a bigger file feels inconvenient.
FLAC compresses the data without changing the decoded audio. FL Studio offers 16- and 24-bit FLAC. Its compression level changes encoding effort and file size, not the decoded sound, so level 8 won’t give you a better-sounding master than level 5. A receiver who asked for WAV may still reject a perfectly lossless FLAC.
FL Studio’s MP3, Ogg Vorbis and AAC-in-M4A exports are lossy. That detail matters, since a container name alone doesn’t tell you which codec another application might put inside it. For a convenient MP3 review, 320 kbps is the highest MP3 bitrate offered here. Keep the lossless master and listen to the compressed copy itself.
For MP3, 44.1 or 48 kHz is a practical choice in line with Image-Line’s MP3 encoding troubleshooting advice. The export manual also lists 32 kHz. Don’t assume a high-rate project can produce MP3 at that same rate; if the encoder refuses, check the rate before you start flipping unrelated quality switches.
The documented FL Studio MP3 conversion adds a short leading silence, so use WAV instead of that MP3 for loops or files that must line up sample-accurately. Bitrate, depth and interpolation are different ideas, too: “512-point sinc” is an interpolation method, not a 512 kbps WAV setting.
What does render resampling actually affect?
Resampling in the export dialog picks the interpolation for Sampler and Audio Clip channels. FL Studio needs in-between sample values when pitch or rate conversion puts playback between source sample points. This setting isn’t a global oversampling control for every synthesizer and effect.
- Linear: the fastest basic method. Large pitch changes can expose aliasing.
- 6-point Hermite: a quick curved interpolation method that Image-Line describes as suitable for good-quality exports. Listen for problems before assuming it ruined a mix.
- Sinc methods: higher point counts increase interpolation accuracy and render cost. Image-Line suggests going above 64-point sinc if lower methods audibly alias; 512-point is an available cautious offline choice, not a guarantee of an audible improvement.
Live interpolation is set separately under Options > Audio Settings, in the Mixer section. The documented live default is 24-point sinc. Different live and export settings can change the high-frequency character of pitched samples. Matching them helps when you compare, but a high live setting may eat too much CPU.
To investigate, export the same exposed passage with two interpolation choices while keeping format, gain, effects and range the same. Compare them at matched playback levels in a suitable separate application, with any needed Trial session still open. If the problem comes from a third-party synth, look at that plugin’s own processing instead of expecting the Sampler setting to fix it.
Should HQ for all plugins be enabled?
HQ for all plugins asks supported native FL Studio plugins for a high-quality mode. It doesn’t override every generator and effect, and some native implementations only affect one part of a plugin, such as a waveshaper.
A hosted VST can also respond to Notify about rendering mode in its Wrapper’s Processing settings, if it supports a different offline mode. The Wrapper reference explains that notification and suggests testing it off when a plugin renders incorrectly. Many plugins have independent quality or oversampling controls; check the important plugin’s manual.
For a final render, turning on the supported HQ paths is reasonable, but listen to the result instead of treating the checkbox as a certificate. Also look at Disable maximum polyphony: it ignores a Channel’s Max poly limit, but not Mono. Removing a voice limit you set on purpose can change how notes overlap.
When should FL Studio’s Dithering switch be on?
The FL Studio export switch has a narrow documented scope: 32-to-16-bit dithering for 16-bit WAV and MP3 output. If you use it, apply it once at the final 16-bit reduction. Leave it off for 24-bit and 32-bit float intermediates, because it isn’t a generic dithering processor with a selectable depth.
That doesn’t mean dithering only exists at 16-bit. Other tools offer other target depths. For example, iZotope’s dithering guidance covers 24-bit reductions as well. Follow the chosen tool’s target-depth and final-processing instructions instead of mixing unrelated recommendations.
If a mastering plugin already handles the final dither, don’t stack FL Studio’s dither on top. Make any sample-rate, level or effect changes before that final stage. For a file going to an engineer for further processing, agree on who does the final reduction.
Dither trades correlated quantization error for very quiet noise, and FL Studio uses noise shaping. It won’t raise loudness, improve bass or restore missing detail. If you hear obvious noise during normal listening, look for another cause, such as source noise, a plugin, interpolation or lossy encoding.
Why does the export sound different?
A numerical quality setting is only one possible cause. Check these before swapping a working format for a larger one:
| What changed? | Check first |
|---|---|
| Clipping or unexpectedly sharp distortion | Actual file levels and earlier clipping; 24-bit fixed output cannot preserve floating-point overs as clean playback |
| Missing processing | Enable insert effects and Enable master effects; split Mixer files bypass Master |
| Narrow or missing stereo information | Export channel layout and the player’s processing |
| Different pitched-sample brightness | Live versus render interpolation |
| Different note overlap or plugin tone | Maximum-polyphony override, HQ mode and the plugin’s own offline settings |
| Wrong beginning or ending | Song/Pattern, Playlist selection, Tail and WAV-only Trim PDC silence |
Trim PDC silence removes compensation-added leading silence from WAV exports when enabled; it does not switch delay compensation off or repair an offset already recorded into a clip. The Playlist guide helps with arrangement selections, while the song-export walkthrough covers the full endpoint and tail procedure.
On Windows, the FL Studio ASIO Hard-clip output at 0dB option affects live audio, not rendered files. With it off, a Windows limiter can hide live clipping, and Windows audio enhancements can also change what you hear. Check the actual file and playback path before deciding a different driver raised the export’s bit depth.
The monitor volume knob doesn’t change rendered levels. The levels documentation separates floating-point processing from fixed-depth output. Neither a 0 dBFS peak nor an invented −6 dBFS target is required for every delivery. Use the mastering guide for loudness and tone, and the Mixer guide for routing and gain.
Apply and verify FL Studio export settings
- Confirm the destination. Get the required format, rate, depth, channel layout and processing state.
- Preserve the project. Use
File > Save new version. In standard Trial, keep needed work open until its exports are complete. - Set the rate deliberately. Keep the established rate unless the brief requires a change; after a change, audition the affected material.
- Choose the export format and depth. Open
File > Export > Wave filefor WAV, choose a destination filename, then select the agreed integer or float depth and channel layout. - Review processing choices. Set interpolation for the relevant sample paths; check HQ, plugin offline modes and intentional voice limits.
- Decide on the final dither. Use FL Studio’s switch only for its documented final 16-bit output path, if needed, and not on top of another final dither.
- Check musical content before rendering. Confirm Song or Pattern, range, tail, required effects and any split-output choice, then start the render.
- Inspect the actual file safely. Check format metadata and listen to the start, ending and exposed passages in another suitable application. Do not replace a needed Trial project to do this.
Give the file a name that says which version it is and what it’s for, such as Track_v3_mix_24bit.wav and Track_v3_review.mp3. Check the actual metadata, though, since a filename is only a label. Match listening levels and switch off extra player EQ or enhancements when you compare.
You can select multiple output formats in one render. A WAV production file and MP3 review copy still have different uses and restrictions. Audio does not replace editable notes or the project: use the MIDI export guide for note data, or the zipped loop project workflow for editable FL Studio work. A ZIP does not supply plugin installations, licenses or every third-party sample library; the project-format reference describes its sample limits.
Frequently asked questions
What are the best FL Studio export settings for mastering?
Follow the engineer’s specification. A practical broad-exchange starting point is 24-bit WAV at the established project rate. Use 32-bit float when the engineer accepts it for continued processing. Agree on level, effects and final-dither responsibility rather than treating one preset as universal.
Should I use 24-bit or 32-bit float?
Use 24-bit integer for a compatible production handoff, or 32-bit float for further processing in a supporting application. Float does not repair earlier clipping or override the receiving platform’s format requirements.
Where do I change the export sample rate?
Set the project output sample rate in Options > Audio Settings. Choose WAV bit depth separately in the export dialog. The audio device’s input/output bit-depth setting is another control, not the exported WAV depth.
Should I always use 512-point sinc?
No. Render interpolation affects Sampler and Audio Clip paths when intermediate sample values are needed. Higher sinc settings can help when lower methods produce audible aliasing, but cost render time and do not upgrade every synth or effect.
Does HQ for all plugins override every plugin?
No. It requests HQ from supported native plugins. A hosted VST may respond to Wrapper render notification, while other quality choices remain inside the plugin. Check its documentation and listen to the actual export.
Should FL Studio dithering be on or off?
The export switch is documented for final 32-to-16-bit dithering to 16-bit WAV or MP3. Use it once if it is your chosen final dither; leave it off for 24-bit or float intermediates and when another plugin already performs that final stage. Other dithering tools can support other target depths.
Can I verify an export while using the standard Trial?
Yes. Keep the needed FL Studio project open and inspect the rendered file in another suitable application. Trial can save and export, but saved projects cannot be reopened until purchase and unlock; the owned edition and plugins must cover the project.
Pick settings for the next person or application, then check that file. The Export & Collaboration hub connects the different delivery workflows, and the Workflow hub helps you organize the source project before the next handoff.
