All Categories

Get a Free Quote

Our representative will contact you soon.
Email
Name
WhatsApp
Company Name
Message
0/1000
why your file won t cut dxf svg and the problems between design and machine-1

News/Blogs

Home >  News/Blogs

Why Your File Won't Cut: DXF, SVG, and the Problems Between Design and Machine

Nov 16, 2026

Why Your File Won't Cut: DXF, SVG, and the Problems Between Design and Machine

Most "Machine Faults" Arrive as Files

A support engineer can usually tell within a minute whether a complaint is about the machine or about the file. The symptoms differ in a specific way: a machine fault is inconsistent, while a file fault is perfectly consistent — it does exactly the wrong thing, every time, in exactly the same place.

That distinction matters commercially. A shop that blames the machine for a file problem stops production, waits for a technician, and often pays for a visit that ends with someone opening the file and clicking one button. A shop that recognises the pattern fixes it in ten minutes.

This article covers the ten things that actually go wrong between a design and a cut. It is written in the order a file travels — from the drawing, through export, into the machine's software, onto the bed — because that is the order in which errors accumulate.

Units and Scale: The Most Expensive Decimal Point

The most common complaint in laser cutting, by a wide margin, is that the part came out the wrong size.

Almost always the cause is units, and almost always it is one of three things.

The file was drawn in one unit system and imported as another. A drawing in millimetres read as inches comes out roughly twenty-five times too large; inches read as millimetres comes out correspondingly too small. The factor is so large that it is instantly obvious — which makes it easy to fix but also easy to be embarrassed by.

The design was made at a reduced scale. Architectural and furniture drawings are often produced at a ratio for printing. If a part is drawn at one fifth of full size, the machine will cut it at one fifth of full size, faithfully and without complaint.

The export applied a scale factor. Some exporters convert units on the way out; some preserve the number and change the label. A file that opens correctly in one program and wrongly in another is almost always this.

The defence is simple and worth institutionalising: put a known dimension in every file. A reference rectangle of a stated size, or a dimension line on the artwork, gives everyone — designer, operator, and any technician — a way to verify scale in one measurement. When a file arrives without one, measuring a known feature before cutting the whole sheet is the cheapest test in the workshop.

Symptom Usual cause First thing to check
Part roughly 25× too big or small mm/in mix-up The import unit setting
Part uniformly small by a round ratio Design drawn at reduced scale The drawing's stated scale
Two programs disagree on size Export applied a conversion Both the number and the unit label

Open Paths: The Cut That Never Finishes

A vector that does not close is not a shape; it is a line that stops. The machine will trace it faithfully and leave the part attached to the sheet, or produce a gap that nobody notices until assembly.

Open paths come from three sources. Breakpoints left by editing — a path split to delete a segment and never rejoined. Traced artwork — auto-tracing often produces outlines that look closed at screen resolution but have microscopic gaps. Imported drawings where two segments share a position but not a node.

The check is to look at the nodes rather than the shape. Zoom to the outline, select it, and look for endpoints — a closed path has no loose ends. Most software can also report whether a selected path is closed.

Two practical notes. Fill the shape and see whether it holds — an open path often fills unpredictably, which is a fast visual test. And close paths deliberately rather than dragging the last node onto the first: a dragged node sits close, not coincident, and the gap returns as a hairline in the cut.

Duplicate and Overlapping Lines: Cutting Everything Twice

The most wasteful file fault is also the most invisible: the same line existing twice.

It happens through copy-paste over an existing outline, through offsetting a curve and deleting the original badly, through merging two versions of a drawing, or through auto-trace producing a doubled contour. On screen it is indistinguishable from a single line.

The consequences are all bad and all avoidable: the beam cuts the same path twice, so the kerf effectively doubles, the edge chars more, the job takes longer, and on thin material the part can fall apart or distort.

Detection is a matter of discipline rather than eyesight. Select all and count objects — a shape that should have one outline and reports two has a duplicate. Look at the cut preview for a doubled path — many controllers draw repeated moves as a heavier line. Weld or union the artwork before export, which removes exact overlaps and joins touching outlines.

A related fault is near-duplicate geometry: two lines a hair apart, from an imprecise trace or a careless offset. Those do not merely double-cut; they can produce a sliver of material that breaks loose during cutting and damages the work or the bed.

Stroke Width: Why the Machine Cuts a Band Instead of a Line

Some software interprets an outline's stroke width as a real width and cuts two parallel paths — one on each side of the stroke — instead of a single centre line.

The result is a slot rather than a cut: the part is undersized by the stroke width on every edge, and on fine detail a small feature can disappear entirely.

The fix is to use a hairline or zero-width stroke for anything that will be cut, and to keep decorative stroke widths for artwork only. The trap is that a drawing can look correct on screen — a heavy line looks like a confident outline — while being wrong for a machine that reads geometry rather than appearance.

Setting What the machine does When to use it
Hairline or zero stroke Cuts on the path, single kerf Cutting geometry
Visible stroke width May cut both sides Never for cutting
Filled shape, no outline Engraves the area, or cuts the boundary depending on layer Engraving, if that is the intent

Text That Is Not Curves

A file containing live text depends on the font being present on the machine's computer. When it is not, the text either substitutes — wrong spacing, wrong shapes — or fails to render at all, and some systems cut a placeholder box.

The rule is unambiguous: convert text to curves before export. Not after the file is sent, not in the machine software, but in the design file, before it leaves the designer.

Two consequences worth knowing. Converting to curves makes the file impossible to edit as text later — so keep the editable original alongside the cut file, named clearly. And converted text increases node count substantially, which brings the next problem.

Layer and Colour Mapping: One File, Several Operations

A single file usually carries more than one intention: cut the outline, engrave the logo, score the fold line, mark a reference. The machine distinguishes them by layer or colour, mapped to operations in its software.

That mapping is where good files become bad parts. A logo intended as an engrave cuts straight through the panel because the colour was mapped to cut. A fold line intended as a score cuts the part in two. The reverse — a cut line mapped to engrave — leaves a panel still attached to its sheet, which is discovered when the operator tries to lift it.

The discipline is a small standard, applied every time: a fixed palette for a fixed meaning. One colour for cut, one for engrave, one for score, one for marks, documented and used by everyone who produces files. Files from outside designers arrive with their own colours, so the layer mapping has to be checked rather than assumed.

Node Density: When the File Is Fine and the Machine Is Slow

Auto-traced artwork and over-detailed vectors can carry thousands of nodes along a contour that needs a fraction of them. The cut is correct and the machine crawls: every node is a change of direction, and the controller spends its time decoding rather than moving.

The symptoms are recognisable. The head hesitates along curves. A job that should run smoothly takes far longer than its length suggests. Curves show tiny facets under magnification rather than a clean arc.

The fix is to simplify the path — most vector software offers a smoothing or reduction function — but with care. Over-simplification changes the shape, and on parts that fit together that change is a tolerance error. Simplify the decorative contours; leave the functional geometry alone.

Embedded Raster and Traced Images

A "vector" file can contain a bitmap. Logo artwork pasted from a web page, a scan, a photograph placed in the drawing — each arrives as pixels, and the machine either ignores it or, if traced, produces the ragged outline of every antialiased edge.

The check is to look at the object list rather than the canvas. A bitmap appears as an image object; a true vector appears as paths. If the job needs the logo cut, the artwork must actually be vector, not merely look like it.

What Did I Cut Twice and Why Is It Slower

Two of the faults above combine into a complaint that reaches every support desk: the job took far longer than expected, and the edge is over-charred.

The usual pair is duplicate geometry and excessive node count — one doubling the path, the other slowing the motion. Neither is a machine problem, and neither is visible on screen at normal zoom. Both are found by selecting the geometry and reading what the software reports about it.

Which Format, and Why It Matters Less Than You Think

Shops ask which format to send. The more useful answer is that format matters less than discipline, because the common faults cross format boundaries.

Still, there are practical differences worth knowing:

Format Strength Watch for
DXF Universal, dimension-aware, preserves units Version differences; some exporters bundle odd entities
SVG Clean curves, web-native Units often implicit; text and CSS effects
PDF Good for proofs and drawings May contain raster, fonts, or print-specific scaling
Native (AI, CDR, DWG) Fully editable Requires matching software version
PLT / HPGL Direct to many controllers Loses layer information

The practical recommendation for a shop receiving files from customers: agree one format, ask for a known dimension inside the file, and check the layer mapping on arrival. Those three habits prevent most of what follows.

A Pre-Flight Check That Takes Two Minutes

Before a sheet is loaded, a short routine catches nearly every fault described above.

Check What it catches
Units confirmed against a known dimension Scale errors
All paths closed Parts left attached, gaps
Object count sane for the shape Duplicate geometry
Stroke width is hairline for cut lines Slot-width cutting
Text converted to curves Font substitution, boxes
Layer and colour mapping reviewed Cut where engrave was intended
Node count reasonable on curves Slow jobs, hesitation
No bitmap hiding in the artwork Ignored or ragged elements
Nesting and spacing checked Parts too close, cut-through
First article cut before the full sheet Everything else, cheaply

The last row is the one that makes the rest optional in practice: cut one part, measure it, and check the fit before committing the sheet. Two minutes against a wasted panel is the best trade in the workshop.

Symptom to Cause: The Table Worth Pinning Up

What you see Most likely cause Where to look
Part the wrong size, in a round ratio Units or drawing scale Import unit setting, drawing scale
Gaps in an outline Open paths Node view, endpoint detection
Edge charred more than usual, job slow Duplicate lines Object count, preview
Part undersized on every edge by a similar amount Stroke width being cut Set hairline stroke
Text cut as boxes or wrong shapes Fonts not converted Convert to curves
Engrave area cut right through Layer mapped to cut Layer/colour mapping
Cut line left as a faint mark Cut mapped to engrave Layer/colour mapping
Head hesitates, curves look faceted Excessive nodes Node count, simplify
Logo missing or ragged Bitmap in a "vector" file Object list
Nothing cut at all Geometry on a hidden or unassigned layer Layer visibility and mapping

Nine of those ten are file problems. That ratio is the reason this article exists: the machine is usually doing exactly what it was told.

Conclusion

A laser is an obedient machine. It cuts what the file describes, at the size the file states, along the paths the file contains, in the operations the layers dictate. Every one of the faults in this article is the machine being correct and the file being wrong.

That is good news, because file faults are cheap. They are found by measuring one known dimension, looking at nodes rather than shapes, counting objects, and cutting one part before cutting a sheet. None of it requires a technician, and all of it can be standardised into a two-minute routine.

The shops with the fewest "machine problems" are not the ones with the best machines. They are the ones whose files arrive in a state the machine can obey.

why your file won t cut dxf svg and the problems between design and machine-2

Get a Free Quote

Our representative will contact you soon.
Email
Name
WhatsApp
Company Name
Message
0/1000