LightBurn 2.0.05
The current stable branch I found in official announcements is LightBurn 2.0.05, released as a patch release on December 3, 2025. Treat this as the baseline for production work unless LightBurn publishes a newer stable build.
LightBurn is powerful laser software, but it is not automatically the right path for every machine. This guide separates the stable branch, 2.1 release-candidate notes, Core vs Pro licensing, xTool Studio caveats, and a safer first-project workflow.
As of May 14, 2026, LightBurn 2.0.05 is the stable release and LightBurn 2.1.00 RC-11 is the public release-candidate branch. Use Core for GCode lasers and Pro for DSP/Galvo. For xTool, P2/P2S have limited LightBurn flat-processing support; P3 and F2/F2 Ultra UV are xTool Studio paths.
Release candidates are public test builds before official release. LightBurn says RC builds are generally stable, but the conservative shop move is to save frequently and avoid testing a new RC under deadline.
The current stable branch I found in official announcements is LightBurn 2.0.05, released as a patch release on December 3, 2025. Treat this as the baseline for production work unless LightBurn publishes a newer stable build.
RC-11 was posted May 1, 2026 as the latest and likely final 2.1 release candidate. Release candidates are useful for testing, but I would not try them first under a customer deadline or on expensive material.
Quick Nest and future nesting tools changed during the 2.1 cycle. Check LightBurn's official Core vs Pro comparison before buying a license specifically for nesting.
LightBurn is layout, device-control, and production workflow software for supported laser controllers. It helps you create vectors, assign layer operations, tune speed and power, preview jobs, manage material libraries, calibrate cameras, and reuse repeatable shop files.
It is not universal magic. Compatibility is controller-based, not brand-name-based. A laser can be mostly compatible while still missing cameras, accessory control, extended axes, rotary behavior, or vendor-specific automation.
The most expensive LightBurn mistake is not the license price. It is buying the wrong license tier for your controller, then discovering that your machine, OS, or camera path does not match the workflow you expected.
Core is the practical default for GCode-based hobby and entry-level machines. That includes many GRBL, Marlin, Smoothieware, FluidNC, grblHAL, and xTool-style GCode workflows when the specific model is supported.
Official pricing page showed $99 USD during the May 14 source check.Pro adds DSP and Galvo controller support on top of GCode. It is the tier to check for Ruida, Trocen, TopWisdom, EZCAD2, EZCAD2 Lite, BSL, and similar production or galvo workflows.
Official pricing page showed $199 USD during the May 14 source check.LightBurn is sold as a perpetual license with one year of updates included. After the update year expires, you can keep using the newest version released during your valid update period.
LightBurn's May 2026 renewal messaging listed a $40 USD update-year renewal and early-renewal bonus months.Current LightBurn 2.x support moved to modern Windows and macOS. LightBurn 1.7 is the fallback branch for Linux, pre-Windows 10, and older macOS systems.
Check your OS before upgrading a shop machine that already runs an older stable install.Start with the controller family, then verify the exact model. LightBurn's own compatibility language separates high, medium, low, and incompatible support levels, and partial support can still mean missing cameras, axes, or vendor automation.
| Machine / controller family | LightBurn status to explain | Reader takeaway |
|---|---|---|
| GCode diode / hobby gantry lasers | Generally supported when controller/firmware is supported. LightBurn Core usually sufficient. | Usually a strong LightBurn candidate once the exact controller, firmware, homing behavior, and profile are confirmed. |
| DSP CO2 lasers | Supported controller family. LightBurn Pro. | A common production-shop LightBurn path when the DSP controller is confirmed and the Pro license makes sense. |
| Galvo / fiber / UV with EZCAD2-class controller | Supported controller family. LightBurn Pro. | A good LightBurn Pro path when the controller, driver, lens setup, and vendor configuration are correctly imported. |
| EZCad3 galvo | Initial 2.1 RC support; Labs planned. LightBurn Pro, 2.1 RC/Labs context. | Promising, but still best treated as a release-candidate or Labs path until the final support story matures. |
| K40 with M2 Nano controller | Not supported by LightBurn without controller replacement. Not applicable unless upgraded. | Do not assume stock K40 compatibility; many K40 owners need a controller upgrade before LightBurn is realistic. |
| xTool P3 | Not LightBurn-supported per xTool FAQ. xTool Studio PC only. | Treat P3 as an xTool Studio PC machine unless xTool publishes a different support path. |
| xTool P2 / P2S | Partial LightBurn support. LightBurn possible for flat processing; xTool software for full functions. | Use LightBurn only for the limited flat-processing workflow; use xTool software when cameras and full features matter. |
| xTool F2 | Not LightBurn-supported per xTool FAQ. xTool Studio. | Treat F2 as an xTool Studio machine, not a LightBurn machine. |
| xTool F2 Ultra / F2 Ultra Single | Not LightBurn-supported per xTool Q&A. xTool Studio / Atomm where noted by xTool. | Do not present F2 Ultra as LightBurn-compatible unless xTool publishes a new support path. |
| xTool F2 Ultra UV | Not LightBurn-supported per xTool FAQ. xTool Studio PC/Mac. | Treat F2 Ultra UV as xTool Studio PC/Mac, not a third-party software path. |
| OMTech / Ruida-style CO2 machines | Often compatible via DSP controller family. LightBurn Pro. | Often a sensible LightBurn Pro path when the actual DSP controller is confirmed. |
Use this source-backed lookup as a first pass, then confirm the exact controller, firmware, vendor profile, camera path, and software support before you change a production workflow.
These rows translate the reference matrix into practical decisions for GCode, DSP, galvo, xTool, OMTech, K40, and closed-ecosystem paths.
xTool support has moved sharply toward Studio on newer machines, so the brand name alone is not enough to answer a LightBurn question.
For most newer xTool owners, start with xTool Studio, not old XCS. xTool describes Studio as the newer platform developed from XCS, says XCS V2.7 was the final XCS version, and says future devices and updates move to Studio.
This is not a universal cut recipe. It is a controlled workflow for learning LightBurn without wasting material, damaging a machine, or teaching a beginner to press Start too early.
Confirm whether your laser is GCode, DSP, or Galvo and whether it needs Core or Pro. LightBurn support depends on the controller and firmware, not just the brand badge.
Try Find My Laser for supported USB machines, but do not assume detection is universal. If it fails, create the device manually or import the vendor/device profile.
Do not begin with a customer piece. Use manufacturer starting settings for your wattage, lens, material, thickness, focus, and air-assist setup.
Use one layer for text or a filled test shape and one layer for a score or cut. The layer settings, not the layer color alone, control speed, power, mode, passes, and air assist.
Preview the job order, travel moves, and cut sequence. Frame on scrap, confirm focus, and usually engrave before cutting so loose parts do not shift.
Confirm exhaust, enclosure/interlocks, wavelength-appropriate eye protection, air assist, and material safety before pressing Start. Never leave the laser unattended.
LightBurn becomes valuable when you stop treating it as a Start button and begin using it as a repeatable production system.
LightBurn color layers separate fill engraving, line scoring, cutting, and tool layers. A practical rule: engrave first and cut last because a cut-free part can shift.
Kerf is the material removed by the beam. For boxes, inlays, ornaments, and press-fit parts, cut a test slot, measure the fit, adjust kerf offset, and save the setting.
Run a material test grid before trusting a recipe from YouTube, Reddit, or a seller chart. Lens, focus, material supplier, moisture, air assist, and real optical power all matter.
LightBurn improved camera calibration in 2.0 and added newer AprilTags calibration paths as Labs work. Built-in vendor cameras are not always accessible, as the P2/P2S caveat shows.
Use nesting as a version-sensitive feature, and build repeatable .lbrn2 templates with material libraries, notes layers, and file names that include material, thickness, and date.
Most first-week pain comes from detection, profiles, coordinates, origin, camera access, USB/network stability, or vendor automation that LightBurn cannot control.
LightBurn controls a laser; it does not make the laser safe. Follow your machine manufacturer's instructions, use proper wavelength-rated eye protection, plan ventilation, keep fire risk in view, and never leave a running laser unattended.
Amazon Support Gear
LightBurn helps dial in the software side, but safe laser work still depends on machine-specific eye protection, exhaust, and cleanup PPE. Match eyewear to your laser wavelength and optical-density requirement; no single pair is universal.
As an Amazon Associate, I earn from qualifying purchases at no additional cost to you.
Use this page for the software decision. Use the machine pages for the deeper hardware comparisons, ownership questions, and vendor-specific accessory notes.
Use this for the full 55W CO2 machine comparison; use this LightBurn guide for the software caveats.
Studio-only noteP3 is an xTool Studio PC path at this update, not a LightBurn-controlled machine.
Model separationKeep the normal F2 Ultra and F2 Ultra UV branches separate when evaluating software support.
Buyer's guideCompare xTool, OMTech, Glowforge, and Gweike when controller/software fit is one piece of the decision.
This guide uses official LightBurn and xTool materials first. Third-party posts can be useful for workflow color, but model support and license claims should come from official sources before they become buying advice.
Yes if your machine/controller is supported and you want deeper layout, layer, material-test, and cross-machine workflow control. Use vendor software when proprietary features are required.
As of the May 14, 2026 source check, official announcements show LightBurn 2.0.05 as a public stable patch release and 2.1.00 RC-11 as a release candidate.
The LightBurn 2.1 docs reviewed are release-candidate docs; release candidates are pre-release builds for public testing.
Core is for supported GCode devices. Pro supports GCode plus DSP and Galvo devices.
Core is listed at $99 USD and Pro at $199 USD; update renewal is $40 USD as of May 4, 2026.
No. LightBurn says the license is not a subscription; updates after the included period require renewal, but compatible released versions continue to work.
Current LightBurn 2.x supports Windows 10+ and macOS 11+; Linux is no longer supported in current 2.x releases.
No, according to xTool’s P3 FAQ; P3 works with xTool Studio PC version only.
Partially. xTool says LightBurn supports only flat material processing and cannot access the P2/P2S camera images.
No. xTool’s F2 FAQ says F2 does not support LightBurn.
No. xTool says F2 Ultra/F2 Ultra Single is no longer compatible with LightBurn.
Avoid unknown plastics and materials that release dangerous gases/dust, including PVC, PVB, PTFE/Teflon, chromium VI leather, beryllium oxide, and halogenated materials.
Common reasons include missing drivers, another app already connected, networked devices requiring manual setup, or Marlin controllers needing manual setup.
Colors assign objects to layers/processes; they are not final output colors. Objects on the same layer share the same settings.