Logic Pro or GarageBand Project Won’t Open? Read This

You open a Logic Pro or GarageBand project you have spent weeks on and it refuses to load, opens with empty regions, or greets you with a long list of missing audio files. For a home or project studio on a Mac this can feel like losing the whole song. Very often the recordings still exist and the project has simply lost track of them, but sometimes the real cause is a failing drive underneath. This guide explains how Logic and GarageBand store your work, what to check first, and when to stop before you make things worse.

How Logic Pro and GarageBand store a project

By default Logic Pro saves a project as a single .logicx file, and GarageBand uses a .band file. Each one is actually a package: a folder that the Finder displays as one document. Inside it are the arrangement, settings and, usually, the audio you recorded. You can look inside by Control-clicking the project in the Finder and choosing Show Package Contents.

The important detail is that audio does not always live inside the package. Logic can be set to copy audio files into the project, or simply to point at files wherever they already are: a samples folder, a Downloads folder, or an external drive. Projects that were moved, renamed or opened on a different Mac are the ones most likely to report missing files.

Common symptoms and what they usually mean

  • “Missing files” or audio regions shown as empty. Logic cannot find audio at the path it remembers. Often the files are on an external drive that is not connected, or a folder has been renamed or moved.
  • The project will not open at all, or Logic quits while loading. This can be a damaged project file, a plug-in that crashes on load, or the package being incomplete because it was copied from a failing drive.
  • Recent changes are gone. The project may have been saved over with an older version, or a sync service may have replaced it with an earlier copy.
  • The external audio drive will not mount, or mounts and freezes. This points to the drive itself rather than Logic, and needs handling with much more care.

Safe checks to try first

  1. Make a copy of the project before anything else. Duplicate the whole .logicx or .band package to another healthy drive, so that every experiment happens on the copy.
  2. Reconnect every drive the project used. If you record or keep samples on an external drive, connect it and make sure it has its original name. Logic finds files by their path, so a drive renamed from “Audio” to “Audio 1” can break every link.
  3. Use the missing files dialog carefully. When Logic reports missing audio it offers to locate or search for the files. Point it at the correct folder rather than skipping, then save the copy under a new name.
  4. Look for backups. Logic keeps automatic backups of a project each time you save. Open the project and use File > Revert to to see the available backups, and try the most recent one that predates the problem. If you used project alternatives, check those too.
  5. Rule out plug-ins. If Logic crashes during loading, a third-party plug-in may be the cause rather than your audio. Try opening the copy on another Mac, or with the problem plug-in removed, before assuming the recordings are lost.
  6. Check Time Machine and any cloud folders. An older complete copy of the project package, audio included, may already be in a backup.

When the drive is the real problem

Studios tend to work drives hard: large sessions, long recordings and sample libraries streamed from external disks. If the drive holding your projects is clicking, disconnecting during playback, mounting read-only or making the Mac beachball whenever it is plugged in, the missing files are a symptom, not the cause. In that situation:

  • Stop opening the project and stop letting Logic search the drive. Every scan and every attempt to load a session reads large amounts of data from a disk that may be failing.
  • Do not run Disk Utility First Aid repeatedly or use a “repair” app on it. These tools write to the drive and can make a failing disk worse.
  • Do not reformat it or let macOS initialise it if it asks.
  • Power it down and keep it safe until the important projects have been recovered.

If the project lives on the Mac’s internal SSD and the Mac itself will not start, the situation is different again. On many recent Macs the storage is built into the logic board and encrypted, so the drive cannot simply be removed and read elsewhere. Our pages on Apple Mac data recovery and MacBook data recovery explain more.

Protecting the next project

  • Set Logic to copy audio files into the project, so the package contains everything it needs.
  • When moving a project to another drive or Mac, use File > Save As with the option to copy assets, rather than dragging the package alone.
  • Keep at least one backup of active projects on a separate drive, and check from time to time that the backup actually opens.
  • Replace a studio drive that has started disconnecting or slowing down before it fails completely.

Speak to Data Retrieval

If your sessions are on a drive that has stopped behaving, or the project and its audio cannot be found anywhere, call Data Retrieval on 020 7064 4996. We offer a free assessment with no obligation, or you can request a quote online.