You import the DXF and nothing shows up? Four failures look exactly like this.

No error message, or a useless one, and an empty canvas. The file is probably not empty. Four unrelated problems all end in the same blank import, and because the symptom is identical, staring at the screen cannot tell you which one you have.

Cause 1: binary DXF, ASCII expected

DXF exists in two flavours. The common one is plain text; a rarer binary variant packs the same data more compactly, and most laser and hobby CNC importers, LightBurn included, read the text flavour. You can check in any text editor. An ASCII DXF opens as readable pairs of group codes and values, like this:

  0
SECTION
  2
HEADER

If the editor shows unreadable garbage instead, you have a binary DXF. Re-export it as ASCII from the source CAD, or open it in a CAD that reads binary and save it back out as a text DXF.

Cause 2: the file is truncated

Interrupted downloads, half-synced cloud folders and botched copies leave a DXF that stops in the middle of an entity. Strict parsers then discard everything; AutoCAD-family tools report "Invalid or incomplete DXF input, drawing discarded", while friendlier importers show nothing at all. Encoding damage behaves the same way: a file re-saved as UTF-16 or with a byte order mark in front can defeat a parser even though it looks normal in an editor. The fix is not repair but replacement: transfer the file again, or have it exported fresh at the source.

Cause 3: nothing the importer understands

A DXF can be complete, valid and full of geometry that a 2D importer still skips: 3D solids, proxy entities written by specialised AutoCAD verticals, or blocks the importer never resolves. It reads the whole file, finds nothing it can draw, and presents an empty canvas with a clear conscience. The cure is to re-export from the source CAD targeting ASCII DXF R12 or 2000. Those older dialects predate most of the exotic entity types, so exporters write plain lines, arcs and polylines that every importer knows.

Cause 4: the version is too new

DXF has grown through many releases, and an importer built against an older one may skip sections it does not recognise, sometimes everything. The symptom and the fix are the same as cause 3: save as an older dialect, R12 or 2000, and import that. Nothing about your geometry changes; only the container does.

A five-minute diagnosis workflow

First, the text editor: readable group codes mean ASCII, garbage means binary, and a file that visibly just stops is truncated. Second, a free viewer: open the file in LibreCAD, DraftSight or Inkscape. If the geometry appears, the file is fine and your importer is the picky one, so re-save as ASCII DXF R12 or 2000 from the viewer and import that instead. Carbide Create users report the smoothest route is LibreCAD followed by an SVG export. If the geometry does not appear in the viewer either, stop fiddling and get the file re-exported at the source. Hand-repairing a header in a text editor is possible for advanced users, but it only pays off when a re-export is truly impossible.