STL Resolution & Tessellation: How Much Detail Do You Need?
Every STL generator and CAD exporter gives you some way to control detail — a resolution slider, a segment count, a "fine / coarse" toggle. Crank it up and your sphere looks glassy-smooth; the file balloons to megabytes. Crank it down and the file is tiny, but the curve turns into a faceted gemstone. This guide explains what that control actually does, why more is not automatically better, and how to pick a setting that prints smoothly without wasting space.
What tessellation actually is
An STL file stores geometry as flat triangles and nothing else — it has no concept of a true curve. So when you export a sphere, a cylinder, or any rounded surface, that smooth shape has to be approximated by a shell of tiny flat faces. Breaking a curved surface into triangles like this is called tessellation, and "resolution" (or segment count) is simply how many triangles you spend doing it.
Picture a circle drawn as a polygon. With 8 sides it is an obvious octagon; with 24 sides it starts to look round; with 96 sides your eye can no longer pick out the individual edges. A sphere works the same way in three dimensions: more segments around and over its surface mean more, smaller triangles, and a silhouette that reads as a smooth curve instead of a stack of flat panels.
The core trade-off
Resolution is a balancing act, and both extremes have a real cost:
- Too few facets — you get visible faceting: flat panels and hard edges where the surface should be smooth. On a printed part this shows up as obvious facets on rounded corners, cylinders that look like prisms, and a generally "low-poly" appearance.
- Too many facets — the surface looks lovely on screen, but the file size climbs fast (each triangle costs 50 bytes in a binary STL), the slicer takes longer to load and process the mesh, and very dense models can chew through memory or even choke older slicers and printers.
The temptation is to slam the slider to maximum "just to be safe." That habit produces 100 MB STLs of simple objects that print identically to a version a fraction of the size. The interesting question is not "how smooth can I make it?" but "how smooth does it actually need to be?"
The key insight: resolution only matters up to a point
Here is the part most beginners miss. Extra triangles only help while each triangle is still big enough to see. Once your facets are smaller than what the printer — and your eye — can resolve, every additional triangle adds file size for exactly zero visible benefit.
A desktop FDM printer lays down plastic through a nozzle that is typically about
0.4 mm wide, in layers often 0.1–0.2 mm tall. That is the
real floor on detail: the machine physically cannot reproduce a feature finer than its nozzle and
layer height. If your tessellation is already producing triangle edges shorter than the layer
height, the printer simply averages them away. You have paid for smoothness the hardware throws
out.
Print scale matters just as much, because faceting is about the size of each triangle, not the number of them. Consider two parts:
- A 4 mm bead with a curved surface. Its whole circumference is only a few millimetres, so even a modest segment count puts the facets well below the nozzle width. Smooth, and tiny.
- A 200 mm vase with the same curve. Now that same segment count stretches each triangle across centimetres of surface, and the flat panels become plainly visible. A large, gently curved part viewed up close is exactly where you need more resolution.
Practical guidance
For the large majority of prints, a moderate resolution is plenty. Most functional parts, brackets, and small decorative objects look perfectly smooth well short of the maximum setting. Reach for higher resolution only when all three of these are true at once:
- the part is large, so triangles stretch across a big surface;
- the surface is smoothly and gently curved (broad domes and sweeps show faceting far more than tight fillets do); and
- it will be viewed up close as a display piece rather than a hidden mechanical component.
The best habit is to stop guessing and watch the numbers. When you adjust the resolution control here, the readout shows the live triangle count and the estimated STL file size updating in real time. If pushing the slider higher barely changes the preview but doubles the triangle count, you have passed the point of useful detail — back it off.
Chord height: how CAD does it "properly"
A raw segment count is the simple way to think about resolution, but it is a blunt instrument: the same count over-tessellates small features and under-tessellates large ones. Professional CAD exporters use a smarter, geometry-aware control instead, usually labelled chord height (also called deviation or tolerance).
Chord height sets the maximum allowed gap between the flat triangle and the true curved surface
it is replacing — literally how far the chord sags away from the arc. You specify a tolerance
like 0.05 mm, and the exporter automatically uses more triangles on tight curves
and fewer on gentle ones to keep that gap satisfied everywhere. Because the tolerance is in real
millimetres, it scales correctly: the same chord-height setting gives the bead and the vase each
the detail it actually needs. A sensible deviation for FDM printing is roughly a fraction of your
layer height; chasing values far below that just inflates the mesh.
See the trade-off live
Pick a curved shape, drag the resolution slider, and watch the triangle count and estimated STL size change as you go. It is the fastest way to build a feel for "enough detail" — free, in your browser, nothing to install.
Open the STL generator →Frequently asked questions
Does higher STL resolution make a stronger print?
No. Resolution only affects how smooth the surface looks; it does not change the object's strength, which comes from wall thickness, infill, and material. For load-bearing parts, focus on wall thickness rather than triangle count.
Why is my STL file so huge?
Almost always because the resolution was set far higher than the print needs — file size scales directly with triangle count (about 50 bytes per triangle in a binary STL). Lower the resolution until the on-screen preview just starts to show faceting, then nudge it back up a step. You will often cut the file by 80 percent with no visible difference.
Can too many triangles cause print problems?
Indirectly, yes. Extremely dense meshes slow slicing, use more memory, and on weaker hardware can crash the slicer or stutter the print. Excess triangles also make it harder for repair tools to keep a mesh water-tight and manifold. Sensible resolution avoids all of that.