FL Studio 
Moving an FL Studio project safely means moving more than the FLP. The project file stores the arrangement and plug-in state, but it can still point to recordings, one-shots and third-party libraries elsewhere. The reliable move is: create the new project data folder, copy supported samples, save a new FLP there, reopen that copy, and keep the old folder until the complete song passes a dependency check. The project-folder controls and package limits below were checked September 4, 2026 against current Image-Line documentation.
Decide whether you are moving one project or all FL Studio data
FL Studio has two similarly named storage ideas. A project data folder belongs to the current song. The global User data folder contains projects, recordings, presets, the plug-in database scan and other user files for FL Studio as a whole. Changing one does not automatically perform the other job.
Use Project General Settings when one song needs a new folder or drive. Use Options > File settings only when you intend to relocate the entire Image-Line user-data tree. Image-Line advises keeping User data on a local, permanently connected drive rather than iCloud, OneDrive, Dropbox, a network path or a drive that can disappear during a write.
Make a rollback copy before the move
Open the project from its current location and use File > Save new version before changing paths. Note any missing-file warning now; a move cannot preserve a dependency that is already gone. Check that third-party instruments open and that their libraries are available. Then close any extra FL Studio windows that might save an older copy over the new one.
Create the destination on a drive with comfortable free space. Avoid putting a live working folder inside an automatically synchronized cloud directory. Cloud storage can still hold a closed archive, but a session that is recording, rendering and saving backups needs predictable local writes.
Set the new Project Data Folder
Open Project General Settings and find Project Data Folder. The current manual offers three modes:
- Don't use a data folder keeps using the global user-data and common locations.
- Store relative to the project file creates a same-name folder beside the FLP. Image-Line calls this the cleanest long-term project-management choice.
- Store in the specified folder lets you choose an explicit destination and is useful for a dedicated project drive.
For a new move, choose relative storage or a clearly named specified folder. A project folder can contain the FLP plus Audio, Renders and Backups subfolders. The setting is stored with the project, so save after choosing it.
Copy used samples and created files
Use Copy used samples to the project folder in Project Settings. In the accompanying File management choice, decide whether recordings, rendered audio, slices and other files created by the project should be copied or moved. That includes audio created when you consolidate Playlist tracks for editing or delivery. Copy is safer during migration because the original remains a rollback source.
Samples dragged from the Browser or another location normally stay where they were until you explicitly copy/package them. The official Project General Settings documentation distinguishes those referenced samples from recordings and dragged data created inside the project. Watch the destination folder populate; an empty Audio folder is not proof that every source file has been collected.
Save As to the destination and close the original
Use File > Save As and save a clearly named FLP in the new destination. Add a migration suffix if both copies will exist temporarily, for example songname_movecheck.flp. Save once more, close FL Studio completely, then reopen the FLP by browsing to the new folder, not from Recent projects, which can point to the old copy.
The close-and-reopen step matters because a project may play while old assets remain in memory. A fresh launch forces FL Studio and its plug-ins to resolve files from disk. If the title bar or Project Settings still shows the old path, stop and correct it before recording new material.
Verify the moved project before deleting anything
- Open the new FLP after a complete FL Studio restart.
- Play from the first bar through every section, including muted alternates.
- Open each sampler channel and check its source path.
- Open third-party samplers and load their instruments.
- Record a short test take and confirm it lands in the new Audio folder.
- Render a short WAV and confirm the default points to the new Renders folder.
- Save, reopen again, and inspect the project backup location.
If the project reports a missing sample, do not save over the last known-good copy. Use the original folder to locate the file, copy it into the new project, reload it, and repeat the clean launch. When several missing samples appear, stop and compare both folder trees before saving. The project recovery guide covers wider failure cases when the issue is more than a missing asset.
Know what an FLP, project folder and ZIP contain
A normal FLP retains project data but not the referenced wave samples. A project folder collects FLP data, recordings, renders, backups and the supported samples you tell FL Studio to copy. A zipped project packages the FLP with supported project samples and presets into one archive, which is convenient for an additional backup or transfer.
The current FL Studio project-file documentation is explicit about the limit: samples used inside third-party sampler plug-ins are not automatically included unless that plug-in has its own self-contained format. Keep those libraries, plug-in installers and licenses backed up separately. A ZIP is a useful archive, not proof that an unrelated sampler vendor's library has been embedded.
Move the global User Data Folder only when you mean it
To relocate all FL Studio user data, open Options > File settings and use the User Data Folder control. FL Studio can offer to copy existing data to the new location. Confirm the target contains the expected Image-Line structure before relying on it, then restart FL Studio and test the Browser, favorites, templates, recordings and several unrelated projects.
Do not select the application install directory, the root of a disk or a temporary external drive. The current File Settings manual explains both the default location and the risks of cloud-synced, network and removable storage. The installation guide covers host updates; it should not be used as a shortcut for moving user files.
Move the project to another computer without guessing
A project folder can carry the FLP and copied audio, but it does not contain every instrument, effect or licence needed to recreate the session. Before moving between computers, note the FL Studio build, the exact third-party plug-in formats and versions, and any library presets the song uses. FL Studio’s project-file documentation distinguishes the FLP from a zipped loop package: the ZIP can collect project data and samples, but installed plug-ins still have to exist on the destination system.
Open the copied project on the second computer before touching the original. Check for missing-sample warnings, silent plug-ins and substitutes loaded in place of the expected format. Windows VST paths and macOS Audio Unit locations are not interchangeable, and even the same product can expose a different plug-in identifier after a major update. If collaboration matters more than editability, also export clearly named audio stems from bar one. They are not a replacement for the project, but they give the recipient an audible reference and a recoverable fallback.
Build a project-folder habit for future sessions
Choose the folder when the song is created, not after dozens of recordings have accumulated in a global directory. Keep a short name, store alternate FLPs as sequential versions, and put deliberate exports under Renders. A local project backup and a separate offline or versioned backup protect against different failures; one is not a substitute for the other.
Before a long recording day, confirm the data folder and audio device together. The audio-settings guide handles the driver and buffer side; the clean recording route checks where each new take is written; and the beginner workflow keeps the first session orderly. Continue through the Workflow hub when the storage move is stable.
Frequently asked questions
Can I move an FL Studio project by moving only the FLP?
Only if every referenced sample and third-party library remains available at a path FL Studio can resolve. For a reliable move, copy supported samples to the project folder and test the moved FLP after a full restart.
What is Store relative to the project file?
It creates a same-name project data folder beside the FLP and stores project-created data in organized subfolders. Image-Line recommends it as the cleanest long-term project-management option.
Does a zipped project include every third-party library?
No. It packages the FLP and supported project samples, but content loaded inside a third-party sampler may remain external and must be backed up separately.
Should I put my FL Studio User data folder in OneDrive or iCloud?
Image-Line advises against cloud-synced, removable and network locations for live User data because files can be locked, moved or written late. Use local always-connected storage and back it up separately.
When can I delete the old project folder?
After the new copy survives a complete restart, full playback, plug-in/library check, test recording, render, save and second reopen. Keeping the old copy until an external backup also exists is safer.
