In order to install this product you will need to download its corresponding setup file to the computer you are planning to use this product on (Internet connection is not required for the product to function).
For VST, VST3, AAX plug-ins on Windows platform:
You should execute the downloaded setup file, select plug-in types you would like to install, and for VST plug-ins specify the VstPlugins folder location, the one which is connected with the audio application you are using and where this application expects VST plug-ins to reside (the "Voxengo" sub-folder will be also created there). VST3 plug-ins are always installed into the standard "Common Files/VST3" folder. AAX plug-ins are always installed into the standard "Common Files/Avid/Audio/Plug-Ins" folder.
(the installed Voxengo plug-in DLL files can be moved around freely)
For AudioUnit, VST, VST3 plug-ins on macOS platform:
You should open the DMG disk image and drag & drop the "component" (or "vst", "vst3") package from it into the corresponding plug-in folder located in the "/Library/Audio/Plug-Ins/" folder on the harddisk (the "component" package should go to the "/Library/Audio/Plug-Ins/Components/" folder while the "vst", "vst3" package should go to the "/Library/Audio/Plug-Ins/VST/" (VST3/) folder). Note that direct links to these folders are present in the DMG archive. The "component" package is distributed separately from the "vst" and "vst3" packages.
Note that you need to install AudioUnit plug-in for use in Logic Pro, GarageBand and other AudioUnit-compatible audio applications.
For AAX plug-ins on macOS platform:
AAX plug-in can be installed in a similar manner: the "aaxplugin" file resides in the "ProTools AAX" folder. This file should be manually copied into the "Plug-Ins" folder on the harddisk for which a direct link is available.
After this has been done you will need to order your audio application to rescan plug-ins, or if that option is unavailable you will need to re-start this application. Note that plug-ins cannot work without an audio application that hosts/loads them.
If you cannot get plugin component to work on macOS, you have to logout from the system and login again, it's a known issue not caused by plugin's own bug.