Guide

Installing plugins

Third-party plugins, extension panels, scripts and audio plugins, from Collider or a terminal.

Neutron puts each plugin where its Windows installer would, inside the prefix your Adobe apps run from. Hand it the plugin files, an extension package, a UXP plugin, a script, or the vendor's own Windows installer. This needs Neutron 1.0.0-beta.29 and Collider 0.1.12 or newer.

In Collider

  1. Open Plugins in the sidebar, under Library. It works on the prefix selected on the Prefixes tab.
  2. Drop plugin files or folders onto the page, or use Choose files… or Choose a folder….
  3. Each item gets a line: green when it's installed, red with the reason when it isn't.
  4. Restart the Adobe app to load what you added.

Scripts (.jsx, .jsxbin): Collider asks which app the script is for.

A vendor's installer (.exe, .msi): close the Adobe apps first. The installer opens its own window; click through it as you would on Windows. Collider waits until the installer and anything it opens afterward (a readme, for example) have closed.

The page also lists what the prefix already holds, and has an Open folder button for each plugin folder, so you can add a plugin by hand.

From a terminal

neutron plugins install <file or folder>... neutron plugins install --app aftereffects MyPanel.jsx neutron plugins list neutron plugins folder

They work on the prefix selected in Collider; add --prefix <path> to pick another. neutron plugins folder prints the Linux path of each plugin folder.

Where each kind goes

All inside the prefix:

If a plugin is already there, the new one replaces it. After Effects loads plugins from the shared folder: Gyroflow, Boris FX Mocha and Satori appear in its Effect menu.

Tested in Photoshop with G'MIC-8bf, installed as its unzipped folder: it appears under Filter > GMIC and applies its filters to the image. Tested in Illustrator with anchorGrabber, a tool plugin: it appears at the bottom of the toolbar's All Tools list (the … button), under Add Ons, and works once dragged into the toolbar.

Audio plugins in Premiere Pro

Premiere Pro finds new audio plugins only on its very first launch. After you install one, with the vendor's installer or as a .vst3, load it:

  1. In Premiere Pro, choose Edit > Preferences > Audio, then Manage Audio Plug-ins….
  2. Click Scan for Plug-Ins. The plugin appears in the list with its status.
  3. Click OK. It's now under Effects > Audio Effects > VST3.

Tested with FabFilter's Windows installer: Pro-Q 4 installed, passed Premiere's scan, and processed audio on a clip with its own interface open. Tested with plugdata's .msi installer: its effect, plugdata-fx, passed the scan and appears under Effects > Audio Effects > VST3. Premiere lists audio effects only, so a VST3 instrument the same installer adds doesn't appear.

UXP plugins (.ccx)

Photoshop's newer plugins come as .ccx files. Neutron unpacks one into the folder Photoshop loads UXP plugins from, and replaces any other version of the same plugin. Restart Photoshop: the plugin is in the Plugins menu. This needs runtime 11.10-155 or newer.

Tested with an open-source plugin (Auto-Photoshop-StableDiffusion): it installed, appeared under Plugins, and its panel opened.

If the Creative Cloud app ever installed UXP plugins into the prefix, it left a plugin list behind, and Photoshop then loads only the plugins on that list. Neutron says so when it installs a .ccx into such a prefix.

Extension packages (.zxp)

Neutron checks a package's signature before it installs it. A damaged package is refused, and the extension that was already installed stays as it was.

A package that isn't signed at all is installed with a note: the Adobe apps list it under Window > Extensions but refuse to load it unless PlayerDebugMode is on, and its developer's instructions say how to turn that on. Tested in Premiere Pro with Adobe's own sample panel (PProPanel): it opened only after PlayerDebugMode was turned on.

Not supported yet

If a plugin won't activate, or keeps asking to be activated again, see Troubleshooting.