Designing Custom PCB Outlines: Fixing DXF and SVG Import Failures

A non-rectangular board almost always starts outside the PCB editor: a mechanical engineer hands over a DXF file, or a designer exports an SVG, and the shape needs to become the board's edge cuts layer.

The handoff breaks often: a vague error appears, the shape loads at the wrong scale, or nothing appears at all. An import DXF board outline error rarely means the file is corrupt; it usually means the file was built for CAD software, which tolerates geometry a PCB editor's import engine rejects. This guide covers the common failure modes and how to fix them.

Key Takeaways

• DXF board outline errors typically trace back to open paths, unit mismatches, or unmapped layers in the source file.
• A "path not continuous" error clears once every open endpoint gets closed, ideally by converting the geometry to one closed polyline before export.
• Agreeing on file format, units, and layer content with the mechanical engineer beforehand prevents most outline import errors before they happen.

Why You Get an Import DXF Board Outline Error

PCB editors reject non-rectangular outlines for specific, diagnosable reasons. Whatever the error message says, an import DXF board outline error usually reduces to one of five causes:

• Open paths: Boolean operations in the CAD tool leave micro-gaps at a seam that trigger a "path not continuous" error.
• SVG coordinate mismatches: pixel units instead of millimeters, or an origin offset the PCB editor doesn't account for.
• Unsupported curve types: splines and complex arcs the PCB editor approximates poorly or rejects outright.
• Unmapped layers: the DXF layer holding the outline was never assigned to Edge.Cuts or the board outline layer.
• Unit scale errors: the CAD tool exported in inches while the editor expects millimeters, so the board comes in sized like a postage stamp.

Fixing "Path Not Continuous" DXF Errors

A "path not continuous" error means the outline has at least one endpoint that never connects to another segment, even if the contour looks closed on screen.

What typically creates the gap:

• Boolean operations: a union or subtract leaves a sliver gap where two profiles meet.
• Coincident, unmerged endpoints: two segments occupy the same point but are still separate entities.
• Split arcs on export: some exporters break a single arc into disconnected fragments.

Closing Open Paths by CAD Tool

PCB editors typically set a small tolerance for path closure, so gaps under that threshold snap shut and gaps beyond it fail. When a CAD tool keeps producing open contours, convert the outline to one closed polyline before exporting.

Fixing SVG Import Problems

SVG files fail on a different set of issues than DXF, mostly because SVG was built for screens rather than fabrication. A few export practices resolve the common SVG import problems:

• Set units to millimeters before export. Most PCB editors expect SVG import at millimeter scale rather than the pixel-based default. Check your editor's import settings to confirm, since SVG itself defaults to pixels at 96 DPI. Importing at pixel resolution without adjusting for this produces a board sized nothing like the intended outline.
• Flatten every transform and group. Nested groups and unresolved transform matrices shift coordinates the import engine can't reliably reverse.
• Convert strokes to paths. PCB editors read filled shapes rather than stroke width, so a stroked outline imports as a zero-width line.
• Export cleanly from Illustrator or Inkscape. In Illustrator, run Outline Stroke, then flatten transparency. In Inkscape, run Path \> Union and set document units to mm before exporting.

Importing Custom Outlines into Flux

Flux imports DXF and SVG files directly into the PCB editor's layout shape tool, and the same path-continuity rules apply. A DXF file for a Flux board outline can contain lines, splines, arcs, circles, and ellipses; polylines are excluded, and the geometry must form a single closed polygon. A file exported with polylines needs those exploded into simple lines and arcs first, the same step KiCad requires for its own DXF import.

Preview the imported shape before assigning the geometry to the board outline. Flux snaps closed geometry within its coordinate tolerance and flags shapes it can't resolve into a clean loop. Set the import origin to match the existing board coordinate system, or the new outline will land offset from components already placed on the board.

Building a Clean CAD-to-EDA Mechanical Handoff

Preventing an import error costs less time than fixing one after the mechanical engineer has moved to the next revision. A few agreements upfront remove most of the failure modes above:

• Agree on format and units first. Confirm DXF or SVG, and millimeters or inches, before the drawing starts.
• Use DXF format R14 or 2000. Newer format versions introduce compatibility issues older, stable formats avoid.
• Deliver simple closed polylines instead of surface bodies. A 3D CAD export carries surface data a PCB editor can't parse; request a flat 2D profile instead.
• Send only the outline, cutouts, and mounting holes. Dimension lines and construction geometry on the same layer often import along with the shape and need manual deletion.

This same outline becomes the board-outline layer in your final Gerber export. Correct geometry at the import stage prevents another cleanup pass before fabrication. See our guide to JLCPCB Gerber file requirements for what that layer needs to look like on the way out.

Bring the Next Outline in Clean

Custom board shapes only need one clean import to reach the board outline layer. Flux validates path closure and layer mapping when a DXF or SVG comes into the layout shape tool, and catches an import DXF board outline error before it costs a revision. Bring in your next custom outline using Flux's DXF and SVG import documentation.

FAQs

Why does my DXF board outline fail to import?

How do I fix a path not continuous error in a PCB editor?

Can I import an SVG as a PCB board outline?