A guide to understanding policies for posting Paid Resources on the Hub
1. Free Content versus Paid Content
Free content is content that is hosted on the Hub website, and in most cases, downloadable in-game either through VaM 1.x, or through additional applications.
Free content can also be downloaded directly from the Hub website and copied to the game's designated folder for downloadable content.
Paid content is content that requires a subscription through a paywalled service, such as Patreon.
2. Content formats
Most downloadable content on the Hub comes in the form of .VAR files for use in VaM 1.x.
Specific categories of alternative types of content are explained in our Categories Guide. File formats for VaM2 will be announced at a later date.
For the purposes of this guide, we will mostly be referring to .VAR packaged content.
3. Specific license considerations
Paid resources can carry any license, but the most common is our proprietary license "PC" (or PC EA for content that is Paid but will be released for free at a later date).
"PC" is a restrictive license that essentially carries the function of CC BY-NC-ND with the added stipulation that it cannot be redistributed or used as a dependency.
The following licenses are prohibited as dependencies in Paid content:
- CC BY-NC (including any NC or non-commercial derivative license)
- Questionable
- MISSING
The only exceptions to using non-commercial dependencies would be with written permission from the original author to use their non-commercial content in your Paid resource.
When asking this permission, you must make it clear you plan to sell the content, where you will sell the content, and what license your content will have.
You must indicate in the resource form that you have permission by clicking the checkbox after the resource scan, and a notification will be sent to the creator to confirm.
Falsely claiming that you have permission to use a dependency can result in restrictions being placed on your account, up to and including a permanent ban.
For a full explanation of licenses, see this post.
4. All Paid resources must upload a VAR attachment for scanning
The Hub does not host your Paid content files, and they are deleted immediately after being scanned.
What we do collect is a list of included files, as well as the contents of the meta.json file.
Failure to attach a valid VAR file for scanning will result in the resource being rejected.
If the content is not VAR format, such as a script or other non-var asset in the appropriate category, we may ask to see a copy of the source file for the purposes of moderation or security screening.
5. What you can include in the VAR
You can include:
- Documentation
- Screenshots
- Scene Save Files
- Presets
- Audio files
- Anything in the custom folder that you created yourself
What you cannot include:
- Raw 3d modeling files
- Raw, uncompressed images
- Any .var files hidden inside your var, or anything in the addonpackages folder
- Any archive files (zip, rar, 7z, etc)
- Any dependencies (actual files)*
- Any content that you did not create yourself*
We are aware that the practice in the past has been to include dependencies in the custom folder as long as they are CC BY, often with the excuse "But what if it gets deleted from the Hub".
This is no longer allowed due to stricter enforcement of existing Hub policies on duplicate content: We do not allow duplicate content to be posted on the Hub.
For example:
If you find a look that is CC BY, you cannot download it, rename it, and then upload it yourself.
If you want to customize a look by another creator, then load that look as a dependency, make your modifications, and upload your version with the original as a dependency.
In cases where content has been re-shared with edits, the moderation team will decide if it satisfies the minimum amount of creativity and quality to be considered "not a duplicate".
Likewise, you cannot take someone else's content and then package it directly in your var without permission from the author and without a valid reason to provide to the moderation team.
This creates a mess of duplicate files in everyone's folders and causes folder bloat. It also, in many cases, causes license violations (intentional or otherwise).
Even though CC rules allow sharing and distribution for most licenses, this does not provide you a pass to circumvent the policies of websites and companies.
Similar to how you cannot share CC BY content if it violates our content standards (for example, no violence or gore), you also cannot share or repackage CC content if it creates a duplicate of content already available.
In the case of content that is "NOT ON HUB", if the content has a valid shareable license we recommend you provide this content to your subscribers elsewhere while including the package as a proper dependency (referenced in the meta.json, not directly included in your VAR's files).
Please keep in mind that we STRONGLY discourage creators from using these dependencies that are "NOT ON HUB".
Content "NOT ON HUB" is often not there for a good reason, and if that content is gone because it is pirated, stolen, or violates our content rules, then you will accept full responsibility for sharing that file.
Sometimes "NOT ON HUB" is an indication that the content is actually Paid content that is currently posted on the Hub and has been pirated (or you purchased it and forgot where it came from).
Content that is on the Hub in the Free category but not currently hosted (no file is available) should be reported to the moderation team so that we may contact that creator and have them upload the actual file.
If you are concerned that a resource for your subscribers may not be available some time in the future and that resource is CC BY, consider providing your own link to download that resource separately on your subscriber page or your Discord server.
You will be required to include it in the list of dependencies and to build your scene without packaging that content directly in your custom folder.
The reasons for this policy are many, but to name a few:
- folder bloat
- duplicate files on the Hub taking up disk space and bandwidth
- potential license violations (there are nuanced rules for direct packaging, such as direct packaging a CC BY-SA dependency means you must now license your content CC BY-SA and cannot put it in the Paid category)
- robbing creators of their downloads, reviews and reactions
- preventing subscribers from being able to auto-download the most recent version of the dependency
- circumventing the Var Health report scanning process and creating more work for the moderation team
- breaking the "dependency usage" stats and notifications
- content that is "NOT ON HUB" is often not there for a good reason, such as pirated content that will get you banned
6. Images are required in your description
Your resource cannot be posted without a thumbnail image that is representative of the resource itself.
In the case of most scenes and looks, this would be a screenshot of the actual content (not a brand logo or other unrelated image).
In the case of a plugin, we would prefer a screenshot of the actual plugin, but will allow some "creative" thumbnails if the plugin itself does not have a GUI.
In the description, we require at least one image. This image must be inserted into the description, not just attached.
7. Images MUST depict the ACTUAL content
Screenshots and videos in your resource description must show only what's actually included in your package.
"Clothing not included," "hair not included," and similar disclaimers are no longer permitted.
When preparing images for your description, take screenshots of your scene exactly as it will appear to anyone who loads your content into VaM.
If your scene allows the player to load their own presets (clothing, hair, appearance, etc.), consider using VaM's built-in content as a placeholder during your photoshoot.
Post-processing
You may use post-processing plugins (i.e. MacGruber's PostMagic) inside VaM during your photoshoot. These plugins must be credited in your description, and users must be made aware that the images have been altered from what ships in your VAR package.
External image editing — in Photoshop, GIMP, or any similar tool — falls into two buckets:
Allowed: Technical and graphic design work that doesn't alter how the VaM-rendered content itself appears. This includes:
- Cropping, resizing, format conversion, and file size optimization
- Text overlays, titles, and captions
- Frames, borders, and vignettes
- Logos, watermarks, and branding
- Thumbnail compositions and promotional layouts
- Basic exposure and brightness correction (for fixing an underlit or overexposed screenshot)
Not allowed: Edits that alter the appearance of the VaM-rendered content itself. This includes:
- Color grading, stylistic filters, or "look" presets applied to the rendered scene
- Skin smoothing, detail enhancement, or beautification filters
- Painting over, retouching, or compositing elements into the scene
- AI-generated imagery, AI upscaling, or AI-based alterations of any kind
The principle: your screenshots should accurately represent how your content renders in VaM. Graphic design around the screenshot is fine; minor technical corrections are fine; altering the look of the scene itself is not.
Want to show variations or creative uses?
This is exactly what the Community Gallery is for. You can now add images to your own resource's Community Gallery, which appears below your description and is clearly distinct from it.
Use the Community Gallery to showcase:
- Your resource paired with outfits, hair, or accessories from other creators
- Creative scene variations or alternate looks
- "Inspiration" images demonstrating what users could build with your content
All images in the Community Gallery must still follow the Hub's rules regarding media gallery policies.
You can also encourage your fans and subscribers to contribute their own screenshots to your Community Gallery — a great way to build engagement around your work.
Exception for resources that can't stand alone
Some resources can't be meaningfully demonstrated in isolation. A plugin that modifies lighting needs a scene to show what it does; a morph needs a base model to apply to; a pose needs a figure.
If your resource falls into a category where third-party content is genuinely required to illustrate what the resource does, you may include that content in your description screenshots — provided:
- You include a clear disclaimer identifying what is and isn't part of your package
- You properly attribute the third-party content used in the screenshot
- You comply with the non-commercial licensing rules below
This exception typically applies to: Plugins + Scripts, Clothing, Hairstyles, Morphs, Poses, Mocap + Animation, Textures, Environments, Lighting + HDRI, Toolkits + Templates, Comics + Storytelling, and Guides.
It does not apply to: Scenes, Looks, Assets & Accessories, or Demo + Lite resources.
These categories are our most popular and can be fully depicted with only the contents of your package (using VaM built-in content as placeholders where needed), and any "here's how it could look with other stuff" imagery belongs in the Community Gallery.
If you believe your resource is harmed by these restrictions and genuinely requires third-party content to be properly demonstrated, please open a support ticket before uploading.
The moderation team is happy to review the specifics of your resource and grant an exemption if warranted.
Non-commercial licensed content
The rules around NC content depend on who's adding the image and where.
The underlying principle: using NC content to market or promote a paid resource is a commercial use of that content; a visitor sharing a screenshot of their personal VaM session is not.
If you're the creator of a paid resource (including anything behind a paywall, early access, or tiered subscription):
You cannot include content with a non-commercial license anywhere on your resource page — description or Community Gallery — unless you have written permission from the original creator.
This applies whether the image is uploaded by you directly or by someone posting on your behalf.
If you're a visitor contributing to someone else's Community Gallery:
You don't need to worry about non-commercial licensing for your contributions.
Sharing screenshots of your own personal use of Hub content is not a commercial activity, regardless of whether the resource you're contributing to is paid or free.
Media Gallery rules apply as they normally would — just share your cool screenshots.
A note for paid resource creators: If a member adds an image to your Community Gallery that happens to contain NC content, you are not required to remove it — their contribution is their own personal use, not your commercial use.
The rule only governs images you or someone working on your behalf add to promote your resource.
Non-compliance
Resources that violate this policy will typically be temporarily unpublished until the creator updates their images.
This is not a reprimand — just a pause while things are corrected. Misuse of non-commercial content in paid resources is treated more seriously and may result in additional moderation action.
8. Paid posts and updates are limited to 3 a week
In order to prevent spamming or flooding of Paid content, you are restricted to a total of 3 posts and/or updates to Paid content per week.
If you exceed this limit, a system message will notify you and indicate how much time is left before you can make your next post/update.
In the event that you believe there is an error with your limit, please open a Support Ticket and our tech support can look at your account.
Likewise, if you feel you need a temporary exception to this rule, please contact a moderator by opening a Support Ticket.
Additionally, posting meaningless updates in order to "bump" your content is prohibited. Updates may be rejected if they do not contain sufficient cause for the update.
9. No links to external files in the description
Any files you include with your resource must be attached and scanned when you upload your resource.
Putting links to "additional files" or other content inside the description of the resource is not allowed.
10. Advertising your paid content
Where you may advertise Paid content:
- Paid Resources may be posted in the Paid categories only. Posting a resource will create an automatic post in the Paid categories section of the forums.
- Resource links may be posted in the #paid-links section of our Discord server if you have a valid Hub account and are the author of that resource.
- You may advertise your Paid content on your profile page under Profile Posts.
- In the Demo + Lite category (see #12 below)
Where you may NOT advertise Paid content:
- In the description of your Free content
- In our forums, other than the Paid category threads
- In our Media gallery
- In comments or reviews for other content
- On our Discord server, other than the #paid-links channels
- In the actual scene of your Free content when loaded into VaM
Please see the "No advertisements" section of our Free Resource posting guide.
11. Demos and "Lite" or "Extended" versions
The category "Demo + Lite" exists specifically for creators to give a taste of their Paid content before purchase. Here we allow hosted, downloadable scenes that advertise for Paid content.
Content in this category is not visible in the in-game Hub browser, and can be hidden in user preferences if you don't want to see this content.
This category is NOT meant for "Freebies" that link to paid content. A "Free hair" resource that goes with a Paid look should be in the Free->Hairstyles category with NO advertising attached.
In contrast, a "Free 3 hairstyles. Subscribe to the extended version to get all 10 hairstyles" would be allowed. This is the intention behind this category.
If we feel that you are using the category as a way to add "paid hook freebies" then we may opt to remove your content.
Demo content also cannot contain "bait" or "hooks" in the scene. This means no non-working elements or fake buttons that say things like "Get the paid version to use this feature".
The Demo content must be a fully functional scene. If it is a plugin, all of its included features must be fully functional.
If at any time we feel there is gross abuse of this category for the purpose of "easy" money or sketchy advertising practices, we may remove the category entirely.
12. Paid "Early Access"
"Early Access" content on the Hub is different from, for example, Steam "Early Access". Our "Early Access" content is Paid subscription content that will eventually be released for free after a period of time.
Subscribers can get the content "Early" by paying or subscribing to the creator's subscription page.
Early Access content must include an Early Access End Date (a date the content will become free), and a Secondary License (the license the content will adopt after the Early Access period ends)
When the Early Access period ends, you are responsible for moving your content. You will do this by selecting "Convert to Free" from your resource settings menu (the cog icon) on the Hub.
Your resource will be automatically moved to the appropriate category and you will be asked to upload a new version which includes the file.
Your resource will remain unpublished until you upload the file.
When the Early Access period ends, you will receive an automated reminder message from the Hub. You will then have a 3 day grace period to upload your free version. If that period ends, your resource will be automatically unpublished.
13. New Accounts and old accounts posting their first resource
Accounts newer than 30 days old, or older accounts trying to post their first resource must wait for a period of one month before being allowed to post paid content or to share links to Patreon or other subscription services.
Please see this post regarding limitations for new accounts.