What is a .dxf file?

What a DXF actually is

Open one in a text editor and you will see pairs of lines all the way down: a number, then a value. The number is a group code that says what the value means, so 10 is an x coordinate, 20 is a y, and 8 is the layer a thing sits on. Entities are stacked in sections, and the section that matters most is ENTITIES, because that is the drawing itself.

Autodesk created the format in 1982 so that AutoCAD could exchange drawings with other software, and they publish the reference. That is the whole reason DXF is everywhere: a laser cutter, a plasma table and a router can all read a drawing without anyone licensing AutoCAD's native DWG.

Text and binary

Most DXF files are the plain text form described above. There is also a binary form, which begins with the literal words AutoCAD Binary DXF and is smaller but not human readable. Plenty of software writes only text, and plenty reads only text, so if a file is rejected without explanation the binary form is the first thing to check. Saving again as an ASCII or text DXF usually fixes it.

Units are declared, and that is unusual

A header variable called $INSUNITS records what one drawing unit means: 1 for inches, 4 for millimetres, and so on. That makes DXF better behaved than STL or plain OBJ, where the numbers arrive with no statement of what they measure.

The catch is that the variable is optional. A drawing saved without it has coordinates and no declared meaning, and every program that opens it applies its own default. If a part comes in at 25.4 times the size you expected, an inch drawing has been read as millimetres.

Model space and paper space

A DXF holds the drawing itself in model space, and the sheets it gets printed on in paper space: title blocks, borders, viewports, notes. Cutting software usually wants only model space, which is why an imported drawing sometimes arrives with a rectangle around it that nobody asked for. That rectangle is a sheet border that came through with the geometry.

The versions

DXF is versioned alongside AutoCAD releases, from R12 through the AC1032 generation. R12 is the lowest common denominator and the safest thing to ask for when a machine or an old program refuses a newer file. It has no support for some later entity types, so a drawing saved back to R12 can lose features it never had a way to store.

What tends to go wrong

Splines, hatches, dimensions and text are entities that many downstream tools either ignore or draw differently. Blocks are reusable symbols placed by reference, so a drawing can look complete while the geometry lives somewhere else in the file. And a drawing built for viewing may have overlapping or duplicated lines that a cutter will happily cut twice.