Logic Pro collaboration

Published November 2026

Logic Pro has no shared-project mode: two people cannot edit one Logic project at the same time with Logic alone. There are three ways round it. Send the project to another Logic user and take turns. Send stems or a converted project to someone in another DAW. Or keep your project in a Doseedo session with Dø Desktop (in beta), where collaborators work on it in the browser: your changes go up when you save, and theirs come into Logic with a quick save, close and reopen.

With another Logic user: send the project

Choose File › Save As… and tick the options that copy audio files (and sampler and other assets) into the project, so the copy you send carries every file it plays. Send that, by AirDrop, a cloud drive or a transfer service. Your collaborator needs the plugins the project uses, and a version of Logic at least as new as the one that saved it.

Then take turns. Two copies of one project edited at once cannot be merged afterwards: whoever saves second wins, or you end up with two versions of the song. Agree who has the project at any moment and put a version in the file name.

With someone in another DAW

If they only need your sound, send stems: File › Export › All Tracks as Audio Files…, every track from bar 1, at the project’s sample rate, with a note of the tempo and key. If they need to edit your parts, convert the project instead: Logic to Ableton, Logic to FL Studio, Logic to Pro Tools and Logic to REAPER rebuild the project in their DAW with MIDI, automation and markers editable. Both are one person at a time.

Logic Pro in a shared Doseedo session

With Dø Desktop on your Mac, your Logic project can be one side of a shared session. You invite collaborators with a link, and they work on the session in the browser studio. This is what each direction does:

A second Logic user, or someone in Ableton Live, FL Studio, Pro Tools or REAPER, can’t work on the session from their own DAW yet. The overview walks through starting a session and inviting someone.

What a collaborator’s change does to your project

Logic keeps an open project in memory and never rereads it from disk, so a change cannot simply be dropped into a running project. Once changes have stopped arriving for 2 seconds, Dø Desktop asks you, then:

1. If the project is open, saves it, so your own unsaved work goes to disk first, and closes it.
2. Backs the whole project up under ~/Music/Logic/Dø Desktop Backups/, keeping the last 20.
3. Writes the changes into the project file, leaving the rest of your project as it was.
4. Reopens the project.

You can undo it, which puts the backup back, and if writing fails the backup goes back by itself. Dø Desktop needs Accessibility permission to save, close and reopen the project, and asks for it the first time.

What to know first

• Changes cross when you save. Press ⌘S for your changes to go up; nothing is sent as you play.
• Not everything crosses yet. Edits to regions and notes, solo, plugin automation, track colours and tempo changes later in the song don’t sync yet.
• One Logic Mac per session. Only the Mac that synced the project receives track changes.
• Only a session you are working on syncs. An action in Dø Desktop arms the session for 12 hours; a project that is merely open in Logic is never sent.

Related

• DAW collaboration across DAWs: the overview
• Logic and Ableton together
• Let Claude or ChatGPT edit your Logic project
• What is a .logicx file?