Optimization also improves the chance that other players will see your avatar instead of a fallback.
VRChat ranks avatars from Excellent to Very Poor. Exceeding the limit in any single category lowers the avatar’s entire rank.
A practical target is Good for PC and Medium or better for mobile.
| Limit | PC Excellent | PC Good | Mobile Medium |
|---|---|---|---|
| Triangles | 32,000 | 70,000 | 15,000 |
| Texture memory | 40 MB | 75 MB | 25 MB |
| Skinned meshes | 1 | 2 | 2 |
| Material slots | 4 | 8 | 2 |
| PhysBone components | 4 | 8 | 6 |
| Bones | 75 | 150 | 150 |
View all current limits in the VRChat Performance Ranks documentation.
Open the VRChat SDK panel in Unity and select the Builder tab.
The SDK displays your avatar’s:
Check this panel regularly while editing. Disabled GameObjects and components still count toward the performance rank, so remove anything you no longer use.
Detailed avatar bases, clothing, hair, and accessories can quickly push the triangle count too high.
You can reduce triangles by:
Avoid aggressive automatic decimation around the face, hands, and joints. These areas need enough geometry to deform correctly.
Each separate mesh adds rendering work. Skinned meshes are especially expensive.
Where practical, combine the body, clothing, and accessories into fewer skinned meshes using Blender. VRChat recommends aiming for one skinned mesh whenever possible.
Keep separate meshes only when they are genuinely needed for toggles or customization.
Every material slot generally creates another draw call.
Using the same material in several slots does not solve the problem. The number of slots on the renderer still matters.
To reduce material slots:
For PC avatars, staying at eight material slots or fewer allows you to achieve a Good rank.
Textures are often the largest source of excessive VRAM usage.
A texture does not need to be 4K just because the original file was supplied at that size. Small accessories may only need a 512px or 1024px texture.
In Unity, select each texture and adjust:
Use 2K textures only where the extra detail is visible. Combine smaller textures where practical and remove unused maps.
Remember that download size and texture memory are different. A small avatar download can still consume a large amount of VRAM.
PhysBones make hair, ears, tails, and clothing move naturally, but large setups can become expensive.
Improve them by:
Use PhysBones instead of the deprecated Dynamic Bones system.
Unused bones still add skinning work.
Delete bones left behind by removed clothing, accessories, or old PhysBone chains. Merge their weights into a suitable parent bone before deleting them.
You should also remove blend shapes that your avatar never uses. Keep only those required for facial expressions, lip sync, eye movement, and active customization.
Particles and lights can heavily affect performance in busy instances.
Avoid:
Mobile avatars cannot use several PC components, including avatar lights and audio sources. Treat these as optional PC features rather than core parts of the avatar.
Do not upload the full PC avatar directly to Quest, Android, or iOS.
Create a mobile version with:
VRChat supports per-platform avatar overrides, allowing optimized PC and mobile versions to share the same avatar ID.
Current maximum avatar sizes are:
| Platform | Download size | Uncompressed size |
|---|---|---|
| PC | 200 MB | 500 MB |
| Android | 10 MB | 40 MB |
These are upload limits, not optimization targets. Staying far below them gives players a better experience.
Use Build & Test to check the avatar inside VRChat before publishing it.
Look for:
Test both PC and mobile versions when supporting multiple platforms.
Before uploading your avatar:
Optimization does not mean removing everything that makes an avatar unique. Focus on features players will notice and remove the hidden waste they will not.
