Skip to main content

draftwright: technical drawings, generated

crates.io CI Licence: AGPL-3.0

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 A4 drawing of an electronics enclosure base: plan, front and side views, section A–A, an isometric view, the pocket and mounting-hole callouts and a title block
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

The current version is 0.6.0, about ten times faster than the Python 0.4 package in a sixth of the memory (release notes).

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.

Circular flange drawing NEMA 17 mount bracket drawing NIST FTC-06 drawing with hole tables and a section
Flange: bolt circle callout Bracket: slots, chamfers, fillets NIST FTC-06: hole tables, GD&T, section

Install

You use Install Platforms
Python 3.9+ (abi3) pip install draftwright (PyPI, Python guide); no Rust needed Linux x86_64 and aarch64, macOS arm64 and x86_64, Windows x64
Command line uv tool install draftwright; installs draftwright and draftwright-mcp The same five wheel platforms
Rust crate cargo install draftwright for both binaries; draftwright = "0.6" 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 0.6:

uv tool uninstall draftwright        # if you used uv
pipx uninstall draftwright           # if you used pipx
pipx install draftwright             # or: uv tool install draftwright
draftwright --version                # should print 0.6.0 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
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. Start with Drawings from build123d, then 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.

Two agent skills ship in skills/: draftwright-step for any STEP file, as a basic drawing or with requirements written by Specify, and draftwright-build123d for build123d scripts. For Claude Code, copy a folder to .claude/skills/ in your project or to ~/.claude/skills/.

Documentation

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.

  • 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.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for draftwright 0.6.0
File Actions
draftwright-0.6.0-cp39-abi3-win_amd64.whl CPython 3.9 abi3 Windows x86-64 Details for draftwright-0.6.0-cp39-abi3-win_amd64.whl
draftwright-0.6.0-cp39-abi3-manylinux_2_28_x86_64.whl CPython 3.9 abi3 Linux glibc 2.28+ x86-64 Details for draftwright-0.6.0-cp39-abi3-manylinux_2_28_x86_64.whl
draftwright-0.6.0-cp39-abi3-manylinux_2_28_aarch64.whl CPython 3.9 abi3 Linux glibc 2.28+ ARM64 Details for draftwright-0.6.0-cp39-abi3-manylinux_2_28_aarch64.whl
draftwright-0.6.0-cp39-abi3-macosx_11_0_arm64.whl CPython 3.9 abi3 macOS 11.0+ ARM64 Details for draftwright-0.6.0-cp39-abi3-macosx_11_0_arm64.whl
draftwright-0.6.0-cp39-abi3-macosx_10_12_x86_64.whl CPython 3.9 abi3 macOS 10.12+ x86-64 Details for draftwright-0.6.0-cp39-abi3-macosx_10_12_x86_64.whl

Total release size: 84.8 MB

Release files / draftwright-0.6.0-cp39-abi3-win_amd64.whl

Download URL draftwright-0.6.0-cp39-abi3-win_amd64.whl
Size 18.2 MB
Tags CPython 3.9 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
242bde75637164c7a7945d2bbb4c0170ad7494a4d0262ec9368e7b55dd6eacb7
BLAKE2b-256 checksum
How to use checksums
eebe63b06ce4c1545e1559b476bc5477abe99603d7f57f1e0119a1806ca7ec43
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 17, 2026.

Transparency log

Release files / draftwright-0.6.0-cp39-abi3-manylinux_2_28_x86_64.whl

Download URL draftwright-0.6.0-cp39-abi3-manylinux_2_28_x86_64.whl
Size 17.7 MB
Tags CPython 3.9 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
6531658cf836b7048cf267fc43bdf1946405ea34353b88859652d5ff50acc6f4
BLAKE2b-256 checksum
How to use checksums
b0081e006ad9a777517eaa0688b7a06385a80263cd1a51f702f6d2350da31fed
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 17, 2026.

Transparency log

Release files / draftwright-0.6.0-cp39-abi3-manylinux_2_28_aarch64.whl

Download URL draftwright-0.6.0-cp39-abi3-manylinux_2_28_aarch64.whl
Size 16.1 MB
Tags CPython 3.9 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
72db196a364e30e382c49b80c4def16b88aa8d6ceb705c2d66f719b64b0e144b
BLAKE2b-256 checksum
How to use checksums
0f932f3dbeece7539e68f305b5a4dde48056fb9afe6c7904f8b63ea1887852d1
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 17, 2026.

Transparency log

Release files / draftwright-0.6.0-cp39-abi3-macosx_11_0_arm64.whl

Download URL draftwright-0.6.0-cp39-abi3-macosx_11_0_arm64.whl
Size 15.9 MB
Tags CPython 3.9 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
b204205703b67850250f62a58d41398a9c3f2137ac230f713b11ebdc24aaba6b
BLAKE2b-256 checksum
How to use checksums
5254e1062423b50cd61d27e5ac1a2dffc4c1169b20d9a296e5dfa643b728482f
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 17, 2026.

Transparency log

Release files / draftwright-0.6.0-cp39-abi3-macosx_10_12_x86_64.whl

Download URL draftwright-0.6.0-cp39-abi3-macosx_10_12_x86_64.whl
Size 16.9 MB
Tags CPython 3.9 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
cb77a7eeb9f536cbcbc78de57322af3cdb7d5f226963ec9c88430f38799691c1
BLAKE2b-256 checksum
How to use checksums
278149412131566ff3e8d21daed84f165e316fb0cb5e5b25eba2753235775ebb
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 17, 2026.

Transparency log

Security for draftwright 0.6.0

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.

Select from 5 files

Attestation for draftwright-0.6.0-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 17, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release

0.6.0 This release

5 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page