Check your Logic Pro version before moving its Sound Library. Apple documents a movable library bundle for Logic Pro 12 and a Relocate Sound Library command for Logic Pro 11.2.2 and earlier. Following the wrong instructions can leave you searching for a menu that does not match your installation.
Open Logic Pro’s About window and record the version. Also decide whether you need the sounds available on a laptop without the external drive. Moving them frees internal capacity but creates a dependency on the destination.
Logic Pro 12: locate the library bundle
Apple says the default Sound Library file for Logic Pro 12 and MainStage 4 is Logic Pro Library.bundle in the Music folder. Its current Sound Library migration instructions describe moving that file to another location, including an external device.
Save and close your work, copy the bundle to the destination, and test the library in your installed app before removing the original. Treat the initial copy as a verification stage. Do not remove the only known working copy just because Finder finished transferring it.
Logic Pro 11.2.2 and earlier: use Relocate Sound Library
- Connect a suitable Mac-formatted destination with sufficient free space.
- Open Logic Pro > Sound Library > Relocate Sound Library.
- Select the destination and let the operation complete.
- Allow removable-volume access when requested.
- Open an existing project and check several library instruments.
Apple’s same support article gives the older workflow, destination restrictions, and permissions checks. Avoid substituting a manually created symlink for the supported procedure unless you have a specific, independently validated reason to do so.
Test more than one patch
Create a short verification list from your actual work: a drum instrument, a sampler instrument, and a project using sounds you downloaded later. Play the tracks and check for missing-content prompts. If you also use MainStage, include its working set in your checks.
A completed file transfer is evidence that bytes moved. A working project is evidence that the application can find what it needs. Both matter before removing the internal copy or leaving for a performance.
What this does not move
Your projects, recorded audio, third-party sample collections, plug-ins, and exports may have independent locations. Inventory these separately rather than expecting one Sound Library operation to relocate the entire music-production setup.
For example, if the library move frees space but the next recording session fills the internal drive again, check where that project records audio. Repeating the sound-library migration will not address a different destination.
If the destination is unavailable
Reconnect the expected drive before accepting any prompt that would download or reset content internally. Check the drive name, cable, available space, and the app’s removable-volume permission in System Settings. Keep the working drive identity stable so your setup remains easy to recognize.
Apple’s files-and-folders permissions guide explains the macOS access controls. For identifying other music storage, see our Logic storage overview and GarageBand sound-library guide.
Keep a backup separate from the working SSD. Before a live session, test with the exact drive and connection you intend to use, and retain an internal setup if portability matters more than the recovered space.