CADCraft vs AutoCAD: files, workflows and a fair comparison
Compare CADCraft with AutoCAD for one practical task. Documented differences, file limitations and checks for a future hands-on test.
Last updated
Menus and supported features can change. Compare the source-check date below with your current app version.

Is CADCraft a useful option beside AutoCAD? I would decide that around an actual job rather than the resemblance of the interface. For this comparison, the task is to draw a test rectangle and circle.
This is a comparison of public documentation. I have not installed both apps and measured them side by side. There is no verified winner, speed advantage or compatibility score in this article. The table separates what is documented from what still needs testing.
What changes in the workflow?
Familiar commands and snapping are useful, but existing CAD delivery depends on the actual entities and file versions involved. A PDF shows paper layout, while DXF carries drawing geometry. Both need checking against AutoCAD with declared units; visual similarity on screen does not establish correct coordinates or retained editable objects.
| Question | CADCraft | What to check against AutoCAD |
|---|---|---|
| Development stage | early development | The required behaviour in the actual version used |
| Delivery model | Developer describes free, open-source, local work | Official product/plan terms and your workflow requirements |
| Automation | Documented command/agent-control paths | Manual correction needed after a repeated operation |
| Files and results | Supported routes have the limitations discussed below | Compare units, coordinates, curves and dimensions in the same DXF. |
An open-source release lets you inspect the code, but it does not remove time spent learning, checking exports or repairing incompatible files. I have not calculated total cost. Use the linked official baseline page for the relevant regional terms instead of assuming one price applies to everyone.
The file limitation that matters here
The README’s file-support table says entities not yet modelled are not preserved on save. Entities are individual drawing objects such as lines, circles or blocks. DWG reading/writing also has a supported version range rather than universal compatibility. Keep the original and inspect unsupported entities, external references and fonts in a test copy.
How I would make the comparison fair
Use the same inputs in both tools: A new drawing with a rectangle from 0,0 to 10,5 and a circle centred at 5,2 with radius 1. Declare the drawing units first.
Keep the output settings, computer, OS and app versions in the record. If one app cannot complete an operation, record where it stopped; do not quietly give only that app an easier input. Separate installation, editing, revision and export time. Errors and manual recovery are part of the workload, even when the final image or document looks good.
| Check | Matched task | Current result |
|---|---|---|
| Geometry | Compare units, coordinates, curves and dimensions in the same DXF. | Not hands-on compared |
| Preservation | Inspect blocks, external references and unsupported entities in a real DWG. | Not hands-on compared |
| Plotting | Compare line weights, fonts and page size in PDFs at the same scale. | Not hands-on compared |
Agree on what counts as finished
A rectangle can look right on screen while being the wrong size on paper. CADCraft is a command-based CAD editor, so I would start by declaring units and entering a few exact coordinates. A small new drawing lets us inspect geometry and file exchange separately. It is a better starting point than trusting a valuable DWG simply because the file opens.
Check geometry in the DXF separately from paper layout in the PDF. Verify model dimensions first, then printed scale, margins and clipped regions. Do not overwrite an important DWG with the experiment. Compare saved objects and dimensions against the source; an unsupported entity can disappear even when the rest of the drawing still looks plausible.
Producing a delivery file is only one part of completion. Reopening the editable version and making one small change checks whether the next revision remains possible. Keep the first output and the revised one so the difference can be inspected. A source-format round trip also needs a test in the app where the file will actually be received.
Where I would start, and where I would pause
A new simple 2D drawing can introduce command entry and exchange. Production drawings need actual-file checks for objects that may be lost during saving. The useful completion condition is preserved geometry and a verified output scale, not merely a drawing that opens without an error.
Agree on units before comparing identical coordinates. A length of 10 means little without them. For repeated drawings, keep geometry/dimension checks separate from PDF plotting settings. Record missing entities and manual reconstruction time; otherwise a quick export can conceal a costly repair job.
The review can be updated with a hands-on result once there is a record of the installed version, source files, matched settings and failures as well as successes. For now, these are practical comparison criteria based on the checked documents, not observations from a completed benchmark.
Introduction · Task tutorial · Comparison: documented differences
Sources & further reading
- https://getartcraft.com/apps/cadcraft
- https://github.com/storytold/cadcraft/blob/main/README.md
- https://www.autodesk.com/ca-en/products/autocad/features
- https://github.com/storytold/cadcraft/blob/e707ab4d7cc10102e550ad4c5bcecef1084a9baa/README.md
- https://github.com/storytold/cadcraft/blob/e707ab4d7cc10102e550ad4c5bcecef1084a9baa/crates/ui-egui/src/menus.rs