A DAW project file usually does not contain your audio. An FL Studio .flp file points to the samples it uses, and so does an Ableton .als file. So before you convert, it helps to decide one thing: do you want a converted project that works on any computer, or one that keeps using the samples already on your machine?
2 free conversions every month. No card required.
This guide explains what you can upload, how DAWPORT finds your samples, what you get back and what happens when a file is missing.
Two ways to upload
| You upload | What you get | Best for |
|---|---|---|
| Just the .flp or .als file | The converted project keeps the original sample paths | Converting on the same computer that has the samples |
| An archive of the project folder with its samples | A converted project with the samples bundled | Moving to another computer, sharing, selling or archiving |
Uploading just the project file
You can upload a single .flp or .als file up to 16 MB. DAWPORT does not see your samples in this case, so it keeps their original paths in the converted project. The conversion notes say this plainly: the audio was not uploaded or checked, so open the result on the original computer, or relink the samples if they moved or you use another computer.
Some processing needs the actual audio, for example applying a sample's fades or envelope. Without the audio, DAWPORT keeps the instrument and its sample reference but cannot apply those parts.
Uploading an archive with samples
For a self-contained result, put the project folder with its samples into an archive and upload that. DAWPORT accepts:
- .zip, .rar and .7z archives
- up to 512 MB per archive (the limit is the same on every plan)
- at most 4 GB once unpacked
Password-protected (encrypted) archives cannot be read, so archive without a password. Other file types, such as Ableton's .alp pack files, cannot be uploaded. You also cannot upload a folder directly; archive it first.
Preparing your archive
The aim is simple: everything the project uses should be inside the archive, in the same layout as on your computer.
From FL Studio: make sure the samples your project uses are inside the project folder, then zip that folder. FL Studio can also save a zipped package that holds the .flp together with the samples and presets it uses (Image-Line manual), which helps you see which files belong to the project.
From Ableton Live: use File > Collect All and Save first. Live then copies the external samples the Set uses into the Project's Samples folder (Ableton manual). Then archive the whole Project folder.
Keep one project per upload. If your archive holds several projects, DAWPORT picks the main one automatically only when the choice is clear, for example when the others sit in Backup or Autosave folders or have "backup" or "autosave" in their names. Otherwise it asks you to choose the project inside the archive before you can convert.
How DAWPORT finds your samples
DAWPORT can only include samples that are inside your upload. If you upload just the project file, the converted project keeps the original sample paths, such as C:\Users\you\Samples\kick.wav, so it opens with its samples on the computer that has them. To bundle the samples with the result, put them in the archive.
For each sample the project uses, DAWPORT looks inside the archive for:
- the path relative to the project, as stored in the project file
- the same folder structure found elsewhere in the archive
- for Ableton Live Sets, a uniquely named file in the Project's Samples folder, as Collect All and Save lays it out, or a file with the same name whose size or audio details match what the Set recorded
- for FL Studio projects, a unique file with the right name in the archive
DAWPORT is careful about guessing. If two different files could match a sample and it cannot prove which one is right, it does not pick one at random. That sample is reported instead of silently swapped for the wrong sound. For Ableton Live Sets, a file that only shares the name, with nothing else to confirm it, is not used either.
When several FL Studio channels use the same sample, the converted Ableton Live Set gets one shared copy of it. DAWPORT only does this after checking that the files really are identical.
What you download
- FL Studio to Ableton Live: a .zip that contains the .als file and the samples it uses, in a Samples folder next to it (collected samples go into Samples/Collected). Unzip it and open the .als file in Live.
- Ableton Live to FL Studio: a .flp file. When there are samples or plug-in data to include, you get a .zip instead, with the .flp and its samples side by side, so FL Studio finds them relative to the project.
Downloads stay available for a limited time that depends on your plan: 24 hours for a free conversion result, 24 hours for a single purchase, 24 hours on Basic, 3 days on Premium and 7 days on Pro. Save your result once it is ready. See pricing for plan details.
What happens with missing files
A missing sample does not stop the conversion. DAWPORT converts the rest of the project and the conversion notes report the files it could not find in your upload. It does not create placeholder or silent audio files to hide the gap, so the destination DAW shows those samples as missing.
From Ableton Live, an audio file can also be in your upload in a format DAWPORT cannot read, such as .m4a. The clip keeps its link to the file, and the conversion notes say the file was uploaded but could not be read. If it does not play in FL Studio, relink it, or save it as WAV, AIFF, FLAC or MP3 and convert again.
After converting, you can fix missing samples in the destination DAW:
- In Ableton Live, missing files show up in the File Manager. You can point Live to the right file or let it search a folder for it (Ableton manual).
- In FL Studio, load the correct sample into the channel that is missing it.
The easiest fix is usually upstream: gather the samples in your original DAW, archive the folder and convert again.
Quick checklist
- Gather all samples into the project folder (Collect All and Save in Live, a zipped package or tidy folder in FL Studio).
- Archive the folder as .zip, .rar or .7z, under 512 MB.
- One project per archive, or be ready to pick one.
- Read the conversion notes for any missing files.
- Keep your original project and samples.
Ready to convert? Go to FL Studio to Ableton Live or Ableton Live to FL Studio. More questions are answered in the FAQ.

