THE RIGHT FILE FOR YOUR WORKBENCH

Your machine.
The right workflow.

Find your machine or controller, choose the right export, and know what to check before loading it. 26 machine and controller families covered.

Reviewed October 19, 2026 · Based on current Makerloom exports and linked primary documentation.

Compatibility describes a workflow, not a certification. A machine profile is a starting configuration. A controller match is an inference from its documented language. An SVG handoff means another application must finish the job. None of these labels means every model, firmware revision or accessory has been tested on hardware. The project owner uses an M2 workflow; we do not publish model-specific hardware validation records.
Profile available

A preset already exists. Verify your real machine settings.

Controller match

Potential direct G-code workflow. Firmware and setup must match.

SVG handoff

Design here, then make the machine-specific job in external software.

FIND YOUR PATH FROM DESIGN TO MACHINE

Machine & controller directory.

Read the controller label or firmware banner in your machine software. The installed board matters more than the frame’s brand name.

26 workflows listed

Profile available

MakerMade M2

M2 controller / Makerhub workflow

Choose in Makerloom
MakerMade M2
Export / handoff
.nc
Run or finish the job in
Makerhub

Primary workflow used by this project’s owner. Manual router operation; Makerloom’s M2 profile omits spindle-start commands. Set the actual work area and work zero. Its 40 ipm feed cap is an application limit, not a material recipe or a manufacturer maximum.

Manufacturer / controller reference ↗Hardware validation pending

Profile available

LongMill · 30 × 30

GRBL or grblHAL, depending on installed board

Choose in Makerloom
LongMill · 30 × 30
Export / handoff
.gcode
Run or finish the job in
gSender

Confirm your installed controller, usable travel, clearance and router/spindle mode. The profile’s nominal board size and speed caps are editable starting values. No model-specific hardware test is published here.

Manufacturer / controller reference ↗Hardware validation pending

Profile available

LongMill · 48 × 30

GRBL or grblHAL, depending on installed board

Choose in Makerloom
LongMill · 48 × 30
Export / handoff
.gcode
Run or finish the job in
gSender

Use the correct 48 × 30 profile, then confirm real travel and controller settings. A longer machine does not imply a higher safe cutting feed. Check the selected units before loading.

Manufacturer / controller reference ↗Hardware validation pending

Profile available

Sienci AltMill

grblHAL / SuperLongBoard family

Choose in Makerloom
AltMill · 48 × 48
Export / handoff
.gcode
Run or finish the job in
gSender

Check the installed board and spindle controls. Configure usable travel and safe feed/plunge caps for your exact setup. Makerloom does not configure the controller or its accessories.

Manufacturer / controller reference ↗Hardware validation pending

Profile available

Shapeoko · 3 / 4 / Pro / 5 / HDM families

Carbide 3D / Carbide Motion

Choose in Makerloom
Shapeoko · configure your model
Export / handoff
.nc
Run or finish the job in
Carbide Motion

The profile deliberately leaves travel and speed limits blank: enter your model’s values. Use separate single-tool jobs. BitSetter, tool-length probing and machine-specific tool-change sequences need the appropriate Carbide workflow; they are not inserted by this generic export.

Manufacturer / controller reference ↗Hardware validation pending

Controller match · verify first

Carbide 3D Nomad

Carbide Motion

Choose in Makerloom
Custom controller check; SVG handoff is an alternative
Export / handoff
.nc after validation, or .svg
Run or finish the job in
Carbide Motion / external CAM

Carbide documents common G-code support, but Makerloom has no Nomad-specific preset or tested tool-length sequence. Configure the small work envelope and spindle correctly; do not copy Shapeoko dimensions. For sensor/tool-change workflows, generate the file in suitable CAM.

Manufacturer / controller reference ↗Hardware validation pending

Controller match · verify first

OpenBuilds LEAD / WorkBee / custom builds

BlackBox X32 grblHAL; other boards must be checked

Choose in Makerloom
Other GRBL / grblHAL router
Export / handoff
.nc / .gcode
Run or finish the job in
OpenBuilds CONTROL or compatible sender

Compatibility follows the installed controller, not the frame name. Enter real travel and limits; confirm spindle/relay operation. Modified builds can differ substantially.

Manufacturer / controller reference ↗Hardware validation pending

Controller match · verify first

Genmitsu 3018-PRO / PROVer family

GRBL-equipped versions only

Choose in Makerloom
Other GRBL / grblHAL router
Export / handoff
.nc / .gcode
Run or finish the job in
Candle / compatible GRBL sender

Check firmware and your exact revision. Set the actual small work envelope, spindle mode and conservative measured cutting settings. Offline-controller file/SD-card requirements vary.

Manufacturer / controller reference ↗Hardware validation pending

Controller match · verify first

Genmitsu 4040-PRO

GRBL-equipped controller

Choose in Makerloom
Other GRBL / grblHAL router
Export / handoff
.nc / .gcode
Run or finish the job in
Compatible GRBL sender

Check the exact revision, homing direction and usable travel. This row does not certify every PRO MAX, RENO or replacement-controller variant. Manufacturer sample files can help establish the expected sender workflow.

Manufacturer / controller reference ↗Hardware validation pending

Controller match · verify first

Other GRBL / grblHAL CNC routers

Verified GRBL-compatible three-axis firmware

Choose in Makerloom
Other GRBL / grblHAL router
Export / handoff
.nc / .gcode / .tap
Run or finish the job in
Sender matched to the installed firmware

A format-based candidate, not a universal machine preset. Verify every emitted command, machine travel, units, Z direction and spindle behavior. A brand label alone cannot establish support.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

Onefinity Original / PRO with Buildbotics controller

Onefinity Buildbotics-based controller

Choose in Makerloom
SVG → machine-specific CAM
Export / handoff
.svg → controller-specific toolpath
Run or finish the job in
CAM with a Onefinity/Buildbotics post, then controller interface

No dedicated Makerloom postprocessor is provided. Import the SVG into suitable CAM and choose the correct post for your controller. A generic GRBL profile is not a substitute.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

Onefinity with MASSO controller

MASSO-equipped machines

Choose in Makerloom
SVG → MASSO-specific CAM workflow
Export / handoff
.svg → correct MASSO output
Run or finish the job in
Suitable CAM / MASSO controller

Treat separately from Buildbotics models. Makerloom does not add MASSO tool-change, probing or spindle macros. Confirm the actual controller and use its correct postprocessor.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

Avid CNC

CNC12 EX or legacy Mach4, depending on machine

Choose in Makerloom
SVG → Avid-specific CAM workflow
Export / handoff
.svg → Avid postprocessor output
Run or finish the job in
Suitable CAM, then CNC12 or Mach4

Avid documents different controller generations. Select the exact machine/controller post, including any spindle, probing and tool-change handling. Makerloom does not supply that postprocessor.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

ShopBot

ShopBot / OpenSBP workflow

Choose in Makerloom
SVG → CAM with ShopBot post
Export / handoff
.svg → .sbp
Run or finish the job in
Suitable ShopBot CAM, then ShopBot control software

Makerloom does not create native .sbp part files. Generate the ShopBot job in compatible CAM. Renaming a .nc file to .sbp does not translate the commands.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

Shaper Origin

Origin’s on-tool workflow

Choose in Makerloom
SVG artwork handoff
Export / handoff
.svg
Run or finish the job in
Shaper Studio / ShaperHub / Origin

Import the artwork, check its physical size, then set cut type, cutter compensation and depth in the Shaper workflow. Makerloom G-code is not an Origin job.

Manufacturer / controller reference ↗Hardware validation pending

Controller match · verify first

GRBL 1.1 diode / CO₂ lasers

GRBL 1.1 with supported M4 laser mode

Choose in Makerloom
Laser → GRBL 1.1 diode / CO₂ controller
Export / handoff
.gcode
Run or finish the job in
Compatible laser G-code sender

Laser mode must already be configured ($32=1), and S maximum must match $30. Makerloom uses M4 dynamic power, S0 travel and millimeters. No Z/focus, air-assist or firmware-configuration commands are supplied. This is conditional on the actual firmware, not the laser brand.

Manufacturer / controller reference ↗Hardware validation pending

Controller match · verify first

SCULPFUN · GRBL-equipped models

GRBL 1.1 dynamic-power models only

Choose in Makerloom
Laser → GRBL, after checking firmware
Export / handoff
.gcode, or .svg handoff
Run or finish the job in
Compatible sender; SVG can be imported into laser software

Check the installed firmware, S scale, work origin and physical bed. Makerloom does not emit the M8 air-assist command; arrange air assist in the manufacturer-approved workflow. Do not assume every model/revision uses the same settings.

Manufacturer / controller reference ↗Hardware validation pending

Controller match · verify first

Smoothieware laser controllers / converted machines

Smoothieware with configured laser module

Choose in Makerloom
Laser → Smoothieware
Export / handoff
.gcode
Run or finish the job in
Compatible Smoothieware sender

Match S maximum to laser_module_maximum_s_value (commonly 1). Output uses G1 S power and G0 S0 travel. A controller conversion does not make a stock K40 board compatible.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

Ruida-controlled CO₂ lasers

Ruida DSP

Choose in Makerloom
SVG artwork handoff
Export / handoff
.svg → native .rd file or supported software transfer
Run or finish the job in
LightBurn with the correct Ruida device

Import SVG and set all laser operations in the destination software. Makerloom does not generate Ruida binary job files. Check the board model and the software/device support.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

Trocen / TopWisdom CO₂ lasers

Trocen or TopWisdom DSP

Choose in Makerloom
SVG artwork handoff
Export / handoff
.svg → .ud5 (Trocen) / .out (TopWisdom), where supported
Run or finish the job in
Laser software supporting the exact controller

These native jobs are not GRBL G-code. Import SVG, choose the exact device and generate its native output in supported software.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

xTool laser families

Model-specific xTool controller

Choose in Makerloom
SVG artwork handoff
Export / handoff
.svg
Run or finish the job in
xTool Studio supported by your model

Recommended route for D1, S-series, P-series and F-series workflows: import artwork and configure the job in the supported xTool software. Model and firmware support varies. No native xTool project/job file is exported by Makerloom.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

Glowforge

Glowforge app workflow

Choose in Makerloom
SVG artwork handoff
Export / handoff
.svg
Run or finish the job in
Glowforge app

Upload SVG artwork and choose cut/score/engrave settings in the Glowforge app. Makerloom’s CNC or laser G-code is not a Glowforge print job.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

Snapmaker 2.0 / Artisan

Snapmaker-specific CNC/laser workflow

Choose in Makerloom
SVG artwork handoff
Export / handoff
.svg → module-specific job
Run or finish the job in
Snapmaker Luban

Import SVG into the appropriate Luban CNC or laser workspace. Rebuild the toolpaths for the installed module. Generic GRBL output is not a substitute for the Snapmaker workflow.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

FLUX beamo / Beambox / supported Beam family

FLUX workflow

Choose in Makerloom
SVG artwork handoff
Export / handoff
.svg → FLUX task
Run or finish the job in
Beam Studio

Import artwork, verify size and assign laser settings in Beam Studio. Makerloom does not produce native FLUX task files.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

Galvo fiber / UV lasers

EZCAD2 / BSL or another model-specific controller

Choose in Makerloom
SVG handoff only where destination supports it
Export / handoff
.svg → supported controller software
Run or finish the job in
LightBurn only for supported controllers, or manufacturer-approved tools

No native galvo output, lens correction, field calibration, hatch timing or marking parameters are supplied. If your vendor app cannot import SVG, a separate supported vector conversion is required. Verify exact hardware/software support first.

Manufacturer / controller reference ↗Hardware validation pending

SVG handoff · external setup

Stock K40 with M2 Nano board

M2 Nano / stock proprietary board

Choose in Makerloom
External SVG workflow; no native Makerloom output
Export / handoff
.svg → compatible K40 software
Run or finish the job in
K40 Whisperer or software supporting your exact board

Do not send GRBL or Smoothieware G-code to the stock board. Confirm the destination’s SVG preparation rules. A replacement Smoothieware/other board must be assessed as a different controller.

Manufacturer / controller reference ↗Hardware validation pending

A FILE EXTENSION IS ONLY PART OF THE STORY

Which file do I need?

FileWhat Makerloom suppliesWhat happens next
.nc · .gcode · .tapPlain-text CNC toolpaths. These suffixes do not translate one controller dialect into another.Use a matching sender/controller. Renaming the suffix changes the name, not the instructions.
.gcode from LaserSeparate GRBL 1.1 or Smoothieware laser output, in millimeters.Use only the matching configured laser controller. CNC router output is not laser output.
.svgVector artwork: outlines, lettering and layers. No CNC depth, feed rate, tool compensation or laser power is encoded as a machine job.Import into suitable CAM or laser software. Recreate operations, tools, layers and machine settings there.
Makerloom project / ZIPEditable project backup, or an archive of separate exported jobs/tiles.A project backup is not machine code. Extract ZIP files and inspect each individual job before loading.
Native controller / app filesMakerloom does not generate .sbp, .rd, .ud5, .out, .lbrn2, .c2d, native galvo or vendor project files.Where supported, import SVG into the appropriate external software and generate the proper output. Some software needs a separate license.

Native DSP file examples follow LightBurn’s file-management documentation. They are not Makerloom export formats.

KNOW WHAT THE FILE IS SAYING

G-code, in
plain language.

These details describe current Makerloom output. They are not instructions to change your firmware settings.

01

Units and positioning

CNC files use G20 for inches or G21 for millimeters, depending on Export units. G90 means absolute coordinates. CNC controls use inches and inches/minute internally; metric export converts XYZ and feed values. Laser exports are always millimeters and mm/min. If the destination displays mm/s, divide mm/min by 60: 600 mm/min is 10 mm/s. A speed entered with the wrong time unit can be off by a factor of 60.

02

Moves and your work zero

Files use G0 travel and G1 cutting moves, with G17 and G94 setup commands. They do not home the machine or establish your work offset. Zero the sender to the same corner/center selected in the design. CNC Z zero is the stock top; laser export uses bottom-left XY work zero and does not position Z/focus.

03

Spindle versus laser power

Manual router mode does not turn the router on for you. Automatic spindle mode adds M3 S…, startup dwell and M5; use it only with verified controls. GRBL laser output uses M4 dynamic power and S0 travel; its S maximum must match the controller. Smoothieware uses its own configured S scale, commonly 1. These modes are not interchangeable.

04

Tools, layers and accessories

Export separate jobs for different tools or cutting layers. Generic export does not provide machine-specific automatic tool changes, probing, BitSetter routines, air assist, autofocus or rotary calibration. The compatibility labels here cover flat vector laser work and conventional three-axis CNC work; they do not certify multi-axis machining or 3D relief jobs.

BEFORE THE FIRST CUT

A quick file check.

  1. Match the installed controller and firmware to the workflow above.
  2. Set actual travel, stock thickness, bit/laser configuration and clearance. Software caps are not recommended material feeds.
  3. Check exported units and dimensions in your sender. After SVG import, verify a known dimension; one inch must remain 25.4 mm.
  4. Choose exactly the letters, backer, shapes or complete job you intend to cut.
  5. Preview the full path, work zero, cutting depth, pass count and travel moves in the destination software.
  6. Use the manufacturer’s setup procedure and an appropriate test on scrap. For a router, check clear travel with the spindle off before the powered run. Supervise the actual job.

If a file will not load.

Confirm that it is an actual toolpath file, not an SVG design, editable project, or unopened ZIP. A different extension alone cannot fix a dialect mismatch. A loading spinner can also be a parsing or file-complexity issue; try a small known-good job to isolate it rather than assuming the USB connection is the cause.

If it imports at the wrong size, check units and SVG import scaling. If your laser software cannot open a Makerloom G-code file, try the SVG handoff and generate a job in that software.

For help, send the machine/model, installed controller and firmware, sender name/version, chosen export/profile and the exact error. Do not send passwords or account credentials.

Ask about your machine ↗

Third-party names identify workflows and references. Listing a machine is not an endorsement by its manufacturer.