SVG to Gcode: 6 Ways to Do It, and Which One Fits Your Machine

There are at least six ways to get from SVG to G-code, and most comparisons rank them by price or by feature count. Both are the wrong measure.

The right one is narrower: what does each route cost you the second time? Almost every job comes back. The logo gets wider, the material arrives at a different thickness, the customer orders twelve more with one change. A method that takes ten minutes the first time and ten minutes again on every revision is expensive, however free it was to download.

This guide walks through the realistic routes, what each is genuinely good at, and how to pick one based on your machine, where you draw, and how often the work repeats.

Three questions before you pick anything

What are you cutting? A pen plotter needs almost nothing. A diode laser needs power and passes. A router cutting parts needs tool compensation, depth stepping and holding tabs, or the parts come out undersized and loose.

Where does the drawing come from? If you design inside your machine software, no SVG is ever created and nothing needs saving. If you design in CorelDRAW or Illustrator, the export happens on every revision.

Will the job come back? One-offs and production work reward completely different tools. This is the question most people skip and then regret.

Six ways to get from SVG to gcode

1. Browser-based SVG converters

Upload an SVG, set a feed rate, download a .nc file. These are the tools most people find first when they search for an SVG to gcode converter. No installation, no account, nothing to learn.

Good at: single parts, pen plotting, simple engraved outlines, and getting an answer in two minutes.

Limits: most stop short of full CAM. Several state plainly that pocketing, holding tabs, Z-depth and tool compensation are out of scope. Nothing is saved between sessions, so every revision starts from an empty form.

Cost of revision two: you do the whole thing again.

2. Inkscape with gcodetools

Free, local, and the default recommendation in maker forums. Inkscape works in SVG natively, so the drawing and the toolpaths never leave the same program.

Good at: hobby work on a budget, and anyone already fluent in Inkscape.

Limits: the plugin has its own logic for orientation and depth, documentation is scattered across versions, and setup takes patience. Design capability is solid but not a match for a dedicated graphics program on typography and traced artwork.

Cost of revision two: low, because the drawing and the toolpaths live in the same place.

3. Laser software

LightBurn and comparable programs import SVG and handle power, speed and passes properly, with layer-based parameters and a good preview.

Good at: everything laser. If your machine is a laser and your artwork is simple enough to build in the program itself, this is a clean workflow with no export at all.

Limits: laser only. Add a router or a plasma table and you need a second program and a second set of habits. Drawing tools cover shapes, text and boolean operations, but design-heavy work still happens elsewhere.

Cost of revision two: low if you drew it there, full export cycle if you did not.

4. Dedicated SVG to gcode converters

Standalone tools built for one job: read a vector file, write G-code. Offsets, ordering and machine-specific output.

Good at: repeatable output for a known machine, without a CAM learning curve, and without uploading a customer's artwork anywhere.

Limits: they take a file, which means the export already happened. Interfaces are often thin and support depends on the maintainer.

Cost of revision two: re-export, re-import, re-enter the settings.

5. Full CAM software

Fusion 360, SheetCam, CamBam. Tool libraries, operations, simulation, postprocessors.

Good at: complex parts, tight tolerances, and shops that already run a CAM package for other reasons.

Limits: a second program to buy, learn and maintain. Setups are saved, which helps, but they are saved separately from your drawing, so the two can drift apart.

Cost of revision two: moderate. The setup survives, but the SVG has to travel again.

6. A CAM plugin inside your drawing program

The route most comparisons leave out: instead of moving the SVG to the CAM software, put the CAM software where the drawing already is.

Good at: design-driven work that gets revised. Logos, signage, engraving, traced artwork.

Limits: it ties you to one drawing program. If you do not use that program, this route does not exist for you.

Cost of revision two: open the file, change the drawing, regenerate.

The criterion nobody puts in the table

Every SVG to gcode comparison lists features. Almost none lists what happens when the drawing changes, and that is where the real time goes.

Run the numbers on your own work instead of taking anyone's word for it. Take the last job you revised. Count the minutes from the customer asking to the machine running again, and mark which of those minutes were drawing, which were cutting, and which were neither. The third group is what your workflow costs you, and it is invisible until you look for it.

For a one-off, that number does not matter and a free converter is the correct answer. For anything that repeats, it is the only number that matters.

If you draw in CorelDRAW

This is route six, and it only applies if CorelDRAW is where your artwork lives. CamDRAW is a plugin for it, not a standalone converter. If you work in Inkscape or Illustrator, one of the first five routes is your answer.

If you do use CorelDRAW, the SVG step disappears in both directions.

Drawing you made yourself. Set the operations on it and generate the program. No export, no unit assumption, nothing to verify.

File you received. Import the SVG into CorelDRAW and set the operations on the imported curves. This is where a drawing program earns its place, because a downloaded SVG usually needs fixing before it can be cut: outlines that are strokes rather than shapes, text that is a font reference rather than curves, embedded bitmaps hiding inside a vector wrapper, and duplicate paths stacked exactly on top of each other. All four are drawing problems, and you are already in a drawing program.

For the last of those there is a dedicated function. CamDRAW searches the drawing for duplicate curves, lists them, and removes them individually or all at once. On traced or downloaded artwork it regularly finds paths nobody knew were there, each of which would otherwise be cut twice.

The duplicate search finds stacked paths before the machine cuts them twice.

One plugin, not one machine type

The practical difference from laser-only software: the same interface covers laser, plasma and waterjet cutting, contour and pocket milling, drilling, and contour and area engraving. A shop running a diode laser and a small router does not need two workflows and two sets of habits.

Machining decisions are set per operation. Tool on, inside or outside the line with the diameter applied from the tool library. Depth and passes. Lead-ins and lead-outs, linear or tangential, set separately. Material tabs so parts stay fixed in the sheet. Cutting order optimised by shortest path or exactly as drawn. Adjustable curve precision that defines the segment length directly.

Contour cutting for laser, plasma and waterjet, with passes and cutting height per operation.

Postprocessors for more than sixty machines and controllers are preconfigured, from GRBL, Mach3 and LinuxCNC to Langmuir CrossFire, Estlcam, EdingCNC and industrial routers, and each can be edited to match your machine. Check the specifications for the full list and for supported CorelDRAW versions.

Why revision two is fast

Operations, tools, zero points, cutting data and precision are stored inside the CorelDRAW document. Save the CDR and the job saves with it. Reopen it next month, widen the logo, regenerate the program. Nothing to rebuild, one file, and no question about which version is current.

The finished program is rendered in 3D before the machine runs it.

Try it on a file you already know. Start the free trial, import an SVG, and set two operations. There are step-by-step tutorials if you would rather watch first.

Which route fits you

• Pen plotter or a single engraved outline. A browser converter. Anything more is overhead.

• Diode laser, artwork built in the machine software. Stay there. No export means nothing to save.

• Hobby budget, comfortable in Inkscape. Inkscape with gcodetools.

• Router cutting parts to size. Anything without tool compensation and holding tabs will cost you material. Full CAM, a capable desktop converter, or route six.

• Several machine types. One tool that covers all of them beats three that each cover one.

• Design-heavy work that gets revised, drawn in CorelDRAW. Route six, because the export is the part you repeat.

• A file from a customer you will never see again. Whatever is fastest. Nothing here needs to last.

Frequently asked questions

What is the best way to convert SVG to gcode?

There is no single best way. For a one-off outline, a browser converter is faster than anything else. For parts cut to size, you need tool compensation, depth passes and tabs, which most simple converters skip. For work that gets revised, pick the route that keeps the drawing and the machining settings together, because that is where the repeated time goes.

Is there a free SVG to gcode converter?

Yes. Browser-based tools work without installation, and Inkscape's gcodetools plugin is free and runs locally. Both handle straightforward outlines well. What they usually leave out is tool compensation, pocketing, tabs and depth passes.

Why is my SVG the wrong size after converting?

A resolution mismatch. SVG measures in pixels, and programs disagree on how many pixels make an inch, commonly 96, 72 or 90. Work in real units and measure one known dimension after import, every time.

Does converting SVG to gcode lose quality?

The geometry itself survives. SVG stores Bezier curves, so shapes arrive intact, and the curves are approximated into machine moves at whatever precision you set. What gets lost on the way is everything that is not geometry: fills, gradients, masks, live text and embedded bitmaps. If an SVG looks right in a browser but produces almost nothing in a converter, the design is usually a bitmap inside a vector wrapper and needs tracing first.

Why is my cut part smaller than the drawing?

The toolpath is running on the line, so the tool removes material from the part itself. The error equals the tool or beam diameter. Set the contour to outside for parts and inside for holes, with the correct diameter stored.

Do I need SVG at all if I cut on my own machine?

No. SVG exists to move drawings between programs. If you draw in CorelDRAW and cut on your own laser, router or plasma table, you can generate the program inside CorelDRAW and skip the exchange format, imported files included. Related reading: exporting SVG from CorelDRAW and getting from DXF to G-code.