A rare attempt at familiar, open DWG editing
OpenCADStudio is building the sort of open-source CAD program many users have wanted for years: a desktop editor that looks and behaves like a conventional drafting package, reads and writes DWG and DXF files, handles both model and paper space, and does not require a commercial subscription. It is written in Rust, renders through WebGPU, and also runs in a browser.
The scope is much larger than a drawing viewer. The README lists core 2D commands for lines, curves, hatches, offsets, trims, fillets, arrays, and text. Dimensions, leaders, tables, blocks, external references, layers, object snaps, dynamic input, plot styles, layouts, viewports, and PDF output target real drafting workflows. On the 3D side, there are primitives, extrusion, revolve, loft, sweep, arrays, and ACIS solid tessellation, plus STL and STEP export and OBJ import.
That feature list makes OpenCADStudio exciting. It also creates a huge correctness burden. CAD software is not judged by whether a command exists; it is judged by whether a drawing survives round trips, measurements stay exact, annotations plot correctly, blocks retain scale, and another firm sees what the author saw. OpenCADStudio is not yet at the point where those outcomes can be assumed.
Fast progress is producing real capability
The repository had 562 stars when reviewed, far fewer than FreeCAD or LibreCAD, but activity was intense. The main branch was pushed on August 8, 2026, and release v0.9.4 was published earlier that same day. GitHub counted 82 open issues and pull requests. New reports and maintainer changes were appearing within hours, so this is a small but very active project rather than a dormant experiment.
Release v0.9.4 is an instructive snapshot. It added a real units dialog and conversion command, expanded typed input for architectural and angular formats, restored paper-layout behavior, improved selection modes, docked the block palette, and corrected several solid-tessellation cases. Function keys can now change drafting modes without cancelling the command in progress. These are the details that make an editor feel familiar to experienced CAD users.
The rendering foundation is also appealing. WebGPU provides one path for desktop and browser graphics, with anti-aliasing, orthographic and perspective cameras, view-cube navigation, raster images, wide polylines, complex linetypes, and different visual styles. The browser demo is the lowest-risk way to judge interaction and basic file support. There is no account or local installation required for that first test.
File fidelity remains the decisive concern
The same release notes explain why we would not put OpenCADStudio into a professional production path yet. Before v0.9.4, some dimensions were reconstructed from styles instead of drawn from their stored picture. When those sources disagreed, text could become hundreds of times too large and extension lines could run vast distances beyond the measured points. Angular dimensions could measure the wrong geometry. Annotative text could be scaled even when it lacked a representation at that scale.
Fixing these defects is good engineering, and the detailed explanations inspire more confidence than vague patch notes. Still, they concern the semantic integrity of drawings. A client does not care that the renderer's fallback path was understandable if a dimension on a submitted sheet is wrong. Every new version should be tested with a curated set of known DWG and DXF files containing the entities, units, fonts, layouts, and external references your work uses. Round-trip them and compare in an independent viewer before saving over an original.
Fresh issue reports reinforce that caution. Users reported blocks inserted at a different scale from their source objects, unitless blocks converting incorrectly, and a newly created block failing to appear in the palette. Another report says a simple one-page drawing produced a 128MB PDF. Older but recently active reports describe a crash on a 2.42GB mesh-heavy DWG, severe Windows application lag, rendering corruption, and a graphics-window lock. These do not mean every user will hit the same failures. They do map the edges that need deliberate testing.
Installation is simple, trust setup is not
Linux gets the cleanest desktop path: download the x86-64 AppImage, make it executable, and run it. Windows has a standalone x86-64 executable. macOS builds target Apple Silicon only. Source builds require Rust 1.75 or newer and a normal Cargo release command. The web version avoids platform packaging altogether.
The binaries lack the platform credentials ordinary business software carries. Windows SmartScreen may warn because the executable is not code-signed. The macOS app is ad-hoc signed but not notarized, so the README recommends a Homebrew command that disables quarantine or manually clearing the quarantine attribute. These instructions may be reasonable for developers who verify the source and release, but they are a poor fit for centrally managed workplaces. Security teams should not train users to bypass operating-system checks casually.
The GPL-3.0-only license is a strength for community freedom and a constraint for some commercial extensions. Using the application does not force your drawings to become GPL-licensed. Distributing modified or combined software can create obligations, so product vendors planning proprietary integration should consult their own counsel.
The right role today
OpenCADStudio belongs on a test machine, in a classroom, or beside a primary CAD package. It is especially worth following if native DWG exchange, Rust, or browser CAD interests you. The project is turning difficult format and drafting behavior into visible open code, and active users can contribute anonymized regression files that make every release safer.
For paid production, choose based on failure cost. LibreCAD is narrower and focused on 2D DXF. FreeCAD is much more established for parametric modeling. SolveSpace is compact and constraint-driven. OpenCADStudio is the ambitious option for an AutoCAD-like workflow, but ambition is not yet dependability. Keep originals immutable, verify output elsewhere, and it can already be a valuable secondary tool.