How to organize your Logic Pro projects

Organizing Logic Pro projects comes down to four decisions: keep every project under one top-level folder, choose deliberately between saving as a package and saving as a folder and then stick to it, tick the boxes that copy your audio and sampler content into the project so it stays self-contained, and keep tempo, key and status somewhere you can search across the whole library. Logic's own habit of hiding everything inside a .logicx package is what makes the last one hard: the file system shows you one icon per song and tells you nothing else about it.

The package is the whole problem

Logic saves a project as MySong.logicx, and macOS presents that as a single file even though it is really a folder in disguise. That is a good design decision for moving projects around, and a genuinely annoying one for finding anything, because Finder can show you a name and a modified date and nothing more. There is no tempo column, no key column, and no way to tell a finished master from a four-bar loop you abandoned in 2021 without double-clicking it and waiting for Logic to load.

You can right-click and choose Show Package Contents to look inside, where you will find Alternatives, Resources, Media and often a Bounces folder. That is worth knowing about once, for the day you need to rescue a file out of a project that will not open. It is not a way to organize a library, and poking around in there while Logic is not looking is how projects get broken.

1. One folder above all your projects

Whatever else you do, put every project under one top-level folder. Logic's default of Music/Logic is fine. The value is not tidiness for its own sake, it is that one location can be backed up, searched and scanned as a set. Projects spread across the Desktop, iCloud Drive, Downloads and an external SSD cannot be treated as a library, because nothing can see all of them at once.

2. Package or folder, but pick one

Logic's Save dialog offers Organize my project as: Package or Folder. A package is one draggable icon and is the right default for most people. A folder puts Audio Files, Bounces and the rest beside the project as normal directories, which is easier when you need to reach the audio directly, hand stems to someone, or keep a project on storage that dislikes enormous bundles. Both work. What causes trouble is drifting between them over the years, so half your library is one shape and half is the other, and any rule you invent applies to only some of it.

3. Copy your assets in, or old projects will open incomplete

This is the Logic equivalent of the missing-samples problem, and it is the one worth being strict about. When you save, Logic offers to copy the following files into your project: audio files, sampler instruments and samples, impulse responses, movie files. If you leave those unticked, the project merely points at wherever those files happened to live that day. Move a sample library, clean out a scratch folder, or open the project on another Mac, and pieces of it are simply gone.

If you have already been sloppy about it, Logic can fix a project after the fact through File → Project Management → Consolidate, which gathers the assets into the project. Do that on anything you are archiving or sending to a collaborator, before you need it rather than after.

4. Bounce everything worth remembering

A project file holds no audio you can hear without loading Logic. Bounce a reference of every idea worth revisiting, and keep those bounces somewhere consistent, named to match the project. A single exports folder for everything is the easiest arrangement to keep up, and it means any tool, including Finder's own search, can find a track by name in a second.

5. The list nobody keeps

Everything above is a habit you can hold to. The one that fails is the searchable catalog. Every Logic project already knows its tempo, and any project where you set a key signature knows that too, along with the exact version of Logic that last saved it. All of it is sealed inside the package where nothing outside Logic will show it to you, so answering "what have I got around 90 BPM in D minor that is nearly finished?" means opening projects one at a time or maintaining a spreadsheet by hand.

What Saltado Sessions does for Logic Pro

Saltado Sessions scans wherever your projects live, reads what each one already knows, and turns the result into a searchable, sortable, ratable library. It treats a .logicx package as one project and never descends into it, which is the correct behaviour and not a limitation: the inside of a package is Logic's business, and a tool that listed its internals as separate projects would be actively wrong.

Logic is also the one non-Ableton format that gives up a key, so Logic projects get both tempo and key in the library without you typing anything. Here is the honest full picture rather than a feature list that quietly assumes Ableton.

The plugin row deserves a straight answer rather than a footnote. Logic keeps its plugin data in opaque binary chunks, so there is no reliable way to read it from outside the app. Sessions leaves that field empty instead of guessing, on the principle that a plugin list which is quietly wrong is worse than one that is honestly absent. The deepest reads, meaning the per-sample list, missing-sample detection, the arrangement view and the browser-based compatibility checker, are built on Ableton's .als format and are not claimed for Logic. Everything that does not depend on a session's internals works identically: ratings, statuses, tags, notes, search, collections, bounce previews, loudness metering, backups, and the record of which labels heard which track.

One practical note on bounces: because a package is treated as opaque, the surest way to get previews working is to point the app at the folder you bounce into. Name-matching then pairs each bounce with its project automatically, and you can always pick a different file by hand.

Common questions

Should I save Logic projects as a package or as a folder?

A package is tidier to move around, because the whole project is one icon you can drag, and it is the better default for most people. A folder is easier to work with when you want to reach the audio files, bounces and movie files directly, or when the project lives on a drive or a sync service that copes badly with very large bundles. Both are fully supported, and either way the important habit is copying your assets into the project rather than leaving them referenced from elsewhere.

Does Saltado Sessions look inside a Logic package?

Only to read the project metadata, never to list or rearrange what is in there. A Logic project package is treated as one project, not as a folder of files, so the app never descends into it and never presents its contents as though they were separate projects. The inside of a package belongs to Logic.

Can it show me which plugins a Logic project uses?

No. Logic stores its plugin data in opaque binary chunks rather than anything readable from outside the app, so there is no honest way to list them. The app leaves that blank instead of guessing, because a plugin list that is quietly wrong is worse than one that is absent. Tempo, key and the Logic version each project was saved from are all read normally.

What happens with project alternatives?

The project is listed once, as one project, and its tempo and key are read from the primary alternative. Alternatives are a feature inside Logic for trying different versions of the same song, so splitting them into separate rows would misrepresent the library. If you want two ideas tracked separately, save them as two projects.

Working in more than one DAW? The same library holds all of them side by side. There is a companion guide to organizing Ableton Live projects, which goes deeper because the .als format gives up more, and one for FL Studio projects. You can also start from the overview if you want to see the whole app first.