Keep the editable project and the machine-ready output as separate, identified files. Saving artwork preserves the ability to edit; exporting a job prepares output for a particular supported controller workflow. Do not assume the file that opens correctly on a computer can run directly from a card on the X1S Pro.
LightBurn's File menu documentation distinguishes project saving from controller-dependent output commands. The recurring buyer problem is deciding which file to retain and which file an operator should use, especially when a reusable design becomes a production job.
Two files, two different questions
The editable master answers, “What artwork and settings were approved?” The output copy answers, “What exact job was prepared for this machine workflow?” A visual proof helps identify appearance, but it is not a substitute for either file.
Use revision labels consistently. An operator should be able to connect the order record, master, preview and output copy without opening every file in a downloads folder. Preserve the machine configuration used during preparation as part of the job record, without assuming that copying a filename preserves those choices.
| X1S Pro handoff item | Evidence to retain |
|---|---|
| Editable project | Revision and original storage location |
| Output copy | Exact filename produced by the documented procedure |
| Transfer method | Current machine instructions used |
| Visual proof | Dimensions, orientation and approved quantity |
| First sample | Operator, date and acceptance result |
Work through a hypothetical revision
Suppose an order for twelve signs changes from “Room 6” to “Room 9.” The artwork master is updated, but yesterday's output copy remains in the transfer folder. Both files can exist without either being corrupt. The failure is releasing the wrong revision.
Create the revised output through the current documented machine procedure. Move superseded files out of the active release location while retaining the archive. Compare the new output preview with the revised visual proof where the supported workflow permits. Have the receiving operator identify the intended text and orientation before any powered work.
Run a supervised sample on matching, documented compatible material using the verified setup. Confirm the actual mark and dimensions before the twelve-piece run. Record the accepted output filename so a later reorder does not depend on memory. This example is a shop control procedure, not a particular filename extension or TF-card recipe.
What the X1S Pro listing establishes
The X1S Pro page lists LightBurn, TF-card and offline workflows. Its design-format list does not prove direct execution of each format. Obtain the exact export and transfer instructions for your configuration before relying on offline production.
For photo orders, include file identification in the operator image-preparation assessment. If a correctly prepared job still stops before output, the first-console-error recording method describes useful troubleshooting evidence; it does not establish that different models share identical controller behavior.
Can I rename a project file to the machine's expected extension?
No. Renaming changes the label, not the file's contents or controller instructions. Use the supported export process and verify the resulting job instead.
Do I need the master after a successful offline run?
Yes. Revisions, replacement parts and later troubleshooting require a reliable editable source. Keep the successful output too, with enough information to distinguish it from later changes.
