Frequently Asked Questions
Answers about product formats, Unity requirements, shaders, licenses, commissions, Quest support, downloads, and support.
Products and setup
What does a typical product include?
Contents vary by listing and may include a Unity package, FBX, textures, prefabs, or documentation. The file list on the individual product page is the source of truth.
Which Unity version should I use?
Use the version stated by the product and currently supported by VRChat. If those differ because the product is older, test in a duplicate project and consult the creator before migrating the only working copy.
Why are my materials pink?
The required shader may be missing, imported after the asset, or incompatible with the project version. Install the documented shader first, wait for compilation, and then reimport only the affected material or product package.
Does every asset support Quest?
No. Quest or Android support must be stated on the listing. PC shaders, particles, and material features do not automatically convert to mobile.
Do I need VRCFury?
Only when the listing names it as a requirement or uses VRCFury components. Install the documented version before importing the dependent prefab.
Licensing and orders
What is the difference between personal and commercial use?
Personal use generally covers the buyer's own permitted private project, while commercial permission may cover paid, commissioned, public, or distributed work as specifically stated. Always read the selected product license and terms.
Can I share the package with a friend or client?
Do not share source packages or editable files unless the license expressly permits it. Commission workflows may require both parties to own the product. Use the supported gift process for another recipient.
Can I edit or retexture an asset?
Many licenses permit edits for an allowed finished project, but the edit does not transfer ownership or permit resale of the asset or retexture. Preserve credit and license records.
What should I send with a support request?
Include the product name, order reference, Unity and SDK versions, required tool and shader versions, expected behavior, actual behavior, and the first relevant console error. Remove private data from screenshots.
Where can I learn the full workflow?
Visit the articles hub for detailed guides covering imports, performance, materials, cross-platform conversion, AudioLink, fitting, licensing, and release quality control.