/ VST Home / Frequently Asked Questions

Licensing

Q: Do I need to update my existing VST 3-based products to the MIT license?

  • No. You may continue using your current license for existing products.

Q: Can I switch to the MIT license?

  • Yes. Simply use the VST SDK version that is licensed under the MIT License and follow its terms.

Q: Do I have to disclose my source code under the MIT license?

  • No. The MIT License does not require you to disclose your source code.
  • The only obligations are: You must include the original copyright notice and the MIT license text in all copies or substantial portions of the code.
  • In other words: you can license your project under MIT license without making the source code public. You only need to provide the license and copyright notice when you share or distribute the software.

Q: I would like to share the source code of my VST 3 plug-in/host on GitHub or a similar platform.

  • Yes. Since the VST SDK is under the MIT License, you are free to share your plug-in or host source code, including or referencing the VST SDK, on platforms like GitHub. You may also distribute your plug-in/host in binary form.

ⓘ Note: Following the Steinberg VST usage guidelines is considered best practice, but it is optional.

Q: I would like to distribute my VST 3 plug-in/host as freeware/shareware or sell it in binary form only.

  • Yes. The MIT License allows you to distribute or sell your plug-in/host in binary form as freeware, shareware, or a paid version.

ⓘ Note: Following the Steinberg VST usage guidelines is considered best practice, but it is optional.

Q: I would like to adapt the VST SDK's source code to my VST 3 plug-in/host's needs.

  • Yes. Under the MIT License, you may freely adapt and modify the VST SDK source code to meet your specific requirements.
  • If you believe your changes should be included in the SDK, please contact us (use the sdk.steinberg.net).

Q: Can I reuse a modified version of the VST SDK that was distributed by someone else?

  • Yes. The MIT License permits reuse of modified versions of the SDK.

Q: I would like to sell my VST 3 plug-in/host in binary form, based on a third-party SDK like JUCE.

  • Yes. You may distribute or sell your plug-in/host in binary form, even if it is based on a third-party SDK.

ⓘ Note: Following the Steinberg VST usage guidelines is considered best practice, but it is optional.

Q: I would like to distribute my VST 3 plug-in/host in binary form, based on a third-party SDK like JUCE that used the GPLv3 license.

  • Yes, MIT license is compatible with GPLv3.

ⓘ Note: Following the Steinberg VST usage guidelines is considered best practice, but it is optional.

Specific VST 2

Q: I would like to share the source code of my VST 2 plug-in/host on GitHub or other web-based exchange platform.

  • It is allowed but be sure that you do NOT include the Steinberg VST 2 files: like aeffect.h and aeffectx.h. These files are under a different license which does not allow redistribution!

Q: I am a developer/company and I want to develop and distribute a VST 2 plug-in and/or host in binary form.

  • If you have signed the VST 2 license agreement (before October 2018), you can.
  • If not, you are not allowed to distribute it!
  • See here!