PNG to DXF for laser cutting: the whole workflow

Greg Dlubacz

Design Engineer

There is no converter that turns a PNG into a DXF in one honest step, and the ones that claim to are doing the same thing you'd do by hand, just without telling you what they threw away.

A PNG stores pixels. A DXF stores CAD entities: lines, arcs, polylines, splines. Nothing in the first file knows anything about the second. The pixels have to be interpreted into geometry, and interpretation means decisions. Where exactly is the edge of that shape? Is that a cut line or an engraving fill? How big is it in millimetres?

Those decisions get made either by you or by a converter guessing. This is the workflow for making them yourself.

Start by deciding what's a cut and what's an engrave

Before you touch any software, look at your image and separate it into two things:

Cut paths. Outer silhouettes and interior cutouts are usually closed paths. Open paths are valid too, for score lines, slots, and single-line details. What matters is that you know which is which. Your CAM software decides how each path is processed, including power, speed, and number of passes.

Engrave areas. Filled regions, texture, shading. These are raster or fill operations in most laser software, and they often don't belong in the DXF at all.

People skip this step and then wonder why their traced logo produced 200 overlapping shapes. They traced a filled design and expected cut lines.

If your artwork is a solid black silhouette on white, you're in good shape. If it's a photograph or a shaded illustration, the honest answer is that you need to simplify it first, either by hand or by reducing it to a clean two-tone image.

Prepare the raster

The quality of the trace is set here, not in the tracer settings.

Get the highest resolution you can. A 200px logo blown up to cutting size gives you jagged, stair-stepped edges that survive into the vector.

Make it genuinely black and white. Not dark grey on off-white. Push the levels so the shape is solid and the background is clean. Every intermediate grey pixel is an edge the tracer has to guess about.

Reduce anti-aliasing where you can. Soft edges are a common cause of doubled outlines in the result.

Crop tight and clean up noise. Stray pixels, JPEG artefacts, watermarks, scanner dust. All of it traces.

Trace to vector

Run it through Tracer and export DXF, or trace to SVG first if you want to edit in Illustrator or Inkscape before converting.

Either way, this is where the distinction between an outline trace and a filled trace matters. Tracing a filled black shape gives you the region; tracing its boundary gives you a cut path. For a laser, you generally want the boundary.

The three checks that save jobs

Here is where most tutorials stop and most problems start.

Look for doubled contours. Depending on the tracing method, a filled black shape can come back as two paths that look like one: the outer edge and a second edge a fraction of a millimetre inside it. On screen they're indistinguishable. On the machine, the laser cuts both, and you get a hairline ring of char or a part that falls apart.

This isn't universal, so check rather than assume. Select the outline and move it aside; if a second path stays behind, you have duplicates. Then preview the toolpath in your CAM software, which shows you what the machine will actually do rather than what the drawing looks like.

Check the counters. The holes in letters like A, O, R, and any enclosed areas in a symbol. Two different things can go wrong here.

If the trace filled the counter with a white shape instead of leaving a hole, the laser sees two closed paths and cuts both, and the inner piece drops out as scrap. Sometimes that's exactly what you want. The problem is when it isn't, and you only find out after cutting. This article covers how to spot and fix it in the file.

Separately, if you're cutting letterforms as a single piece, a real counter leaves its centre unsupported. The middle of an O has nothing holding it in place once the hole is cut. That's physics, not a file error: add bridges before cutting, or plan for it coming out as two parts.

Check the scale. This ruins more jobs than everything else combined. A raster image has pixel dimensions and possibly a DPI tag, neither of which reliably tells your machine how big the thing should be. A DXF can carry unit information, but don't assume it's set correctly, or set at all. AutoCAD's INSUNITS can be zero, meaning unitless, and plenty of files in the wild are.

Set a known dimension before you export. Pick a measurement you can verify, the overall width for example, and make it an exact number. Then confirm it in your CAM software before you press go.

Tracer exports DXF in millimetres with the longest side set to 100mm. That's a known starting point rather than your final size, so scale it to the dimension you want in your CAM software before cutting.

Verify in your actual software

Open the DXF in the program that will drive the machine, not just in a preview. Lightburn, Fusion 360, whatever you use. Preview tools render DXF generously; CAM software is pickier about open paths, duplicate entities, and unsupported entity types.

Look for three things: that the units came through as you intended, that every path meant as a closed cut is actually closed, and that nothing is sitting outside the bed.

Then cut a test on scrap. A clean DXF is not the same thing as a correct job: power, speed, focus, and material all sit between the file and the result, and your machine's documentation is the authority on those, not an article. A two-minute test on offcut material catches the things a screen can't show you.

What this is worth doing for

Vectorizing an image gets you a cut file in minutes for work that would otherwise be an hour of tracing by hand in CAD. For logos, silhouettes, line art, stencils, signage, and most of what a small shop cuts day to day, that's the whole job.

Where it stops being worth it is precision mechanical parts. If the thing has to fit something else, draw it in CAD with real dimensions. A traced outline is accurate to the pixels it came from, and pixels are not a measuring tool.

Tracer exports DXF with Pro. SVG export is free, so you can check the trace quality before you decide.