Skip to content

Getting started

Install Plectrify, choose an audio device, scan your plugins and get a sound out of it. About five minutes, most of it waiting for the plugin scan.

1. Install

Grab the build for your machine from the download section.

  • Windows: run the installer. It bundles the WebView2 runtime and the Visual C++ redistributable, so there is nothing else to set up. It also offers Plectrify as a VST3 plug-in (checked by default), installed to C:\Program Files\Common Files\VST3 — the same rig, running on a track inside your DAW, sharing your rigs and patches with the standalone. From version 0.1.9, updates install from inside the app: when a newer version is out, the notice in the corner offers Install update, Plectrify downloads and verifies it, Windows asks once for permission, and the new version reopens by itself.
  • macOS (Apple Silicon, 13.3 or newer): run the installer. It installs the app to Applications and Plectrify as a plug-in — VST3 to /Library/Audio/Plug-Ins/VST3 and Audio Unit to /Library/Audio/Plug-Ins/Components, for Logic and GarageBand — the same rig, running on a track inside your DAW, sharing your rigs and patches with the standalone. The build is not notarized, so macOS refuses to open the installer at first: see Opening it on macOS, which is a two-minute detour you do once.
  • Linux (x86-64; Ubuntu 24.04, Debian 13 or newer; from version 0.1.1): install the .deb, for example with sudo apt install ./Plectrify-linux-x64.deb. It installs the app (launch it from your app menu, or run plectrify), and Plectrify as a VST3 plug-in in /usr/lib/vst3, where every Linux DAW looks. From version 0.1.7 the package also adds Plectrify’s update source, so later versions arrive through Software Updater (or sudo apt upgrade) like the rest of your system — there is no need to download them again. Opening a newer .deb from your browser does not work for upgrading: Ubuntu’s App Center shows any installed version as “Installed”. If you are on 0.1.6 or older, install the newest .deb once with sudo apt install ./Plectrify-linux-x64.deb and updates take care of themselves from then on.

Plectrify is a host, not a plugin collection: you bring the amp sims and effects, and it runs them. If you have none yet, the built-in Packages panel can install a starter set for you.

2. Choose an audio device

Open Audio Settings from the toolbar.

  1. Pick your device type first. On Windows choose ASIO if your interface offers it; it is the difference between a rig you can play and one you can only hear. On macOS, CoreAudio is already the native low-latency path and there is nothing to choose. On Linux, choose JACK: on a PipeWire desktop Plectrify finds PipeWire’s JACK by itself, and ALSA is the fallback that silences every other application while the app runs.
  2. Set your interface as the input and your speakers or headphones as the output.
  3. Enable the input channel your guitar is plugged into.

Channels are listed individually, and the first enabled input channel carries the guitar. It is fanned out to both sides of the rack, because a guitar is mono, so you do not need to enable a second channel to get sound in both ears.

If you are not sure what to pick, audio setup and latency goes through it properly.

3. Scan for plugins

Open Plugins and run a scan. Plectrify looks in the standard plugin folders for your OS and caches what it finds, so this is a one-off: you only need to run it again after installing something new. Plugins that live somewhere else — an installer that chose its own folder, a collection you keep on another drive — are found once you add that folder under Settings → Plugin folders; the folder is scanned as soon as it is added.

The scan runs in the background and survives a plugin that crashes on load: the offender is blacklisted and skipped next time, and you are told which one it was. Plectrify loads VST3 plugins (.vst3) and older plugins shipped as single .dll files (.vst bundles on macOS, .so on Linux). AU and CLAP plugins are not loaded.

Everything the scan finds is offered in the drawer, drum machines included. To leave one out, open Settings and drag it from the drawer onto Hidden plugins. That list is also how to bring it back; a rescan does not, and a rig or patch that uses a hidden plugin keeps working.

4. Add your first module

A module is one hosted plugin sitting in one slot of the rack. Add one from the picker and it appears in the chain; add more and they run left to right, exactly like pedals on a board.

GUITAR IN  →  [ overdrive ]  →  [ amp sim ]  →  [ reverb ]  →  OUT

A sensible first chain is an amp sim on its own. Open its own editor window from the module card, dial in a sound you like, and play.

No sound? Check the master meter in the status bar. If it is moving, the problem is downstream: output device or volume. If it is not, the problem is upstream: input channel or input gain. Troubleshooting has the rest.

5. Quieten the hum

Single coils hum and high-gain amps hiss. The GATE pill beside the IN meter switches on a noise gate that sits before the first module, where a pedal gate would go. Hover the pill for its settings: set the threshold just above where the IN meter settles when you are not playing. Shape is how it closes: soft and firm ease a dying note out, hard cuts like a classic gate. If it cuts off too abruptly, soften the shape, lengthen the release or shallow the range; if it clicks when a note starts, lengthen the attack. The pill is bright while the gate is open and dims while it is closed, so a silent rig is not a mystery.

6. Tune up

The tuner lives in the status bar and taps the input directly, so it works no matter what the rack is doing, so you do not have to bypass anything to use it.

7. Save it

Two different things are worth saving, and they are not the same thing:

  • A rig is the whole chain: every module, the order, the routing, each plugin’s complete state. Save it under a name and recall it later. See modules, chains and rigs.
  • A patch is one module’s knob layout plus that plugin’s tone, saved so you can drop it onto any module running the same plugin. See knobs and patches.

You do not have to remember to save the thing you are working on: the working rack autosaves and comes back at the next launch.