Text-to-CAD to STEP file: getting usable output

I once exported a STEP file from a text-to-CAD tool, opened it in Fusion 360, and everything looked perfect. Clean faces. Correct proportions. The holes were even the right diameter. I felt the kind of satisfaction that comes from a tool doing exactly what it promised. Then I tried to shell the part and Fusion threw an error that basically said "this isn't a solid body." Turns out the geometry had an internal face that split what should have been one solid into two touching-but-not-joined pieces. It looked solid. It rendered solid. It was not, in any meaningful sense, solid. I spent fifteen minutes tracking down the phantom face and stitching the body back together, which is a sentence that only makes sense if you've been in CAD long enough to develop strong feelings about surface healing.

STEP is the file format that makes text-to-CAD useful for engineering. Without it, you're working with meshes, and meshes in a CAD context are like being handed a photograph when you asked for a blueprint. STEP gives you real geometry. But "real geometry" and "correct geometry" are different promises, and only one of them is guaranteed.

Why STEP is the format that matters#

STEP (Standard for the Exchange of Product model data, ISO 10303) is the industry standard for exchanging B-Rep solid geometry between CAD tools. When a text-to-CAD tool exports STEP, it's exporting the mathematical definition of surfaces, edges, and their relationships. Not triangles. Not an approximation. The actual geometry.

This means a STEP file from Zoo.dev opens in Fusion 360, SolidWorks, Creo, NX, or FreeCAD as a proper solid body. You can select individual faces. You can measure true diameters, not approximate chord distances across a mesh polygon. You can apply fillets to real edges. You can cut features, add holes, and modify the geometry the same way you would if you'd modeled it yourself.

STL, by contrast, is a triangle mesh. It's fine for 3D printing slicers, which expect mesh input. It's useless for engineering edits. Try to add a chamfer to an STL edge in SolidWorks and you'll get an error, or worse, a "converted" body made of ten thousand tiny planar faces pretending to be a smooth surface. OBJ, FBX, glTF: these are all mesh or visualization formats. They have uses, but engineering isn't one of them.

If a text-to-CAD tool can't export STEP, I don't consider it a CAD tool. It's a shape generator with a marketing problem.

Which tools actually output STEP#

Not all of them, which is a useful filter.

Zoo.dev exports STEP and it's their primary engineering format. The STEP files are clean B-Rep and open correctly in every CAD tool I've tested. For a full review of the tool itself, see Zoo text-to-CAD review.

CADScribe exports STEP and STL. The STEP quality has been mixed in my testing. Simple parts export cleanly. More complex geometry occasionally produces STEP files that import with warnings or degenerate faces.

CADAgent generates geometry inside Fusion 360 directly, so there's no export step needed. The model is already in your CAD environment with native feature history. You can save it as STEP from Fusion if you need to share it.

AdamCAD primarily outputs STL with parametric sliders. STL-first tools are useful for 3D printing workflows but limiting for engineering edits.

The point is: before you invest time in any text-to-CAD tool, check whether it outputs STEP. If the answer is "STL only," adjust your expectations. You'll be able to print the result but not easily edit it in a professional CAD environment.

For a broader look at how file formats play into the text-to-CAD workflow, the text-to-CAD guide covers this alongside tool comparisons and workflow strategies.

What to check when you open a STEP file#

I've imported enough AI-generated STEP files to have a checklist that I run through every time. It takes about two minutes and has saved me from sending bad geometry to colleagues, machinists, and 3D printers more times than I'd like to admit.

First: is it actually a solid body? In Fusion 360, check the Bodies folder in the browser. It should say "Body" with a solid icon, not "Surface Body." In SolidWorks, the feature tree will show it as an imported solid or, if something is wrong, as a surface body. A surface body means the geometry has gaps, open edges, or other defects that prevent it from being a closed solid. You can sometimes fix this with surface healing tools, but it's better to know about it before you start adding features on top of broken geometry.

Second: check overall dimensions. Measure length, width, and height. Compare them to what you asked for in your prompt. I've seen dimensions come back accurate to a tenth of a millimeter, and I've seen them off by 8%. There's no way to predict which you'll get without measuring.

Third: check critical feature dimensions. Hole diameters, slot widths, pocket depths, wall thicknesses. If you asked for M4 clearance holes, they should be about 4.3mm to 4.5mm. If they're 4.0mm, that's not clearance. If they're 5.0mm, that's not M4 anything.

Fourth: check feature positions. Measure from edges to hole centers. Verify bolt patterns. Check symmetry if your prompt asked for it. Position errors are the most common issue I see, more common than size errors. The AI gets the feature right but puts it in approximately the right place rather than exactly.

Fifth: try selecting faces and edges. Can you select individual faces cleanly? Can you pick a single edge for a fillet? If faces seem fused or edges are missing where you'd expect them, the topology of the import might be off. This occasionally happens when the generating kernel produces geometry that's technically valid but topologically messy.

Common problems and how to fix them#

Internal faces. This is the one I described in the opening. The geometry looks solid but contains invisible faces that split it internally. In Fusion 360, try the Combine or Stitch command to see if it resolves. In SolidWorks, Import Diagnostics usually catches these. If not, you may need to manually delete the internal face and knit the body back together.

Non-manifold edges. This means an edge is shared by more than two faces, which shouldn't happen in a valid solid. It usually indicates the generating kernel left an artifact. Most CAD tools flag this on import. Fixing it often means deleting the offending faces and patching the gap, which is tedious but doable.

Dimension inaccuracies. The most common issue and the easiest to fix. If a plate is supposed to be 80mm long and came back at 78.5mm, you can usually adjust it with a direct edit or by modifying the imported body. It's not elegant, and it's not how you'd want to build a part for production, but for prototyping it works.

Missing features. The AI forgot a hole, or ignored a fillet you mentioned in the prompt, or decided that one of your six mounting bosses was optional. Adding features to imported geometry is straightforward in Fusion or SolidWorks. Create a new sketch on the appropriate face, draw what's missing, and cut or extrude.

Degenerate faces. Tiny sliver faces or faces with near-zero area that confuse downstream operations. These show up occasionally and tend to cause problems when you try to apply fillets or shells near them. Delete the tiny face, extend an adjacent face to close the gap, and move on. If you've done surface repair in SolidWorks, you already know this dance.

STEP quality varies between tools#

This is worth saying clearly: not all STEP files are created equal. A STEP file from Zoo.dev and a STEP file from another tool can represent the same shape with very different internal quality.

Zoo's STEP output has been the cleanest in my testing. The faces are well-defined, the topology is consistent, and the files import without warnings in Fusion 360 and SolidWorks almost every time. I attribute this to the fact that Zoo built their own geometric kernel (KittyCAD) from scratch, designed specifically for generating clean B-Rep output.

Other tools that generate geometry through code (OpenSCAD scripts, Python scripts for FreeCAD) and then export to STEP can produce valid but messy files. The STEP is technically correct, but the face structure might be overly complex, with unnecessary splits, redundant edges, or topology that makes subsequent editing awkward. You can work with it, but it's like editing someone else's poorly organized SolidWorks file: technically possible, spiritually draining.

The STEP-to-edit workflow#

My standard workflow after importing a STEP from text-to-CAD:

Import the STEP. Run through the checklist above. Fix any immediate geometry issues (internal faces, non-manifold edges, degenerate faces). Then decide: is this good enough to edit, or should I re-prompt?

If the geometry is within a few percent of what I asked for and the topology is clean, I edit. Move holes, adjust dimensions, add missing features. Working on top of imported geometry in Fusion 360 is slightly more annoying than working with native features because you don't have a parametric history to roll back. But for prototyping, it's fine.

If the geometry is significantly wrong, if major features are missing or positions are wildly off, I don't try to salvage it. I either re-prompt with better wording or model it from scratch. There's a breakeven point where fixing imported geometry takes longer than just drawing the part, and that point arrives sooner than you'd expect.

For simple parts, the text-to-CAD-to-STEP-to-edit pipeline works. It saves me five to fifteen minutes per part compared to starting from a blank sketch. For complex parts, the pipeline produces a starting point that needs so much work it stops being a shortcut. Knowing where that boundary is for your particular kind of work is the difference between using text-to-CAD productively and using it to generate problems to solve.

The format is the feature#

I keep coming back to this: the file format is the single most important feature of any text-to-CAD tool. Not the prompt intelligence, not the generation speed, not the viewport rendering. The format. Because the format determines whether the output is the beginning of an engineering workflow or the end of a visual exercise.

STEP means you can work with the geometry. STL means you can print it and hope for the best. Everything else is somewhere between those two poles, usually closer to the "hope for the best" end.

If you're evaluating text-to-CAD tools, start with the output format. If it does STEP, proceed to testing accuracy and quality. If it doesn't, the rest barely matters. The text-to-CAD tutorial walks through the full generation-to-STEP-to-edit cycle, and the Zoo text-to-CAD review covers the tool that currently does this best. But the principle is tool-agnostic: STEP is the format that makes text-to-CAD real, and everything else is a demo.