Submitting a Print Job

Print jobs in Pluraprint start as a sliced file: a file from your slicer (such as Bambu Studio or PreForm) that’s already been prepared for a specific printer. Pluraprint reads this file to figure out the printer model, estimated print time, and materials needed. Orca 3MF uploads can also provide optional slicer settings such as infill density, whether supports are enabled, and layer height; administrators can use those values in rules.

Step 1: Open Upload#

Open Upload from the sidebar (it’s listed near the top, above “Operations”).

Step 2: Select your file#

Drag your sliced file onto the upload area, or select browse to choose it from your computer. Pluraprint accepts one file at a time.

Step 3: Upload and processing#

Once selected, the file uploads with a progress indicator. After storage completes, an upload receipt shows its reference and processing state. Processing continues if you leave the page.

Step 4: Review the receipt#

The receipt lists every executable plate separately. A sliced multi-plate 3MF creates one job per valid plate; each has its own name, status, requirements and approval. Held or skipped plates remain visible with an explanation. A valid plate does not disappear because a sibling is invalid.

Use each job’s action to configure its details or open preparation. Missing target or material details require definition before approval. Your jobs do not print merely because the upload was accepted. Select Upload another file when you’re ready to submit another file.

Station uploads show the same per-plate receipt. Prepare each job independently through the station’s preparation flow. Policy restrictions leave a job available for an operator to resolve.

Embedded slicer images and vendor screenshots take precedence. Each 3MF plate uses its own image. When an image is missing, Pluraprint renders a shaded preview from that plate’s G-code in the background. The same fallback applies to .gcode and .bgcode uploads without thumbnails. Slicer-marked purge lines, wiping moves and skirts are omitted to keep the object in view. Unsupported motion or resource limits can make the preview unavailable without invalidating the print file. File-declared filament colors are illustrative; they do not verify the material physically loaded in a printer.

Uploading from OrcaSlicer#

With an OctoPrint connection to Pluraprint, both Upload and Upload and Print upload the file for preparation and review. Either button works; neither starts a print. The resulting jobs follow the same requirements and approval process as browser uploads.

After you submit#

Your job doesn’t print immediately. First, Pluraprint builds a requirements checklist for it based on your organization’s rules, for example, it might need someone to confirm the materials, or need approval from staff. Once everything on the checklist is satisfied, the job is queued and will print when a compatible printer is available.

On the Prepare Print Job screen, this checklist updates as you change the job details. Every job requires an identified Job owner before it can queue. Approval identification appears when the active rules require it. A change to the owner, job name, or an approval is reflected immediately. Pluraprint checks the current requirements again before queueing.

If something goes wrong while uploading or parsing your file, you’ll see an error message with a Try again option.

If you have permission to assign printer reservations, upload offers a Reservation choice when current reservations exist. Choose one before selecting the file to hold the job for those printers. See Reserving Printers.