Text-to-CAD vs generative design: different tools, different jobs

A colleague sent me a LinkedIn post last month where someone described text-to-CAD as "basically generative design but with prompts." I read it twice, hoping I'd misunderstood. I hadn't. It's like saying a microwave is basically an oven but faster. They both involve heat and food, and that's where the resemblance ends.

I see this confusion constantly, and I get why it exists. Both involve AI. Both produce 3D geometry. Both promise to make CAD easier. But they solve completely different problems using completely different methods, and confusing the two will land you with the wrong tool for the job and a deadline that doesn't care about your misunderstanding.

So let me separate these properly, because the difference matters if you actually make things.

What text-to-CAD does#

Text-to-CAD generates geometry from a description. You type "a rectangular enclosure, 100mm by 60mm by 40mm, with a lid and four M3 mounting holes in the corners" and the AI produces a 3D model that attempts to match what you described. The output is new geometry that didn't exist before. The AI is creating a shape from language.

The tools doing this right now, Zoo.dev, AdamCAD, CADAgent, and a few others, use transformer-based models trained on CAD datasets to predict sequences of modeling operations (sketch, extrude, fillet, hole) from text input. The quality varies. Simple parts come out reasonably well. Complex parts don't. I've covered the specifics in the text-to-CAD guide, but the essential point here is this: text-to-CAD is a creation tool. It makes something from nothing, guided by words.

The input is natural language. The output is geometry. The AI decides the shape, the features, and the dimensions based on what it learned from training data. You're delegating the design to the model, which is both the appeal and the risk.

What generative design does#

Generative design starts with a problem definition, not a description. You define the design space (the volume the part can occupy), the loads (where forces act and how strong they are), the constraints (where the part attaches, what material it's made of, what manufacturing process will produce it), and the objectives (minimize mass, maximize stiffness, stay within a certain displacement). Then the software runs topology optimization to figure out the best way to distribute material within those constraints.

The output is geometry, yes. But the geometry isn't invented from language. It's calculated from physics. The algorithm removes material that isn't carrying load and keeps material that is. The result often looks organic, like bones or tree branches, because nature solves similar optimization problems and arrives at similar shapes. That's not a coincidence. It's math.

Fusion 360 has generative design built in. Altair Inspire does it. nTopology handles lattice and topology optimization. Siemens NX has it. Most of the major CAD platforms offer some version. The technology is mature compared to text-to-CAD. Companies have been shipping production parts designed with topology optimization for years, particularly in aerospace and automotive where weight reduction has direct cost and performance implications.

The fundamental difference#

Here's the simplest way I can put it.

Text-to-CAD: "Make me a bracket." The AI decides what the bracket looks like.

Generative design: "Here's where the bracket attaches, here's the load, here's the material, here's the manufacturing method, now find the shape that uses the least material while meeting the structural requirements." The algorithm computes what the bracket should look like.

One is creation from description. The other is optimization from requirements. They're not two versions of the same thing. They're different activities that happen to produce 3D geometry.

A text-to-CAD tool doesn't know anything about loads. It doesn't know what the part is made of. It doesn't understand that a thin wall under a bending load will fail, or that a particular feature is impossible to machine from a certain direction. It generates shape. That's it.

A generative design tool doesn't understand natural language. You can't tell it "make me something that looks cool." You have to define boundary conditions, load cases, constraints, materials, and manufacturing processes. If you skip any of those, the optimization either fails or gives you an unrealistic result.

When you'd use text-to-CAD#

Text-to-CAD fits early in the design process, before you know the loads, before you've finalized the mounting points, before you're committed to a manufacturing method. It's for getting a shape on screen quickly so you can react to it, modify it, and decide what to do next.

I use it when I need a starting point. "I need a bracket roughly this size, with holes roughly here, and I'll figure out the details later." For concept exploration, for checking if a form factor makes sense, for generating first-draft geometry that I'll rebuild properly in Fusion 360, text-to-CAD saves time. Not engineering time. Sketching time.

It's also useful for people who don't have CAD skills and need a shape for communication. A hardware startup founder showing a manufacturer what they're thinking. A hobbyist who wants to 3D print a simple enclosure. Someone who needs geometry but doesn't need it to be optimized, just roughly correct.

The text-to-CAD guide covers specific tools and workflows. The honest summary is: it's a fast, imprecise first pass.

When you'd use generative design#

Generative design fits later, when you know the engineering requirements. When you have defined load cases, material choices, and manufacturing constraints. When you need the part to be light, stiff, strong, or some combination, and you want the software to explore the design space more thoroughly than you could manually.

The classic use case is a structural bracket where weight matters. Define the bolt locations, apply the loads, set the material to aluminum, constrain the manufacturing to CNC milling with 3-axis access, and let the optimizer run. The result might be a shape you'd never have drawn yourself, but it meets all the structural requirements while using less material than your instinct-driven design would have.

I've used it for a mounting bracket on a test rig where the weight budget was tight and the loads were well-characterized. The generative result saved about 35% mass compared to my hand-designed version. It also looked like an alien artifact, which the machinist found amusing and slightly offensive. But it worked.

Where generative design doesn't help: early concept phases where the requirements aren't defined yet. You can't optimize for loads you haven't calculated. You can't constrain to a manufacturing process you haven't chosen. Generative design needs inputs that text-to-CAD doesn't, and if those inputs are wrong, the output is useless in an expensive way.

Where people get confused#

The confusion, I think, comes from marketing. Both text-to-CAD and generative design get presented as "AI designs your part for you." And on a very abstract level, that's true. But the kind of "designing" is totally different.

Text-to-CAD is like asking a colleague to sketch you something based on a description. The result depends on their interpretation, their training, their sense of what you probably mean. It might be close. It might be way off. You're trusting their judgment.

Generative design is like giving a structural analyst a fully defined problem and asking them to solve it. The result depends on the inputs, not interpretation. If the inputs are correct, the output is provably good. If the inputs are wrong, the output is provably useless, but at least you know why.

The other source of confusion is that both can produce organic-looking shapes. A text-to-CAD tool might generate a bracket with rounded edges because the training data included a lot of rounds. A generative design tool produces organic shapes because topology optimization tends toward smooth material distributions. They look similar on screen but arrived there by completely different paths.

Can you combine them?#

This is the interesting question, and the answer is: not directly, but the combination makes sense in theory.

Imagine using text-to-CAD to generate an initial design space and boundary conditions, then feeding that into a generative design solver for optimization. You'd get the speed of text-to-CAD for the early concept and the engineering rigor of generative design for the final shape. Nobody is doing this cleanly yet, but it's not a crazy workflow to imagine. The pieces exist, they're just in different software ecosystems.

What I do in practice is simpler: use text-to-CAD for the starting shape, import it into Fusion 360, set up the generative design study manually, and let the optimizer refine it. The text-to-CAD output serves as a design space reference, not the final geometry. It's two separate steps with a human in between, which is about the level of integration the current tools support.

The summary that matters#

If you need geometry quickly from a description, and accuracy and optimization aren't critical yet, text-to-CAD is the right tool. If you need structurally optimized geometry that meets specific engineering requirements, generative design is the right tool. They're not interchangeable, they're not in competition, and treating one as a substitute for the other will waste your time.

Text-to-CAD creates. Generative design optimizes. Both produce shapes. The similarity ends there. And the next time someone on LinkedIn calls them the same thing, you'll know they haven't tried to actually make a part with either one. Which, in my experience, is roughly 90% of people posting about AI and CAD on LinkedIn.