Logic Pro Files

Fix a problem / Mac

A Logic Pro project will not open: recover a copy without overwriting it

Documentation reviewed 8 November 2026 · Logic Pro for Mac

Quick answer

Preserve the original project and its media before testing. Check whether Logic can open a new empty project: an application-wide launch failure and one session that will not open need different routes. Work on copies, inspect available project backups or alternatives, and verify recovered audio and edits before replacing your working version.

Illustration of recovering a working project copy while protecting the original.
AI-generated editorial illustration, not a Logic Pro screenshot.

Match your symptom

What happensFirst check
Every project fails, including a new oneTroubleshoot the application or device first
Only one session failsDuplicate it and isolate project dependencies
A project opens but recent edits are wrongInspect available backups or alternatives
The arrangement opens but audio is missingLocate media rather than reverting blindly
Check order: Decide whether the fault belongs to the app or one project; Keep an original and a clearly named test copy; Inspect the backups and alternatives that actually exist; A recovered arrangement still needs its media; Prepare a reproducible case if nothing opens
Check order. Use the section links below for the full instructions.

Decide whether the fault belongs to the app or one project

Note the exact failure: quit during launch, hang while loading a named plug-in, missing-file alert or a session that opens in an unexpected state. Try a new empty project with a simple setup. This comparison narrows the area; it does not prove the original file is corrupt.

If even a new project cannot open, start with crashing and startup checks. Reinstalling the app will not automatically restore a previous arrangement or bring back missing recordings.

Keep an original and a clearly named test copy

Duplicate the project before attempting a repair and preserve its referenced audio. If media is held outside the package or project folder, copy or back up that location too. Do not overwrite the only surviving project while comparing recovery candidates.

On a copy, use the documented startup options to compare loading without third-party Audio Units where appropriate. If that changes the outcome, investigate plug-in dependencies rather than declaring all project data damaged. Return to plug-in validation and compatibility for the relevant branch.

Also check that the project and storage are accessible locally. Opening a partially downloaded cloud file or a project on an unavailable external drive is a different failure from a bad arrangement.

Inspect the backups and alternatives that actually exist

When the project can open, inspect File > Revert to for available backups and File > Project Alternatives for saved alternative states. These controls and their visibility depend on the version and configuration. The linked archived Apple guide documents the distinction; it is not proof your session has a particular backup.

Open a candidate on the test copy, compare the arrangement and save a separate recovered project. Alternatives share assets with the project and are not a substitute for an independent media backup. Check a Time Machine or other independent backup if the project itself cannot be opened.

Do not remove alternatives or manually delete package contents while investigating. Their names and dates alone are not enough to decide which copy contains the right takes.

A recovered arrangement still needs its media

A backup may restore edits while still referencing audio on another disk. If the recovery opens with missing-file warnings, follow the original-media checks. Confirm that the matched files are the right takes, not just files with the same name.

Once a recovery candidate plays correctly, collect the assets in that copy and use the handoff and archive checklist. Keep the source and failed copy until the recovered version is verified.

Prepare a reproducible case if nothing opens

Record the Logic and macOS versions, whether a new empty project works, the exact alert, the last change before the problem and whether the copy behaves differently without third-party processing. Provide those facts to Apple or the relevant vendor. A procedure cannot guarantee restoration of an overwritten or deleted project.

Verify the fix

  1. Listen from beginning to end and inspect edits, automation and the expected takes.
  2. Save the recovered version under a new name, close it and reopen it.
  3. Make a separate backup that includes the media before replacing any working copy.

If the result changes, note which check changed it. If it does not, undo the test where appropriate and follow the next relevant branch. A failed test narrows the problem; it does not identify a component with certainty.

Frequently asked questions

Will reinstalling Logic recover a song?

Reinstalling replaces the application. It does not automatically restore a previous project state or missing recordings.

Are project alternatives independent backups?

No. They are alternative states within a project and share its assets. Keep an independent backup too.

Sources and version notes

Based on Apple documentation; reviewed 8 November 2026. This is a documentation review, not a claim of hands-on testing on every Logic, macOS or interface version. Archived guides are labelled; confirm menu names in the help for your installed release.