Step-by-step game asset guide

How to Optimise a 3D Model for Web and Games

Reduce triangles, texture memory and scene complexity without destroying the silhouette, materials or animation your asset actually needs.

Updated 27 August 2026 · Reviewed against the current FORM 3D workflow

Typical time: 20–40 minutes
Reading time: 10 minute read
Difficulty: Beginner–intermediate
Result: A lighter asset with measured geometry and texture budgets

What this guide covers

Optimisation is the removal of cost that does not improve the intended result. Blindly reducing every mesh can damage silhouettes, animation and shading, while leaving oversized textures untouched may save almost no download or GPU memory.

Measure geometry, texture pixels, object count and animation complexity separately. The correct budget depends on camera distance, number of simultaneous assets, target hardware and whether the model is a background prop or a hero object.

Before you begin

A representative finished or nearly finished asset
The expected camera distance and target device class
A saved editable project before destructive optimisation

Start with the performance target

Web landing visual: fast download and modest GPU memory matter heavily.
Mobile game: triangle count, overdraw, textures and number of visible objects all matter.
Desktop hero asset: more detail may be justified, but it should still be visible at the target distance.
Animated character: deformation topology and bone count constrain safe simplification.

Audit geometry before reducing it

Open the Edit mesh summary and record the triangle count.
Inspect the asset at its actual gameplay or page display size.
Identify dense areas that do not affect the silhouette.
Check whether subdivision was added where a material or normal change would be enough.
Keep deformation topology stable while skins or Shape States are attached.

Reduce object and hierarchy overhead

Many tiny nodes increase update, traversal and draw-management overhead even when each mesh is simple. Do not merge parts that animate independently, but avoid creating separate objects for detail that could be represented in one texture or surface.

Keep moving parts separate.
Group related pieces with meaningful names.
Use one greedy-meshed voxel surface instead of one cube per cell.
Delete hidden experiments and duplicate reference objects before export.

Control texture memory

Texture GPU memory is related to pixel dimensions, not only compressed file size. A 1024 × 1024 RGBA texture contains four times as many pixels as a 512 × 512 texture. Use the smallest resolution that holds visible information.

Use 256 px for small props and simple colour marks.
Use 512 px for normal game props and moderate logo detail.
Use 1024 px only for close inspection or information that visibly needs it.
Remove painted detail that is invisible at the intended camera distance.
Check transparency because blended surfaces can create overdraw cost.

Use safe optimisation before aggressive changes

Save the editable project.
Open Export and record the current report.
Run Safe optimisation and compare geometry, palette and texture totals.
Inspect the silhouette, shading and paint.
Try Strong optimisation only on a copy or with undo available.
Export both versions for measured engine or web testing when the difference is uncertain.

Measure the result in context

Compare download size and first-load time on a realistic connection.
Measure frame time with the expected number of simultaneous assets.
Inspect texture memory and draw calls in the target runtime.
Test on the slowest supported device, not only a development workstation.
Keep the higher-quality source even when a lighter runtime export wins.

Frequently asked questions

What is a good triangle count for a web 3D model?

There is no single safe number. A lightweight scene of simple props differs from one full-screen animated model. Start from the visual requirement, measure on target devices and reduce geometry that does not change the visible result.

Does reducing GLB file size always improve rendering speed?

No. Download size affects loading, while triangles, materials, texture pixels, transparency, animation and object count affect runtime cost. Compression can reduce transfer size without reducing GPU work.

Should every texture be 1024 px?

No. Use 1024 only when the asset is shown close enough to reveal that information. Smaller props often look identical with 256 or 512 px textures and use much less memory.

Apply this workflow in the editor

Your project remains editable and stored locally on this device.

Open the studio