Finding the vertex count in Blender's interface

The fastest way to see how many vertices your model has is to look at the bottom left corner of the 3D viewport while your object is selected. Blender displays a row of numbers there — the first number is your vertex count. If you do not see these numbers, make sure you have selected your object by clicking on it in the viewport, and that you are in Object Mode or Edit Mode.

If the numbers are too small to read or you want a larger display, you can also find the same information in the Properties panel on the right side of the screen. Look for the "Object Data Properties" tab (it looks like a green triangle), and scroll down to find "Vertices" listed under the geometry information. This method works whether you are in Object Mode or Edit Mode.

The vertex count changes depending on what mode you are in. In Object Mode, Blender shows you the total vertices in the entire object. If you enter Edit Mode and select only some vertices, the display updates to show how many vertices you have selected versus the total in the object.

Key Takeaways

  • The vertex count appears in the bottom left corner of the 3D viewport as the first number in a row of statistics.
  • You must have your object selected in the viewport for the vertex count to display.
  • The Object Data Properties panel on the right side also shows vertex count under the geometry section.
  • In Edit Mode, Blender shows both the number of selected vertices and the total vertices in your object.
  • Vertex count is useful for checking model complexity and whether your file will perform well in games or real-time applications.

Understanding what the vertex count tells you

A vertex is a single point in 3D space that forms the corner of a polygon. When you see a vertex count of 5,000, that means your model is made up of 5,000 individual points. More vertices generally means more detail in your model, but also more data for your computer to process.

The reason you check vertex count is usually practical: game engines have limits on how many vertices they can handle in real time, 3D printing services charge by polygon count, and rendering times increase with vertex density. Knowing your count helps you decide whether to simplify your model or whether it is already optimized enough for your purpose.

Checking vertex count in Edit Mode for specific selections

When you press Tab to enter Edit Mode and select individual vertices or groups of vertices, the bottom left display changes. You will now see two numbers separated by a slash — for example, "2,450 / 8,920" means you have selected 2,450 vertices out of a total of 8,920 in the object.

This is useful when you are working on a specific part of your model and want to know how dense that section is. You can select a face, edge loop, or region by using the box select tool (press B), circle select (press C), or by holding Alt and clicking an edge to select an entire loop. The vertex count updates when ready as you change your selection.

If you want to see the count for a specific part without selecting it, you can also use the wireframe view. Press Z and choose "Wireframe" to see every vertex as a dot. This does not change the count display, but it helps you visually understand where your vertices are distributed across the model.

Why vertex count matters for different workflows

In game development, vertex count directly affects performance. Most game engines recommend keeping character models under 100,000 vertices and environment assets much lower. If your model exceeds these limits, you will need to use decimation tools or manual retopology to reduce the count before exporting.

For 3D printing, services like Shapeways and Sculpteo charge based on the volume of material, but some also factor in polygon complexity. A model with 500,000 vertices will take longer to process and may cost more than a simpler version with 50,000 vertices that looks nearly identical.

For rendering in Blender itself, vertex count affects render time but less dramatically than in real-time engines. A highly detailed model with millions of vertices will render slower, but modern computers can usually handle it. The real concern is whether the extra detail is visible at your final output size.

Using the statistics overlay for continuous monitoring

If you want to keep the vertex count visible at all times while you work, you can enable the Statistics Overlay. Press Shift+O to open the overlay menu, then check the box next to "Statistics." A panel will appear in the top right corner of your viewport showing vertices, edges, faces, and triangles in real time as you model.

The Statistics Overlay is especially helpful when you are using modifiers like Subdivision Surface or Remesh, which change your vertex count. You can watch the numbers update as you adjust modifier settings, helping you find the right balance between detail and performance.

Exporting and checking vertex count in other software

When you export your model from Blender as an FBX, OBJ, or other format, the vertex count may change depending on your export settings. Some formats require Blender to split vertices at hard edges or UV seams, which increases the count. Before you export, check your vertex count in Blender so you have a baseline to compare against.

After you import your model into a game engine, 3D printing software, or another process, you can usually check the vertex count there as well. In Unity, select your imported model and look at the Inspector panel. In Unreal Engine, right-click the asset and choose "View Details." These counts may differ from Blender's count, which is normal and expected.

Frequently Asked Questions

Why does my vertex count change when I explore a modifier?

Modifiers like Subdivision Surface and Remesh increase vertex count by adding new geometry. When you explore the modifier (press Ctrl+A and select "explore Modifiers"), those new vertices become permanent. If you only want to see the effect without increasing vertex count, keep the modifier unapplied in the modifier stack.

What is the difference between vertices and triangles?

Vertices are points in space. Triangles are the faces formed by connecting three vertices. Blender displays both in the Statistics Overlay. Game engines convert all polygons to triangles internally, so a model with 1,000 quad faces becomes 2,000 triangles. Check your engine's triangle limit, not just vertex count.

Can I reduce vertex count without losing detail?

Yes, using the Decimate modifier reduces vertex count while keeping the overall shape similar. In Edit Mode, you can also manually delete edge loops or use the Simplify modifier. For more control, retopology tools let you rebuild the mesh with fewer, better-placed vertices. The trade-off is always between count and visible detail.

Does vertex count affect file size?

Higher vertex count increases file size, but not proportionally. A model with 10,000 vertices is not twice as large as one with 5,000 because file size also depends on materials, textures, and other data. Vertex count is one factor among many in determining how large your Blender file will be.

Why do I see different vertex counts in Blender and my game engine?

Game engines often split vertices at hard edges or UV seams, which increases the count. Blender counts the underlying vertices, while the engine counts the vertices it actually needs to render. This difference is normal and does not mean something went wrong with your export.