DXF drawing files

DXF can use ASCII or binary encoding and can contain only selected objects from the source. Confirm the export scope, version and intended operations. Autodesk DXF import/export overview

Check a known length after import. If a span of 100 meant millimetres but is read as inches, the receiver gets 2540 mm. The DXF header’s $INSUNITS describes default insertion units. It does not establish that the geometry already has the intended scale.

A DXF is an exchange artifact, not automatic proof of a manufacturable part. Keep its relationship to the design revision, dimensions, material and requested operations explicit. A file that opens successfully can still contain the wrong objects, scale or manufacturing interpretation.

Agree on the receiving workflow

Identify whether the recipient needs a flat cutting profile, a drawing for review, engraving paths or another supported geometry set. A fabricator's accepted subset can be much narrower than the format's capabilities.

SendCutSend, for example, accepts DXF among its 2D vector formats and requests 1:1 inch or millimeter geometry. Its checklist calls for one layer, removal of stray points and duplicate lines, no open contours in shapes, and text converted to outlines or paths. These are that service's file-preparation requirements, not universal DXF syntax rules. Other workflows may legitimately require separate operation layers or open engraving paths. Confirm them before simplifying an export. SendCutSend file setup

Do not assign cutting, marking or bending meaning to a color or layer name without an agreed convention. A named layer can preserve organization while still leaving the recipient uncertain about the intended operation.

Format version and numeric export settings

Autodesk's DXF header reference identifies $ACADVER as the drawing database version. Examples include AC1009 for R11/R12, AC1027 for AutoCAD 2013 and AC1032 for AutoCAD 2018. These identifiers describe the saved format level; they do not by themselves identify the application that created the file or its release year. Autodesk 2026 DXF header reference

Choose a version supported by the actual receiving application and confirm the result after import. “Save as an older DXF” is not evidence that all source objects retain the intended geometry. Compare the exported representation with the source before releasing it.

AutoCAD's SAVEAS documentation exposes DXF options for version, binary encoding, selected objects and decimal places of accuracy from 0 through 16. Export precision is a file setting, not a manufacturing tolerance or a claim about the accuracy of the original design. Select it so that rounding does not consume the geometric allowance needed by the task. Autodesk SAVEAS prompts, 2026 documentation

Units: verify coordinates as well as metadata

The DXF header can contain $INSUNITS; Autodesk lists values including 0 for unitless, 1 for inches and 4 for millimeters, describing default insertion units for DesignCenter blocks. That field should not replace a check of physical scale in the receiving workflow. A recipient may apply its own interpretation or insertion settings. Autodesk header variables

Autodesk's insertion-scaling support article identifies wrong drawing units, incorrectly scaled original geometry and insertion variables as possible causes of unexpected scale. It recommends measuring the original geometry and checking drawing/insertion units. Use a known dimension, not the appearance of an automatically fitted viewport, to confirm the handoff. Autodesk scaling guidance, 23 September 2026

Original unit-mismatch example: a coordinate span of 100 intended as millimeters represents 100 mm. If a receiver interprets the same span as inches, it becomes 100 × 25.4 = 2540 mm, a 25.4× length error. A planar area scales by 25.4² = 645.16×. Correct unit labeling without correcting already mis-scaled geometry would not repair that result. Establish whether the required correction changes coordinates, interpretation or both.

Preserve the actual entity geometry

A polyline is not necessarily a sequence of straight segments. Autodesk's LWPOLYLINE reference includes vertex coordinates in the object's coordinate system, an elevation, an extrusion direction, a closed flag and per-vertex bulge values. An importer or inspection routine that connects vertices only with straight lines can misread curved segments. Autodesk LWPOLYLINE reference, 2026

For a planar cutting profile, verify the actual plane and transformed geometry, not only whether the display looks flat. Confirm that arcs, circles, splines and any converted segments meet the recipient's accepted representation. If curves are approximated, define the permitted geometric deviation and compare critical features after conversion rather than relying on a smooth-looking screen display.

Autodesk distinguishes graphical entities from nongraphical objects and notes that entity codes occur within block definitions as well as the main entity section. It also warns against assuming a fixed ordering of an entity's group codes. For automated use, select a reader that handles the actual DXF version and entity types; an ad hoc scan of coordinate-looking values is not a complete drawing interpretation. Autodesk object and entity-code guidance

Geometry checks before manufacturing

Inspect intended boundaries for gaps, duplicate or overlapping paths, unintended intersections and extra objects. A closed-polyline flag alone does not prove a simple, non-self-intersecting profile. Conversely, a set of separate entities may form a valid closed loop for a recipient that supports that representation. Agree on the topology and entity requirements of the actual workflow.

Keep a review drawing separate where necessary. Dimension lines, center marks and explanatory text can be useful engineering information but unwanted cutting geometry. Remove them from a production-profile export only when the separate drawing or order preserves the necessary requirements. Do not erase a functional detail merely to silence an import warning.

A formed sheet-metal part additionally needs an agreed flat-pattern basis and bend requirements. A visually plausible outline does not establish bend allowance, finished dimensions or orientation. The material, thickness and processing instructions must remain associated with the exported revision.

A practical release sequence

1. Agree on the recipient's subset: format level, encoding, entities, units and operation conventions.
2. Export the intended geometry: preserve the source and record the selected revision and export settings.
3. Reopen and compare: check a known dimension, overall extents, feature count, curves and intended plane.
4. Check the receiving preview: resolve changed scale, missing geometry or unintended paths before ordering.
5. Release with manufacturing context: include the applicable drawing, material/thickness, tolerance and finish requirements.

SendCutSend explicitly recommends checking overall dimensions in its part preview after upload. That is a useful recipient-specific confirmation, not a replacement for checking all critical design requirements. SendCutSend preview guidance

Source versions and related reference

Reviewed 2026-11-01, America/Los_Angeles. Autodesk references here are explicitly its 2023 import/export, 2024 entity-code and 2026 header/entity/SAVEAS documentation; documentation version labels are not independent publication dates. The insertion-scaling support page prints 2026-09-23. SendCutSend's cited live checklist has no independently verified technical revision date. Original scaling arithmetic is illustrative, not an export or supplier capability claim.

Drawing and model file references