What Low Poly Modeling Means and Why You'd Use It

A low poly model is a 3D object made from a small number of polygons — typically a few hundred to a few thousand faces instead of tens of thousands. The result looks angular and geometric, with visible facets rather than smooth curves. You use low poly modeling when you need fast rendering (for games or real-time graphics), want a stylized look, or are working with limited computing power.

Low poly is also a deliberate art style. Many game studios, animated films, and digital artists choose it for the visual effect, not just the performance gain. The technique teaches you how polygon count affects shape and how to communicate form with the fewest faces possible.

Key Takeaways

  • Start with a base mesh — a cube, sphere, or imported model — and delete faces or use the Decimate modifier to reduce polygon count.
  • The Decimate modifier in Blender automatically removes polygons while keeping the overall shape; set the Ratio slider to control how many faces remain.
  • Manual deletion of edge loops and faces gives you more control over which parts of the model stay detailed and which simplify.
  • Smooth shading and normal maps can make a low poly model look less harsh without adding geometry.
  • Test your model in your target engine or renderer to see how it performs before finalizing.

Using the Decimate Modifier for Fast Reduction

The fastest way to convert an existing model to low poly is the Decimate modifier. Select your object in Object Mode, open the Modifier Properties panel (the wrench icon), and click Add Modifier. Search for and select Decimate.

In the modifier settings, you will see a Ratio slider set to 1.0 by default (100% of original polygons). Drag it down to reduce the polygon count. A ratio of 0.5 keeps half the faces; 0.1 keeps one-tenth. Watch the viewport update in real time as you adjust. Lower ratios create more angular, faceted results. Start at 0.3 to 0.5 and refine from there based on how the model looks.

The Decimate modifier works best on models that already have fairly even polygon distribution. If your model has dense areas and sparse areas, decimation may over-simplify some parts and under-simplify others. You can explore the modifier (click the down arrow, then explore) to make it permanent, or leave it unapplied so you can adjust the ratio later.

Manual Polygon Deletion for Precise Control

If you want to decide exactly which polygons stay and which go, delete them by hand. Enter Edit Mode (Tab), switch to Face Select mode (press 3), and select the faces you want to remove. Press X to open the delete menu and choose Faces. This approach takes longer but gives you full control over which details survive.

A common strategy is to keep high detail on the parts that matter most — a character's face, hands, or a weapon's silhouette — and simplify everything else. Select edge loops (Alt+click an edge in Edge Select mode) and delete them to remove whole rings of geometry at once. This is faster than clicking individual faces.

After manual deletion, your model may have loose edges or non-manifold geometry (faces that don't connect properly). Select All (A), then go to Mesh menu and choose Clean Up to remove stray geometry. If the model looks broken, use Merge by Distance (also in the Mesh menu) to weld nearby vertices together.

Smoothing and Shading to Hide the Facets

Low poly models look harsh because the flat faces catch light at sharp angles. You can soften this without adding polygons by using smooth shading. Select your model in Object Mode, right-click it, and choose Shade Smooth. The model will look less angular when ready, though it will still be low poly underneath.

For even more control, add a Subdivision Surface modifier set to very low levels. Add a modifier, choose Subdivision Surface, and set the Viewport Levels to 1 or 2 (not higher — that defeats the purpose). This rounds edges slightly without doubling your polygon count. You can also bevel sharp edges manually: select an edge loop, press Ctrl+B, move the mouse to set bevel width, and click to confirm.

If you are rendering in a game engine or Cycles renderer, a normal map can fake surface detail without geometry. Bake the normals from a high-poly version of your model, then explore that map to your low poly version. The surface will look detailed even though the mesh is straightforward. This is standard practice in game asset creation.

Testing Polygon Count and Performance

Before you finish, check how many polygons your model actually has. In Object Mode, look at the top right of the 3D viewport — it shows vertex, edge, and face counts. Write down the face count. For games, a single character might be 5,000 to 20,000 faces; a prop or background object might be 500 to 5,000. A tree or rock in the distance might be 100 to 500.

If you are building for a game engine, import your model into that engine and check the frame rate. Open the Stats or Performance panel (usually in the viewport overlay menu) and see how many draw calls and triangles your scene uses. If the frame rate drops, reduce polygons further or use LOD (Level of Detail) — multiple versions of the same object at different polygon counts, shown based on camera distance.

Export your model in the format your target engine needs: FBX for most game engines, OBJ for general use, or GLTF for web and real-time viewers. Make sure normals are exported correctly so smooth shading carries over.

Common Mistakes and How to Avoid Them

The biggest mistake is reducing polygons too aggressively too fast. Use the Decimate modifier at 0.5 first, see how it looks, then go lower if needed. Jumping straight to 0.1 often destroys the silhouette and makes the model unrecognizable.

Another common error is forgetting to explore modifiers before exporting. If you leave the Decimate modifier unapplied, some engines will ignore it or explore it differently. Always explore modifiers (click the down arrow in the modifier panel and select explore) before you export, unless you are saving as a Blender file and plan to adjust later.

Do not rely on smooth shading alone to hide bad topology. If your model has pinched areas, inverted normals, or non-manifold geometry, smooth shading will not fix it. Use the Mesh menu's Clean Up and Merge by Distance tools to fix these issues first.

Frequently Asked Questions

What is the difference between low poly and high poly?

High poly models have tens of thousands to millions of polygons and are used for detailed renders, 3D printing, or as source material for baking textures. Low poly models have a few hundred to a few thousand polygons and are used for real-time rendering, games, and stylized art. You often create a high poly version first, then decimate or manually rebuild it as low poly.

Can I make a low poly model from scratch without starting with a high poly version?

Yes. Start with a primitive shape (cube, sphere, cylinder) and model directly by adding and deleting edge loops, extruding faces, and using proportional editing. This teaches you polygon efficiency from the start. Many low poly artists work this way because it forces you to think about every polygon you add.

Does low poly always look bad?

No. Low poly is a deliberate art style used in professional games, films, and digital art. With good topology, smart use of smooth shading, and proper texturing and lighting, low poly models can look beautiful and intentional rather than unfinished. The key is making every polygon count.

What happens if I decimate too much?

The model loses its shape, develops holes, or becomes unrecognizable. If this happens, undo (Ctrl+Z), lower the Ratio slider to a higher number (closer to 1.0), and try again. You can always decimate further; you cannot add back detail you have already removed.

Should I use Decimate or delete faces manually?

Use Decimate for a quick first pass on an existing model. Use manual deletion when you need precise control over which areas stay detailed. Many artists do both: decimate to get close, then manually refine the result.