Why a DXF looks right in your design app but fails in CAM
It opens perfectly. Everything is in the right place. And the cutter rejects it, or cuts something that is not what you drew. The reason is structural: a viewer and an importer read different parts of the same file.
The core mismatch
A viewer’s job is to put pixels on screen. It reads whatever it recognises, draws it, and skips the rest — usually without telling you. Looking correct is the easiest bar in the whole pipeline to clear.
A CAM importer’s job is to build closed regions and turn them into toolpaths. It needs to know which loops have an inside, which are holes, which side is scrap, and how far to offset for kerf. Geometry that draws beautifully can be completely unusable for that.
“It looks right” is not evidence that the file is right. It is evidence that one program could draw it.
1. Entities that get silently dropped
Not every CAM tool supports every DXF entity. When an importer meets one it does not understand, the common behaviour is to skip it and carry on — so you get a part with a missing feature rather than an error message.
The usual offenders are hatches, dimensions, proxy and custom objects from vertical applications, and blocks that were never exploded. Splines are the interesting case: nearly everything can draw one, but tools differ in how they convert one to a toolpath, and some refuse.
What to do: export to R12 ASCII when your tool offers it. R12 predates most of the exotic entity types, so exporters are forced to write simple lines, arcs and polylines that everything understands. If your service publishes a supported-entity list, that list beats any general advice.
2. Model space versus paper space
A DXF holds your actual geometry in model space, and any printable sheet layouts separately in paper space. What you see on screen may be a layout — with a title block, a border, and a scaled viewport looking into the model.
Most cutting workflows read model space only. If you drew in a layout, or your geometry is arranged for printing rather than cutting, the importer can come back with nothing, or with the border and title block treated as cut geometry.
What to do: confirm your cut geometry lives in model space at real size, and that the layout is empty or absent. This tool does not read paper space at all, by design.
3. Blocks that were never exploded
A block is a reference: the file stores the shape once and then says “put a copy here, rotated, scaled.” A viewer resolves those references happily. An importer may not resolve them the same way, may not apply the transform identically, or may ignore them.
Xometry states plainly that files “cannot contain inserts or multiple assembled components”. Explode blocks before exporting so the geometry is really there rather than referenced.
4. Units the file never declared
Your design app knows it is working in millimetres because you told it. That knowledge lives in the application, and it only reaches the file if the exporter writes it into the header. Plenty of exporters do not, or write the wrong value.
On screen this is invisible — the drawing looks the same whatever a unit means. At the cutter it becomes a part that is 25.4 times the wrong size. This has its own article: my DXF is the wrong size at the cutter.
5. Defects that are smaller than a pixel
A contour with a 0.001 mm gap is closed to your eye at every zoom level you would ever use. Two lines on identical coordinates draw as one line. Neither is visible in principle — not because you were not looking carefully, but because the screen has no way to show them.
The importer, working in exact arithmetic, sees both immediately, and both are grounds for rejection at an automated service.
The general lesson
Every stage in this pipeline reads a different subset of the file, and each one fails quietly in its own way. Your design app skips what it cannot draw. The importer skips what it cannot toolpath. Nobody tells you what was skipped.
That is the entire argument for checking the exported file rather than trusting the drawing you were working in. It costs seconds, and it is the only step that looks at what you are actually about to send.
You can check a DXF here in your browser, without installing anything and without the file leaving your machine.
Free. No account, no sign-in, and no permissions requested. Your drawing is never uploaded.