Where Does MuseHub Install Things? Windows and macOS Paths
MuseHub uses different folders for the desktop app, plugins, loops, MuseSounds, and courses. This MuseHub install guide starts with the operating-system path that matches your product, then shows how to confirm the format before moving or deleting anything.
On macOS, MuseHub installs the app in /Applications, Audio Units and VST3 plugins in the standard /Library/Audio/Plug-Ins folders, and user content below ~/Library/Application Support/Muse Hub. On Windows, the app uses C:\Program Files, VST3 uses C:\Program Files\Common Files\VST3, and user content is under C:\Users\{USER}\Muse Hub. Elements, Instruments, and Courses have separate subfolders.
Default locations at a glance
| macOS app | /Applications |
|---|---|
| macOS plugins | /Library/Audio/Plug-Ins and the user Audio Plug-Ins folder |
| macOS user content | ~/Library/Application Support/Muse Hub/Elements and Instruments |
| Windows app | C:\Program Files |
| Windows VST3 | C:\Program Files\Common Files\VST3 |
| Windows user content | C:\Users\{USER}\Muse Hub\Elements, Instruments, and Courses |
MuseHub install locations on macOS
The MuseHub install on macOS normally places the desktop application in /Applications. Launching the copy in Applications matters because a package left in Downloads, a mounted disk image, or a temporary folder can behave differently when macOS applies permissions and background-item rules. If you see more than one MuseHub icon, open Finder, choose Applications, and use that copy before troubleshooting.
Plugins use the normal macOS audio locations. Audio Units are commonly found in /Library/Audio/Plug-Ins/Components or the matching folder inside your home Library. VST3 products use /Library/Audio/Plug-Ins/VST3 or the user VST3 folder. A product can also have a vendor-specific installer, so the presence of a file in MuseHub does not guarantee one fixed path for every plugin.
MuseHub user content is kept under ~/Library/Application Support/Muse Hub. The official location article separates Elements for loops and related content from Instruments for MuseSounds. Courses may have their own product folder. The tilde means your home folder, so two macOS accounts on the same Mac can have different content locations.
MuseHub install locations on Windows
The MuseHub install on Windows normally places the application under C:\Program Files. Windows may hide some folders from casual browsing, and a managed computer can apply different permissions to Program Files. Use File Explorer's address bar or the Run dialog to open a known path instead of guessing from a shortcut's display name.
VST3 plugins normally use C:\Program Files\Common Files\VST3. That is a shared host folder, not the same place as your MuseHub downloads. If a plugin does not appear in a DAW, check the DAW's plugin scan path, the product format, and whether the installation finished. Do not copy a DLL into the VST3 folder just because the filename looks similar.
Per-user MuseHub content is stored below C:\Users\{USER}\Muse Hub. Replace {USER} with the Windows account name. The official table identifies Elements, Instruments, and Courses as separate folders. Another account on the same PC will not automatically see the same libraries, and a Windows service account is not a safe destination for personal content.
| Content | Windows path | What it usually contains |
|---|---|---|
| Application | C:\Program Files | MuseHub desktop application files |
| VST3 | C:\Program Files\Common Files\VST3 | VST3 plugin binaries |
| Elements | C:\Users\{USER}\Muse Hub\Elements | Loops and element content |
| Instruments | C:\Users\{USER}\Muse Hub\Instruments | MuseSounds and instrument data |
| Courses | C:\Users\{USER}\Muse Hub\Courses | Course downloads when supplied by a product |
Can you change the MuseHub download location?
The official location table documents the default folders; it does not promise one universal switch that relocates every application, plugin, loop, MuseSound, and course. Some products can expose a custom content setting, while the desktop app and plugin formats still follow operating-system conventions. Treat a setting as product-specific unless the current MuseHub screen and support article describe it clearly.
Moving a large library is different from moving the manager application. Copy the library only after closing MuseHub, preserving folder names and permissions. Keep the original until the new location is recognized and a product opens successfully. If MuseHub offers a rescan or repair action, use it instead of editing database files by hand.
When upgrading from an older MuseHub release, read the current first-party migration guidance. Newer per-user paths can differ from legacy root-level folders, and Windows migration behavior is not identical to macOS migration. Back up projects, note custom locations, and expect that an affected library may need a controlled re-download if its metadata cannot be migrated.
Troubleshoot a missing app, plugin, or library
If MuseHub itself is missing, check Applications on macOS or the Start menu and system tray on Windows. A hidden tray icon does not mean the application was not installed. On macOS, confirm that the app is in Applications and that its background permission remains enabled. On Windows, check whether security software quarantined the installer or whether a work policy blocks Program Files changes.
If a plugin is missing, confirm the format first. A VST3 plugin will not appear in a host that scans only Audio Units, and an Audio Unit will not appear in a Windows host. Rescan from the host's own settings, restart it, and check that the install completed before moving files manually.
If MuseSounds or Elements are missing, open the per-user folder for the same account that owns the MuseHub installation. Check free disk space and the product's download state, then use MuseHub's repair or retry controls. For account, authorization, network, or update problems, continue with the MuseHub troubleshooting guide instead of deleting content as a first step.
- Confirm the app is running from the standard Applications or Program Files location.
- Check the exact host format and scan path before copying plugin files.
- Match the content folder to the signed-in operating-system user.
- Leave metadata and manifests intact when backing up a library.
- Use official support instructions for migrations or repeated authorization errors.
MuseHub install location FAQ
Where does MuseHub install on Windows?
The app normally uses C:\Program Files, VST3 uses C:\Program Files\Common Files\VST3, and per-user Elements, Instruments, and Courses folders are under C:\Users\{USER}\Muse Hub.
Where does MuseHub install on a Mac?
The app normally goes to /Applications. Plugins use the standard Audio Plug-Ins folders, while user content is under ~/Library/Application Support/Muse Hub.
Where are MuseSounds stored?
The official table places macOS instruments under the Muse Hub Application Support Instruments folder and Windows instruments under C:\Users\{USER}\Muse Hub\Instruments.
Where are MuseHub loops stored?
Loops and Elements are normally under the Elements folder in the Muse Hub user-content directory for the current operating-system account.
Can I move the MuseHub application to another drive?
The default app paths are platform-managed. Some content may support a custom location, but do not move folders until the product documentation or MuseHub setting confirms the workflow.
Why can’t my DAW see a MuseHub plugin?
Check whether the product is VST3 or Audio Unit, confirm the host scans that format and folder, finish the installation, then rescan from the DAW.
Does every user on Windows share MuseHub content?
No. MuseHub content is stored under the installing user's profile, so another Windows account may need its own installation, permissions, or product access.
Official location sources
The path table and product distinctions were checked against the MuseHub Help Center on October 8, 2026.
- Where does MuseHub install things? - Official application, plugin, loop, instrument, and course locations.
- Updating from MuseHub v1 - Migration cautions for older content locations.
- MuseHub system requirements - Platform, architecture, and product compatibility context.