FL Studio project to WAV

Drop an .flp to get a WAV, or select a file. It opens in the studio, ready to export.

FLP · ZIP

How to get a WAV out of an FL Studio project

You need audio out of an .flp (a file to send a mixer, open in another DAW, or keep working on), and FL Studio is not on the machine in front of you. The project carries no sound: every channel names a generator plugin, or a sample by a path that only resolves on the computer that made it. What it carries is the writing. That is what gets played here, and written to WAV.

  1. Drop your .flp: The project is read in your browser. Nothing is uploaded to read it, and no account is needed. Have the project folder? Choose it instead, and the samples its audio clips play come with it.
  2. It renders by itself: The studio opens on the arrangement and starts the WAV straight away. Each track's notes are played by a stand-in picked from the track's name (a kick lane on a drum kit, a bass on a bass), rendered on our server from a General MIDI sound set, usually in seconds.
  3. Download the WAV: One file of the whole arrangement lands in your downloads. Your first three a month need no account; a free account gives you 120. For stems, 32-bit float or a loop range, use File → Export audio….

Questions about the FL Studio project to WAV converter?

We have answers.

Can I convert an .flp to WAV without FL Studio?

Yes, drop it here. What you get is the arrangement played on stand-in instruments, plus any audio clips the project folder carries; not the mix FL Studio makes with the project's own plugins. That one only comes out of FL Studio, on a machine that has them all.

Is it free? Do I need an account?

Your first three WAVs a month need no account. A free account raises that to 120 a month. The .flp is read in your browser and the stand-in render runs on our server, so there is nothing to install.

What bit depth and sample rate is the WAV?

16-bit at 48 kHz when everything playing is a stand-in, 24-bit when your recordings are in the mix. File → Export audio… writes 16-bit, 24-bit or 32-bit float, at 44.1 or 48 kHz, for the tracks that carry audio.

My project is mostly samples. Will that work?

With the folder, yes: choose the project folder, or a zip of it, and every audio clip plays from your copy. FL Studio's File → Export → Project data files makes that zip. With the .flp alone, clips that point at samples have nothing to play, and the studio tells you how many are missing.

How long can the project be?

Up to 20 minutes and 40,000 notes for the stand-in render.

How do I export a WAV from FL Studio itself?

File → Export → Wave file…, choose where it goes, pick the depth in the render window and press Start. That renders with the project's own plugins and samples, so it only sounds right on a machine that has every one of them.

Try our free FL Studio project to WAV converter

  • What an .flp actually stores

    Open an .flp and there is no audio in it anywhere. What there is: a channel list, each channel naming a generator plugin and carrying its settings as an opaque blob; sample channels pointing at file paths; patterns of notes; and the playlist that places them. The audio path is a set of references outward: to Serum, to Sytrus, to a one-shot three folders deep in a pack you bought. Those parts make the sound, and they live on the machine that made the project. What can be lifted out is the music as written: the notes, their velocities, the tempo, the arrangement. The performance has to be made fresh.

  • Bit depth, and why it depends on what is playing

    When every track is a stand-in, the WAV comes from our server at 16-bit, 48 kHz. The General MIDI samples doing the playing are 16-bit themselves, so a deeper file would only carry zeros below them. When your recordings are in the mix (the project folder brought them), the file is written in your browser at 24-bit instead, because those clips may hold detail a 16-bit file would round away. Stereo 24-bit at 48 kHz runs about 17 MB a minute, so four minutes lands near 70 MB.

  • Stems, and what each file holds

    File → Export audio… → Stems writes one WAV per track that has audio (a recording from the project folder, or a track you have played on a modelled instrument in Sources), in one zip, every file starting at the same timeline zero so they drop back into line in one drag. A stand-in track is in the mix, not in the zip: it is rendered as part of the whole, on the server. Automation lanes, aux sends, plugin chains and time-stretch are not rendered either way.

Try these Doseedo tools