STL mesh files
Using triangle meshes with explicit scale, tessellation, topology and manufacturing checks.
Tags: parts-and-design, file-formats, meshes
On this page
STL exchanges triangular facets. A smooth CAD surface becomes a polygonal approximation, and a successful import still needs scale and closure checks.
Autodesk's Alias 2016 STL-import documentation explicitly identifies STL as unitless and tells users to establish the construction units before import. An exporter can write coordinates scaled for millimeters or inches, but the receiving workflow still needs the intended interpretation. An export dialog's unit selection should not be mistaken for a standard unit declaration embedded in STL. Autodesk Alias 2016, STL import options
The Library of Congress describes two STL encodings, ASCII and binary, with each facet carrying its vertex coordinates and outward normal. Its description also explains outward-facing counterclockwise vertex order, following the right-hand rule. Both encodings represent facets; choosing binary instead of ASCII does not inherently improve geometric fidelity. Library of Congress, STL format family, updated 25 February 2025
What STL does and does not preserve
STL transfers a tessellated boundary. A mathematically smooth CAD cylinder becomes planar triangles, so downstream software no longer receives that original analytic cylinder merely because the mesh looks round. Keep the native or another agreed geometric source when future editing, exact analytic surfaces or feature relationships matter.
Ordinary STL is not a dependable container for material assignments, textures or a complete assembly definition. The Library of Congress notes that original STL lacks color support and that binary color extensions use conflicting conventions. Do not rely on an attribute-byte color convention unless both applications explicitly agree on it. Library of Congress, Binary STL
| Need | Required handoff check |
|---|---|
| Correct shape | Compare the mesh with the intended source geometry |
| Correct scale | State units and measure a known reference dimension |
| Intended parts | Check disconnected shells and component inclusion |
| Material/process | Supply the agreed manufacturing specification separately |
| Repeatable build | Retain the appropriate build/project settings, not only STL |
One STL can contain multiple disconnected shells. That does not necessarily mean they are a mechanically joined part or a recognized assembly. Agree whether the delivery is one printable object, several separate objects or nested geometry intended to form a hollow part.
Units must be agreed
Verify overall bounds and at least one critical dimension after import. If a 2-inch edge is interpreted as 2 mm rather than 50.8 mm, the linear scale is wrong by a factor of 25.4. An automatic “fit to build plate” operation changes size for placement; it does not demonstrate restoration of intended units. Preserve the agreed orientation and origin where separate files must register with one another.
Tessellation settings are an approximation budget
SOLIDWORKS's export explanation distinguishes linear deviation—the permitted distance of facets from source geometry—from angular deviation between neighboring triangles. It notes that coarse tessellation can produce visible faceting while excessive refinement increases file size and processing burden. Record actual settings and units; “Fine” is a software preset, not a universal numerical specification. SOLIDWORKS, Preparing Models for 3D Printing
A tighter mesh does not make the printer equally accurate. Allocate tessellation error with the complete manufacturing and inspection requirements, including process distortion, finishing and measurement uncertainty. Do not set a mesh deviation equal to the entire available part tolerance and assume the remaining process contributes no error.
Original circular-section example: approximate a 10 mm-radius circle with a regular inscribed polygon. The maximum radial chord error is e = R × (1 − cos(π/n)), where n is the number of equal segments around the circumference.
| Segments around the circle | Maximum radial chord error |
|---|---|
| 36 | 0.03805 mm |
| 72 | 0.00952 mm |
Doubling the segment count reduces this example's error by approximately fourfold. This is an ideal cross-sectional calculation, not a complete triangle count or an STL export recommendation. Real surfaces, uneven tessellation, axial subdivisions and angular/edge-length controls can change the mesh. A “round” rendered view may hide facets that remain in the geometry.
Binary layout and file-size screening
The Library of Congress describes standard binary STL as an 80-byte header, a 4-byte triangle count and 50 bytes per triangle. The triangle record contains twelve 32-bit floating-point values—normal and three vertices—plus a two-byte attribute field. Library of Congress, Binary STL, updated 25 February 2025
For that layout, original arithmetic gives file bytes = 84 + 50 × triangle count. A 100,000-triangle file occupies 5,000,084 bytes, approximately 5.00 MB using decimal megabytes. A length/count inconsistency is a reason to investigate truncation, malformed content or a nonstandard writer. Matching the formula only checks this structural relationship; it does not establish valid coordinates, topology or design accuracy.
Mesh validity and repair
For a solid object, check closed boundaries, consistent orientation, degenerate triangles, duplicate/internal faces, non-manifold connections and self-intersections. A through-hole in a valid solid still has a continuous boundary around its bore; it is not the same as an accidental gap in the mesh surface. Hollow parts likewise require intentional inner surfaces rather than arbitrary missing triangles.
Stratasys Direct's STL-preparation guidance calls for continuous, watertight models and fixing gaps before export. Its instructions cover several CAD systems, including older versions, so use the geometric principle without assuming every listed menu path matches an installed release. Stratasys Direct, How to Prepare STL Files
Prusa explains that slicers can repair some defects automatically but cannot repair every corrupted model. Its repair guidance also warns of resolution loss with a make-solid operation. Preserve the original and compare the repaired result: closing a hole, removing a shell or rebuilding a surface can erase an intentional feature. A warning disappearing is not proof of equivalence to the source design. Prusa, Corrupted 3D models for printing
Release to manufacturing
Before release, use a short receiving check:
- Confirm source revision, intended units, encoding and tessellation settings.
- Reopen the delivered STL and measure size, placement and critical geometry.
- Check shell count, topology and the effect of any repairs or simplification.
- Review the sliced/toolpath representation for missing walls, unintended fills and unsupported regions.
- Apply process-specific design and inspection requirements to the finished part.
Watertightness does not guarantee minimum wall thickness, powder/resin drainage, support access or service strength. Similarly, STL is not G-code and does not identify every printer setting. If a recipient needs materials, object relationships or build settings, agree a supported richer format or project delivery. Prusa's 3MF discussion illustrates that its project workflow can retain setup information that a simple STL cannot. Do not assume all applications consume the same project extensions. Prusa, 3MF file format and why it is useful
Source versions
Both Library of Congress descriptions identify 25 February 2025 as their last significant update and label themselves preliminary format descriptions. They are not new STL specification editions. The cited Autodesk page is explicitly Alias 2016. The other cited manufacturer pages do not state a technical revision edition; no legacy menu path or example setting above is presented as a universal current workflow.