Guides:Avatar Performance Ranking: Difference between revisions

From VRChat Wiki
← Older edit
VisualWikitext
m Added categories.
~Pausbe (talk | contribs)
Community Moderators
1,454 edits
Simplify SDK category.
 
(20 intermediate revisions by 7 users not shown)
Line 1: Line 1:
[[Category:Avatars]]
{{Noticebox/Community}}
[[Category:Performance]]
[[Category:Introduction]]
 
== Introduction ==
== Introduction ==
'''VRChat''' has many ways of managing performance and safety within the game, Avatar '''Performance Ranks''' are one of them.<br>
VRChat uses several systems to help manage performance and safety within the platform. Avatar Performance Ranks are one of these systems and are used to communicate how resource intensive an avatar is.<br>


== Performance Ranks ==
== Performance Ranks ==
Ranks range from '''Very Poor''' to '''Excellent''', based on avatar complexity and resource usage in-game.<br>
Ranks range from '''Very Poor''' to '''Excellent''', based on avatar complexity and resource usage in-game.<br>


[[Category: Performance Ranks]]


{| class="wikitable mw-collapsible"
{| class="wikitable mw-collapsible"
Line 16: Line 12:
! Rank !! Icon !! Meaning
! Rank !! Icon !! Meaning
|-
|-
| '''Excellent''' || [[File:Excellent.png|thumb|114x114px]]|| '''"Excellent"''' rated avatars are highly optimized and there is minimal impact on performance.
| '''Excellent''' || [[File:Perf_excellent.png|114x114px]]|| Highly optimized avatars with minimal impact on performance.
|-
|-
| '''Good''' || [[File:Good.png|thumb|114x114px]]|| '''"Good"''' rated avatars are well optimized, and are generally considered safe for most users.
| '''Good''' || [[File:Perf_good.png|114x114px]]|| Well optimized avatars that are generally safe for most users.
|-
|-
| '''Medium''' || [[File:Medium.png|thumb|114x114px]]|| '''"Medium"''' rated avatars are considered acceptable; May cause minor performance issues
| '''Medium''' || [[File:Perf_medium.png|114x114px]]|| Acceptable avatars that may cause minor performance impact.
|-
|-
| '''Poor''' || [[File:Poor.png|thumb|114x114px]]|| "'''Poor"''' rated avatars are considered heavy on impact; They may cause lag or potentially crash lower-end systems.  
| '''Poor''' || [[File:Perf_poor.png|114x114px]]|| Avatars with noticeable performance impact, especially on lower-end systems.  
|-
|-
| '''Very Poor''' || [[File:Verypoor.png|thumb|114x114px]]|| '''"Very Poor"''' rated avatars are the most common; They are considered unsafe and are hidden by default safety settings, unless manually shown. They have a decent change at lagging low-to-mid end systems and some high-end systems. May cause crashes. These avatars '''exceed''' VRChat's performance limits in one or multiple ways.
| '''Very Poor''' || [[File:Perf_vpoor.png|114x114px]]|| Avatars that significantly exceed performance limits and are hidden by default safety settings unless manually shown.
|}
|}


[[Category:Avatar Metrics]]
== Avatar Metrics ==
== Avatar Metrics ==
'''VRChat''' has a unique avatar metric system that outlines the performance of each avatar, or world. An avatar's metrics are the main measurement for your Avatar's '''Performance Rank'''. These metrics measure how resource-intensive your avatar is. The more demanding the metrics are, the lower your avatar will be ranked. Lower ranks effect visibility, performance, and other user's experience.
'''VRChat''' has a unique avatar metric system that outlines the performance of each avatar. An avatar's metrics are the main measurement for your Avatar's '''Performance Rank'''. These metrics measure how resource-intensive your avatar is. The more demanding the metrics are, the lower your avatar will be ranked. Lower ranks affect avatar visibility, performance, and the experience of other users.


=== Metric Elements ===
=== Metric Elements ===


* '''Polygons''': These measure how complex your avatar's geometry is. A polygon count of an avatar is the number of tiny triangles that make up an avatar's 3D shape. More triangles = more detail, but more performance-intensive; Therefore more work for a system to process and render. This is also known as '''Triangle Count'''.
* '''Triangles''': These measure how complex your avatar's geometry is. A triangle count of an avatar is the number of tiny triangles that make up an avatar's 3D shape.
* '''Materials''': Unique surface types that apply to each part of your avatar. Skin, clothing, eyes, harnesses, etc. More materials = more performance-intensive; Therefore more work for a system to process and render.
* '''Bounds Size''': The total size of the avatar. This can be very large if a user has large animation on the avatar, even if it isn't showing all the time. (Note Bounds Size will not cause the avatar to be blocked, even if it is below the "Minimum Displayed Performance Rank" setting)
* '''Textures''': These are image files (Such as PNGs, or JPGs), that give color and detail to the materials. Larger textures mean more detail, but make an avatar's '''size''' bigger. Bigger size means bigger download, and people may not render your avatar well. Too big of an avatar is not allowed, and cannot be uploaded.
*'''Texture Memory''': The amount of memory estimated to be in use by the avatar's textures. These textures occupy space in both system RAM and in the video card's memory.
* '''Dynamic Bones (Physbones)''': Bones that move or "jiggle" dynamically with how the avatar itself is moving. Things such as hair, tails, ears, or small accessories may have '''Dynamic Bones'''. These can be converted and/or removed easily for avatar performance.
*'''Skinned Meshes''': The number of [https://docs.unity3d.com/2022.3/Documentation/Manual/class-SkinnedMeshRenderer.html Skinned Mesh Renderer components] on the avatar.  
* '''Meshes (skinned)''': These are meshes that deform with the bones. Things such as the body, face, and clothing. Each mesh adds complexity to the avatar; it is recommended to merge and blend meshes when possible.
*'''Basic Meshes''': The number of (non-skinned) [https://docs.unity3d.com/2022.3/Documentation/Manual/class-MeshRenderer.html Mesh Renderer components] on the avatar.
* '''Audio Sources''': These sources are simply sound emitters that are attached the the avatar. Voice lines, music, sound effects are '''audio sources'''. Multiple sources may cause lay or audio clutter. It is recommended to use 1-2 maximum; Avoid looping audios unless necessary.
*'''Material Slots''': The number of [https://docs.unity3d.com/2022.3/Documentation/Manual/Materials.html material]  slots on the avatar. [https://docs.unity3d.com/2022.3/Documentation/Manual/Materials.html Material] slots are the slots on the mesh where you fit materials in.
* '''Real-Time Lights''': These are lights that cast shadows or change dynamically. Things like glowing eyes, flashlights, or built-in light probes on some avatars. More lights cause '''heavy lag'''. It is highly recommended to bake lighting into textures instead.
*'''PhysBone Components''': The number of [https://creators.vrchat.com/common-components/physbones/ PhysBone] components on the avatar.
* '''Shaders:''' Code that controls how materials look. Things such as a materials glow, if it is transparent (PC only), or animated. Complex shaders are highly performance-intensive, and '''will''' crash low-mid end systems if not used carefully. Simple shaders such as '''VRChat'''<nowiki/>'s built-in shaders are '''safe for all devices'''. It is typically recommended to avoid transparent shaders and animation unless they are optimized.
*'''PhysBone Affected Transforms''': The total number of transforms affected by PhysBones components on the avatar.
*'''PhysBone Colliders''': The number of PhysBone collider scripts on the avatar.
*'''PhysBone Collision Check Count''': The sum of how many PhysBone transforms each collider can affect. This can count transforms twice or more, because a single transform can be affected by multiple colliders.
*'''Contacts''': The number of [https://creators.vrchat.com/common-components/contacts/ Contacts] on the avatar.
*'''Constraint Count''': The total number of [https://creators.vrchat.com/common-components/constraints/ VRChat constraints] and Unity constraints on the avatar.
*'''Constraint Depth''': The deepest chain of dependencies across all constraints on the avatar. (See [https://creators.vrchat.com/common-components/constraints/#performance here] for more information)
*'''Animators''': The number of [https://docs.unity3d.com/6000.3/Documentation/Manual/class-AnimatorController.html Animators] on the avatar.
*'''Bones''': The number of Bones in the avatar's rig.
*'''Lights''': The number of Light components on the avatar.
*'''Particle Systems''': The number of Particle System components on the avatar.
*'''Total Particles Active''': The sum of maxParticles across all particle systems on the avatar.
*'''Mesh Particle Active Polys''': The total number of triangles of Mesh Particles emitted by Particle Systems that are active.
*'''Particle Trails Enabled''': If any Particle Systems on the avatar have Particle Trails enabled, this will be True.
*'''Particle Collision Enabled''': If any Particle Systems on the avatar have Particle Collision enabled, this will be True.
*'''Trail Renderers''': The number of Trail Renderers on the avatar.
*'''Line Renderers''': The number of Line Renderers on the avatar.
*'''Cloths''': The total number of Cloth components on the avatar.
 
Note all GameObjects and Components, including those that are currently disabled, count towards the Avatar Performace Rank.
 
Note if Mesh Read/Write on '''any''' mesh on the avatar (including particle systems), the "Triangles" count will read "Mesh Read/Write Disabled" and the avatar's Performance Rank will be immediately downgraded to "Very Poor" regardless of the actual triangle count on the avatar.
 
=== Rank Thresholds on PC ===
 
The below table shows the maximum value of each metric for each performance rank on PC.
 
{| class="wikitable mw-collapsible"
|+ Rank Thresholds on PC
|-
! Rank !! Excellent !! Good !! Medium !! Poor
|-
| '''Triangles''' || 32,000 || 70,000 || 70,000 || 70,000
|-
| '''Bounds Size''' || 2.5m x 2.5m x 2.5m || 4m x 4m x 4m || 5m x 6m x 5m || 5m x 6m x 5m
|-
| '''Texture Memory''' || 40 MB || 75 MB || 110 MB || 150 MB
|-
| '''Skinned Meshes''' || 1 || 2 || 8 || 16
|-
| '''Basic Meshes''' || 4 || 8 || 16 || 24
|-
| '''Material Slots''' || 4 || 8 || 16 || 32
|-
| '''PhysBone Components''' || 4 || 8 || 16 || 32
|-
| '''PhysBone Affected Transforms''' || 16 || 64 || 128 || 256
|-
| '''PhysBone Colliders''' || 4 || 8 || 16 || 32
|-
| '''PhysBone Collision Check Count''' || 32 || 128 || 256 || 512
|-
| '''Contacts''' || 8 || 16 || 24 || 32
|-
| '''Constraint Count''' || 100 || 250 || 300 || 350
|-
| '''Constraint Depth''' || 20 || 50 || 80 || 100
|-
| '''Animators''' || 1 || 4 || 16 || 32
|-
| '''Bones''' || 75 || 150 || 256 || 400
|-
| '''Lights''' || 0 || 0 || 0 || 1
|-
| '''Particle Systems''' || 0 || 4 || 8 || 16
|-
| '''Total Particles Active''' || 0 || 300 || 1000 || 2500
|-
| '''Total Particle Active Polys''' || 0 || 1000 || 2000 || 5000
|-
| '''Particle Trails Enabled''' || False || False || True || True
|-
| '''Particle Collision Enabled''' || False || False || True || True
|-
| '''Trail Renderers''' || 1 || 2 || 4 || 8
|-
| '''Line Renderers''' || 1 || 2 || 4 || 8
|-
| '''Cloths''' || 0 || 1 || 1 || 1
|-
| '''Total Cloth Vertices''' || 0 || 50 || 100 || 200
|-
| '''Physics Colliders''' || 0 || 1 || 8 || 8
|-
| '''Physics Rigidbodies''' || 0 || 1 || 8 || 8
|-
| '''Audio Sources''' || 1 || 4 || 8 || 8
|-
|'''Raycasts''' || 1 || 2 || 5 || 9
|}
 
=== Rank Thresholds on Mobile ===
 
This includes VRChat running on Android, IOS, and Meta Quest. Avatar Rank thresholds are stricter than on PC.
 
The below table shows the maximum value of each metric for each performance rank on Mobile.


[[Category:Rank Thresholds]]
=== Rank Thresholds (Limits) ===
{| class="wikitable mw-collapsible"
{| class="wikitable mw-collapsible"
|+Thresholds (Limits)
|+ Rank Thresholds on Mobile
!Rank
|-
!Polygons
! Rank !! Excellent !! Good !! Medium !! Poor
!Materials
|-
!Textures
| '''Triangles''' || 7,500 || 10,000 || 15,000 || 20,000
!Dynamic Bones (Physbones)
|-
!Audio Sources
| '''Bounds Size''' || 2.5m x 2.5m x 2.5m || 4m x 4m x 4m || 5m x 6m x 5m || 5m x 6m x 5m
!Real-Time Lights
|-
!Shaders
| '''Texture Memory''' || 10 MB || 18 MB || 25 MB || 40 MB
|-
| '''Skinned Meshes''' || 1 || 1 || 2 || 2
|-
| '''Basic Meshes''' || 1 || 1 || 2 || 2
|-
| '''Material Slots''' || 1 || 1 || 2 || 4
|-
| '''PhysBone Components''' || 0 || 4 || 6 || 8
|-
| '''PhysBone Affected Transforms''' || 0 || 16 || 32 || 64
|-
| '''PhysBone Colliders''' || 0 || 4 || 8 || 16
|-
| '''PhysBone Collision Check Count''' || 0 || 16 || 32 || 64
|-
| '''Contacts''' || 2 || 4 || 8 || 16
|-
| '''Constraint Count''' || 30 || 60 || 120 || 150
|-
| '''Constraint Depth''' || 5 || 15 || 35 || 50
|-
|-
|'''Excellent'''
| '''Animators''' || 1 || 1 || 1 || 2
|Under 10,000
|1-2
|Lower count; Small (512x512 or less)
|Minimal Use / None
|0-1
|None
|Simple (Unlit or Mobile)
|-
|-
|'''Good'''
| '''Bones''' || 75 || 90 || 150 || 150
|10,000-30,000
|3-10
|Okay count; mid-size (up to 1024x1024)
|Light Use
|1-2
|None
|Basic with minimal transparency
|-
|-
|'''Medium'''
| '''Particle Systems''' || 0 || 0 || 0 || 2
|30,000-50,000
|10-15
|Larger or multiple (up to 2048x2048)
|Moderate Use
|2-4
|Avoid if possible
|Moderate Complexity
|-
|-
|'''Poor'''
| '''Total Particles Active''' || 0 || 0 || 0 || 200
|50,000-70,000
|15-20
|Large or memory-intensive
|Heavy Use
|4+
|Acceptable
|Complex or transparent
|-
|-
|'''Very Poor'''
| '''Total Particle Active Polys''' || 0 || 0 || 0 || 400
|70,000+
|-
|20+
| '''Particle Trails Enabled''' || False || False || False || True
|Excessive Usage
|-
|128+ Components
| '''Particle Collision Enabled''' || False || False || False || True
|4+
|-
|Any
| '''Trail Renderers''' || 0 || 0 || 0 || 1
|Complex, layered, animated, transparent
|-
| '''Line Renderers''' || 0 || 0 || 0 || 1
|-
|'''Raycasts''' || 1 || 2 || 3 || 5
|}
|}


[[Category:Optimization Tips]]
Lights, Cloths, Total Cloth Vertices, Physics Colliders, Physics Rigidobdies, and Audio Sources are not shown since they can never appear on avatars.
 
If the Very Poor value is exceeded on mobile, no matter the current "Show Avatar" state of the avatar, all PhysBones, Contacts, and VRChat Constraints on the avatar will be removed.
 
== Optimization Tips (Per Metric) ==
== Optimization Tips (Per Metric) ==


Line 113: Line 198:
Compress textures (make smaller size, less detail) when possible. It is recommended to use formats like JPEG or WebP for lightweight assets. Use 1024x1024 or lower if possible.
Compress textures (make smaller size, less detail) when possible. It is recommended to use formats like JPEG or WebP for lightweight assets. Use 1024x1024 or lower if possible.


=== Dynamic Bones (PhysBones) ===
=== PhysBones (Dynamic Bones) ===
Switch to PhysBones (Newer system). Limit bone chains, colliders, and detail. Use bone filters to exclude unnecessary movements, and reduce bugs.
If using Dynamic Bones (an older system), switch to PhysBones. Limit bone chains, colliders, and detail. Use bone filters to exclude unnecessary movements, and reduce bugs.


=== Meshes (Skinned) ===
=== Meshes (Skinned) ===
Line 126: Line 211:


=== Shaders ===
=== Shaders ===
Annoying, but necessary. Use lower-intensive shaders. Unlit and Mobile of course are recommended, but don't look as good or flashy. Avoid transparency, animation, or multi-pass effects unless they are optimized and minimal.<blockquote>It is possible to view your current avatar metrics from the VRChat avatars menu. Useful to identify possible avatar bottlenecks, and to know where adjustments need to be made if necessary.
Use lower-intensive shaders (like [https://creators.vrchat.com/platforms/android/quest-content-limitations/ VRChat's Mobile shaders]). Avoid transparency, animation, or multi-pass effects unless they are optimized and minimal. Use


</blockquote>
It is possible to view your current avatar metrics from the VRChat avatars menu as well as inside the [https://creators.vrchat.com/sdk VRChat SDK] in Unity. Useful to identify possible avatar bottlenecks, and to know where adjustments need to be made if necessary.
 
== Frame time context ==
At 90 fps the total frame time budget is roughly 11 ms; at 60 fps it is roughly 16 ms. Community benchmarks provide approximate per-component costs measured on mid-to-high-end hardware (see [[Community:VRChat Performance Benchmarks]] for full methodology). Key results relevant to performance ranking include:
 
{| class="wikitable"
! Component
! Approximate cost
|-
| Animator layer (basic 2-state toggle)
| ~0.01 ms per layer (quadratic scaling with layer count)
|-
| Direct Blend Tree toggle
| ~75% less frame time than equivalent layer toggles
|-
| PhysBone transforms
| ~0.66 ms per 1000 affected transforms
|-
| VRC Constraints
| ~0.25 ms per 1000 active constraints (increases with depth)
|-
| Unity Constraints (auto-converted)
| ~0.75 ms per 1000 (native VRC Constraints recommended)
|-
| Contact Senders/Receivers
| ~0.5-0.75 ms per 1000, depending on toggling activity
|-
| Draw calls (material slots × meshes)
| ~2 ms per 1000 draw calls
|-
| Cloth vertices
| ~0.2 ms per 1000 vertices (up to ~200k)
|-
| Bones on Skinned Mesh Renderers
| ~0.32 ms per 1000 bones (while moving)
|}
 
State behaviors on any layer of any controller increase the runtime of ''all'' controllers on that avatar by roughly 50%. Since the default Action and Gesture layers use state behaviors, this cost is typically always present.


[[Category:Related Systems]]
== Related Systems ==
== Related Systems ==


===== [[Dynamic Bones|Avatar Dynamics]] =====
* [[Avatar Dynamics|Avatar Dynamics]]
 
* [[Trust and Safety|Trust and Safety System]]
 
* [https://creators.vrchat.com/avatars/avatar-size-limits/ Avatar Size Limits]
 
* [https://creators.vrchat.com/avatars/avatar-components Avatar Components]


===== [[Trust and Safety|Trust and Safety System]] =====
* [https://docs.vrchat.com/docs/avatar-fallback-system Avatar Fallback System]


===== [https://creators.vrchat.com/avatars/avatar-size-limits/ Avatar Size Limits] =====
== Official resources ==


===== [https://creators.vrchat.com/avatars/avatar-components Avatar Components] =====
* [https://creators.vrchat.com/avatars/avatar-performance-ranking-system Avatar Performance Ranking System] on Creator Docs
* [https://creators.vrchat.com/avatars/avatar-optimizing-tips Avatar Optimization Tips] on Creator Docs


===== [https://docs.vrchat.com/docs/avatar-fallback-system Avatar Fallback System] =====
== References ==
* [https://vrc.school/docs/Other/Benchmarks VRC School: Unity/VRChat Performance Benchmarks]
* [https://github.com/jellejurre/UnityBenchmark UnityBenchmark] on GitHub (data generation tool)


__FORCETOC__
[[Category:Avatars{{#translation:}}]]
__INDEX__
[[Category:Guides{{#translation:}}]]
[[Category:SDK{{#translation:}}]] <!-- probably not needed -->
[[Category:Needs images{{#translation:}}]]

Latest revision as of 02:37, 16 April 2026

V · ECommunity-written content
The following was created by the community. It may contain material not directly endorsed by the VRChat team. To learn more, consider reading Contributing to the VRChat Wiki.

Introduction

VRChat uses several systems to help manage performance and safety within the platform. Avatar Performance Ranks are one of these systems and are used to communicate how resource intensive an avatar is.

Performance Ranks

Ranks range from Very Poor to Excellent, based on avatar complexity and resource usage in-game.


Avatar Performance Ranks
Rank Icon Meaning
Excellent Highly optimized avatars with minimal impact on performance.
Good Well optimized avatars that are generally safe for most users.
Medium Acceptable avatars that may cause minor performance impact.
Poor Avatars with noticeable performance impact, especially on lower-end systems.
Very Poor Avatars that significantly exceed performance limits and are hidden by default safety settings unless manually shown.

Avatar Metrics

VRChat has a unique avatar metric system that outlines the performance of each avatar. An avatar's metrics are the main measurement for your Avatar's Performance Rank. These metrics measure how resource-intensive your avatar is. The more demanding the metrics are, the lower your avatar will be ranked. Lower ranks affect avatar visibility, performance, and the experience of other users.

Metric Elements

  • Triangles: These measure how complex your avatar's geometry is. A triangle count of an avatar is the number of tiny triangles that make up an avatar's 3D shape.
  • Bounds Size: The total size of the avatar. This can be very large if a user has large animation on the avatar, even if it isn't showing all the time. (Note Bounds Size will not cause the avatar to be blocked, even if it is below the "Minimum Displayed Performance Rank" setting)
  • Texture Memory: The amount of memory estimated to be in use by the avatar's textures. These textures occupy space in both system RAM and in the video card's memory.
  • Skinned Meshes: The number of Skinned Mesh Renderer components on the avatar.
  • Basic Meshes: The number of (non-skinned) Mesh Renderer components on the avatar.
  • Material Slots: The number of material slots on the avatar. Material slots are the slots on the mesh where you fit materials in.
  • PhysBone Components: The number of PhysBone components on the avatar.
  • PhysBone Affected Transforms: The total number of transforms affected by PhysBones components on the avatar.
  • PhysBone Colliders: The number of PhysBone collider scripts on the avatar.
  • PhysBone Collision Check Count: The sum of how many PhysBone transforms each collider can affect. This can count transforms twice or more, because a single transform can be affected by multiple colliders.
  • Contacts: The number of Contacts on the avatar.
  • Constraint Count: The total number of VRChat constraints and Unity constraints on the avatar.
  • Constraint Depth: The deepest chain of dependencies across all constraints on the avatar. (See here for more information)
  • Animators: The number of Animators on the avatar.
  • Bones: The number of Bones in the avatar's rig.
  • Lights: The number of Light components on the avatar.
  • Particle Systems: The number of Particle System components on the avatar.
  • Total Particles Active: The sum of maxParticles across all particle systems on the avatar.
  • Mesh Particle Active Polys: The total number of triangles of Mesh Particles emitted by Particle Systems that are active.
  • Particle Trails Enabled: If any Particle Systems on the avatar have Particle Trails enabled, this will be True.
  • Particle Collision Enabled: If any Particle Systems on the avatar have Particle Collision enabled, this will be True.
  • Trail Renderers: The number of Trail Renderers on the avatar.
  • Line Renderers: The number of Line Renderers on the avatar.
  • Cloths: The total number of Cloth components on the avatar.

Note all GameObjects and Components, including those that are currently disabled, count towards the Avatar Performace Rank.

Note if Mesh Read/Write on any mesh on the avatar (including particle systems), the "Triangles" count will read "Mesh Read/Write Disabled" and the avatar's Performance Rank will be immediately downgraded to "Very Poor" regardless of the actual triangle count on the avatar.

Rank Thresholds on PC

The below table shows the maximum value of each metric for each performance rank on PC.

Rank Thresholds on PC
Rank Excellent Good Medium Poor
Triangles 32,000 70,000 70,000 70,000
Bounds Size 2.5m x 2.5m x 2.5m 4m x 4m x 4m 5m x 6m x 5m 5m x 6m x 5m
Texture Memory 40 MB 75 MB 110 MB 150 MB
Skinned Meshes 1 2 8 16
Basic Meshes 4 8 16 24
Material Slots 4 8 16 32
PhysBone Components 4 8 16 32
PhysBone Affected Transforms 16 64 128 256
PhysBone Colliders 4 8 16 32
PhysBone Collision Check Count 32 128 256 512
Contacts 8 16 24 32
Constraint Count 100 250 300 350
Constraint Depth 20 50 80 100
Animators 1 4 16 32
Bones 75 150 256 400
Lights 0 0 0 1
Particle Systems 0 4 8 16
Total Particles Active 0 300 1000 2500
Total Particle Active Polys 0 1000 2000 5000
Particle Trails Enabled False False True True
Particle Collision Enabled False False True True
Trail Renderers 1 2 4 8
Line Renderers 1 2 4 8
Cloths 0 1 1 1
Total Cloth Vertices 0 50 100 200
Physics Colliders 0 1 8 8
Physics Rigidbodies 0 1 8 8
Audio Sources 1 4 8 8
Raycasts 1 2 5 9

Rank Thresholds on Mobile

This includes VRChat running on Android, IOS, and Meta Quest. Avatar Rank thresholds are stricter than on PC.

The below table shows the maximum value of each metric for each performance rank on Mobile.

Rank Thresholds on Mobile
Rank Excellent Good Medium Poor
Triangles 7,500 10,000 15,000 20,000
Bounds Size 2.5m x 2.5m x 2.5m 4m x 4m x 4m 5m x 6m x 5m 5m x 6m x 5m
Texture Memory 10 MB 18 MB 25 MB 40 MB
Skinned Meshes 1 1 2 2
Basic Meshes 1 1 2 2
Material Slots 1 1 2 4
PhysBone Components 0 4 6 8
PhysBone Affected Transforms 0 16 32 64
PhysBone Colliders 0 4 8 16
PhysBone Collision Check Count 0 16 32 64
Contacts 2 4 8 16
Constraint Count 30 60 120 150
Constraint Depth 5 15 35 50
Animators 1 1 1 2
Bones 75 90 150 150
Particle Systems 0 0 0 2
Total Particles Active 0 0 0 200
Total Particle Active Polys 0 0 0 400
Particle Trails Enabled False False False True
Particle Collision Enabled False False False True
Trail Renderers 0 0 0 1
Line Renderers 0 0 0 1
Raycasts 1 2 3 5

Lights, Cloths, Total Cloth Vertices, Physics Colliders, Physics Rigidobdies, and Audio Sources are not shown since they can never appear on avatars.

If the Very Poor value is exceeded on mobile, no matter the current "Show Avatar" state of the avatar, all PhysBones, Contacts, and VRChat Constraints on the avatar will be removed.

Optimization Tips (Per Metric)

Polygons

Use decimation tools in Blender or Unity to reduce triangle counts. Avoid higher-poly accessories if possible. Combine meshes when possible.

Materials

Merge materials using texture atlases and tools available in Unity. Fewer materials = fewer draw calls, which improves render speed.

Textures

Compress textures (make smaller size, less detail) when possible. It is recommended to use formats like JPEG or WebP for lightweight assets. Use 1024x1024 or lower if possible.

PhysBones (Dynamic Bones)

If using Dynamic Bones (an older system), switch to PhysBones. Limit bone chains, colliders, and detail. Use bone filters to exclude unnecessary movements, and reduce bugs.

Meshes (Skinned)

Combine skinned meshes in Unity using tools like Mesh Baker, or available 3rd party software. Avoid separate meshes for small accessories if possible.

Audio Sources

Use one audio source per avatar if possible. Avoid looping audios, or higher-bitrate audio unless absolutely essential.

Real-Time Lights

Avoid real-time lights at all possibilities. Instead, bake the lighting into textures or use emissive materials.

Shaders

Use lower-intensive shaders (like VRChat's Mobile shaders). Avoid transparency, animation, or multi-pass effects unless they are optimized and minimal. Use

It is possible to view your current avatar metrics from the VRChat avatars menu as well as inside the VRChat SDK in Unity. Useful to identify possible avatar bottlenecks, and to know where adjustments need to be made if necessary.

Frame time context

At 90 fps the total frame time budget is roughly 11 ms; at 60 fps it is roughly 16 ms. Community benchmarks provide approximate per-component costs measured on mid-to-high-end hardware (see Community:VRChat Performance Benchmarks for full methodology). Key results relevant to performance ranking include:

Component Approximate cost
Animator layer (basic 2-state toggle) ~0.01 ms per layer (quadratic scaling with layer count)
Direct Blend Tree toggle ~75% less frame time than equivalent layer toggles
PhysBone transforms ~0.66 ms per 1000 affected transforms
VRC Constraints ~0.25 ms per 1000 active constraints (increases with depth)
Unity Constraints (auto-converted) ~0.75 ms per 1000 (native VRC Constraints recommended)
Contact Senders/Receivers ~0.5-0.75 ms per 1000, depending on toggling activity
Draw calls (material slots × meshes) ~2 ms per 1000 draw calls
Cloth vertices ~0.2 ms per 1000 vertices (up to ~200k)
Bones on Skinned Mesh Renderers ~0.32 ms per 1000 bones (while moving)

State behaviors on any layer of any controller increase the runtime of all controllers on that avatar by roughly 50%. Since the default Action and Gesture layers use state behaviors, this cost is typically always present.

Related Systems

Official resources

References

Retrieved from "https://wiki.vrchat.com/index.php?title=Guides:Avatar_Performance_Ranking&oldid=69366"