iZotope RX Plugins Not Showing in Your DAW: Fixes

If an iZotope RX plug-in is missing from your DAW, do not reinstall the whole suite yet. First prove that the RX tool has a plug-in version, then match its format to the host, confirm the file is in the default system location, and read the host’s scan or validation result. They tell you whether to repair an installation, change a host setting, or use a different RX workflow.

There are three different “missing plug-in” problems. An RX Audio Editor module may never have been built as a DAW plug-in. A real RX plug-in may be installed but not scanned or may have failed validation. Or a third-party plug-in may be missing inside RX itself. The steps below solve the first two. The third is a plug-in-hosting problem and follows a different compatibility path.

First identify what is actually missing

Write down the exact name you expected, the RX edition, operating system, DAW version and menu where you looked. “RX is missing” is not enough. “RX 12 De-click VST3 is absent from the Plug-ins section of Ableton Live’s Browser after installation” can be tested.

Then answer four questions:

1. Does the current RX 12 plug-in comparison list that tool?
2. Does your edition include it?
3. Which format does the DAW load on this operating system?
4. Is the plug-in file absent, unscanned, rejected, or visible but unauthorized?

Each answer points to a different fix. If the tool is editor-only, stop here: another scan will not make it appear.

Not every RX module is a DAW plug-in

RX Standard and Advanced include the standalone Audio Editor, whose module list is larger than the plug-in list. Elements has six DAW plug-ins and no standalone editor. The official RX 12 module and plug-in matrices show those lists separately.

Phase, for example, appears in the Audio Editor module table but not in the RX plug-in table. No VST3 rescan can create a Phase plug-in that RX 12 does not ship. Connect, by contrast, is a Standard/Advanced plug-in. Ambience Match, De-rustle and Scene Rebalance have format restrictions in the matrix, specifically AAX AudioSuite-only availability for those three Advanced tools, so a Pro Tools user may need to look under AudioSuite rather than among normal real-time inserts.

If the expected tool is editor-only, use the standalone editor, RX Connect where supported, or an external-editor round trip. Our RX Editor vs plug-ins vs Connect guide explains which route preserves the workflow you need.

Match AU, VST3 or AAX to the host

RX 12 lists AU on Mac, VST3, AAX, AAX AudioSuite, AU ARA on Mac and VST3 ARA. All listed plug-in formats are 64-bit only. That does not mean every host supports every format.

The current RX Standard release notes list VST3, not VST2. If an old tutorial tells you to add a custom VST2 directory, it is not the right default path for RX 12.

Check edition and ARA restrictions

A correct format can still be unavailable in your edition or host. Compare the edition you own with the RX matrix before touching folders. A Standard license does not include Advanced-only tools. A component that happens to be installed is not proof that your license authorizes it.

Use the current RX Standard product page only as a product-level check, then return to the manual’s detailed matrix for the exact module and plug-in row. Marketing feature lists often group editor functions and plug-ins together; the matrix is the better answer to “should this exact name appear in my insert menu?”

ARA needs an extra compatibility check. The RX 12 manual lists Spectral Editor AU ARA for Logic Pro 10.7 or later; on Apple silicon, that ARA workflow requires Logic to run through Rosetta. Intel Macs do not need Rosetta. It lists VST3 ARA for the named Studio One 7 and Studio Pro 8 hosts. Treat those as explicit conditions, not a blanket promise that “RX supports ARA everywhere.” Current RX plug-ins support native Apple silicon in the applicable formats; iZotope identifies RX AU ARA in Logic as a Rosetta exception. Do not switch every host to Rosetta just because an ordinary RX AU or VST3 is missing.

Confirm installation before scanning

Close the DAW before installing or repairing RX so the host is not holding an old component in memory. Use the current installer route associated with the product entitlement, and make sure the expected plug-in formats are selected. iZotope’s product-not-found support article points users back to the DAW for plug-in discovery and warns that host compatibility varies.

Do not drag modern RX plug-in files into a convenient custom folder. iZotope’s current custom-location guidance says VST3 and AAX should remain in their default locations on Windows, and VST3, AAX and AU should remain in their default locations on Mac. Its custom VST2 advice is for older software, not the normal RX 12 setup.

Check the format’s actual component folder, not the folder containing the RX Audio Editor application. The default locations below are documented by Ableton for macOS, Ableton for Windows VST3 and Avid for AAX.

• Mac AU: /Library/Audio/Plug-Ins/Components/
• Mac VST3: /Library/Audio/Plug-Ins/VST3/
• Windows VST3: C:\Program Files\Common Files\VST3
• Mac AAX: /Library/Application Support/Avid/Audio/Plug-Ins/
• Windows AAX: C:\Program Files\Common Files\Avid\Audio\Plug-Ins

Look for the expected RX component in the relevant location. File presence confirms that something was installed; it does not prove that the build is compatible or undamaged. Reinstalling can repair an incomplete or damaged installation, but first keep the scan error so you can tell whether anything changed.

Logic Pro: check hidden items and AU validation

After a new AU installation, save your work and restart the Mac if Logic has not discovered the component. Open Logic Pro > Settings > Plug-in Manager (Preferences in older versions), then select iZotope in the manufacturer list. Apple’s Plug-in Manager guide distinguishes two easily missed states:

• Hide: the plug-in is absent from the Insert menu, but remains scanned and can load in existing projects.
• Ignore: the plug-in is excluded from the Insert menu and scanning.

If these columns are available in your version, use Show All to reveal hidden or ignored entries, then clear the relevant checkbox for the RX component you want. Look for RX audio effects in an Audio FX slot, not the instrument slot.

Read the Compatibility or validation result. Select a failed RX entry and choose Reset & Rescan Selection. If it still fails, check the RX update and host/OS compatibility before repeating the scan. Apple’s missing Audio Units troubleshooting provides a broader Full Audio Unit Reset when a targeted rescan is insufficient. After that full reset, quit and reopen Logic to start the new scan. It rescans other Audio Units too, so it is a later step, not the first response to one missing RX effect.

Ableton Live: enable the right source, then rescan

Open Live’s Settings/Preferences > Plug-ins. For an RX VST3 installed in the default location, turn Use VST3 Plug-In System Folders on. You do not need to select that same system directory as a custom folder. On Mac, if you installed and want the AU build instead, enable the Audio Units source.

Let the scan finish, then look in the Browser’s Plug-ins section. Clear a leftover search term or filter that could hide the effect. Search for the module name as well as RX; do not expect a suite-wide “RX editor” device.

If the component is still absent, use the rescan control. Ableton documents a deep rescan with Alt on Windows or Option on Mac held while clicking Rescan. A launch by itself is not a substitute for this explicit check. If scanning rejects the component, record the result and verify the installed build rather than moving files between VST2 and VST3 folders.

Pro Tools: check AAX and the AudioSuite menu

Quit Pro Tools before repairing the AAX installation, then relaunch it and check both the track insert menus and AudioSuite. RX Connect is an AudioSuite workflow; iZotope’s Pro Tools Connect instructions place it under Noise Reduction or the iZotope manufacturer grouping. An AudioSuite-only tool will not become a real-time insert after a rescan.

If the component is missing from the normal AAX folder, check whether it is in the adjacent Plug-Ins (Unused) folder described by Avid. Establish why it was moved there before restoring it: do not bulk-enable components that were deliberately set aside after crashes. If the correct file is present but still not loading, retain the startup or scan error and follow Avid’s troubleshooting for your Pro Tools version.

Premiere and Audition: use the audio plug-in manager

In Premiere, open the Audio preferences and select Manage Audio Plug-ins. Adobe’s Audio preferences reference identifies this as the entry to the Audio Plug-in Manager for VST3 and, on Mac, AU effects. Inspect the RX entry and use that manager’s scan and enable controls, rather than looking for an AAX component.

In Audition, save and close a multitrack session if it is using effects, then choose Effects > Audio Plug-in Manager. Click Scan For Plug-ins; after a plug-in update, select Rescan Existing Plug-ins. Check the RX effect’s Enable box. If it is marked Not Working, use Reload to rescan it. Adobe’s Audition plug-in instructions also warn that the custom VST folders section is for legacy VST effects: do not add a VST3 directory there. Click OK to confirm the plug-ins you want to use.

Work on one host at a time. If the same RX VST3 build loads in another compatible DAW, that is useful evidence to focus the investigation on the first host’s settings or compatibility. It does not guarantee that every host will load it.

Read the result: absent, rejected or unauthorized

Absent means the host never reports the component. Recheck edition, selected format and default location. Rejected means the host found it but validation failed or it was blocked; record the exact error, DAW build, OS build and RX version before changing anything. Unauthorized means the host or plug-in reports an authorization problem. Follow the vendor’s licensing instructions for that exact message; another folder scan is not a substitute for resolving it.

Do not use authorization as a universal explanation for an empty plug-in list. A host cannot validate a file that was never installed, and licensing the product does not manufacture an editor-only plug-in. Diagnose the stage that actually failed.

Do not confuse missing RX plug-ins with plug-ins missing inside RX

If your problem is “Ozone does not appear inside RX,” RX itself is the plug-in host. The RX 12 plug-in-hosting manual confirms VST3 support on Windows and Mac, including native Apple silicon. Windows also supports VST2; Intel Macs and RX running through Rosetta support AU, VST3 and VST2. Native Apple silicon RX supports AU and VST3, not VST2.

In RX’s Preferences > Plug-ins tab, choose the format and use its Scan VST2/VST3/AU Plug-ins control. The RX preferences reference explains that failed entries can carry tags such as [Crashed] or [Failed]. Update the third-party plug-in as necessary; RX’s Rescan option can clear the blacklist and retry after an update fixes an incompatibility. Custom folders in this tab apply to VST2.

An older search result titled “I Cannot Find Some Plug-Ins in RX 10” describes an earlier VST3-hosting limitation. Even RX 10 gained VST3 hosting in version 10.4.0, according to its release notes. Do not use that old answer to diagnose RX 12, and do not confuse hosting another company’s effect inside RX with finding RX De-click in Logic.

When reinstalling RX is the right next step

Reinstall if the correct component is absent, if you have evidence of an incomplete or damaged installation, or if vendor troubleshooting recommends it after the compatibility and scan checks. iZotope provides a Product Portal reinstall procedure. Save your work and close the hosts first, keep current formats in their default locations, then run the affected host’s documented scan. Reinstalling cannot turn an editor-only module into a DAW plug-in or add an edition entitlement.

If validation still fails, capture the plug-in name, format, RX version, OS, processor architecture, DAW version and exact validation message. That is the useful support ticket. “I reinstalled three times” is not diagnostic evidence.

A fast decision tree

1. Not in official plug-in matrix? Use the Audio Editor or another supported round trip.
2. Wrong edition? Use an included tool or change the entitlement; scanning will not add it.
3. Wrong format/menu? Switch to AU, VST3, AAX or AudioSuite as the host requires.
4. File not installed? Repair the correct component with the current installer.
5. File present but hidden or ignored? Restore its visibility or scanning state in the host’s manager.
6. File present but scan failed? Run the host’s documented reset/rescan and record the validation error.
7. Plug-in opens but requests activation? Fix authorization separately.

For wider troubleshooting, return to the RX Problems hub. The RX 12 review provides the edition boundary, and the beginner hub covers editor basics once the correct tool is visible.

Frequently asked questions

Why can I see an RX module in the editor but not in my DAW?

Some RX tools are Audio Editor modules without a DAW plug-in version. Check the current RX 12 module and plug-in matrices before troubleshooting installation.

Where are the RX 12 VST2 plug-ins?

The current RX 12 documentation lists VST3, not VST2. Use VST3 in a compatible 64-bit host and leave it in the standard VST3 location.

Which RX format does Logic Pro use?

Logic Pro loads Audio Units. Check the AU component and its Plug-in Manager validation result. The separate Spectral Editor AU ARA workflow has additional version and Rosetta conditions.

Which RX format does Pro Tools use?

Pro Tools uses AAX. Also check AudioSuite, because some RX tools are available there rather than as ordinary real-time inserts.

Should I move RX VST3 files to my DAW’s custom plug-in folder?

No. iZotope says current VST3, AAX and AU formats should remain in their default system locations. Custom-folder advice usually concerns older VST2 products.

Do I need to reinstall RX first?

No. Check the plug-in matrix, edition, format, location and host scan result first. Reinstalling can repair missing or damaged components, or be a vendor-directed next step, but it cannot fix an unsupported format or an editor-only tool.

Why is an RX plug-in visible but not working?

If the host found it, the problem is no longer simple discovery. Read the validation or authorization message and troubleshoot that specific stage with the exact DAW, OS, architecture and RX version.

Why are third-party VST3 plug-ins missing inside RX?

RX 12 can host VST3 on Windows and Mac, including native Apple silicon. Check the third-party build and the selected format’s scan results in RX Preferences. Legacy RX 10 guidance about missing VST3 hosting does not describe RX 12.