Logic → Pro Tools. Drop a Logic Pro .logicx project and get a native Pro Tools .ptx project — the real session rebuilt, not bounced to stems.
Full walkthrough: How to convert your session to another DAW
Every track, clip and automation lane — rebuilt natively in Pro Tools, not flattened to stems.
Third-party effects arrive as the same plugin with their saved settings when the plugin is installed on the Pro Tools machine, and stock plugins map to the closest native equivalent. Summing buses and sends arrive as real routing, and mixer automation lanes — volume, pan, mute, sends — carry over. Plugin-parameter automation lanes and third-party instrument state don't cross the Logic–Pro Tools boundary yet — they're reported, never silently dropped. Nothing is silently dropped.
Local conversions stay right in your browser — your session never leaves your computer, nothing uploaded, nothing stored. Uploaded sessions move over an encrypted connection into your own private space, with access only you control, and yours to delete anytime.
Logic Pro saves a project as a .logicx package; Pro Tools saves a session as a .ptx file (older versions: .ptf or .pts). So a Logic to Pro Tools converter, converting .logicx to .ptx (LOGICX to PTX), turning a Logic file into a Pro Tools file, opening a Logic project in Pro Tools, importing a Logic project into Pro Tools, exporting Logic to Pro Tools, and moving, transferring or migrating a project from Logic Pro to Pro Tools all name this one conversion — and it runs here, free to start, online, with nothing to install.
.logicx package (a folder macOS shows as one file)..ptx file (legacy .ptf / .pts), with its audio in the session’s Audio Files folder.Step by step: how to convert Logic to Pro Tools · the other way: Pro Tools to Logic (.ptx to .logicx) · every DAW converter direction
Not directly — Pro Tools can't read Logic Pro's .logicx format. Doseedo converts it: upload your .logicx (zip the .logicx package first — right-click it in Finder → Compress) and it rebuilds the session as a native Pro Tools .ptx project you can open and keep working in. The download is the whole Pro Tools session folder — the .ptx with its Audio Files/ — zipped, so it opens with the audio in place.
Logic Pro exports AAF and Pro Tools reads it, so AAF is the usual hand-off — but an AAF is an audio timeline: clips in position, edits, basic fades. No MIDI, no software instruments, no plugin state. The mix engineer opens a shell of your session and rebuilds around it. Converting the .logicx instead writes the session itself into Pro Tools — tracks named and ordered, MIDI clips at their arrangement positions, summing buses and sends as real routing, mixer automation lanes, and stock plugins mapped to their closest Pro Tools equivalents.
A real Pro Tools session folder — the .ptx together with its Audio Files/ — zipped, so it opens with every clip in place and nothing to relink. Tracks arrive named, ordered, leveled and panned, with your buses and sends as routing rather than a flat list of consolidated audio, so the mix starts from your session instead of from stems.
People describe the same job five ways — export Logic Pro to Pro Tools, import a .logicx into Pro Tools, transfer the project, open a Logic Pro project in Pro Tools — and none of it needs stems. Upload the .logicx and it converts to a native .ptx that opens in Pro Tools with tracks, MIDI, audio and the tempo map intact. Want to check the project first? Open the .logicx in your browser and play it before converting.
Tracks with their names, order, levels, pans, mutes and solos; MIDI clips at their arrangement positions with every note; audio clips with their files traveling in the session folder; summing buses and sends as real routing; mixer automation lanes (volume, pan, mute and sends); stock plugins mapped to real native equivalents; tempo, time signature and markers. Third-party effects arrive as the same plugin with their saved settings when the plugin is installed on the other side. Plugin-parameter automation lanes and third-party instrument state don't cross the Logic–Pro Tools boundary yet — they're reported, never silently dropped.
Third-party effects do — the same plugin arrives with its saved settings when it's installed on the Pro Tools machine, and stock plugins map to the closest native equivalent. Plugin-parameter automation lanes and third-party instrument state don't cross the Logic–Pro Tools boundary yet — they're reported, never silently dropped.
Your project is uploaded over an encrypted connection into your own private space, converted, and is yours to delete anytime.
2 conversions a month with no account, or 5 with a free account, both at full fidelity. Pro is $12/mo for 1,000 conversions a month, no watermark, cancel in one click. One conversion is one project translated one direction; a round-trip is two.
Zip the .logicx package (right-click it in Finder → Compress) and drop the zip on the converter above — the direction is read from the file — then download the .ptx and open it in Pro Tools. The .logicx isn't renamed or wrapped: the project is rebuilt as a native Pro Tools session — tracks, clips, MIDI, tempo map and markers in place.
Yes — this page. It runs in the browser on macOS, Windows, ChromeOS or Linux with nothing to install: 2 conversions a month free with no account, 5 with a free account, 1,000 a month on Pro at $12/month, every plan at full fidelity. You don't need Logic Pro installed to convert; you need Pro Tools to open the result.
Not directly — Pro Tools has no .logicx import and Logic Pro has no .ptx export; both formats are proprietary. Converting the project here rebuilds it as a native .ptx, and Pro Tools then opens that like one of its own sessions — that is the import.