What to check before you release music or share a plugin you made
Answer in brief
Using a made instrument in your own song is usually the simple case. Sharing or selling the plugin itself is where licenses matter, so read the maker’s terms and find out what license the generated code carries.
Using what you made in your own music
Most makers allow what they build in your own productions, commercial ones included. pluginmaker.ai says so in its FAQ, and Studio 56 allows songs, videos, live shows and commercial releases. Check the plan you are on, because some makers tie rights to a tier.
Open-source licenses inside generated code
When a maker writes code on top of an open-source framework, that framework’s license travels with your plugin. The README of Noizefield Audio Plugin Coder (APC) says APC itself is MIT licensed, but plugins built with it inherit the dual license of JUCE. Under JUCE’s free AGPLv3 option you must offer the plugin’s full source code to the people you give it to. To ship a closed-source plugin, JUCE’s licensing page says you need a JUCE license, which is free below a revenue limit and paid above it.
What the maker may do with your work
Terms also say what a maker may do with what you upload or publish. pluginmaker.ai says your samples stay private to your account and that it will not train AI models on them. A community library such as Amorph’s Hub gives its maker a license to host what you publish there, so read those terms before you share. If a term is unclear, write to the maker before you release rather than after.
Rights to the music itself
The US Copyright Office’s report on AI and copyrightability says AI output is protected only where a human decided enough of its expressive content, and it treats prompts alone as not enough. An instrument maker is a tool like any synth, and the notes you write, play and arrange on it are your contribution. This is general information rather than legal advice, so ask a music lawyer about a release with real money behind it.
A short checklist
- Find the line in the maker’s terms that covers commercial use on your plan.
- If you plan to share or sell the plugin, find out what license its code carries.
- Save a copy of the terms page as it read on the day you released.
- Feed in only samples you own or have permission to use, which pluginmaker.ai’s FAQ also asks of its users.
Questions and answers
Can I sell a plugin I made with an AI plugin maker?
It depends on the maker and the plan. Imagine Plugins and Romplur are made for selling, pluginmaker.ai allows it on its Pro plan, and code built on JUCE carries JUCE’s license terms. Studio 56 does not allow selling what you make with it.
Sources for this page
- Studio 56: Studio 56’s official website, the publisher of this reference.
- pluginmaker.ai: pluginmaker.ai’s official page, the source of its description here.
- Romplur: Romplur’s official page, the source of its description here.
- Imagine Plugins: Imagine Plugins’s official page, the source of its description here.
- Noizefield Audio Plugin Coder: Noizefield Audio Plugin Coder’s official page, the source of its description here.
- Amorph: Amorph’s official page, the source of its description here.
- JUCE licensing: JUCE’s own page on its license tiers and the AGPLv3 option.
- US Copyright Office: Copyright and Artificial Intelligence: The Office’s report, whose second part covers the copyrightability of AI output.
The practical advice here is our own. A maker's description of its product is not a test of how it performs.
Keep reading
Cite this page
Best AI Plugin Maker. “What to check before you release music or share a plugin you made.” Studio 56 Reference. Content reviewed November 8, 2026.
https://bestaipluginmaker.com/before-you-release/