SolidWorks DXF to CNC Nesting — What Nesting Software Actually Expects

SolidWorks exports flat patterns correctly. Nesting software imports DXF correctly. The problem is that what SolidWorks produces by default and what nesting software expects are often misaligned — and the failures are silent. Profiles import with no errors but cut the wrong features. Bend lines disappear. Splines approximate differently on each machine. Scale is off by 25.4×.

This post covers the specific mismatch between SolidWorks DXF output and what ProNest, SigmaNEST, Lantek, and similar nesting tools expect, and the exact export configuration changes that fix it.

How Nesting Software Identifies Operations

Every nesting tool assigns a cutting or marking operation to each profile in the DXF based on which layer that profile lives on. There is no standard — each software vendor implements its own layer mapping system, and each shop configures it differently. The common thread is: one operation per layer, and each layer must be configured before import.

An unconfigured nesting installation treats everything as a cut layer. Bring in a SolidWorks flat pattern that has bend lines, form tool boundaries, and cut profiles all mixed on default layers, and the machine will attempt to cut geometry that was never meant to be cut.

ProNest (Hypertherm)

ProNest maps DXF layer names to operation types through a configurable alias system. In Settings → Importing Parts, you define aliases that tell ProNest which layer names correspond to which process. Multiple aliases can be comma-separated, allowing files from different shops with different conventions to coexist in the same ProNest configuration.

ProNest operation categories:

• Exterior — the outer part boundary (typically layer CUT or 0)
• Interior — holes and interior cuts (CUT_INNER, INT, or HOLE)
• Open — non-closed profiles assigned to a cut process (requires explicit mapping)
• Special Open — profiles assigned to both cut and another process
• Scribe — surface marking operations (ETCH, SCRIBE, or MARK)
• Punch — punch process (PUNCH or DRILL)

An important ProNest behavior: an Open profile layer must also be mapped to a cut process or ProNest will reject it. Profiles assigned to both a cut and a scribe process become “Special Open.” If you have open geometry on a scribe layer (e.g., a partial engraving path), it must either be mapped explicitly as Special Open or closed into a complete profile.

SigmaNEST

SigmaNEST offers two integration paths for SolidWorks files. The first is standard DXF import with its own layer mapping. The second — and the reason it appears on more demanding fabrication floors — is CAD Import Direct: a direct SolidWorks API integration that bypasses DXF entirely. CAD Import Direct pulls geometry, feature data, bend line information, hole recognition, and BOM data directly from the SolidWorks model. Material, thickness, and part number come through automatically without re-entry.

For DXF import specifically, SigmaNEST supports automatic error correction for common DXF problems (gap bridging, duplicate geometry removal) and has dedicated sheet metal DXF options including bend line customization and drill/hole type recognition.

If your shop uses SigmaNEST and is experiencing DXF import problems, the direct API integration eliminates the DXF step entirely and is worth evaluating before spending time on DXF configuration.

Lantek Expert

Lantek identifies operation type by DXF layer name and/or entity color. Layer-to-process mapping is configured in Lantek’s CAM settings and is customer-defined. Forum discussions from SolidWorks engineers using Lantek confirm that Lantek reads specific layer names for cut vs. etch/mark operations, and that the configuration must be done in Lantek before DXF files will classify correctly on import.

Cross-software layer naming conventions

While no universal standard exists, these conventions are consistent enough across software and forum discussions to treat as defaults until a vendor specifies otherwise:

The universal rule: every layer that appears in your DXF must be configured in the nesting software before import. Any unconfigured layer defaults to cut.

Seven SolidWorks DXF Export Problems for Nesting

1. Spline entities (most common failure)

SolidWorks exports curved geometry as DXF SPLINE entities (NURBS with control points and knot vectors) by default. Many nesting tools do not implement full NURBS parsing:

• Some approximate splines with too few polyline segments → flat facets appear on curved part edges
• Some throw a parse error and skip the spline → missing profile segments → open contour error on import
• CNC G-code natively handles only linear and circular moves; splines sent to the controller are approximated at the machine level with unpredictable tolerance

Fix: In SolidWorks flat pattern DXF export, enable “Map to Polylines” and set chord tolerance to 0.05–0.1mm for production parts. This outputs arc-fit LWPOLYLINE entities that every nesting tool reads correctly. For tight curves on precision parts, use 0.001–0.025mm chord tolerance. Access this via: File → Save As → DXF → Options → Export Options → Map splines to polylines.

2. Open contours

Nesting algorithms require strictly closed loops to identify part boundaries and hole boundaries. A gap of even 0.001mm between line endpoints breaks the contour parser — the software sees disconnected line segments rather than a unified closed profile. The result is an “open contour” warning on import and the part is rejected.

Open contours originate from:

• Sketch geometry with tiny gaps from over-constraints or precision mismatches
• Flat pattern fold definitions with unresolved sketch segments
• Spline end-point rounding errors during DXF export

Fix: Before DXF export, run a sketch repair on the flat pattern. In the DXF export options, enable “Merge faces” if available. In nesting software, check whether the error correction settings can automatically bridge gaps under a configurable tolerance (SigmaNEST’s error correction handles this; ProNest requires pre-fixed geometry).

3. Units mismatch — the 25.4× scale error

The DXF $INSUNITS variable encodes the file’s unit system: 1 = inches, 4 = millimetres, 0 = undefined. SolidWorks templates default to different unit systems depending on whether you’re using an ANSI (inches) or ISO (metric) drawing template.

When SolidWorks exports in inches and the nesting software defaults to millimetres — or vice versa — the imported part is 25.4× too large or too small. A 10-inch bracket imports as a 254mm bracket; both are plausible sizes for sheet metal, so the error isn’t always caught visually.

Fix: Check File → Properties on the flat pattern before export. Confirm $INSUNITS in the DXF file using a text editor. Ensure your nesting software’s import unit setting matches the DXF unit variable.

4. Block references produce empty geometry

When SolidWorks DXF is exported from a drawing view of a flat pattern (rather than directly from the part’s flat pattern), geometry is often embedded as INSERT/BLOCK references. Nesting tools that don’t resolve block definitions import the file as empty or as a single reference point at the origin.

Fix: Export DXF directly from the flat pattern: with the part open in SolidWorks, select the flat pattern feature in the feature tree, then File → Save As → DXF. Do not export from a drawing view. If you must export from a drawing, run EXPLODE in AutoCAD/DWG TrueView before sending to nesting software.

5. Bend lines missing in SolidWorks 2022 and later

This is the change that catches the most shops off guard.

• Pre-SolidWorks 2022: Bend lines were automatically exported to a layer named BEND in flat pattern DXF files.
• SolidWorks 2022+: The automatic BEND layer was removed. Bend lines are not included in DXF export unless the user explicitly configures a custom DXF mapping.

If your shop upgraded to SolidWorks 2022 or later without reconfiguring the DXF export template, your flat pattern DXF files are silently missing bend reference lines. Press brake operators are working without them.

Fix for SolidWorks 2022+: File → Save As → DXF → Options → select “Custom Map SOLIDWORKS to DXF/DWG” → add an entry mapping “Bend lines – up direction” to a layer named BEND with line style Section (dashed). Do the same for “Bend lines – down direction” if your parts have downward bends.

The line style must be Section, not Hidden (dashed-hidden). Fabrication software including SendCutSend has confirmed that hidden-style bend lines are not detected by their import tools — the geometry must be on the Section linetype.

Apply this mapping in the SolidWorks system options so it persists across future exports: Tools → Options → Import/Export → DXF/DWG Output → configure the custom map and save it as a template file (.slddxfmap).

6. Form tool geometry appearing as cut profiles

SolidWorks form tools — louvers, dimples, ribs, lances, struck-outs — leave their sketch boundary in the flat pattern. When exported to DXF without layer mapping, these boundaries appear as closed interior profiles on the default cut layer. Nesting software classifies them as holes and adds cut operations for features that should not be cut.

Fix: Map form tool geometry to a non-cut layer: in the DXF export options, add a mapping rule for “Form tool features” or similar (the exact label depends on SolidWorks version) to a layer named FORM or DIMPLE. Configure that layer in your nesting software as a marking or informational layer, not a cut layer.

7. Hidden lines from drawing views included as geometry

When exporting from a drawing view rather than directly from the flat pattern, geometry behind faces may be included as visible entities in the DXF. Nesting software sees these as additional profiles — either duplicate geometry or false boundaries — and creates spurious cut paths or boundary validation errors.

Fix: Export from the flat pattern directly (see fix #4). If drawing-based export is required, confirm the DXF export options are set to export only visible geometry, not hidden lines.

Entity Types: What Nesting Software Handles

The practical rule: target LWPOLYLINE entities for all profiles. Every nesting tool reads them correctly. Avoid SPLINE and ELLIPSE entirely by configuring the SolidWorks polyline map.

Configuring SolidWorks DXF Export for Nesting

A minimal working configuration for most nesting tools:

In SolidWorks Tools → Options → Import/Export:

1. Set DXF version to R2000 or later (R12 is missing spline-to-polyline conversion support)
2. Enable “Map splines to polylines” with chord tolerance 0.05mm
3. Enable “Custom Map SOLIDWORKS to DXF/DWG”

In the custom map:

In SolidWorks File → Save As → DXF export options:

• Select: “Export this configuration’s data only”
• Uncheck: “Include hidden edges from drawing view”
• Check: “Merge faces” to close minor gaps in flat pattern sketch geometry

Save this as a .slddxfmap template and load it on every machine in the shop. Consistent layer naming across machines means nesting software configuration only needs to be done once.

Part Naming and Material Handoff

Nesting software identifies parts by DXF filename and assigns material/thickness manually or through configured filename conventions. SolidWorks does not embed material or gauge in DXF geometry — the three approaches shops use:

Filename encoding: Include material and thickness in the filename — e.g., Bracket_01_3mm_SS316.dxf. Operators manually match the filename to the material when loading the nest.

Layer name encoding: Encode material in the layer name — e.g., CUT_3mm_SS316. ProNest and SigmaNEST can map layers with specific names to pre-configured material/process combinations.

Text annotations in the DXF: SolidWorks can include part number and material notes as text entities on an informational layer (e.g., spec). SigmaNEST’s direct API import and some other tools can read these annotations. ProNest can extract spec text if it’s on a layer named spec — contact your ProNest configuration for the exact layer name.

The cleanest solution for high-volume SolidWorks shops is SigmaNEST’s direct API integration: material, thickness, BOM quantity, and bend data flow directly from SolidWorks without DXF mapping configuration at all. For shops that prefer DXF (for flexibility, compatibility with multiple machines, or multiple downstream tools), the custom layer mapping approach above handles 95% of import problems.

For the upstream step — actually getting flat patterns out of SolidWorks assemblies efficiently — batch DXF export from SolidWorks assemblies covers the per-body and per-configuration export workflow. For the specific export entity settings that affect output quality, SolidWorks DXF export settings in detail covers the Options dialog systematically. And for context on what fabricators need from DXF files beyond geometry, see what fabricators actually need in your DXF files.

If your shop also runs waterjet machines with specific lead-in geometry requirements, DXF file preparation for waterjet cutting covers the tolerance and lead-in conventions that differ from laser cutting workflows. For laser shops specifically, kerf compensation in SolidWorks DXF for laser cutting covers where kerf offset belongs in the workflow — and why it isn’t in the CAD file.