VST3 folder locations

[ericzang]

There could be an inconvenience to manually moving a vst3 to your own custom folder after it has been installed in the default folder (installer giving no custom option, which is quite common I've seen). When installing an update that is intended to overwrite the previous, it won't find your custom folder. Then there will be two versions of the same name existing. DAWs may have their own ways to respond to this.

[legendCNCD]

If installer throws them to common files, I'll manually copy them to vstplugins dir which is elsewhere.

[chk071]

A Symbolic Link would fix this. Check out:

<span class="skimlinks-unlinked">https://www.howtogeek.com/howto/16226/c ... inux</span>/

Yeah, didn't think of that. I did that as well to link to the WavesShell thingie.

[Mushy Mushy]

A Symbolic Link would fix this. Check out:

<span class="skimlinks-unlinked">https://www.howtogeek.com/howto/16226/c ... inux</span>/

Yeah, didn't think of that. I did that as well to link to the WavesShell thingie.

I've tried moving the WavesShells but there are hundreds of them (almost literally TBH). The same ones are saved in about 4 places and I have 5 of each. Ok so thats only 20

Though it didn't work the last time I tried so will need to give it another shot. The Waves ones will save me the most room so they're my first priority.

[cleverr1]

A Symbolic Link would fix this. Check out:

<span class="skimlinks-unlinked">https://www.howtogeek.com/howto/16226/c ... inux</span>/

Yeah, didn't think of that. I did that as well to link to the WavesShell thingie.

I've tried moving the WavesShells but there are hundreds of them (almost literally TBH). The same ones are saved in about 4 places and I have 5 of each. Ok so thats only 20

Though it didn't work the last time I tried so will need to give it another shot. The Waves ones will save me the most room so they're my first priority.

You're most welcome!

I've got a tip to add to this - it's a good idea to keep a list of all the links you create so you can always find where you've put stuff. I ended up with 9 of these on my last PC as simple way to move stuff without having to figure out how to reconfigure software.

e.g. mklink /j "C:\ProgramData\Arturia" "E:\ProgramData\Arturia"

That one would currently be worth 17.4GB here.

[george]

As I understand it, on Windows systems, all VST3 plug-ins have to be installed in (a sub-folder in) Prog Files\Common Files\VST3 or Prog Files(x86)\Common Files\VST3.

Is that correct?

Isn't that contrary to the Windows protection scheme and run into file access / UAC problems on Windows 7 (and Vista)?

Check https://steinbergmedia.github.io/vst3_d ... t3loc.html

[cleverr1]

As I understand it, on Windows systems, all VST3 plug-ins have to be installed in (a sub-folder in) Prog Files\Common Files\VST3 or Prog Files(x86)\Common Files\VST3.

Is that correct?

Isn't that contrary to the Windows protection scheme and run into file access / UAC problems on Windows 7 (and Vista)?

Check https://steinbergmedia.github.io/vst3_d ... t3loc.html

ok, great, but in the context of clearing down a C: drive what's your point?

[Mushy Mushy]

You're most welcome!

I've got a tip to add to this - it's a good idea to keep a list of all the links you create so you can always find where you've put stuff. I ended up with 9 of these on my last PC as simple way to move stuff without having to figure out how to reconfigure software.

e.g. mklink /j "C:\ProgramData\Arturia" "E:\ProgramData\Arturia"

That one would currently be worth 17.4GB here.

That would be quite the win indeed. Looking forward to finding a moment to test it.

[pekbro]

Just FYI some plugin installers will not fall for the symbolic link under windows and will overwrite it. It's a good idea to keep the command in a text file somewhere, as you will inevitably have to redo the link every so often.

[steve.bradford1]

Hello i notice melda was mentioned and im having a hell of a time getting these plugins to work proper in reaper. At one point I got them to work and then one day every time I load one (doesnt seem to matter what ) crash. Its become extremely annoying. I love these plugins and use multiple in a given project. Any advice ?

[SampleScience]

Is it possible to install VST3 in another path other than the Common Files\VST3\? I gave it a try with the latest version of FL Studio and when I install a VST3 on an external hard drive, FL Studio doesn't see it.

[PTV]

Is it possible to install VST3 in another path other than the Common Files\VST3\? I gave it a try with the latest version of FL Studio and when I install a VST3 on an external hard drive, FL Studio doesn't see it.

I place all my VST3 files in C:\VST3 Plugins and they are all working fine in all my hosts (Live, Bespoke, VCV Host, VSTHost)

[newjunkcity]

As part of the official Steinberg VST3 standard, the installation folder/plug-in location is fixed. This is why installers don't provide an option to change the installation location for VST3s.

For the VST2 standard, the plug-in location was never fixed in the VST2 specification, but certain folders became "the unofficial accepted norm" (e.g. "C:\Program Files\Steinberg\VSTPlugins"). The lack of a folder in the VST2 standard specification is the reason why plug-in installers ask you where you want to install VST2s, and often suggest a location.

This is all described on Steinberg's website here.

---

Is it possible to install VST3 in another path other than the Common Files\VST3\? I gave it a try with the latest version of FL Studio and when I install a VST3 on an external hard drive, FL Studio doesn't see it.

I place all my VST3 files in C:\VST3 Plugins and they are all working fine in all my hosts (Live, Bespoke, VCV Host, VSTHost)

While it's possible to move VST3 plug-ins to a different folder after installation, you shouldn't do it (say for example if you depend on your music production workstation for your job/business, and you want to be 100% sure that things will work), as you're going against the VST3 standard specification. This is also the reason that many DAWs don't allow you to specify a custom VST3 path.

If you need to gain space on your boot partition (C:), the correct solution would be to use either junction points, or symbolic links as suggested by @cleverr1:

A Symbolic Link would fix this. Check out:

https://www.howtogeek.com/howto/16226/c ... -or-linux/

---

For VST3 plug-ins on Windows
For:

• 64-bit plug-ins on 64-bit Windows
• 32-bit plug-ins on 32-bit Windows

...the installation folder is here:

Code: Select all

C:\Program Files\Common Files\VST3

For:

• 32-bit VST3 plug-ins on 64-bit Windows

...the installation folder is here:

Code: Select all

C:\Program Files (x86)\Common Files\VST3

[PTV]

While it's possible to move VST3 plug-ins to a different folder after installation, you shouldn't do it (say for example if you depend on your music production workstation for your job/business, and you want to be 100% sure that things will work), as you're going against the VST3 standard specification. This is also the reason that many DAWs don't allow you to specify a custom VST3 path.

Luckily (for me) all the DAWs I own don't have that limitation/feature so for me it's working, I always move my plugins (VST2 and VST3) to custom locations after installation/update. I also prefer plugins that are fully portable and doesn't need installation.

[SampleScience]

As part of the official Steinberg VST3 standard, the installation folder/plug-in location is fixed. This is why installers don't provide an option to change the installation location for VST3s.[...]

Thank you for your post, that explains a lot! I don't understand why Steinberg would create a new format with limitations the previous format didn't have.