CADScribe review: mixed results, honest take

I asked CADScribe for a flanged bearing mount with four bolt holes and a central bore. What came back looked, at first glance, like a flanged bearing mount. The flange was there. The holes were there. The bore existed. I felt a brief moment of optimism, the kind you get right before the geometry collapses under inspection. I opened the STEP export in Fusion 360, selected a face, and noticed the bore wasn't actually centered. It was off by about 1.5 mm to one side, just enough to look right in the viewport and be completely wrong in reality. The bolt holes were evenly spaced, at least. One out of two isn't bad for a ten-second generation. Except it is bad, because "almost right" in CAD is just "wrong with better presentation."

That's been my experience with CADScribe across maybe twenty test prompts. It generates real geometry, sometimes in STEP, sometimes in STL. The output occasionally nails what you asked for. More often, it gets the general idea right and the specifics wrong in ways that require either significant rework or a full rebuild. The tool is free, it's fast, and it's sitting in an uncomfortable middle ground between "impressive demo" and "usable engineering tool."

What CADScribe does#

CADScribe is a browser-based text-to-CAD generator. You type a description of a part, it generates a 3D model, and you can export the result as STL or STEP. The generation is fast, usually ten to fifteen seconds, and the interface is conversational. You can refine your prompt by telling it things like "make the hole bigger" or "add a chamfer to the top edge," and it'll attempt to update the model.

It also shows dimension sliders on some models, though this feature seemed inconsistent in my testing. Some models got sliders, some didn't, and the ones that did had sliders for only a few parameters. It's a feature that's clearly in development rather than fully baked.

The tool is currently free to use, which puts it in a different competitive position than paid alternatives. You're not risking a subscription to find out whether it works for your use case. You're risking fifteen minutes, and if you're already sitting at your computer procrastinating on a real model, that's time you were going to lose anyway.

Where it works#

Simple prismatic parts. Boxes. Plates with holes. Basic brackets. Cylindrical features. If the part you need can be described in one sentence and doesn't involve features that reference each other in complex ways, CADScribe has a reasonable chance of giving you something recognizable.

I got a decent rectangular enclosure with corner mounting holes on the first try. The dimensions were within about five percent of what I prompted, the wall thickness was consistent, and the holes were positioned symmetrically. For a 3D print prototype where "close enough" is the actual specification, this was fine. I exported the STL, sliced it, and had a physical part in a couple of hours. The fact that the wall was 2.1 mm instead of the 2 mm I asked for didn't matter for a test fit.

Basic geometric primitives with modifications also work reasonably well. A cylinder with a bore. A plate with a slot. A block with pocketed features. The tool seems to handle single-operation modifications better than compound features, which makes sense given the nature of the underlying model.

Both All3DP and Xometry have published tests of CADScribe. The Xometry evaluation included it among seven text-to-CAD tools and found it generates "fairly accurate CAD files" that are useful for "simple prototyping, educational demos, and visual exploration." That tracks with my experience. CADScribe sits in the "useful for simple things" bucket, not the "ready for engineering" bucket.

Where it falls apart#

Anything with geometric complexity. The flanged bearing mount I mentioned was a moderate prompt, not even a particularly demanding one, and it came back with misaligned features. A gear request produced something that looked vaguely gear-shaped but had tooth geometry that would mesh with nothing in this or any other universe. A sheet metal bracket came back as a solid extrusion with no bend features, no flat pattern, and no awareness that sheet metal has rules.

The consistency problem is worse than the accuracy problem. I ran the same prompt three times on different days and got three different models. The general shape was similar each time, but the specific dimensions, feature positions, and geometry quality varied. One version of a simple bracket had clean fillets. Another had no fillets at all. The third had fillets on two edges but not the other two. If you're generating geometry that needs to be repeatable, or that other parts will mate to, this inconsistency is a real problem.

The conversational refinement is hit or miss. "Make the holes larger" sometimes scaled the holes. Sometimes it regenerated the entire model with different proportions. Once it kept the original model and added new, larger holes next to the existing ones, which was creative in a way I did not appreciate. The lack of parametric continuity between iterations means each refinement is partly a new generation, and each new generation is a new roll of the dice.

STEP export quality varies. Some exports opened cleanly in Fusion 360 with selectable faces and proper topology. Others had stitched surfaces, zero-thickness walls, or internal faces that made the solid body act like it was held together with optimism. If you're exporting to STEP for downstream engineering work, you need to inspect every file. Not spot-check. Inspect.

How it compares#

Against Zoo.dev, CADScribe loses on almost every axis that matters for engineering work. Zoo produces cleaner B-Rep geometry, handles more complex prompts, outputs more reliable STEP files, and has better dimensional accuracy. The gap is significant. Where CADScribe gives you geometry that looks approximately right, Zoo gives you geometry that's closer to actually right. Zoo also has a well-documented API and a Python SDK, which matters for anyone trying to integrate text-to-CAD into a larger workflow.

Against AdamCAD, CADScribe lacks the parametric slider editing that makes AdamCAD's post-generation workflow faster. AdamCAD's OpenSCAD foundation also means the output is inherently parametric and readable as code, while CADScribe's output is generated geometry without transparent logic. For iterative design exploration, AdamCAD's slider approach beats CADScribe's regeneration approach.

Against CADGPT, the comparison doesn't apply. CADGPT doesn't generate geometry at all. It's a scripting assistant. Different tool, different job.

The best text-to-CAD tools comparison covers the full field if you want to see where CADScribe sits relative to everything else.

The free factor#

The strongest thing CADScribe has going for it is that it's free. In a category where Zoo.dev has a free tier but rate-limits it, and AdamCAD charges $9.99 a month for standard access, CADScribe lets you generate as many models as you want without paying anything. For students, hobbyists, and people who just want to see what text-to-CAD can do before investing in a paid tool, that matters.

Free doesn't fix the accuracy problems. Free doesn't make the STEP exports more reliable. Free doesn't add parametric editing or manufacturing awareness. But free does lower the bar to the point where "try it and see" costs nothing, and for a tool in this category, that's a valid strategy. Many of the people who start with CADScribe will eventually move to Zoo or another tool when they need better output. CADScribe is a gateway, and there's nothing wrong with that.

The text-to-CAD limitations problem#

CADScribe's weaknesses are not unique to CADScribe. They're the same limitations that affect every text-to-CAD tool right now: inconsistent accuracy, no manufacturing awareness, no tolerance handling, unreliable feature trees, and output that needs human review before it goes anywhere near a machine shop. The text-to-CAD guide covers these broader issues in detail.

Where CADScribe sits specifically is closer to the bottom of the accuracy spectrum among tools that generate actual geometry. Zoo.dev is ahead. AdamCAD is roughly comparable on simple parts but better on iterative refinement. CADAgent, which operates inside Fusion 360, produces output with better feature history because it's working inside a real parametric environment. CADScribe is competing with tools that have technical advantages it doesn't currently match.

The verdict#

CADScribe generates real 3D models from text prompts, and sometimes those models are usable. For simple geometry, quick prototyping, educational purposes, or just satisfying your curiosity about what text-to-CAD feels like, it's fine. It's free, it's fast, and the barrier to trying it is effectively zero.

For anything that matters, check the output. Measure the features. Inspect the STEP file before you build around it. The geometry CADScribe produces is a starting suggestion, not an engineering document. If you treat it as a rough first draft that needs manual verification and cleanup, you'll be in the right mindset. If you treat it as finished geometry, you're going to have the kind of afternoon that ends with you arguing at a screen about why a hole isn't where it's supposed to be.

I keep CADScribe bookmarked as a quick test tool. When I want to see if a concept makes sense as a shape, it's faster than opening Fusion 360 and sketching from scratch. When I need geometry I can trust, I go somewhere else. That's an honest assessment from someone who wanted it to be better than it is, and who'll check back in six months to see if it got there.