How to share an FL Studio project with its samples

If someone only needs to listen, send a rendered audio file. If they need to edit patterns, instruments and arrangement, send the project and its dependencies. A single .flp is not a recording of everything you hear.

Before preparing a handoff, save your current work and keep a separate copy. Tell the recipient whether this is a sketch for feedback, an editable collaboration or a final mix. A short message with the track name, tempo and requested next step prevents more confusion than a large folder with no explanation.

This guide covers two routes: FL Studio’s own zipped loop package, and SpendLess exports for projects already managed in its library. Neither route transfers a licence to commercial plugins or samples.

Open the project and resolve any existing missing-file warnings first. Choose File → Export → Zipped loop package, then save the ZIP to a location you can find. FL Studio packages the project with its samples. The recipient can open that ZIP directly in FL Studio.

A package cannot collect a sample that is no longer available on your machine. Keep the original session and send a copy of the exported archive. If you are copying a project data folder instead, include the whole folder rather than only its .flp.

For plugin compatibility, compare FL Studio versions and the plugins used before sending. Use the same or a newer FL Studio version at the destination. Windows cannot use macOS-only AU plugins. When the other producer cannot reproduce an instrument, render its part to audio in FL Studio and include that separately.

These steps follow Image-Line’s project-sharing guidance.

For a project already in SpendLess, use its export action and choose .zip or .spend. The exporter includes the project file and the files in its managed samples folder. It does not search the recipient’s computer or install missing instruments.

A .spend archive also carries SpendLess-specific project information and associated files, such as an attached cover or audio preview when present. Choose it when the recipient uses SpendLess. Choose ZIP for a more conventional file handoff, and verify the result in FL Studio.

Before export, check that the managed project opens correctly and that the samples you need are actually available. Do not assume changing the archive extension repairs unresolved file paths. After export, keep your original project until the recipient confirms the copy works.

New to the app? Start with the SpendLess installation guide and a simple organization system.

Use a separate test folder, or ideally the destination computer. Test the exported copy rather than reopening the original from your recent-files menu. A successful test on your own machine is useful, but it can still find sample libraries that your collaborator does not have.

Ask the recipient to check three things: the archive opens, the arrangement sounds as expected, and the project can be saved as a new working copy. Send a reference render so both of you can compare the sound. If a part differs, identify the instrument or audio file involved instead of repeatedly sending the same ZIP.

A concise handoff message could be:

Night Bus — arrangement 03. Please work on the drums. The ZIP is the editable session; the WAV is a listening reference. Let me know about missing files before changing the arrangement.

Do not overwrite your source session with the returned collaboration until you have reviewed it.

Separate the symptoms. A missing audio file, a missing instrument, a different preset and a muted mixer track are different problems. An archive may contain the audio while an instrument still depends on a library managed by a third-party plugin.

Record the exact warning and compare it with the files you included. If a source file was deleted before the export, recover it from your own backups or the original licensed library; exporting again cannot recreate it.

Keep one agreed project version for the next handoff, and name returned copies clearly. For a longer-term safety copy, read the projects and backups guide. A collaboration upload should not be your only backup.