Guides
Roblox tree models: low-poly trees that don't lag your game
How to make and place Roblox trees that look good and stay fast: triangle budgets, reusing meshes, collision and shadow settings for forests.
3 min read

Quick answer
How do you add trees to a Roblox game without lag?
Make two or three light tree meshes and reuse them hundreds of times instead of importing many unique trees. Identical meshes can be batched together, so a forest of copies costs far less than a forest of originals. Turn off collision on leaves and keep each tree to a few hundred triangles.
Why trees are where maps get slow
One tree is cheap. Five hundred trees are not, and maps need forests. The good news is that Roblox is built to draw many copies of the same mesh efficiently. The performance guide explains that identical meshes sharing the same mesh content can be batched into one draw call, and recommends uploading each mesh once and duplicating it in Studio.
So the rule for trees is: few unique meshes, many copies.
How light should a tree be?
Roblox allows 20,000 triangles per mesh (specifications), but a tree you'll place hundreds of times should be far below that:
- Background trees: tens to a few hundred triangles. Low-poly cones and blobs read fine at distance.
- Trees players walk past: a few hundred to around 1,500.
- A single hero tree in a plaza: more, if it's a landmark.

Raw scans and raw AI output are often far denser than this. Run them through retopology or decimation first. Our triangle limit guide covers both.
Settings that matter for every tree
Select all your trees and set these once:
- CanCollide off on leaves. Players shouldn't bump into a canopy. Keep a simple collision on the trunk only, or use an invisible cylinder part.
- CollisionFidelity = Box on anything that still collides. Box has the lowest memory overhead (performance guide).
- CanTouch and CanQuery off if nothing needs to detect the tree.
- CastShadow off on small bushes and distant trees, where shadows aren't visible anyway.
- RenderFidelity = Automatic, so distant trees use simpler versions (meshes).
Variety without new meshes
Three or four tree meshes can look like a varied forest:
- Rotate each copy randomly around the Y axis.
- Scale copies by 80 to 120%.
- Tint the leaves. With
SurfaceAppearanceand a tint mask, one texture can give green, autumn orange and snowy variants. - Mix sizes. A few tall pines among short bushes reads as natural.
A small plugin or a few lines in the command bar can scatter copies with random rotation and scale.
Style: match the rest of your map
Trees take up a lot of screen, so they set the look of a map more than almost anything else. Pick one style, such as faceted low-poly, rounded cartoon or semi-realistic, and make every tree in it. A low-poly texture palette keeps colours consistent across trees, rocks and buildings.
Building a forest
Once you have your trees, a forest is about placement: dense clusters, clearings for gameplay, paths that guide players, and fog to hide where the forest ends. The forest map guide goes through it, and low-poly maps covers the wider look.
Make tree meshes in Vi3W
Describe the tree ("low-poly pine tree, faceted, three layers of branches, flat green") or upload a sketch. Vi3W generates a textured mesh, retopologises it to a lighter version, and exports GLB, FBX or OBJ. Make each species once, then reuse it in Studio. Check the triangle count before importing, especially for trees you'll place hundreds of times. Make a tree in Vi3W.
Last reviewed

