Geometry
Last updated
Last updated
Geometry - meaning the number of objects and polygons in a scene - is one of the main factors affecting both project size and real-time performance.
Reducing polygon count wherever possible is always a good practice. While scenes with up to 500,000 polygons generally perform well, performance may degrade beyond that. The recommended target is under 100,000 polygons for the best experience.
For AR projects, keeping polygon count below 100,000 is recommended.
Simplify modifier – Use the to reduce polygon count while maintaining the overall shape of the object. Note that very high-polygon models may cause the browser tab to become unresponsive.
Use linked duplicates (instances) – For repeating objects, use linked duplicates instead of full copies. Use Ctrl+Shift+D
or the right-click context menu to create an instance. Instances share geometry, meaning they do not increase polygon count. Changes made to one instance update all linked ones. This same principle applies to .
Simplify distant or hidden objects – For objects that are far away or barely visible in the scene, consider reducing their detail or simplifying their geometry.
Remove internal or hidden geometry – Some models may contain internal geometry or objects that are not visible. These should be removed or hidden to reduce complexity.
Weld disconnected parts – In Geometry edit mode, use the to merge disconnected parts into a single mesh. This helps simplify and optimize the model.