macOS audio & VST compatibility checker
DAWs & production stack
Your setup is analyzed locally in this browser.
02What’s in your setup?
Browsers cannot scan your PC. Import an inventory JSON from a local scanner, or enter a list.
View import format
JSON up to 5 MB · up to 10,000 components · imported verdicts are recomputed.
{
"schemaVersion": 1,
"vertical": "studio",
"platform": "macos",
"architecture": "arm64",
"generatedAt": "2026-10-05T00:00:00Z",
"host": {
"name": "macOS",
"version": "15"
},
"components": [
{
"id": "my-component",
"name": "My component",
"version": "1.0",
"category": "DAW",
"critical": true
}
]
}What’s in your setup? 0
Changes to your setup recalculate the report immediately.
My setups
03Upgrade verdict
Loading environment data…
Your inventory · Missing verified evidence stays UNKNOWN.
Compare target
Full compatibility report
| Component name | Installed | Recommended | Status | Evidence confidence | Reason |
|---|
Your entire music production stack
macOS and Apple Silicon upgrades involve DAWs, VST2/VST3/AU/AAX, audio interfaces, drivers, control software and license managers. Import the inventory with a pasted list or scanner JSON.
Native, Rosetta and driver dependencies
Specify the DAW, plugin formats and runtimes in advanced options. Evidence-backed Rosetta/Intel constraints and driver/license dependency failures affect the dependent components too.
Studio Preflight evaluates a music production inventory before an operating-system update. Include the DAW, audio interface, drivers, control software, license managers and audio plugins, not just VST files. Specify the target architecture, available plugin formats and runtimes. Dependencies and source-backed native or Rosetta requirements influence the report. The initial catalog needs additional vendor statements before real product compatibility can be affirmed.
How it works
Music stack: Being listed in the catalog does not establish compatibility.
Music stack: Based on source authority, verification dates and the weakest relevant requirement.
Worked example
A fictional music Mac changes from OS 15 to 26. Its driver is blocked and its audio plugin needs a translated execution mode; the report does not approve the upgrade.
SAMPLE: macOS 15 → 26Check the result
- Music stack: Your inventory · Missing verified evidence stays UNKNOWN.
- Music stack: Your setup is analyzed locally in this browser.
Troubleshooting
| Symptom | Likely cause | How to check | Fix |
|---|---|---|---|
| Music stack · Unknown compatibility | No verified statement matches the target | Read the vendor link and installed version | Keep the verdict cautious until verified |
| Music stack · Dependency failure | A required runtime is missing or blocked | Open the component dependency section | Resolve the dependency before upgrading |
| Music stack · JSON rejected | Wrong vertical or unsupported inventory schema | Check schemaVersion, host and component IDs | Export a version 1 inventory for this vertical |
Other ways to do it
| Option | When it is the better choice |
|---|---|
| Vendor documentation | Music stack: Verify target support for with the vendor. |
What this page does not cover
- Music stack: SAMPLE DATA · Fictional components for demonstration. Not real product compatibility.
- Music stack: Browsers cannot scan your PC. Import an inventory JSON from a local scanner, or enter a list.