How to move UAD plugins to a new computer.
Universal Audio migration has two related but distinct paths: native UAD software managed through UA Connect and iLok, and UAD-2 DSP software tied to registered Apollo or Satellite hardware. Identify which path each plugin uses before rebuilding.
Fix the whole setup—not just one plugin file.
A dependable result accounts for software, formats, versions, licenses, presets, supporting files, and the sessions that depend on them.
Separate Native from DSP
UAD Native plugins run on the computer, while UAD-2 plugins use registered UA DSP hardware.
Use UA Connect
UA Connect manages software installation, updates, redemption, and other UA product functions.
Check iLok locations
Native UAD licenses may be activated to supported computer, iLok USB, or cloud locations depending on the license type.
Identify which UAD plugins you use
Before installing anything, separate your inventory into UAD Native products and UAD-2 DSP products. Some titles exist in both forms, but the software, authorization, and processing requirements are not identical.
- Scan the old computer with FX Recall.
- Open UA Connect and your UA account to review owned products.
- Open iLok License Manager and note where native licenses are activated.
- Record every registered Apollo, Satellite, or UAD-2 device and the UA system/account that contains it.
Move UAD Native plugins with UA Connect
Install UA Connect
Download the current UA Connect application, install it, and sign in with the Universal Audio account that owns the plugins.
Link the correct iLok account
Make sure UA Connect is associated with the iLok account that holds or will receive your native UAD licenses.
Redeem available products
If a product shows a Redeem button, complete that step so its license is deposited to the linked iLok account.
Install the plugins
Use UA Connect to download and install the native titles required by your sessions.
Activate the license location
Use UA Connect or iLok License Manager to activate to an eligible computer, iLok USB, or cloud location, depending on the license type.
For broader iLok migration instructions, see how to transfer iLok licenses to a new computer.
Move UAD-2 DSP plugins and Apollo software
For Apollo, Satellite, and other UAD-2 systems, install the current compatible UA software and connect the registered hardware. UAD-2 plugin authorizations are associated with the UA account and system containing that hardware.
- Confirm the hardware is registered to the correct UA account and system.
- Install the supported Apollo, Console, driver, and UAD-2 software through UA’s current process.
- Connect and power the hardware before testing DSP plugins.
- Authorize the system after installation when prompted.
- Do not transfer hardware ownership unless you are actually selling or giving away the device.
Preserve UAD presets, Console settings, and sessions
Reinstalling the plugin does not guarantee that every custom preset, Console configuration, LUNA template, or session-specific asset is preserved.
- Export important plugin presets and Console sessions.
- Back up DAW presets and channel-strip templates.
- Document Apollo routing, cue mixes, I/O labels, and sample-rate settings.
- Open test sessions that use both native and DSP versions so you can verify the exact instance type.
Use the plugin reinstall checklist to track validation across the rest of your vendors.
UAD plugins missing after migration
UA Connect shows the plugin but it will not install
Update UA Connect, verify the account, confirm disk permissions and free space, and follow UA’s official reinstall procedure when the application itself is damaged.
The native plugin asks for activation
Open iLok License Manager and verify the license is activated to an eligible location. Subscription and perpetual licenses may support different locations.
The DSP plugin is disabled
Confirm the Apollo or UAD-2 device is connected, powered, recognized, registered to the correct system, and running compatible software.
An old session cannot find the plugin
Check whether the session used a native UADx instance or a DSP UAD instance. Installing only one form may not satisfy the other reference.
Official resources
Related FX Recall guides
Frequently asked questions
What is the difference between UAD Native and UAD-2 plugins?
UAD Native plugins run on the computer and use iLok licensing. UAD-2 plugins are processed by compatible Universal Audio DSP hardware.
Do I need my Apollo connected to use UAD Native plugins?
Generally no. Native UAD products run without Apollo DSP, but they still require the appropriate software and license activation.
Can I activate UAD Native licenses directly to a computer?
Eligible perpetual native licenses can support local computer activation, while UAD Spark subscription licensing has different location requirements. Check the current UA instructions.
Does FX Recall know whether a UAD plugin is native or DSP?
It inventories installed plugin files and metadata. You should still verify instance type, licenses, and hardware requirements inside UA Connect, iLok, and your sessions.
Do not rebuild your plugin library from memory.
Scan your old computer with FX Recall, save a cloud-synced inventory, and track what still needs to be installed on the new machine.