Set the face count after you see the form.

Why the prompt is the wrong place for a count

A sentence can name an object and a material. It cannot reliably name 12,000 triangles. Asking for a count in the prompt and then regenerating until it lands is slower than setting the budget once.

Generate until the silhouette is right. Remesh after that. The two decisions stay separate, which is why a bad material is a texture problem and a heavy mesh is a remesh problem.

Quad or triangle

Quads are the better handoff when someone will keep sculpting or retopologizing. Triangles are the better handoff for a real-time scene and for a print.

Either result is meant to hold the shape you already approved. If the silhouette changes, the budget is too low for that object. Raise it. Do not regenerate the prompt to get the density back.

Match the budget to the job

A background prop can be lighter than a hero asset. A print cares more about a closed surface than about a low count. An engine scene cares about the count.

Smart Remesh is on Pro. It does not include a skeleton. If the asset has to walk, the next step is auto-rig on Studio, after the density is settled.

Limits to check before delivery

A face budget is a target, not a guarantee of deformation quality. glTF export triangulates quads, and UV seams can increase exported vertex counts. Assess the exported mesh rather than equating the editing count with runtime cost.

• Blender Manual — glTF 2.0 import and export
• Khronos — glTF 2.0 specification

Handoff checklist

Save the original mesh. Compare silhouette and small features at the intended camera distance after remeshing. Check UVs, shading, open boundaries, and the imported triangle count. For a character, test bent joints before accepting the new topology.