Running Your Laser Cutter Headless from a Raspberry Pi: LightBurn Bridge and GRBL Web Control

This site already covers running a GRBL CNC router headless from a Raspberry Pi using CNCjs, but diode laser and CO2 laser owners running LightBurn are stuck with a different reality: LightBurn is a full desktop application that most people run tethered to a Windows or Mac laptop sitting next to the machine. That works fine on a bench, but it means the laser can't run unattended overnight, can't be queued from another room, and ties up a full-size computer for a machine that mostly just needs to receive G-code and execute it. This guide covers the real options for getting a laser cutter running headless from a Raspberry Pi — LightBurn's own network rendering feature, and the GRBL-native alternatives when LightBurn isn't in the picture at all.

Option 1: LightBurn Bridge Mode (Keep LightBurn, Move the Heavy Lifting)

LightBurn has a feature specifically built for this: a "Bridge" mode where a lightweight LightBurn Bridge application runs on a Raspberry Pi connected directly to the laser controller, while the full LightBurn design application keeps running on your normal desktop or laptop over the network. The Pi-side Bridge software receives the fully rendered job (already converted to the laser's native command language, not raw G-code) and streams it to the controller in real time, while your desktop LightBurn instance can disconnect entirely once the job starts — the laser keeps running even if you close the laptop or walk away from the network. This is the closest thing to "headless LightBurn" without giving up LightBurn's editor, camera alignment, and material library features.

Setting Up LightBurn Bridge on a Pi

• Install Raspberry Pi OS (Lite is sufficient; you don't need a desktop environment on the Pi itself) and connect it to your network via Ethernet for reliability
• Download and install the LightBurn Bridge package for ARM/Raspberry Pi from LightBurn Software's downloads page
• Connect the laser controller (Ruida, GRBL board, or supported controller) to the Pi via USB, exactly as you would to a laptop
• Start the Bridge service on the Pi; it advertises itself on the local network for discovery
• On your normal desktop LightBurn install, select the Bridge-connected Pi as the active device instead of a directly-connected USB port — from this point, design and job setup still happens on your desktop, but execution routes through the Pi

The practical benefit is you keep every LightBurn feature you already rely on — camera capture and alignment, the material test grid, nested-cut ordering — while the actual cutting continues even if your laptop goes to sleep, disconnects from WiFi, or you close the lid.

Option 2: GRBL-Native Web Control (No LightBurn License Needed)

If your laser runs plain GRBL firmware (most budget diode lasers, including many Ortur, Sculpfun, and Longer Ray5-class machines) and you're willing to give up LightBurn's editor for something more web-based, the CNCjs approach from our Raspberry Pi CNC guide applies almost directly — CNCjs doesn't care whether the GRBL controller on the other end of the USB cable is driving a spindle or a laser diode, it just streams G-code and reports status. The practical difference for laser use is in how you generate the G-code in the first place, since you lose LightBurn's laser-specific power/speed curve tools and have to rely on a G-code generator (Inkscape's laser extensions, jscut, or LaserGRBL's own G-code export) that understands laser-specific commands like M3/M4 spindle-as-laser mode and dynamic power scaling.

ApproachKeeps LightBurn Editor?Runs Fully Unattended?CostBest For LightBurn BridgeYesYes, once job startsIncluded with LightBurn licenseAnyone already using LightBurn who wants headless execution CNCjs (GRBL laser)NoYesFree/open sourcePlain GRBL lasers, budget setups without a LightBurn license LaserWeb / other GRBL laser web UIsNoYesFree/open sourceLaser-specific web control with some laser-aware settings CNCjs lacks

Network Rendering Considerations

Whichever path you choose, the network link between your design computer and the Pi matters more for a laser than it typically does for a CNC job, because engraving jobs (as opposed to vector cuts) can be enormous streams of tiny G-code moves for raster image engraving. LightBurn Bridge handles this well because it pre-renders the job on the desktop side before streaming to the Pi, so the Pi never has to parse the raw raster data itself. If you go the GRBL-native web-UI route instead, be aware that very dense raster engraves can produce G-code files in the tens of megabytes, and a Pi Zero or Pi 3 can struggle to buffer and stream that smoothly compared to a Pi 4 or 5 — use at least a Pi 4 if you're doing serious photo-engraving work rather than mostly vector cuts.

Safety Reminder for Unattended Operation

Running a laser unattended, even briefly, raises the stakes on fire safety specifically because there's no one in the room to notice a flare-up starting. Never leave a laser cutting or engraving unattended without a smoke detector in the room, a fire extinguisher rated for the material you're cutting nearby, and ideally a camera feed you can check remotely. Materials that can flare (acrylic edges, some woods with resin pockets, anything with an unknown coating) are a bad candidate for unattended jobs regardless of how good your remote monitoring setup is — headless control is for convenience and workflow, not a substitute for the judgment you'd apply standing next to the machine.

Whichever path fits your machine and software, the payoff is the same: a laser cutter that can run a multi-hour engraving job overnight, get queued from your phone, and free up the laptop that used to be chained to the bench for the duration of every job.