How to make a low poly 3D model

There are two ways to make a low poly 3D model: build it with a deliberate low-detail style, or simplify an existing mesh to meet a performance target. Decide which problem you are solving before choosing a tool.

A faceted illustration may need careful control of shape and shading. A scanned object for a web viewer may mainly need fewer triangles and smaller textures. Both can be called low poly, but their workflows differ.

What counts as low poly?

There is no universal triangle threshold. The useful budget depends on the asset's screen size, how many copies appear together, its materials, and the device rendering the scene.

Count triangles in the exported model rather than assuming the face count in your modeling application will match. Also record vertices separately: UV seams and shading boundaries can require separate vertex data, so a fixed triangle-to-vertex conversion is unreliable.

For performance planning, use the polygon budgets by platform guide to build a target from scene measurements.

Path 1: model the low poly shape from scratch

This approach gives you control over where detail is spent. In a modeling tool such as Blender, start with a few primitives and check the object from the camera angles that matter.

1. Block out the silhouette. Get the proportions readable before adding small features.
2. Add geometry where it changes the visible shape. Keep loops around important curves, joints, and openings.
3. Choose the shading intentionally. Flat shading exposes facets; smooth shading can suit a low-triangle model too.
4. Plan deformation if the object will animate. Elbows and other bending regions need topology that works in motion.
5. Export a test early. Check scale, orientation, materials, and appearance in the destination application.

Subdivision, sculpting, and retopology can also be part of the process. The useful question is whether the final exported topology supports the intended look and behavior.

Path 2: reduce an existing model

Simplification is useful when a model already has the right shape but carries more detail than the destination needs. Keep the original file, then work on a copy.

For a browser workflow, open the polygon reducer:

1. Load a supported model and record its starting triangle count.
2. Set a modest reduction or a triangle target where available.
3. Compare the original and reduced previews at the intended camera distance.
4. Export a separate file and check the result in your target application.

Do not assume that every importer and exporter preserves every material, rig, or animation feature. A model that looks correct in one static pose still needs testing through its required animation clips.

Understand reduction percentages

“Remove 30%” and “keep 30%” are different instructions. Starting with 200,000 triangles:

• A 30% reduction targets 140,000 remaining triangles.
• Keeping 30% targets 60,000 remaining triangles, a 70% reduction.

Treat these as targets and verify the actual exported count. There is no reliable universal percentage at which organic or hard-surface models become unusable. Thin parts, holes, material boundaries, and curved outlines can reach their visual limit at different settings.

If simplification breaks essential topology, use a gentler setting or rebuild that area manually.

Check more than the triangle count

Open the exported asset in the polygon inspector and compare its counts with your baseline. Then use the 3D viewer to inspect silhouettes, shading, seams, transparency, and small details.

Finish the check in the destination engine or application. Test the real camera distance, animations, materials, and scene lighting. If the problem is download size, geometry may be only part of it: the GLB file-size guide explains how textures and compression affect the result.

Add levels of detail when the scene needs them

A close-up mesh and a distant mesh do not always need the same detail. LOD systems select less detailed representations when appropriate, but the number of levels and switching thresholds depend on the project. Godot's mesh LOD documentation gives an example of automatic generation and screen-space selection.

Use the LOD tool when preparing alternate meshes fits your workflow. Check transitions in the destination application and measure whether they improve frame time. The goal is a model that looks right and works within your scene's budget, with its important features intact.