How to Set Up and Use Plugin Types

Bought or downloaded a new plugin and not sure what to do with it? You're not alone — installers vary wildly between developers, and DAWs don't always find new plugins automatically. Here's a proper, no-nonsense walkthrough of getting any plugin installed, scanned and actually working, whatever plugin type it is.

Before You Install Anything

Two quick checks save a lot of head-scratching later, whichever of the plugin types you're setting up. First, confirm the plugin's format (VST3, AU or AAX) matches what your DAW supports. Second, note where your DAW expects plugins to live — most Windows DAWs default to a standard VST3 folder, while macOS keeps AU and VST3 plugins in set system locations. Knowing this in advance means you'll spot immediately if an install has gone to the wrong place.

How to Set Up a New Plugin in Five Steps

1. Run the installer (or copy the files). Most plugins come with a proper installer that handles this automatically; some simpler ones just need their files copied into the correct plugin folder by hand.
2. Authorise or activate the licence. Depending on the developer, this might mean entering a serial number, logging into an account inside the plugin, or using a dedicated licensing app.
3. Rescan your plugin folders in your DAW. Open your DAW's plugin manager and trigger a rescan. This is the step people forget most often — a plugin that's correctly installed still won't appear until your DAW knows to look for it.
4. Insert it and check it loads properly. Add an instance to a track, confirm the interface opens without errors, and check audio is actually passing through or being generated as expected.
5. Save it into a template or preset if you'll use it often. If this is a plugin you'll reach for regularly, add it to your default template or a favourites list so you're not hunting for it in a long menu every session.

That's genuinely the whole process for the vast majority of plugin types, instrument or effect alike.

When a Plugin Doesn't Show Up After Installing

This is the single most common hiccup, and it's almost always one of these:

• Wrong format for your DAW. An AAX-only plugin won't appear in a DAW that only supports VST3, for example.
• Installed to the wrong folder. Check the installer actually pointed at the plugin folder your DAW is scanning.
• Scan not triggered. Most DAWs need a manual "rescan plugins" action after a new install rather than picking it up automatically.
• Blocklisted after a crash. If a plugin has previously crashed your DAW during scanning, it may sit on a blocklist and need manually re-enabling.

Setting Up an Instrument Plugin

Instrument plugin types — synths, samplers, drum machines — need an instrument or MIDI track rather than an audio track. Once inserted, arm the track for recording, select a MIDI input source (a keyboard, or your computer keyboard as a substitute), and confirm you can hear sound when you play a note before you start recording anything properly.

Setting Up an Effect Plugin

Effect plugins need audio already present to process, so they're inserted directly on a track or a send/return bus rather than an instrument track. For effects you'll want on several tracks at once — reverb is the classic example — a send/return setup is generally more efficient than loading a separate instance on every single track.

A Sensible Signal Chain Order

Once several plugins are set up on one channel, order matters. A common, sensible default is EQ, then dynamics (compression or gating), then any saturation, then time-based effects like delay and reverb last. It's not a strict rule, and plenty of good engineers break it deliberately, but it's a solid default while you're still finding your feet with a new plugin.

If you're still deciding which plugin types are actually worth having in that chain, our full guide to plugin types explains what each category does, and our buyer's guide covers compatibility before you install something new.

Keeping Things Running Smoothly

Update plugins periodically, but not necessarily the moment every update appears — check release notes for anything that might affect an existing project first. Keep a note of which plugin types a project uses if you're likely to move it between machines, and don't be afraid to delete or disable ones you've genuinely stopped using; a leaner plugin list scans faster and crashes less.

It's also worth organising plugins into folders by category once your collection grows — separating instruments, dynamics, EQ and time-based effects makes finding the right plugin type in a long menu far quicker mid-session.

The Bottom Line

Installing, activating, scanning, inserting and (if you like it) saving to a template — that's the whole process, whatever the plugin does once it's running. Get comfortable with these steps once and every future plugin, whatever type it is, takes a few minutes rather than an afternoon of troubleshooting. If you're brand new to all this, our beginner's guide to plugin types is a friendlier starting point.

Frequently Asked Questions