LightBurn 2.2.00 Early Access Adds True Nest and Project Tools
LightBurn 2.2.00 Early Access adds True Nest, Center Line Trace, multi-page projects, 3D model import, a local/network API, and native macOS ARM builds.
LightBurn has announced 2.2.00 as an Early Access release that can be installed beside the current official release. The announcement names True Nest, Center Line Trace, multi-page projects, 3D model import, a local/network REST API, and native macOS ARM builds. True Nest is a Pro-only feature, and the release is not a stable version.
An Early Access update with workflow additions
It can be installed beside the current official release, but it is not a stable version.
LightBurn identifies True Nest as a Pro-only feature.
LightBurn says the REST API is for local or network use and does not replace direct operator supervision.
ReportLightBurn announcement
A separate test install for new nesting and project tools
LightBurn says 2.2.00 Early Access can be installed beside the current official release. Its announcement names True Nest, Center Line Trace, multi-page projects, 3D model import, a local/network REST API, and native macOS ARM builds. True Nest is Pro-only.
We have not tested LightBurn 2.2.00 Early Access. This report reflects LightBurn's announcement and its stated limits; Early Access is not a stable release. Treat this as a test release, not a reason to change a working production setup. LightBurn cautions that low-resolution Center Line Trace inputs can create offshoots. Its API is local or network based, and the company says it is not a substitute for direct operator supervision.
How to try it safely
Start with a copy of a familiar project and one feature. For Center Line Trace, use a clean, adequately detailed input and inspect the result for offshoots before sending a job. For the API, keep a directly supervised operator in the loop; the announcement describes local or network use, not unattended control.
Who should investigate this next: This release is useful for LightBurn users who can isolate a test setup and have a specific nesting, multi-page, import, or integration task to evaluate. Keep your current official software in place for production work until the new workflow has been proven on your own files.
- Which new feature solves a repeated problem in your own files?
- Does a duplicate project produce the expected result before you change a production workflow?
Wait if:You need a stable, repeatable setup for jobs that cannot tolerate a software change.
Try Early Access if:You can install it beside your current release and test a copy of a representative project under direct supervision.
Published Early Access details
| Announced field | LightBurn 2.2.00 Early Access |
|---|---|
| Release state | Early Access; not a stable release |
| Installation | Can be installed beside the current official release |
| True Nest | Pro-only |
| Center Line Trace | Low-resolution inputs can create offshoots |
| API | Local/network only; direct operator supervision remains required |
Sources: Official announcement
Test an Early Access copy before changing a working laser workflow.
Use the current official release for work that has to ship.
Install Early Access alongside your current release and try a duplicate of a representative project before changing a regular process.
Official Early Access details checked
LightBurn describes 2.2.00 as Early Access, with a separate installation alongside the current release.
Primary pages and records used for this report.
Have a launch, correction, or test opportunity?
Brands, product teams, and knowledgeable sources can send relevant details, approved media, or corrections. Coverage is selected independently.
Choose the useful next step.
Keep production work on the current official release and test any Early Access feature on a copy of a real project before relying on it.
Get the next useful workshop update.
When a source-backed change affects what to buy, update, test, or ignore, we send a short decision brief with the evidence, the workshop consequence, and what remains unknown.
Know what changed. Know what it means at the bench. Decide whether to act, wait, update, test, or ignore.
Scanned daily. Sent only when the signal changes a workshop decision, with a rare alert when waiting would matter.
See how The Workshop Signal works