Text-to-CAD for beginners: start here

A friend of mine who runs a small electronics business asked me last month if he could "just type what he wants and get a 3D model." He'd seen a demo on social media where someone typed a sentence and a bracket appeared on screen, fully formed, ready to print. He wanted to know if that was real. The short answer is yes, sort of. The longer answer took me twenty minutes and involved a lot of sentences that started with "but."

Text-to-CAD is real, it works for simple parts, and it's not going to replace knowing what you're doing. If you've never tried it and you're wondering whether to bother, this is the honest beginner's version.

What text-to-CAD actually does#

You type a description of a physical part. An AI turns that description into 3D geometry. Not a picture of a part. Not a rendering. Actual solid geometry that you can open in CAD software, measure, edit, and manufacture from.

The key word in that paragraph is "solid geometry." There are a lot of AI tools that generate 3D shapes from text, but most of them produce meshes: collections of tiny triangles that approximate a shape. Meshes are fine for video games and 3D printing. They're not fine for engineering, because you can't easily select a face, add a hole, change a dimension, or do any of the things you'd normally do in a CAD tool. For the full explanation of why this distinction matters, the what is text-to-CAD post covers it in detail.

Text-to-CAD tools, the ones worth your time, produce B-Rep (Boundary Representation) solid models. These are the same kind of geometry you'd get from SolidWorks, Fusion 360, or any professional CAD program. Real faces, real edges, real topology. The difference is you got there by typing a sentence instead of spending ten minutes sketching and extruding.

Where to start#

Two options that I'd recommend for beginners:

Zoo.dev has a free tier. You create an account, type a prompt, and get a 3D model in a web browser. No software to install. No CAD knowledge required to generate a part. The output can be exported as a STEP file, which opens in any professional CAD tool. If you just want to see what text-to-CAD feels like, this is the fastest path from curiosity to a generated model.

CADAgent is a free, open-source add-in for Fusion 360. If you already have Fusion installed (the personal use license is free), CADAgent lets you generate models directly inside the Fusion environment. The advantage is that the output has native feature history, which means you can edit it like any other Fusion model. The setup requires an Anthropic API key, which costs a small amount per generation.

For this post, I'll assume you're starting with Zoo.dev because it requires the least setup and no existing CAD software.

Your first part#

Go to zoo.dev, create a free account, and open the Design Studio. You'll see a text box and a 3D viewport. That's essentially the whole interface.

Start simple. Don't try to generate an engine block. Try something like this:

"Flat rectangular plate, 80mm by 50mm, 5mm thick, with four 5mm through-holes near the corners, 8mm from each edge."

Type that in, click Generate, and wait about fifteen seconds. A 3D model should appear in the viewport.

Rotate it around. Does it look like a rectangular plate with four holes? It probably does. This is the kind of part text-to-CAD handles well: flat, rectangular, with simple features that can be described with dimensions.

Now try exporting it. Click the export button, choose STEP. A file downloads to your computer. If you have Fusion 360 or SolidWorks, open that file. You'll see a solid body with selectable faces, measurable edges, and real geometry you can modify.

If you don't have CAD software, you can also export as STL and open it in a free viewer or 3D printing slicer. But the real value of text-to-CAD is in the STEP export, because that's what makes the output editable.

For a more detailed walkthrough of the Zoo.dev interface and workflow, the how to use text-to-CAD guide covers each step.

What works for beginners#

Simple parts with clear geometry and explicit dimensions. I'm going to keep repeating "explicit dimensions" because it's the single most important habit for getting good results.

Parts that tend to work:

Rectangular plates with holes. Brackets (L-shaped, U-shaped, flat). Simple boxes and enclosures. Standoffs and spacers. Adapter plates with bolt patterns. Basic cylindrical parts.

These are prismatic shapes: combinations of rectangular and cylindrical geometry with cuts, holes, and fillets. Text-to-CAD tools are good at these because the AI can map your description to a straightforward sequence of CAD operations (sketch a rectangle, extrude it, cut some holes, add fillets).

What tends not to work:

Anything with curves that aren't simple arcs or circles. Gears, turbine blades, organic shapes, aerodynamic profiles. Anything where multiple parts need to fit together with specific clearances. Sheet metal parts that need to unfold. Parts with features that depend on each other in complex ways (snap-fit joints, living hinges, undercuts for molding).

If you're a beginner, stick with the simple stuff. Not because the simple stuff is trivial, but because it's where the tool actually delivers on its promise. A mounting plate with four holes is boring, but it's also genuinely useful, and generating one in thirty seconds instead of modeling it in ten minutes is a real time savings.

The text-to-CAD guide maps out the full range of what works and what doesn't across different tools.

Things beginners get wrong#

I've watched a few people try text-to-CAD for the first time, and the same mistakes come up.

Being too vague. "Make me a bracket" produces something bracket-shaped but with random dimensions. "Make me an L-bracket, 3mm thick, 50mm legs, with two M4 holes on each leg" produces something you can use. Treat the prompt like a specification, not a conversation.

Expecting perfection. The generated part will not be exactly what you asked for. Dimensions might be off by a millimeter or two. Features might shift slightly from where you specified them. This is normal. Text-to-CAD gives you a starting point, not a finished part. Every output needs verification.

Exporting as STL when they should export as STEP. STL is a mesh. STEP is solid geometry. If you want to edit the result in a CAD tool, STEP is the only option that makes sense. STL is for sending to a 3D printer slicer, not for engineering work.

Trying complex parts too early. I get it, the technology seems magical, so why not ask for something ambitious? Because the tool will return something that looks plausible but is wrong in ways that are hard to catch if you don't already know what the correct geometry looks like. A gear with wrong tooth profiles looks like a gear to someone who hasn't designed gears. Start simple. Build intuition for what the tool can and can't do.

Forgetting that this is a first draft. Text-to-CAD generates geometry. It doesn't generate manufacturing intent, tolerances, material specifications, surface finishes, or assembly relationships. If you're planning to actually make the part, the generated model is the beginning of the process, not the end.

Do you still need to learn CAD?#

Yes.

I know that's not the answer the marketing suggests. But here's the reality: text-to-CAD gives you geometry. Understanding whether that geometry can be manufactured, whether the dimensions are appropriate, whether the material thickness works, whether the holes are in the right places for standard fasteners, that requires knowing what good geometry looks like. And that knowledge comes from actually using CAD software.

Think of text-to-CAD like autocomplete for code. It helps if you already know how to program. It's less helpful, sometimes dangerously so, if you don't, because you can't evaluate whether the output is correct.

If you're a beginner with no CAD experience, text-to-CAD is a great way to get a feel for 3D parts and start thinking in three dimensions. But it's not a substitute for learning Fusion 360 or SolidWorks if you plan to do any serious design work. The best text-to-CAD tools comparison can help you pick the right tool to experiment with, and learning a real CAD program alongside it will make you much better at evaluating and fixing the output.

Where to go from here#

Once you've generated a few simple parts and exported them as STEP files, you'll start to develop a sense for what kind of prompts work and what kind of parts the tool handles well. That intuition is worth more than any tutorial.

If you want to go deeper, the text-to-CAD guide covers the full tool landscape, output quality, and workflow integration. The prompt engineering post explains how to write prompts that produce more accurate geometry. And if you decide to get serious about Zoo.dev specifically, the how to use text-to-CAD walkthrough covers the interface and export process in detail.

My honest advice for beginners: try it. Generate five or ten simple parts. Export them. Open them in a free CAD viewer or Fusion 360's personal license. Measure the results. You'll know pretty quickly whether text-to-CAD is useful for the kind of work you do, or whether it's a neat trick that doesn't quite fit your needs yet. Either answer is fine. The technology is early, the tools are improving, and the worst thing you can lose is half an hour of curiosity.