This release is a pre-release and may not be stable for production use.
Draftwright turns a STEP model into a dimensioned engineering drawing: SVG, PDF or editable DXF. It recognises manufacturing features, reads requirements from the STEP file, chooses views and dimensions, and lays them out on standard sheets. It reports what it could not state.
An electronics enclosure base made by a text-to-CAD tool, drawn by 0.6.0-alpha.2 from its STEP
file with only the title set. Every view, dimension and callout is placed automatically.
Contents: Examples · Install · Command line · Output and the Spec · Python · What it does · Assemblies and revisions · With agents · Documentation · How it's built · Related projects · Licence and contributing
0.6.0 is in alpha (pre-release); the current version is 0.6.0-alpha.2. The Rust half of the build123d API remains to be completed; layout regressions are tracked in #452.
Examples
To see what draftwright does with real parts, browse
pzfreo/dw-examples: NIST test parts, FreeCAD
library parts, text-to-CAD and build123d parts, and assemblies, each drawn by the stock CLI with
only a title block set. They are unreviewed output, mistakes included, and each drawing's
.review.json lists what draftwright found it could not state. Its CI rebuilds them whenever the
pinned draftwright release is bumped.
| Flange: bolt circle callout | Bracket: slots, chamfers, fillets | NIST FTC-06: hole tables, GD&T, section |
Install
These commands select the pre-release; unqualified installs can select older releases.
| You use | Install | Platforms |
|---|---|---|
| Python 3.9+ (abi3) | pip install --pre draftwright (PyPI, Python guide); no Rust needed |
Linux x86_64 and aarch64, macOS arm64 and x86_64, Windows x64 |
| Command line | uv tool install --prerelease allow draftwright; installs draftwright and draftwright-mcp |
The same five wheel platforms |
| Rust crate | cargo install draftwright --version 0.6.0-alpha.2 for both binaries; draftwright = "=0.6.0-alpha.2" for the library (operations) |
Native Rust toolchain |
| Prebuilt archives | Download a CLI archive from Releases; includes both binaries, schemas and agent docs | macOS arm64, Linux x86_64, Windows x64 |
| Browser | draftwright.io | WebAssembly (package guide) |
0.6 replaces the old Python package of the same name; pin draftwright<0.6 to keep it.
Upgrading from the old Python package. If you installed 0.4 or 0.5 as a tool with uv or pipx,
its draftwright command stays on your PATH and the new install won't replace it. Remove the old
one first, then install the pre-release:
uv tool uninstall draftwright # if you used uv
pipx uninstall draftwright # if you used pipx
pipx install --pip-args=--pre draftwright # or: uv tool install --prerelease allow draftwright
draftwright --version # should print 0.6.0-alpha.2 or later
If pipx says the command "is not on your PATH" or points elsewhere, pipx install --force takes
the link over. An older Rust build in ~/.cargo/bin can also shadow it: cargo uninstall draftwright.
Command line
draftwright render part.step -o part --formats svg,pdf,dxf # includes editable DXF in alpha.2
draftwright render part.step -o part --units in --paper ansi
draftwright review part.step
review prints JSON containing the drawing as SVG text, the problems and lint's findings.
The engine guide covers the full command line, including
--shaded, --below and paper choices. draftwright completions zsh prints a completion
script; the same guide gives installation commands and the other supported shells.
Output and the Spec
A Spec is a small JSON file of drawing settings and edits. Without one, draftwright uses
its automatic choices. render writes part.svg, part.pdf and part.dxf for the first
command above (SVG and PDF by default); PNG is also available. Extra sheets get numbered
files, while PDF holds all the sheets. Each format embeds the Spec that made it, and the
command prints JSON listing the files and problems.
For example, save this as part.drawing.json to fill in the title block:
{ "sheet": { "title": { "title": "Mounting plate", "number": "MP-001" } } }
draftwright render part.step --spec part.drawing.json -o part
draftwright spec part.pdf # read the embedded Spec
The model and Spec reference describes the settings, documents and Rust API.
Python
from draftwright import make_drawing, Part
svg, dxf = make_drawing("part.step", out="drawing", title="Bracket")
from build123d import Box
part = Part(Box(120, 80, 20), "plate", title="Mounting plate")
svg, dxf = part.drawing(sheet="A3").render("plate")
Install build123d separately for shapes and Part. See the Python guide
for requirements, layout edits and the parts of the build123d API still being completed.
Moving from 0.4: see Python migration and CLI migration.
What it does
- Recognises features with quiddity: holes, counterbores, patterns, slots, pockets, turned steps, grooves, chamfers, fillets and threads.
- Dimensions features with rules for each family; omissions and placement failures are reported with a reason.
- Reads AP242 PMI (tolerances and GD&T stored in the STEP file), including fits, datums, threads and surface finish. Unsupported requirements are reported.
- Lays out sheets with views, sections, details, hole tables and an ISO 7200 title block; it chooses scale and paper size, using more sheets when needed.
- Produces deterministic output: the same inputs give the same bytes. SVG and PDF carry real, searchable text; DXF has editable text, dimensions, blocks and title-block attributes.
Assemblies and revisions
draftwright pack assembly.step -o pack
draftwright diff old.step new.step --spec part.drawing.json -o changes
pack draws each made part once and writes an ISO 7573 parts list, item numbers and a CSV/JSON
bill of materials. diff carries the Spec to a new revision, marks up what changed and reports
edits that need a decision. See bills of materials and the engine guide.
With agents
The CLI release archives include draftwright-mcp, a local stdio MCP server for Claude
and other MCP clients; the wheel and Cargo installs provide it too. Clients can inspect a
part, edit its Spec, render the drawing and read the findings. The MCP guide
also covers the newer local draftwright mcp-stdio and draftwright mcp-http adapters.
The Spec is the steering surface: an agent inspects the drawing and findings, changes settings or edits by item ID, then renders and reviews again. Requirements belong in STEP; the Spec controls the drawing.
Documentation
- Engine guide: building, the full command line, what is and isn't supported, known limitations, checking a change
- Model and Spec reference: the Analysis, Spec and Plan, and every setting
- Python API and migration
- MCP and agents
- Browser / WASM package
- Thread callouts · Bills of materials · Finding impact
- Changelog
How it's built
Draftwright is AI-coded with Claude and Codex, directed by its maintainer. Large changes get independent review. The output is deterministic, and the public examples are built by the stock CLI with no hand edits.
Related projects
- quiddity: feature recognition from STEP B-rep, built on the haecceity geometry kernel that draftwright uses.
- Specify: writes tolerances, fits, GD&T and BOM data into STEP as AP242 PMI; available at draftwright.io/specify.
- dw-examples: the public example drawings.
- draftwright-python: the earlier Python implementation, being retired.
Licence and contributing
Draftwright is licensed under the GNU AGPL v3.0, and is also available under separate commercial terms; contact paul@draftwright.io. quiddity and haecceity are Apache-2.0. The bundled IBM Plex fonts are under the SIL Open Font License 1.1.
Contributions are welcome. See CONTRIBUTING.md; pull requests need the Contributor License Agreement.
Metadata
Release files for draftwright 0.6.0a3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| draftwright-0.6.0a3-cp39-abi3-win_amd64.whl | CPython 3.9 | abi3 | Windows x86-64 | Details for draftwright-0.6.0a3-cp39-abi3-win_amd64.whl |
| draftwright-0.6.0a3-cp39-abi3-manylinux_2_28_x86_64.whl | CPython 3.9 | abi3 | Linux glibc 2.28+ x86-64 | Details for draftwright-0.6.0a3-cp39-abi3-manylinux_2_28_x86_64.whl |
| draftwright-0.6.0a3-cp39-abi3-manylinux_2_28_aarch64.whl | CPython 3.9 | abi3 | Linux glibc 2.28+ ARM64 | Details for draftwright-0.6.0a3-cp39-abi3-manylinux_2_28_aarch64.whl |
| draftwright-0.6.0a3-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details for draftwright-0.6.0a3-cp39-abi3-macosx_11_0_arm64.whl |
| draftwright-0.6.0a3-cp39-abi3-macosx_10_12_x86_64.whl | CPython 3.9 | abi3 | macOS 10.12+ x86-64 | Details for draftwright-0.6.0a3-cp39-abi3-macosx_10_12_x86_64.whl |
Total release size: 82.0 MB
Release files / draftwright-0.6.0a3-cp39-abi3-win_amd64.whl
| Download URL | draftwright-0.6.0a3-cp39-abi3-win_amd64.whl |
|---|---|
| Size | 17.5 MB |
| Tags | CPython 3.9 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
d3d3c9ff6caaaa87c8fcf04ba391542830036e7a4393cfb8e88417f3e9898d42
|
|
BLAKE2b-256 checksum How to use checksums |
8634cb8035e3666787b12be27e63aa78c52c3f2138a0ab2cb80ee601cae8939d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logRelease files / draftwright-0.6.0a3-cp39-abi3-manylinux_2_28_x86_64.whl
| Download URL | draftwright-0.6.0a3-cp39-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 17.2 MB |
| Tags | CPython 3.9 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
0fabac27d226de5da8009f3aad67b03376edcb7e7ab2e47750d054454be2d60b
|
|
BLAKE2b-256 checksum How to use checksums |
2cba92e1163449434ee55a29047f26b0bcb0453213812c7d55c97b29fbe9818a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logRelease files / draftwright-0.6.0a3-cp39-abi3-manylinux_2_28_aarch64.whl
| Download URL | draftwright-0.6.0a3-cp39-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 15.6 MB |
| Tags | CPython 3.9 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
1c8ce67fabf9be99645406cdfcd9e663b90115cf902a02b75545ca285e86babd
|
|
BLAKE2b-256 checksum How to use checksums |
2addf6d0f4529c41e459e2ff4e3329f023ccca8ae53173d0aaa13aa681169933
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logRelease files / draftwright-0.6.0a3-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | draftwright-0.6.0a3-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 15.3 MB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
7b22fd2a83ffb6038a5737d1d491772eb78ef5db33689d909a784d2817716b05
|
|
BLAKE2b-256 checksum How to use checksums |
622d74778bf724c06c73c7dec0850b42d6eea3298fc7ad0202f01a2c18bd0d8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logRelease files / draftwright-0.6.0a3-cp39-abi3-macosx_10_12_x86_64.whl
| Download URL | draftwright-0.6.0a3-cp39-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 16.4 MB |
| Tags | CPython 3.9 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
f0d380016a3a8c4504cb6cb9c873bea8948845b0740e29eb5ff7a972becce61a
|
|
BLAKE2b-256 checksum How to use checksums |
e338026e619ab23811e5fbb4d89939ef75ae6655d1d26b6e4fc5608874e06e80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logSecurity for draftwright 0.6.0a3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 5 files in this release have been uploaded with provenance metadata.
Attestation for draftwright-0.6.0a3-cp39-abi3-win_amd64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.