How to Share or Upload Your Own Plugin Skins on VSTskins

Updated

VSTskins is built around three verbs in its own description: discover, download, and share skins for audio plugins and DAWs. If you have made a skin and want it listed on the site, the practical path is to contact the site with your files and the details that every listing on VSTskins already displays — skin name, target plugin, supported platforms, and author credit. The site does not expose a public self-service upload form in the material available here, so treat submission as a manual, contact-based process rather than an instant publish button.

What a VSTskins listing actually contains

Looking at how existing entries are structured tells you exactly what information you need to prepare. Every item in the site's listing follows the same pattern:

Field Example from the site
Skin name "CamelCrusher - Neon Forge", "T-Force Alpha Plus - Alternative 2"
Date October 10, 2026
Author "by Fazıl Irak", "by Paulo", "by killihu", "by Lizzy Lazer"
Target plugin "for CamelCrusher", "for T-Force Alpha Plus", "for OsTIrus", "for SSL EV2", "for MV2", "for Discovery Pro"
Supported platforms "Mac Win32 Win64", "Linux Mac Win64", "Win32 Win64"

That table is effectively your submission checklist. If you send a skin without a platform tag or without naming the plugin it targets, it cannot be listed in the same format as everything else on the site.

Step-by-step: preparing a submission

  1. Name the skin. Follow the existing convention of PluginName - SkinName (for example, "CamelCrusher - Yellow" or "CamelCrusher - Analog Style Amber"). Distinct names matter because the site already hosts many skins for the same plugin — CamelCrusher alone has Neon Forge, Yellow, Analog Style Amber, Analog Style, Antique 2, Mechanical, Desert, Rapture, Yellow Jacket, Noisemaker, Noisemaker 2, and New Age.
  2. Identify the exact target plugin. Not just "a compressor" — the specific plugin, as shown by entries like "for SSL EV2", "for MV2", or "for Discovery Pro".
  3. List every platform you support. The site uses tags such as Mac, Win32, Win64, and Linux. A skin tagged "Mac Win32 Win64" is claiming compatibility across all three; only claim what you have actually tested.
  4. Decide your author credit. Contributors are credited by name in the listing ("by Fazıl Irak", "by Paulo"). Decide whether you want your real name, a handle, or a studio name shown.
  5. Package the skin files in the format the target plugin expects for its GUI/theme, and include any install notes the user will need.
  6. Contact the site to submit. Since no public upload form is documented in the available material, reach out through the site's contact channel and provide the name, plugin, platforms, author credit, and files together in one message.

What to expect after submitting

  • Credit is public and permanent-looking. Your name appears on the listing alongside the date, so check the spelling you want displayed before sending.
  • Listings are dated. Entries carry a specific date (e.g., "October 10, 2026"), which is how the site orders and presents new contributions.
  • You are not the only contributor for a given plugin. Popular free plugins like CamelCrusher and T-Force Alpha Plus accumulate many skins from different authors, so a clear, distinct name and a genuinely different look help yours stand out.
  • Platform accuracy is on you. A wrong platform tag means users download something that will not load, which is the fastest way to get a bad reception.

Common sticking points

  • Assuming there is an instant upload button. The evidence here shows a curated, credited listing model, not a user dashboard. Plan for a manual submission.
  • Forgetting the platform tag. "Mac Win32 Win64" is not decoration — it is the compatibility contract with the downloader.
  • Vague plugin naming. "For a synth" will not map to the site's "for [PluginName]" format.
  • No install instructions. Skins for different plugins install differently; a short readme prevents support questions.

The short version

To share a skin on VSTskins, prepare it the way the site already presents skins: a clear Plugin - SkinName title, the exact target plugin, an accurate platform list (Mac / Win32 / Win64 / Linux), and your preferred author credit — then submit it through the site's contact channel. Because the site's own description centers on sharing as a core function, contributions are clearly welcome; the constraint is format and accuracy, not permission.