The Format Problem Nobody Talks About
You just spent an hour designing a part. You export it, send it to a colleague, and they open it in their CAD software. Everything looks fine at first glance. But when they try to add a chamfer to one edge, nothing works. The software doesn't even recognize it as an edge. It's just a collection of triangles pretending to be a shape.
This is the mesh vs B-Rep problem, and if you've ever worked across different CAD tools or sent files to a machine shop, you've probably run into it.
Mesh: Good for Screens, Bad for Engineering
A mesh file (STL, OBJ, 3MF) represents your 3D shape as a bunch of tiny flat triangles stitched together. Think of it like wrapping a sculpture in mosaic tiles. From a distance, it looks smooth. Up close, it's all flat surfaces and hard edges.
This works fine for some things:
- 3D printing. Slicers need triangulated geometry anyway, so STL is the native language of most printers.
- Visualization and rendering. Game engines, web viewers, and AR apps all work with meshes.
- Quick sharing. STL files are small, simple, and universally supported.
But meshes have real limitations that matter for engineering work:
- A circle isn't a circle. It's a polygon with 36 (or 72, or 144) straight edges. Zoom in far enough and you'll see the facets.
- There are no "features" to speak of. A hole is just a ring of triangles. A fillet is just smaller triangles in a curve-like pattern. Your CAD software can't tell the difference.
- You can't meaningfully edit the geometry. Want to change a dimension? You're starting over.
- Tolerances become meaningless. If the "circle" in your STL is actually a 64-sided polygon, what's the true diameter?
B-Rep: What Engineers Actually Need
B-Rep (boundary representation) stores geometry as exact mathematical definitions. A cylinder is defined by its axis, radius, and height. Not approximated. Defined. A fillet has a precise radius. A plane is truly flat, not "flat enough."
STEP, IGES, and native CAD formats (SLDPRT, F3D, etc.) all use B-Rep under the hood. This matters because:
- True curves and surfaces. A 10mm radius fillet is exactly 10mm, not "roughly 10mm if you squint."
- Feature recognition works. Open a STEP file in SolidWorks and FeatureWorks can identify holes, bosses, fillets, and chamfers automatically. Try that with an STL.
- You can actually edit things. Change a dimension, add a feature, modify a face. The geometry stays clean because it was mathematically defined from the start.
- Manufacturing workflows need it. CNC toolpath generators, injection mold designers, and CMM inspection software all need exact geometry, not triangle soup.
STEP: The Universal Translator
Among B-Rep formats, STEP (specifically AP214 and AP242) is the one that works everywhere. It's the PDF of the CAD world. SolidWorks reads it. Fusion 360 reads it. Onshape, FreeCAD, CATIA, NX, Creo. If it's professional CAD software, it opens STEP files.
This universality is why STEP export matters so much. When you generate a model in Ragnar CAD, the output is true B-Rep geometry. That means the STEP file you download isn't a dumbed-down approximation. It's real, editable, manufacturer-ready geometry.
The Practical Decision: Which Format When?
| Use Case | Format | Why | |----------|--------|-----| | 3D printing | STL or 3MF | Slicers expect triangulated mesh | | CNC machining | STEP | Exact geometry for toolpath generation | | Sending to another engineer | STEP | They can edit it in whatever software they use | | Web or app visualization | GLB | Optimized for real-time rendering | | Manufacturing drawings | STEP | Needed to generate proper 2D drawings | | Archiving a design | STEP | Preserves full geometric intent |
The Bottom Line
If you're just 3D printing a phone stand, STL is fine. But the moment your workflow involves another person, another piece of software, or any kind of manufacturing process, you need B-Rep geometry in a STEP file.
Ragnar CAD generates both. Every model comes with STEP export for engineering work and STL export for 3D printing. You don't have to choose.