Guides
How big can a Roblox game be? Size and memory limits
The size limits that apply to Roblox games: per-mesh and texture caps, distance limits, device memory, and how big games stay playable.
2 min read

Quick answer
Is there a size limit for Roblox games?
The limits that matter are per asset and per device, not one total game size. Each mesh is capped at 20,000 triangles, textures at 4096×4096, and pathfinding at 3,000 studs per path. The real ceiling is memory on players' phones, which is why big games use StreamingEnabled, reused assets and multiple places.
The hard limits you'll actually hit
These are published per asset or per system, not as one "game size" number:
- Triangles per mesh: Value: 20,000; Source: Mesh specifications
- Texture size: Value: Up to 4096×4096; Source: Texture specifications
- Solid-modelling result: Value: Simplified above 20,000 triangles; Source: Solid modeling
- Pathfinding request: Value: Straight-line distance up to 3,000 studs; Source: Pathfinding
- Heightmap import: Value: 4096×4096 pixels, 4 studs per pixel; Source: Terrain
- Avatar items: Value: 4,000 triangles; 2048×2048 textures; Source: Accessory specifications
Roblox's performance docs don't publish a single cap on how many parts or how much content a place can hold. If you find a figure quoted as "the Roblox game size limit", check where it comes from.
The real limit: players' devices
What stops big games is memory and performance on phones. Every unique mesh, texture and sound has to fit in memory on the player's device. A map that loads fine on your PC can crash a phone.
How big games stay playable:
- StreamingEnabled, so devices only hold what's near the player. The default target radius is 1,024 studs (streaming). See StreamingEnabled.
- Reused assets. A few hundred unique meshes reused thousands of times, not thousands of unique ones (performance guide).
- Sensible textures. Most props at 512 or below (texture size).

Very large worlds
- Floating-point precision. Far from the origin, positions lose precision and physics can jitter. Keep the play area reasonably close to 0, 0, 0.
- Multiple places. A game (experience) can contain several places, and players teleport between them. Big games split into a hub and separate worlds, so each place stays small.
- Distance and travel. Huge maps feel empty and take forever to cross. Most successful games are smaller than they look.
Practical sizes
There's no rule, but as a rough guide: a 1,000 by 1,000 stud map is plenty for most games. Survival and open-world games go bigger with streaming. Obbies and arenas go much smaller. Measure your map against how long it takes to walk across. More than a couple of minutes needs a reason.
Keep each asset small
Most "my game is too big" problems are really "my assets are too heavy". Vi3W retopologises every model from high poly to low poly before export (GLB, FBX or OBJ). Reuse each mesh, and check triangle counts before importing. Make light props in Vi3W.
Last reviewed

