BREP vs Mesh: Why Your Choice of Geometry Representation Determines Whether Your Design Can Actually Be Manufactured
Understanding the difference between BREP (Boundary Representation) and mesh geometry is crucial for manufacturing. Learn why BREP is essential for CNC, metrology, and professional manufacturing workflows.
Engineers argue endlessly about SolidWorks versus Fusion versus Onshape. They debate file formats, cloud versus desktop, subscription versus perpetual licenses. But these arguments miss the more fundamental choice that happens earlier in any design workflow, a choice that determines whether your model is a picture of a part or a specification for making one.
That choice is between BREP and mesh.
If you've ever exported an STL for 3D printing and wondered why your CAM software complained, or tried to add a fillet to an imported model and watched your CAD system crash, you've encountered this distinction. Understanding it isn't just academic. It's the difference between geometry that can be manufactured and geometry that can only be rendered.
What BREP Actually Is
BREP stands for Boundary Representation, and the name describes exactly what it does: it represents a solid object by defining its boundaries mathematically.
When you create a cylinder in a BREP-based CAD system, the software doesn't store a collection of points approximating a round shape. It stores the mathematical definition of a cylinder: a center axis, a radius, a height. The curved surface exists as an equation, not as a list of coordinates.
This matters more than it might seem.
A BREP cylinder is a perfect cylinder. You can zoom in infinitely and the curve remains smooth. You can query any point on the surface and get an exact answer. The radius is 10.000mm, not "approximately 10mm based on 36 facets." When you ask the system where the center of that cylindrical face is, it knows. When you ask for the tangent direction at any point on the curve, it can compute it precisely.
The same principle applies to every geometric primitive. Planes are infinite mathematical surfaces. Spheres are defined by center and radius. NURBS surfaces capture complex curvature through control points and knot vectors. Edges are the mathematical intersections of adjacent surfaces.
This mathematical precision is what makes BREP the foundation of professional CAD systems. SolidWorks, Fusion 360, Onshape, CATIA, NX, Creo, Inventor—they all use BREP under the hood because manufacturing requires mathematical certainty, not visual approximation.
What Mesh Actually Is
Mesh representation takes the opposite approach: approximate everything with small flat facets.
A mesh cylinder isn't curved. It's a collection of flat rectangular faces arranged in a ring, creating the illusion of curvature from a distance. Zoom in far enough and you see the individual facets. The "radius" isn't stored anywhere—it's an emergent property of where the vertices happen to be placed.
The mesh knows nothing about what it represents geometrically. It doesn't know that certain faces are supposed to form a cylinder. It doesn't know that two flat regions are supposed to be parallel. It stores only vertices (3D coordinates), edges (connections between vertices), and faces (closed loops of edges). Everything else must be inferred, if it can be inferred at all.
STL, OBJ, and 3MF are mesh formats. When you export a model for 3D printing, you're typically converting BREP geometry into mesh approximation. The CAD system tessellates each surface into triangles, and the mathematical precision evaporates.
This is fine for visualization. It's fine for 3D printing, where the slicer just needs to know which regions are inside versus outside the part. But it creates serious problems when you need to do anything else with the geometry.
Where the Difference Becomes Brutal
#### CNC Toolpath Generation
When a CNC machine cuts a fillet, the toolpath generator needs to know "this is a 5mm radius arc" to produce smooth G-code. The cutter should follow a continuous curved path, and the controller needs mathematical arc definitions to make that happen.
BREP provides this directly. The fillet is stored as a toroidal or cylindrical surface with explicit radius information. The CAM software can generate true arc moves, and the machined surface comes out smooth.
Mesh provides triangles at angles. The CAM software must either approximate curves from the facet pattern (introducing deviation) or generate point-to-point linear moves that leave witness marks on the part. The higher the mesh resolution, the closer you get to the intended geometry—but you never actually reach it.
#### Feature Recognition
Consider a 0.5mm chamfer versus a 0.5mm fillet. These are different manufacturing operations with different implications for deburring, coating adhesion, and stress concentration. A BREP model stores them as explicit features with precise dimensions. Inspection software can verify them. PLM systems can track them.
A mesh stores triangles at angles. Is that faceted edge a chamfer, a fillet, or just coarse tessellation? Automated recognition algorithms struggle with complex geometry because the semantic information simply isn't there.
#### Tolerancing and Metrology
BREP maintains explicit relationships between faces. Two faces can be defined as parallel, a bore as concentric to a boss, a pattern as equally spaced. These relationships are queryable and verifiable.
Mesh has no concept of relationships. Parallelism becomes "these triangle clusters have normals pointing roughly the same direction." Concentricity becomes "these two sets of vertices form shapes that are approximately circular and approximately share a center." CMM software can measure mesh parts, but the comparison to nominal is always approximate.
#### Surface Continuity
For aerodynamics, mold flow, and anywhere surface quality affects function, engineers care about continuity between surfaces. G0 means surfaces touch. G1 means they share tangent direction. G2 means they share curvature. G3 means curvature changes smoothly.
BREP distinguishes these explicitly. A Class A automotive surface maintains G2 or G3 continuity across panel boundaries, and the CAD system enforces and verifies this.
Mesh flattens everything into triangles. G0, G1, G2, G3—they all become indistinguishable faceted approximations. A Class A surface becomes indistinguishable from a low-polygon model at the data level.
Why This Matters Now: The AI Problem
Most "AI CAD" tools generate meshes.
This isn't because meshes are better for design. It's because neural networks output triangle soups more easily than parametric BREP. Training data is more available. The mathematical constraints of valid BREP topology are harder to enforce in generative models.
The result: AI tools that produce geometry which looks impressive in screenshots but falls apart when you try to manufacture it.
Export that AI-generated bracket to STEP? The mesh-to-BREP conversion introduces approximation errors, loses feature information, and often produces geometry that downstream CAD systems can't edit. Try to add a fillet to that AI model? The system doesn't know which edges form the feature you want to modify, because edges in the source mesh were arbitrary tessellation artifacts.
This is why demos stop at renders and 3D prints. Mesh geometry works when you only need to know inside-versus-outside. It breaks when you need to do anything that requires understanding what the geometry actually represents.
The Path Forward
The choice between BREP and mesh isn't going away. Both representations serve valid purposes. Meshes excel at visualization, 3D printing, and cases where approximate geometry is sufficient. BREP excels at manufacturing, analysis, and cases where precision and editability matter.
The challenge for AI-native CAD is generating BREP directly—not as a conversion from mesh, but as the primary output. This means producing geometry with explicit surfaces, precise dimensions, and semantic feature information intact.
It's a harder problem. Valid BREP topology has constraints that mesh doesn't: surfaces must connect properly at edges, shells must be watertight, face orientations must be consistent. Generating geometry that satisfies these constraints while also meeting design intent requires more than pattern matching on training data.
But it's the only path to AI-generated designs that can actually be manufactured.
At Henqo, this is why we build on professional BREP kernels rather than mesh-based generation. When you describe a part in natural language, the output is mathematically precise geometry—surfaces with explicit definitions, edges with exact positions, features that downstream tools can recognize and modify.
The render might look the same as a mesh. The STEP file tells a different story.
---
Key Takeaways
BREP (Boundary Representation):- Mathematically exact surfaces and curves
- Stores geometric relationships explicitly
- Required for CNC, metrology, and professional manufacturing
- Editable and feature-aware
- Larger file sizes, more complex data structures
- Approximates geometry with flat facets
- No semantic information about features
- Sufficient for visualization and 3D printing
- Difficult to edit or analyze precisely
- Smaller files, simpler data structures
---
Henqo generates manufacturing-ready BREP geometry from natural language descriptions. Try it at henqo.com.