Guides
Why your Roblox game is laggy, and how to fix it
Fix Roblox game lag by cause: rendering, memory, physics, scripts and network. How to diagnose each and the fixes that make the biggest difference.
3 min read

Quick answer
How do you make a Roblox game less laggy?
Find which kind of lag you have first: low frame rate (rendering), slow loading or crashes (memory), or rubber-banding (network or scripts). Then fix the cause: reuse meshes and textures, shrink oversized textures, simplify collision, turn on StreamingEnabled, run code less often, and send less data through remotes.
Step 1: Work out which lag you have
- Low frame rate, choppy camera: Rendering: too many draw calls, heavy meshes, shadows, transparency
- Long loading, crashes on phones: Memory: big textures, many unique meshes, huge maps
- Players teleport or rubber-band: Network or server: too much remote traffic, heavy server scripts
- Stutters when things happen: Scripts: work running every frame, or big tasks in one go
Studio's Developer Console (F9) and MicroProfiler show where time and memory go. Check on a real phone, not just your PC.
Rendering fixes
From Roblox's performance guide:
- Reuse meshes. Identical meshes sharing the same mesh content can batch into one draw call. Upload once and duplicate in Studio. Importing a whole map can create separate copies that don't batch. See draw calls.
- Use RenderFidelity Automatic or Performance, not Precise, so distant meshes simplify (LOD guide).
- Turn off CastShadow on small parts, especially distant ones.
- Avoid overlapping transparency. Stacked semi-transparent objects draw pixels many times.

Memory fixes
- Shrink textures. Memory depends on pixel count: a 1024×1024 texture uses four times the memory of a 512×512 one, and most minor images should be under 256×256 (performance guide). See texture size.
- Tint instead of duplicating textures for colour variants.
- Fewer unique meshes. A forest of three reused trees beats a forest of fifty different ones.
- Turn on StreamingEnabled so phones only hold nearby content (StreamingEnabled).
Physics fixes
- Box collision has the lowest memory overhead. Use it on small anchored parts (collision fidelity).
- Turn off
CanCollide,CanTouchandCanQueryon decoration. - Anchor everything that doesn't need to move.
- Avoid PreciseConvexDecomposition except where shape truly matters.
Script fixes
- Run code on RunService events sparingly. Move work that doesn't need every frame to slower loops.
- Spread big jobs over frames with
task.wait(). - Use multithreading for heavy work that doesn't need the data model.
- Clean up connections and objects you no longer need.
Network fixes
- Don't send big data through remotes all at once.
- Send changes, not every frame. Replicate state when it changes.
- Tween on the client. Server-side tweens replicate every frame and cause jitter.
Don't forget the assets themselves
Heavy, messy meshes are a common hidden cause. Raw scans and raw AI output can be tens of thousands of triangles for a simple prop. Our optimise Roblox meshes and triangle limit guides cover reducing them.
Start with lighter meshes
Vi3W retopologises every model from high poly to low poly before you export GLB, FBX or OBJ, so props start lighter than raw generator output. Check the triangle count before importing, and reuse each mesh. Make light props in Vi3W.
Last reviewed

