3D printing accuracy starts before the printer, it starts at tessellation

How 3D printing software can handle CAD-to-mesh conversion without losing accuracy

Here's something worth thinking about if you build 3D printing software: the STL file format has been the industry's default exchange format since 1987. It's older than the World Wide Web. And while it's lasted this long for good reasons — simplicity, universal support, and a low barrier to implementation — it does carry real limitations. STL encodes geometry as triangulated surfaces only. No unit information, no color data, no material properties, no build orientation metadata. Just triangles.

That simplicity was a strength in the early days of stereolithography. Today, as printers hold single-digit micron tolerances and applications span aerospace, medical, and high-performance engineering, the gap between what STL carries and what the workflow needs has widened.

If you're developing print preparation software, understanding where the CAD-to-mesh pipeline introduces errors — and what you can do about it — is worth the time.

Where accuracy gets lost

The process starts when someone exports a CAD model to STL. The original model is a B-Rep built from exact NURBS surfaces. Exporting to any triangulated format, STL included, replaces that precision with an approximation. That's not a flaw in STL specifically — it's inherent to any tessellated representation.

The practical challenge is triangle density. Too few triangles and curved surfaces come out faceted, with dimensional errors that compound through the build. Too many and file sizes balloon, straining slicing software and memory. Uniform tessellation almost never gets the balance right — you end up over-meshing flat regions and under-meshing tight curves simultaneously.

Beyond density, meshes can carry defects that look fine in a viewport but cause real trouble for slicers:

• Holes and gaps where triangles don't quite meet, leaving the mesh non-watertight — slicers can't reliably determine inside from outside
• Flipped normals where some triangles point inward, confusing the slicer about which side is material and which is air
• Self-intersections where triangle surfaces pass through each other, creating ambiguous geometry
• Non-manifold edges where three or more triangles share a single edge — topologically valid as a triangle collection but physically meaningless

Then there's the assembly issue. CAD assemblies often contain overlapping volumes at press-fit interfaces. In the original B-Rep, this is fine. But once tessellated and sent to a metal powder-bed printer, overlapping mesh regions can cause the laser to expose the same powder twice, affecting material behavior.

These aren't STL-specific problems — they can arise with any tessellated format. But because STL doesn't carry topology or semantic information that could help software detect and resolve them automatically, they tend to surface as manual repair work.

And there's the practical reality that tessellation is a one-way conversion. Once you've gone from exact surfaces to triangles, the mathematical definition is gone. Repairs to the mesh are approximations applied to an approximation. Each fix drifts slightly further from the original design.

Delay tessellation as long as possible

The single highest-impact architectural decision for 3D printing software is keeping exact B-Rep geometry alive as long as possible. Don't tessellate until you must — ideally right before slicing.

Every operation on exact geometry — Boolean operations, wall thickness analysis, orientation optimization, support structure placement — is mathematically precise. Once you convert to mesh, every subsequent operation adds an approximation error.

The 3D ACIS Modeler kernel supports this approach directly. It lets you operate on B-Rep geometry throughout the pipeline and defer tessellation to the final step. For medical implants, aerospace brackets, and anything with tight tolerances, the difference between "tessellated early" and "tessellated late" can determine whether a part passes inspection.

Smarter meshing when you do tessellate

When you do need triangles, curvature-adaptive meshing is a significant improvement over uniform approaches. It varies triangle density based on local geometry: more triangles where surfaces curve tightly, fewer where they're flat or gently curved. The result is a lighter mesh that's often more accurate than a uniform one with many times the triangle count.

CSM/CVM implements this kind of adaptive tessellation, reading the underlying surface curvature and adjusting triangle size accordingly. You stop wasting triangles on planar faces and start allocating them where they actually affect accuracy.

Fixing meshes that arrive broken

Plenty of real-world workflows don't give you the luxury of controlling tessellation. Customers send STL files exported from unknown systems. Legacy data exists only as meshes. Downloaded models arrive pre-tessellated. You need a healing pipeline.

A practical mesh repair sequence looks like this:

1. Duplicate node removal — merge nearly coincident vertices, closing tiny gaps from floating-point noise
2. Orientation healing — make all triangle normals point consistently outward
3. Hole filling — patch gaps, ideally following surrounding curvature rather than spanning holes flat
4. Sliver removal — eliminate degenerate triangles that cause numerical instability in slicers
5. Stitching — connect disconnected mesh shells that should be joined
6. Global remeshing via voxelization — when local repairs aren't enough, voxelize the model and extract a clean mesh; a last resort since it trades some detail for guaranteed manifold output

CGM Polyhedra and ACIS Polyhedra handle this kind of polyhedral repair and manipulation programmatically, so you can automate it rather than requiring users to fix meshes manually in a separate tool.

Hybrid workflows: B-Rep and mesh together

Modern 3D printing software doesn't have to choose between exact geometry and mesh. You can use both simultaneously:

• Keep the designed part as B-Rep for precision operations — design changes, dimensional analysis, Boolean cuts for internal channels
• Generate lattice structures and supports as mesh, since lattices are inherently discrete and don't benefit from NURBS representation

Both ACIS Polyhedra and the CGM Core Modeler support this kind of hybrid modeling, where B-Rep and polyhedral data coexist in the same model and interact through Boolean operations.

Import native CAD when you can

One effective way to sidestep tessellation-related problems entirely is to import native CAD formats directly. If your software reads CATIA, SolidWorks, NX, Creo, STEP, JT, or Parasolid files natively, you receive exact B-Rep geometry without any tessellation loss. The export step — where most defects originate — gets removed from the pipeline.

3D InterOp reads and writes over 30 CAD formats natively, giving 3D printing applications direct access to original geometry with metadata intact.

This doesn't mean abandoning STL support. STL remains essential for compatibility, and plenty of valid workflows depend on it. But offering native CAD import as an option gives users a higher-fidelity path when they have access to the source files. 3MF is also worth supporting — it carries units, color, materials, and build information, and adoption is growing steadily.

What Renishaw did about it

Renishaw, the metal additive manufacturing company, faced these exact challenges with their build preparation software, QuantAM. Their workflow handled STL well, but they wanted to go further — reducing mesh repair time, supporting larger assemblies, and offering customers the option to skip the tessellation step entirely when native CAD data was available.

They integrated native CAD import using 3D InterOp, exact modeling with the ACIS kernel, and mesh processing through CGM Polyhedra.

The software could now read customers' native CAD files directly while still providing high-quality healing for STL files when that's what customers sent. The practical outcome: fewer failed builds, faster file preparation, and less time spent on manual mesh cleanup.

Building this into your software

If you're developing additive manufacturing preparation tools, simulation software, or print management platforms, the geometry pipeline is the foundation everything else sits on. Getting it right means your users spend their time optimizing builds instead of fighting mesh artifacts.

Spatial's SDK portfolio covers the full workflow:

3D InterOp. Read native CAD formats directly, eliminating tessellation as an error source when native files are available.

3D ACIS Modeler and CGM Core Modeler. Exact B-Rep modeling throughout the pipeline — defer tessellation to the last possible moment.

ACIS Polyhedra and CGM Polyhedra. Mesh healing, repair, and hybrid B-Rep/mesh workflows — automated, not manual.

CSM/CVM. Curvature-adaptive tessellation when you do need triangles, allocating mesh density where it actually affects accuracy.

These are the same SDKs that Renishaw and other additive manufacturing software companies build on when the geometry pipeline needs to work reliably across thousands of customer files — not just clean demo models.