Do I need my own website to sell a plugin?

You need a website; you do not need to sell from it. A site with documentation, demo material and a way to contact you is what a customer checks before buying anywhere, including on a marketplace. Selling directly adds payment processing, tax compliance, license delivery and support to your workload — worthwhile for some developers, a distraction for others.

What does it cost to list on MuseHub?

There is no hosting, bandwidth or licensing fee. MuseHub acts as Merchant of Record and takes its share from each sale after handling payments, taxes and currency conversion; you set the base price and receive monthly payouts. The current terms are on the Distribute on MuseHub page and in the partner documentation.

Should I launch on several channels at once?

Usually not. Each channel has its own assets, pricing rules and support load, and a launch is when bugs surface. Launch where infrastructure is handled for you, fix what the first customers find, then expand with a product that already has reviews.

How do I protect the plugin once it is out?

With a licensing system, not with hope. On MuseHub, Muse DRM adds licensing to an existing binary without code changes and the Muse SDK integrates with your own activation flow. Elsewhere, established licensing platforms do the same job for a fee. The licensing and protection guide on this site compares the options.

How to sell and distribute VST plugins

For developers

You have a finished plugin. The question now is how it reaches the people who will use it, and on what terms. There are four real routes — a marketplace built for audio developers, your own store, the big plugin retailers and bundles with other developers — and most successful developers end up using more than one.

This guide walks through each route with its trade-offs, what to have ready before you publish anywhere, and how to market a plugin without a marketing team.

Before you distribute anything

Distribution exposes every rough edge in a product, so the preparation is the same whichever channel you choose:

Test across hosts and operating systems. A plugin that passes in one DAW on one machine has not been tested. Check the formats you ship (VST3, AU, AAX) in the DAWs your customers actually use, on both current and previous OS versions.
Package it properly. Installers for Windows and macOS, code-signed and notarized where the platform requires it. An installer that triggers a security warning loses a sale before the plugin has made a sound.
Write the documentation. Installation steps, a short user guide, and answers to the questions your beta testers asked. Support requests are expensive; documentation is cheap.
Prepare the demo material. Screenshots at the sizes stores want, a short video of the plugin doing its one thing well, and audio demos with a dry/wet comparison. These assets are reused on every channel below.

A studio desk with monitors and a DAW session open — Distribution starts before the first upload: tested builds, signed installers and demo material that every channel can reuse.

The four distribution routes

1. MuseHub: a store built for audio developers

MuseHub is Muse Group’s marketplace for music software, the home of Audacity and MuseScore Studio and the exclusive store for MuseSounds. Developers list apps, plugins and sound libraries directly, and the platform takes care of the parts that usually need their own infrastructure:

Installation and updates. MuseHub installs common installer formats (macOS packages, Windows MSI, MSIX and EXE, and macOS apps directly) and installs VST3, AU and AAX plugins without an installer at all. Updates you publish are delivered and installed for your customers automatically, so you do not have to build or maintain an auto-update framework.
Payments as Merchant of Record. MuseHub handles payment processing, fees, sales taxes, currency conversion and the associated costs. You set base prices and the store calculates localized pricing for 50 territories; proceeds are paid out monthly.
Pricing models. One-time purchase, subscription or free — and free products can still earn through tipping, where customers send money to your account balance.
Licensing without code. Muse DRM protects an existing binary and enables trials and subscriptions with no integration work; the Muse SDK gives you license information over a secure channel inside your own code. Both are provided free. The licensing and protection guide compares them with the alternatives.
Delivery. Downloads go through MuseHub’s CDN with no hosting or bandwidth cost to you, whether a product is downloaded once or a million times a month.

The trade-off is the one every store carries: the store sets the customer relationship and the checkout, and your product sits next to others in its category. Details of the program are on the Distribute on MuseHub page.

2. Your own website and store

A website is not optional: it is where a customer checks who you are. Whether you also sell there is a separate decision.

What you gain: full control of branding, pricing and messaging; a direct relationship with each customer (and their email address); and the largest share of each sale, since you pay only your payment processor.

What you take on: driving your own traffic, which is the expensive part; running the site, the store platform and license delivery; handling sales tax and VAT across jurisdictions, which is now a legal obligation in many of them; and doing your own customer support.

3. Plugin marketplaces

Retailers such as Plugin Boutique and KVR Audio’s marketplace put your plugin in front of a large audience that is already shopping for plugins.

What you gain: reach and the credibility of an established storefront, plus whatever promotion the retailer runs.

What you take on: a commission on every sale, direct competition with hundreds of similar products in the same category, and less control over pricing and how your product is presented — sales calendars in particular tend to be set by the retailer.

4. Collaborations and bundles

Bundling with other developers or appearing in a partner’s promotion puts your plugin in front of a new audience at almost no acquisition cost.

What you gain: cross-promotion and visibility you could not buy on your own.

What you take on: revenue sharing, coordination across several parties and the risk that a heavily discounted bundle anchors the perceived value of your product.

Choosing a mix

Most developers do not pick one route. A common shape is:

Launch on MuseHub to get installation, licensing and payments handled from day one, so the first weeks go into support and fixes rather than infrastructure.
Run your own site as the home of your brand, documentation and mailing list, whether or not it also sells.
Add marketplaces once the product has reviews and a steady release cadence, so it lands with social proof rather than as an unknown.
Bundle and collaborate when you have a partner whose audience overlaps yours and a promotion that makes sense for both.

Weigh each channel against your budget, the time you can spend on marketing and support, and the audience you are trying to reach. A tool for professional mix engineers and a $20 creative effect for bedroom producers want different mixes.

Marketing a plugin without a marketing team

Marketing a plugin is mostly showing what it does to sound, repeatedly, in the places producers already are. The methods below need time rather than budget:

Lead with the problem. Producers do not search for features; they search for the thing that is wrong with their mix. Demo videos, product copy and tutorials land better when they start from that problem and end with the result.
Short video where producers scroll. Fifteen to sixty seconds of the plugin working on real material, with the sound audible and the interface visible, on the platforms where your audience spends time. Longer walkthroughs belong on YouTube, where they keep working for years.
A real trial. A time-limited, fully functional trial converts better than a crippled one, because the producer can finish a track with it. Pair the trial with a short set of tutorials, and make watermark-free export part of it if you can.
Communities, as a participant. Forums, subreddits and Discord servers for specific DAWs and genres are where niche plugins are discovered. The rule is to help with the technical questions first; the plugin comes up naturally when it is the answer.
Creators who already use the sound. A collaboration with a producer or engineer whose work fits your plugin — presets, a walkthrough, an honest review — carries more weight than an ad. Affiliate terms make it sustainable for both sides.
Measure something. Trial downloads, trial-to-paid conversion and where sales came from (UTM links, store analytics) tell you which of the above deserves more of your time. Start with those three numbers before adding more.

FAQ

Next steps

If you are still building, how to make VST plugins covers formats, SDKs and frameworks, and licensing and protection covers what happens after release. To see what listing looks like from the customer’s side, browse the plugins on MuseHub.

Ready to publish? Start with Distribute on MuseHub.