The reason Launchpad folders mattered is simple: app categories are personal. A system may categorize an app as Productivity, Utilities, Developer Tools, or Graphics, but your actual workflow might place it somewhere else. A developer may want Xcode, Terminal, TablePlus, Docker, Paw, and Safari Technology Preview together. A photographer may group Lightroom, ImageOptim, camera vendor utilities, cloud backup, and invoice software. A teacher may want presentation tools, screen recording, grading apps, and curriculum resources in one place.
When a launcher removes custom folders or makes them harder to maintain, the app library becomes less useful even if launching still works. A search box can open a known app, but it does not help you browse a work area. Good folders create context. They answer the question "what tools do I use for this job?" rather than only "what is the name of the app?"
That is why the macOS Tahoe shift from Launchpad toward Apps and Spotlight feels different depending on the user. If you always typed app names, the change may feel like cleanup. If you built folders around projects, clients, games, creative work, or family use, the change removes part of the map.
Native folder workarounds
The Finder workaround is to create folders or aliases and add them to the Dock. This can be effective for a small number of stable categories. You can make folders such as Writing, Design, Finance, and Utilities, put aliases inside them, and access them from the Dock. It is free, transparent, and backed by macOS rather than a third-party app.
The downside is maintenance. Finder aliases are not launcher-native. New apps do not automatically appear in the right place, duplicates can creep in, and the experience is not full-screen or page-based. It also mixes launching with file management, which is not how many users think about their applications.
Spotlight's Apps view is the other built-in answer. It can browse apps and filter categories, and it is excellent when you know enough to search. But it does not restore user-defined Launchpad folders. Automatic categories are useful for discovery; they are not the same as your own project map.
What proper launcher folders need
A Launchpad-style folder system should support drag-to-folder creation, inline renaming, manual sorting, page overflow, and clear folder previews. It should also support undo. Folder organization is easy to damage during cleanup, especially when moving several apps at once. If a launcher lets you reorganize, it should also let you recover.
Nested folders are not necessary for everyone, but they are useful for large app libraries. A broad Work folder can contain Client Tools, Meetings, Finance, and Writing. A Games folder can separate stores, launchers, utilities, and actual games. A Utilities folder can separate cleanup tools, network tools, and system information. Nesting should not be forced, but it should be available when app count justifies it.
Folder search is another important detail. If you search for "finance", the launcher should understand that the folder name matters. If an app is inside a folder, search should still find it. Users should not need to remember whether an app is on page three or inside a nested category.
| Folder feature | Why it matters |
|---|---|
| Manual sorting | Preserves spatial memory instead of alphabetical drift. |
| Nested folders | Keeps large libraries browsable without endless top-level categories. |
| Folder search | Lets category names act as retrieval cues. |
| Undo and backups | Makes reorganization less risky. |
| Hidden apps | Keeps helpers, uninstallers, and vendor tools out of the main path. |
How LaunchingPad approaches folders
Why LaunchingPad is the best Launchpad replacement for folders
LaunchingPad treats folders as part of the launcher layout, not as a Finder workaround. You can group apps, rename folders, use nested folders, move apps across pages, and rely on search when you do not remember the exact location. The goal is to preserve the simple Launchpad mental model while adding features that make larger libraries manageable: multi-select moves, undo, smart folder names, hidden apps, and saved arrangements.
The feature-page details are exactly what folder-heavy users need: folder name suggestions turn groups of apps into readable categories, folders can contain folders, spring-loaded drag opens a destination while you are still moving an app, open folders can have their own pages and grid sizing, and nested folders can be moved back out or broken apart as your library changes.
If folders are the reason you miss Launchpad, LaunchingPad is the best replacement because folders are a core feature rather than a workaround. It restores the personal app library that automatic categories and alphabetical lists cannot provide. For many Mac users, that is the difference between an app drawer and an app library.