DWG vs DXF — What's the Difference and When to Use Each Format

DWG and DXF come from the same software house and both describe 2D geometry, but they are not interchangeable. DWG is AutoCAD’s native binary storage format. DXF is a text-based exchange format designed so that non-Autodesk software can read AutoCAD data. That distinction has practical consequences for every engineer who exports flat patterns, sends files to fabricators, or receives drawings from a customer.

What DWG Actually Is

DWG was created by Mike Riddle in 1982, predating AutoCAD itself. Autodesk acquired the format when they acquired the early Interact CAD program. It is a binary file format — you cannot open it in a text editor and make sense of it. The internal structure has changed with every major AutoCAD release:

AC1032 has remained unchanged from AutoCAD 2018 through AutoCAD 2027 — the DWG format stabilized.

DWG stores everything AutoCAD knows about a drawing: parametric constraints, dynamic block definitions with all their variants, XREF paths, custom linetypes, layer states, and proxy entities from third-party ARX applications. It is optimized for round-trip fidelity within the AutoCAD ecosystem. A DWG saved in AutoCAD 2026 and reopened in AutoCAD 2026 is bit-for-bit reproducible.

DWG is not formally documented. The Open Design Alliance (ODA) produces a compatible open-source implementation through reverse engineering. Most non-Autodesk software that reads DWG — QCAD, LibreCAD, Rhino, Vectorworks, ZWCAD — uses ODA’s libraries. There is occasional version lag: a file saved in the very latest AutoCAD release may not open correctly in ODA-based readers until ODA updates their support.

What DXF Actually Is

DXF (Drawing Exchange Format) was introduced with AutoCAD 1.0 in 1982, explicitly to allow other programs to read AutoCAD drawings. It is a plain-text ASCII format: every entity, property, and coordinate is human-readable. A binary DXF variant exists (introduced in R10) that reduces file size by roughly 25%, but the ASCII form is what the world uses.

Autodesk publishes the DXF specification as part of their developer documentation. This open publication is why DXF became the universal 2D CAD interchange format. Every program that reads or writes 2D geometry supports DXF: nesting software, laser controllers, plasma table firmware, CAM packages, GIS tools.

DXF is structured as group code / value pairs. A group code (integer) on one line is followed by the value on the next. Here is a simple line entity:

0
LINE
8
CUTS
10
25.4
20
0.0
11
152.4
21
0.0

This reads as: entity type LINE, on layer CUTS, from (25.4, 0.0) to (152.4, 0.0). No special parser required — a regular text search finds coordinates. This transparency is why DXF survives as the manufacturing format decades after every other Autodesk interchange format has been superseded.

DXF Version History and Manufacturing Compatibility

The DXF format has versions tied to AutoCAD releases. The version most relevant to manufacturing is R12 (AC1009). R12 predates spline entities, 3D ACIS solids, and dynamic blocks. This is a feature for CNC and laser work: R12 is simple enough that every cutting machine ever built understands it.

For laser and plasma cutting: export as R12. For waterjet with complex geometry: R14 or 2000 if the controller handles it, to preserve ellipses as true ellipse entities rather than polyline approximations. For data exchange with modern CAM software (Mastercam, Hypermill): 2000 or 2004 is safe.

The DXF version implications for multi-view exports covers the downstream consequences of version choice in more detail.

When to Use DWG

Use DWG when:

• Staying entirely within AutoCAD or AutoCAD LT
• Sending files to a customer who uses AutoCAD and needs to edit the drawing (not just cut it)
• Preserving dynamic blocks, parametric constraints, or XREF paths
• The receiving workflow explicitly requests DWG

One important check: if a fabrication shop asks for DWG “because that’s what we always use,” ask whether they need editability or whether they just cut from the file. If they cut from it, DXF is simpler and eliminates version compatibility risk. Many shops default to requesting DWG because their operators learned AutoCAD and DWG is the only format they knew to ask for, not because DWG provides them any benefit in the cutting workflow.

When to Use DXF

Use DXF for every manufacturing file:

• Laser cutting, plasma cutting, waterjet, CNC routing
• Nesting software (Sigmanest, NestPact, FastCAM, ProNest, Lantek)
• 2D CNC milling where the controller reads DXF directly
• Any workflow where the receiving software is not AutoCAD

The universal rule: if a machine is going to cut, punch, engrave, or route your geometry, send DXF. Nearly all nesting tools read DXF as the primary format. Some accept DWG via internal conversion, but DXF eliminates the conversion step and any version-compatibility risk.

DXF requires nothing to open. There is no Autodesk licensing requirement, no DWG TrueView download, no ODA version-lag risk. Any text editor shows you exactly what is in the file.

SolidWorks DXF vs DWG Export — What’s Actually Different

SolidWorks exports both DXF and DWG from flat patterns and drawings. The export options dialog is mostly identical. The relevant differences:

DXF: ASCII text at a chosen version. Any text editor can inspect it. No AutoCAD license needed at the receiving end.

DWG: Binary at the chosen AutoCAD version. Slightly smaller file. Requires AutoCAD, DWG TrueView, or an ODA-based application to open. Best choice when a customer explicitly requests DWG.

Common to both:

Splines to polylines is the most consequential option. SolidWorks sheet metal parts with curved edges export SPLINE entities by default. Many laser software packages either silently ignore SPLINE entities or error out. Enabling “Convert splines to polylines” makes SolidWorks approximate splines as polyline segments. The chord tolerance setting controls accuracy — 0.001mm is safe for most sheet metal tolerances. For precision parts where the curve profile is functional, verify that the approximation stays within part specification.

Scale: Flat-pattern exports from parts are always 1:1. Drawing exports need the view scale set correctly — a 1:2 drawing view exports at half size unless overridden.

Units: DXF/DWG files are unitless. The $INSUNITS variable indicates intent but many tools ignore it. A part modeled in millimeters exports millimeter coordinates. A machine that interprets coordinates as inches will cut the part 25.4x too large. Confirm units at the receiving end whenever you send files outside your organization.

Layer mapping: Custom DXF/DWG layer mapping routes bend lines, outer geometry, forming tool sketches, and annotations to separately named layers. This is essential for laser workflows where the machine needs to distinguish cut paths from etch paths. The DXF layer mapping guide for laser cutting covers the full configuration.

The DXF entity export settings that actually matter documents entity selection options and the silent defaults that contaminate flat-pattern files with unwanted geometry.

File Size Comparison

DWG files are roughly 25% the size of equivalent ASCII DXF. Binary DXF sits between the two. For typical flat-pattern files (a few hundred kilobytes), this difference is irrelevant. The only scenario where DWG file size matters is archiving large libraries of complex drawings — at that scale, the DWG size advantage is real but rarely the dominant concern.

The Spline Problem in Detail

Splines deserve attention because they are the most common source of incompatibility between SolidWorks flat-pattern DXF and what CAM or laser machines accept.

SolidWorks sheet metal parts with curved edges — formed channels, radiused cutouts, complex perimeter profiles — contain spline curves in the flat pattern. When exported to DXF without conversion, these become SPLINE entities (cubic B-spline, degree 3 by default). Many laser software packages cannot consume SPLINE entities.

Enable “Convert splines to polylines” for all flat-pattern exports going to cutting machines. SolidWorks will approximate the spline as a sequence of line or arc segments. Set chord tolerance at 0.001mm — tight enough for sheet metal tolerances without generating thousands of segments.

If the machine absolutely needs spline entities and the controller supports them, test with a simple file first before a production run.

What Fabricators Need vs What They Receive

Fabricators who receive DXF files from engineering have consistent complaints:

1. Geometry not at 1:1 scale — the drawing sheet scale was applied instead of the model scale
2. Dimension annotations and title block included — contaminate the cutting path; the operator must delete them before nesting
3. Bend lines included — annotation-only lines with no machining intent, but they add noise to the nesting file
4. Open contours — gaps in the profile outline that prevent automatic nesting or cause the cutter to miss a segment
5. Spline entities the CAM software cannot process

Items 2–4 are controlled by entity selection settings in the SolidWorks DXF export dialog. Item 5 is the splines-to-polylines conversion. Item 1 is a scale setting. Getting all five right consistently in a production workflow requires either a well-documented manual procedure or automation.

For batch DXF exports from SolidWorks assemblies, these settings need to be consistent across all parts. A macro or add-in enforces them at export time rather than relying on each user’s personal SolidWorks preferences — which change machine by machine.

DWG vs DXF Decision Table

Common Pitfalls Summary

Splines-to-polylines not enabled: Most frequent cause of fabricator complaints. Enable for all flat-pattern exports going to cutting machines.

Annotations in flat-pattern DXF: Dimension entities, balloon notes, and surface finish symbols add noise the fabricator must remove. Export only outer profile, holes, and bend lines if your fabricator uses them.

Units mismatch: Hard to spot visually. The parts look correct in shape but are the wrong size. Confirm units at every handoff outside your organization.

Wrong DXF version for old controllers: Some legacy tables choke on DXF R2000+ entities. When in doubt, default to R12.

DWG sent to a shop without AutoCAD: If the fabricator does not have AutoCAD or DWG TrueView installed, they cannot open the file.

For teams producing flat-pattern DXF files in volume from SolidWorks assemblies, the DWG vs DXF vs STEP vs IGES comparison covers where STEP and IGES fit into the same workflow — and which format each downstream consumer actually needs.