Shapefile to DXF converter

Why convert Shapefile to DXF?

People convert a Shapefile to DXF when GIS data needs to enter a CAD workflow. A shapefile holds parcels, boundaries and network layers built in ArcGIS or QGIS, but the engineers and surveyors who need them draft in tools that read DXF instead. The conversion turns GIS geometry into CAD linework on named layers, which lets you drop published parcel boundaries onto a site plan or hand vector features to a design team. DXF also travels cleanly between different CAD tools, so it remains the common drawing exchange format between mapping and engineering.

Coordinate system handling

A zipped shapefile declares its coordinate system in the .prj, and the converter picks that declaration up without any input from you, so the one decision on this page is whether to reproject on the way out. The optional coordinate system box transforms the features before they are redrawn as entities, which is the last convenient moment to move them onto the grid the receiving project is drafted in.

Once written, the DXF holds bare numbers, and no part of the format records which grid produced them. A note in the transmittal email gets separated from the file sooner or later, so put the EPSG code where it cannot drift away: a TEXT entity on a notes layer inside the drawing survives every rename and copy, and it is the first thing a GIS analyst asks for when the file eventually makes the return trip through DXF to Shapefile.

What to check when converting Shapefile to DXF

Two things will not reach CAD: the attribute table and the coordinate system. DXF stores drawing geometry rather than a data table, so export a CSV alongside the drawing if the recipients need the fields. A DXF also carries no coordinate system tag; tell the recipient which system the coordinates are in.

Troubleshooting Shapefile to DXF

• The drawing comes in at the wrong size when inserted into an existing plan. A converted DXF carries no insertion-units flag the receiving template can rely on, so AutoCAD falls back to its own default and an insert can scale by 0.3048 or by 1000. Set INSUNITS in the host drawing to match the data before inserting, or insert with an explicit scale factor.
• Smooth parcel boundaries arrive as chains of short straight segments. A shapefile stores no true curves, only the vertices that approximated them, and the DXF repeats those vertices faithfully. Fit arcs back through the chains with PEDIT in AutoCAD where the drafting needs real curves, or keep the segments as they are for reference linework.
• Parcels and buildings show up as empty outlines. Polygon features become closed polylines, and the solid fills you saw in QGIS were rendering rather than data, so nothing fillable travels with the geometry. Hatch the closed boundaries in CAD where the sheet needs filled areas; HATCH picks them up directly because the polylines arrive closed.
• AutoCAD counts far more entities than the shapefile had features. DXF has no multipart entity, so a feature made of several islands or disconnected segments is written as one polyline per part. The geometry is complete; select the parts and GROUP them in CAD when they need to move as one object.

About the formats

A Shapefile holds finished GIS geometry, parcels, boundaries or utility lines, paired with an attribute table in its .dbf. DXF is where that geometry needs to land when a colleague opens it in AutoCAD or Civil 3D, and the conversion rewrites each feature as CAD linework on named layers. Engineers typically pull a road network or survey parcels out of desktop GIS this way and drop them straight into a site drawing.

Related converters