Find Intel Plug-Ins, Drivers, and Extensions on Your Mac (Beyond the App List)

If you've already audited the apps on your Mac for Apple silicon readiness, you've done the easy part. The harder part is everything that doesn't show up in /Applications: audio plug-ins, video effects, Photoshop filters, Spotlight importers, QuickLook generators, virtual cameras, launch agents, and the helper binaries tucked inside otherwise-Universal apps. All of these are independent Mach-O binaries with their own architecture, and any one of them can be the reason a feature you depend on stops working on macOS 28.

Rosetta Check 2.0 scans for all of them. Here's what's actually on your Mac, why it matters, and how to find it.

Why plug-ins are the next Rosetta problem

A Universal host app loading an Intel-only plug-in is a uniquely awkward failure mode. The host opens, the splash screen looks normal, the project loads, and then the plug-in slot is empty. Or the file format your scanner saves to has no thumbnail, or the camera you usually use in Zoom isn't in the list. Nothing crashes. Nothing alerts you. The feature simply isn't there.

Once macOS 28 ships in autumn 2027 and Rosetta 2 is gone for general use, every Intel-architecture component on your Mac falls into this silent-failure category. Auditing apps catches the obvious cases. Auditing plug-ins, extensions, and helpers catches the rest. For many Macs, the rest is where the real exposure lives.

What macOS treats as "code that needs to be Intel-or-not"

Apple silicon readiness isn't a property of an app. It's a property of every Mach-O binary on disk. A Mac running entirely on macOS 26 typically has hundreds of these scattered across well-known directories. Rosetta Check organises them into eight categories, each of which is scanned independently.

Audio

Found under ~/Library/Audio/Plug-Ins/... and /Library/Audio/Plug-Ins/..., plus the Avid plug-in folder for Pro Tools.

• Audio Units (.component)
• VST and VST3 (.vst, .vst3)
• AAX (.aaxplugin, used by Pro Tools)
• HAL drivers (.driver, used by virtual audio devices like BlackHole, Loopback, Krisp)
• MIDI drivers (.plugin)

A single Intel AU loaded by Logic Pro on macOS 28 won't fail loudly. The host will simply skip it and your project will be missing an instrument or effect. For musicians and audio engineers, this is the largest exposure surface on the Mac.

Video

• FxPlug (.fxplug, used by Final Cut Pro and Motion)
• OFX (.ofx.bundle, used by DaVinci Resolve, Nuke, Fusion)
• Motion templates (.moti)
• Premiere Pro plug-ins (.bundle inside the Premiere app)
• After Effects plug-ins (.plugin inside the After Effects app)

The Adobe video plug-ins live inside the host app's bundle rather than in a shared system folder, so a generic disk scan misses them. Rosetta Check enumerates the Adobe apps explicitly and walks their internal Contents/Plug-ins directory for each.

Photo

• Photoshop plug-ins (.plugin)
• Illustrator plug-ins (.aip)
• Lightroom Classic plug-ins (.lrplugin)
• Capture One plug-ins (.coplugin)
• Sketch plug-ins (.sketchplugin)

Same pattern as the video category: Photoshop and Illustrator plug-ins live inside the parent app, so they're walked vendor-by-vendor.

3D

• Cinema 4D modules (.xdl64)
• Maya plug-ins (.bundle)
• Houdini plug-ins (.dylib)
• Rhino plug-ins (.rhp)

Niche by population, but a single Intel plug-in here can break a production pipeline.

System extensions

These are the categories most users have never thought about, and they're also the ones most likely to ship in legacy form from third parties.

• Spotlight importers (.mdimporter). These decide which file formats are searchable by content. An Intel importer means that file format silently stops being indexed.
• QuickLook generators (.qlgenerator). These power Finder previews and Spacebar quick look. An Intel generator means the file's preview goes blank.
• Preference panes (.prefPane). Third-party panels that appear in System Settings. An Intel pane simply vanishes from the list.
• Input methods (.app in Input Methods). Third-party keyboards and IMEs.
• Screen savers (.saver).
• Color pickers (.colorPicker).
• Services (.service). Right-click menu items.
• Mail bundles (.mailbundle).
• Internet plug-ins (.plugin). Legacy NPAPI-style components.
• Filesystem bundles (.fs). Third-party filesystem drivers.
• Third-party Frameworks (.framework in ~/Library/Frameworks or /Library/Frameworks).

If you have Sophos, MacFUSE, NTFS for Mac, or any utility that integrates deep into the OS, this category is where its components live.

Virtual cameras

• CoreMediaIO DAL plug-ins (.plugin in /Library/CoreMediaIO/Plug-Ins/DAL)

This is how OBS Virtual Camera, Snap Camera, mmhmm, and Reincubate Camo expose themselves to Zoom, Teams, FaceTime, and Safari. An Intel DAL plug-in on macOS 28 means the virtual camera is no longer selectable in any video conferencing app.

Helpers

• LaunchAgents (.plist in ~/Library/LaunchAgents and /Library/LaunchAgents)
• LaunchDaemons (.plist in /Library/LaunchDaemons)
• Privileged helper tools (binaries in /Library/PrivilegedHelperTools)

The plist itself isn't a binary, but it points at the executable that gets launched at login or at boot. Rosetta Check follows the Program / ProgramArguments keys to the underlying binary and reads its architecture from there. Many auto-update agents, syncing tools, and background services live in this category, and an Intel helper that won't launch on macOS 28 may break the parent app's update flow even if the parent itself is Universal.

Embedded inside .app bundles

This is the category that catches the most experienced users by surprise. macOS apps can ship as a Universal main binary that contains an Intel-only sub-binary inside their internal directories. The app launches fine on Apple silicon, runs natively, and then silently fails to start a sub-feature when the embedded helper won't load.

• App extensions (.appex in Contents/PlugIns)
• XPC services (.xpc in Contents/XPCServices)
• Login items (.app in Contents/Library/LoginItems)
• Embedded frameworks (.framework in Contents/Frameworks)
• Embedded helper binaries (anything in Contents/Helpers)

Rosetta Check deep-inspects every .app bundle on your Mac for these, separately from the parent app's architecture, so you can spot Universal-app-with-Intel-helper combinations. These are the most insidious form of Rosetta dependency that exists.

How Rosetta Check finds them

The scan uses two complementary strategies, neither of which involves crawling your entire disk or asking for Full Disk Access.

For the standard plug-in folders (Audio, Video, Photo, System Extensions, Virtual Cameras, Helpers), each detection rule runs as an NSMetadataQuery with a Spotlight predicate of the form "path begins with this folder, and extension matches this pattern." Spotlight responds in milliseconds, even on Macs with thousands of plug-ins, and the scan respects the system's existing index permissions.

For vendor-walked plug-ins (Adobe, Avid, Maxon, Autodesk, SideFX), Rosetta Check first finds the parent app by bundle identifier prefix, then walks that app's internal plug-in directory directly. Spotlight isn't used here because the contents of an .app bundle aren't indexed.

For embedded items, every .app bundle on your Mac is deep-inspected for the five embedded sub-paths. The architecture for each finding is read with the same Mach-O parser used for the main app scan: a few bytes of header read, no execution, no crash risk.

The result, in the app's Components view, is a list grouped by the eight categories above, with per-category readiness gauges and a host label on each row. You see "Photoshop / Plug-In", "AAX (Avid Pro Tools)", "App Extension (in Slack)", or "Spotlight Importer" rather than just a path on disk.

What you'll see for each finding

Every component that's still Intel-only carries the same metadata as a regular app: name, parent host, location on disk, install size, and (where the community has confirmed a native version exists) a "Native version spotted" indicator. Components that the community has confirmed as Universal or Apple silicon native are reported back to the community database anonymously (if you've opted in to sharing) so the next person who scans gets a head start.

Only Intel components are uploaded as primary records to the database. Native and Universal components are reported via the same lightweight "I've seen this" signal used for native app sightings, so a Mac with a healthy plug-in folder produces a tiny upload payload regardless of how many components you have installed.

What to do if you find Intel components

The migration playbook differs by category.

• Audio plug-ins: check the vendor's site or installer (Waves Central, FabFilter Installer, iZotope Product Portal, Native Access, Universal Audio Connect, Steinberg Download Assistant, Slate Digital). Most major audio vendors completed Apple silicon ports by 2024; a vendor's install tool will offer the native build automatically. For abandoned plug-ins, look for a community-maintained replacement before macOS 28.
• Photo and video plug-ins: these are usually shipped as part of the host app's installer. Updating Photoshop or Premiere Pro to the current Creative Cloud release will replace most Intel plug-ins. For third-party effects (Red Giant, Boris FX, Magic Bullet, etc), check the vendor's standalone installer.
• 3D plug-ins: vendor-specific. Cinema 4D's Maxon One, Maya's Autodesk Access, and Houdini's launcher all surface plug-in updates separately from the host. SideFX in particular has a long tail of community plug-ins that may need manual review.
• Spotlight importers, QuickLook generators, preference panes: if the parent app is gone, delete the orphaned component. If the parent is still installed, update the parent app.
• LaunchAgents and LaunchDaemons: trace the Program value to the parent app, then update or remove that app. Be cautious deleting daemons in /Library/LaunchDaemons. They are system-wide and may be required by enterprise software.
• Embedded items inside an Apple silicon app: the parent app needs an update from the developer. Open the developer's release notes or contact their support; they may not realise their app ships an Intel sub-binary. This category is worth reporting upstream because the developer often has the easiest fix of anyone.

A note for IT administrators

Plug-in inventory matters most for fleets running creative-services workloads: broadcast, post-production, music production, photography studios, design agencies, and motion graphics. The same MDM-deployable build of Rosetta Check that you use for app inventory now also reports plug-in inventory in the CSV and JSON exports, with the same anonymous, on-device-by-default behaviour. See the MDM deployment guide for configuration profiles and collection scripts, and the broader fleet audit guide for the end-to-end workflow.

For mixed fleets, the Components scan is particularly useful at exposing the embedded category: enterprise apps that look Apple silicon-ready in the standard inventory but ship an Intel helper that will fail on macOS 28. These are exactly the cases where giving the vendor twelve months of notice produces a fix, and discovering them at upgrade time produces a support ticket.

Closing

Auditing apps gets you most of the way to a clean macOS 28 transition. Auditing plug-ins, system extensions, and embedded helpers gets you the rest of the way. Install or update Rosetta Check 2.0 from the App Store, run a Components scan, and you'll have a complete picture of every Intel binary on your Mac, not just the ones in /Applications.

For the wider context, see what happens to your Intel apps in macOS 28, how to prepare your Mac for macOS 27, and Apple's official guidance in the support article Using Intel-based apps on a Mac with Apple silicon.