What is a DXF file?

DXF is a plain-text format you can open in any editor. It stores shapes and coordinates rather than pixels, so it stays sharp at any size — a logo scaled to a billboard loses nothing. It is used for CAD and moving data between programs.

The extension is .dxf, and the full name is Drawing Exchange Format. Both matter less than what the file can hold, which is what the rest of this page is about.

Autodesk published it in 1982.

A format that has been readable for that long is a format worth trusting with something you want back in ten years.

It is written down and implementable, though the vendor decides what the next version looks like. In practice that is enough for the file to keep opening; it is not enough to be sure of it.

DXF stores its content exactly. Saving it again changes nothing, so it can be opened, edited and re-saved as often as you like without accumulating damage — which is what makes it a working format rather than a delivery one.

DXF stores the parts of an image separately rather than flattened together, which is what makes it a working file. Almost every format it converts into flattens them, and the flattening is not reversible — keep the layered original.

AutoCAD, LibreCAD and FreeCAD read it, and so do most programs of the same kind.

If a file will not open, the format is rarely the problem — it is more often that the program predates it. Converting to something older is the reliable way past that, and it is what the rest of this site is for.

No browser reads it.

That is the single most common reason to convert it: not that the format is bad, but that the place you want to show the file cannot read it.

DXF is meant to be opened and changed. Keep the file in this format for as long as the work is going on, and export from it whenever a finished copy is needed.

Autodesk published DXF in 1982 so that data could leave AutoCAD, and it succeeded to the point of becoming the interchange format for the whole industry. Every drafting program, every CAM package, every laser cutter and router driver reads it, whatever it uses natively.

That is the entire reason it is still in use. A DWG is AutoCAD’s own file and carries more; a DXF is what you send to somebody whose software you do not know. Fabricators, sign makers, cutting services and machine shops all ask for it, and almost none of them ask for anything else.

DXF has been revised repeatedly since 1982, and a program reading a newer version than it understands will refuse the file or drop the parts it does not recognise. There is no negotiation and often no useful error.

The practical convention is to export to an older version when handing a file over — R12 or 2000 rather than the current one. R12 in particular is understood by essentially everything, at the cost of newer entity types being converted into simpler ones. If a fabricator says your file will not open, exporting to an older version is the first thing to try, and it usually works.

A CAD drawing is organised into layers, and in a production file the layers are instructions rather than decoration: cut here, engrave here, this is a fold line, this is a dimension that should not be machined at all.

DXF carries layer names, colours and line types, so that structure survives the handover. It is also what conventions are built on — cutting services routinely specify which layer name means cut and which means engrave, and a file that ignores those conventions will be machined wrongly rather than rejected. Check the specification before exporting, not after.

A DXF stores numbers. Whether a value of 100 means millimetres, centimetres or inches is a setting on the drawing, and it travels poorly — a receiving program frequently applies its own assumption, so a part detailed in millimetres arrives 25.4 times too large.

For a part that will be cut in metal, this is not a nuisance but an expense. State the intended units in an email, add a dimensioned rectangle of known size to the drawing if the fabricator is unfamiliar, and check the bounding box in the receiving software before anything is cut.

A DXF can hold true arcs, circles, ellipses and splines, and a machine path built from real arcs cuts more smoothly and faster than one built from thousands of short line segments. Exporting curves as curves is worth doing where the option exists.

The other requirement is closed geometry. A cutting path must be a closed loop, and a shape whose ends do not quite meet — a gap of a hundredth of a millimetre — will be treated as an open path and either refused or cut as a line. Joining segments into closed polylines before export prevents almost every rejection a cutting service issues.

DXF is a plain-text format with a distinctive shape: a group code on one line, its value on the next, repeated tens of thousands of times. Nobody reads it for pleasure, and files are large for what they contain.

It is genuinely useful twice. Diagnosis — the header states the version, which answers the most common failure immediately. And bulk edits, such as renaming a layer throughout a file, which is a find-and-replace rather than a CAD operation. A binary variant of the format also exists, is smaller and is rarely used, because the readability is most of the point.

To show a drawing to somebody who has no CAD software, PDF is the answer: it keeps the vectors, prints at a true scale, and opens everywhere. This is the right conversion for approvals, documentation and anything going into a report.

SVG is the answer for the web and for graphic design tools. Both conversions keep the geometry and flatten what makes a DXF a CAD file — layers may collapse, dimensions become drawn lines and text rather than live measurements, and blocks become plain shapes. Convert for viewing, keep the DXF for making.