3DPrinterOS Review

3DPrinterOS is worth considering if several people share your printers and you need control over who submits, approves and starts each job. It puts printer management, uploaded files and user access in one cloud service you reach through a browser. People can submit jobs while staff decide what gets printed.

The main drawback is that your printers won’t necessarily support the same workflow. Some still need desktop slicing or a separate computer to connect them. For one person with one printer, I’d first consider the existing printer software or OctoPrint. A shared lab has more reason to pay for 3DPrinterOS.

Connecting Your Printers to 3DPrinterOS

Check your exact model and firmware—the software inside the printer—before choosing a plan. You need four separate answers: can 3DPrinterOS prepare its files, queue its jobs, monitor its progress and control printing? A supported-printer listing alone doesn’t answer all four.

Most connections use the 3DPrinterOS Client, a small program running on a nearby computer or Raspberry Pi. Windows, Ubuntu and Raspberry Pi installation options are documented; the general connection guide warns that macOS clients may not work with the latest macOS versions. Some printers, including the Dremel 3D40 and 3D45, have a built-in connection option using an access code.

For a client-based setup, install the client, connect the printer, then select its model in the Add Printer wizard. Follow the model-specific instructions for USB or network access. For example, supported Prusa network printers still require a separate client host; having Wi-Fi doesn’t eliminate that computer.

Bambu setup adds more conditions. Current instructions recommend the Beta client, require printer storage for job uploads, and call for Developer Mode on newer firmware. Test the camera connection as well as sending a file.

There’s also an important distinction for industrial equipment: 3DPrinterOS can maintain a queue from which an operator downloads jobs and transfers them manually. That’s useful tracking, but it doesn’t establish remote machine control. Ask for a demonstration on your equipment, including what still happens at the printer.

Preparing a File in the 3DPrinterOS Online Slicer

Slicing turns a model into instructions for the printer, usually called G-code. Upload an STL model, select the appropriate slicer and printer profile, then prepare the file. A profile is a saved set of settings for a particular printing setup.

3DPrinterOS now documents Slicer 5, based on Cura, alongside dedicated Prusa, Bambu, MakerBot and Formlabs slicers. Older references to Slicer 3 or the legacy Cloud Slicer are outdated: both are marked discontinued. Available apps and settings also depend on your organization’s configuration.

For a teaching lab, restricting beginners to approved profiles is a useful option. Experienced users can have more control over settings such as layer height, how much plastic fills the inside, and supports—the temporary structures that hold up overhanging parts. The controls differ between slicers: some Expert tabs show settings you can read but can’t change there.

You can also upload externally prepared G-code, provided your permissions allow it, and associate it with the correct printer type. This lets you keep a desktop slicer that already works for your parts.

Bambu’s AMS, its automatic material-changing system, is one reason to keep your desktop slicer. AMS multicolor jobs still need local slicing and a .gcode.3mf upload. Cloud support for single-plate Bambu 3MF projects doesn’t remove that requirement. Formlabs has another limitation: its cloud-sliced file belongs to one physical printer, and its viewer doesn’t show the sliced layers. Use PreForm when you need to check those layers.

Magic Fix remains documented for repairing or converting 3DS, 3MF, AMF, OBJ and STL files. Check dimensions afterward: it automatically shrinks objects above 50 cm to one-tenth their size and enlarges objects below 2 mm tenfold. Inspect the repaired model before printing. Choose cloud slicing for the workflow it offers; don’t expect better quality or faster processing simply because it runs online.

Sharing Printers Through 3DPrinterOS

Imagine a student submitting a small enclosure. The administrator first gives them access through an invitation, an organizational joining rule or a workgroup code. A workgroup connects a set of users with particular printers and permissions. If you’re joining a school lab, use its instructions before buying a personal subscription.

The student uploads and slices the enclosure, chooses a printer and submits it to the queue, optionally adding a note for the operator. With the default Can Queue permission, they can’t start printing or change printer settings. Staff can inspect the submission before starting it.

That permission has a less obvious restriction: the student can’t see the full queue or cancel even their own job. Organizations can customize queue access to allow cancellation. Can Print is much broader; by default, it allows starting, pausing, resuming and canceling other queued jobs too. Give that access deliberately.

Once printing begins, the dashboard shows printer status. Job records can include notes, logs and camera recordings when configured. Administrators can export cancellation reasons, making those records useful when reviewing rejected work. Quotas and print-duration limits can also help you set rules for shared equipment.

A university student consultant reported in 2024 that receiving prepared jobs made the process more efficient, but students sometimes ignored cancellation notes and resubmitted unsuitable files. You’ll still need a clear way to explain rejected work.

Wentworth’s School of Architecture and Design uses 3DPrinterOS for submissions to its Additive Technologies Lab and also provides guidance for preparing jobs in PrusaSlicer. Follow that lab’s own access rules if you’re printing there.

Keep approval separate from AutoQueue. That optional feature, enabled through support, distributes jobs and starts them automatically. It doesn’t support Formlabs jobs or AMS slot selection. A queue that waits for staff and one that starts the next job solve different problems.

When Your 3DPrinterOS Connection Drops

For the hosted service, a working internet connection is necessary to send new jobs from the cloud. If that connection fails, you can’t rely on the cloud dashboard to check progress or control the printer. An “Offline” status means the printer isn’t connected to the cloud; it doesn’t, by itself, tell you whether the physical print has stopped.

What happens to a print that’s already running depends on the connection. On documented Prusa USB connections, the client sends G-code line by line. Bambu network jobs are uploaded to storage on the printer. You can’t assume both methods will behave the same way during an outage.

Before committing, have the supplier demonstrate what happens when internet access drops while the local network stays connected, then explain recovery after a client or printer restart. Verify whether an interrupted job resumes, needs restarting, or requires an operator’s decision. Don’t use the ordinary Resume button as evidence of recovery after a failure.

One specific warning is documented: logging out of the local Client stops its service, disconnects printers and interrupts active prints. That’s different from leaving the cloud dashboard. The Client also has an Offline mode, but that label doesn’t establish offline cloud slicing or a complete replacement for the hosted workflow.

File handling matters even when the connection works. You can download your accessible files and delete files in bulk; files shared with you carry download restrictions. Keep original designs and working print files outside the service too.

The privacy policy allows account-deletion requests and says personal information and system logs may take up to 30 days to be fully deleted, with retention exceptions. That isn’t a blanket promise to erase every backup immediately.

For organizational access, single sign-on lets people use their existing school or company login. Private-cloud and on-premise server deployments are also offered. If your files have specific restrictions, confirm the storage location, backup retention, export process and applicable security documentation in your agreement. Deployment options alone don’t answer those questions.

What You Pay for With 3DPrinterOS

3DPrinterOS is a paid service after the trial. Premium’s advertised base allowance is two printers and one user. Education and Enterprise use custom pricing, so a lab with many students should request an organizational quote instead of treating Premium as a classroom license. Workgroup file sharing specifically requires an organizational license.

Ask for a quote that spells out your printer and user allowances, storage limits, required integrations and support. The plan page includes support across plans and lists priority service commitments and setup assistance for Enterprise. Confirm the response hours and commitments you would actually receive.

Separate the subscription from installation costs. You may need client computers or Raspberry Pis, their power supplies and storage, cameras, and help configuring the network. Someone also has to maintain profiles, change permissions as people join or leave, and handle rejected jobs. A centralized dashboard still needs an administrator.

Historical announcements about an open-source 3DPrinterOS client don’t make the hosted service free or establish the license of every current component.

If your main requirement is browser control of one compatible printer, OctoPrint is the closest useful alternative. Its software is free and open source, with monitoring and print controls; you supply and maintain its host. That can cost less in software fees, though it isn’t an equivalent quote for a managed institutional workflow.

For a shared lab, judge value by whether submissions arrive ready for staff to review, permissions match your rules, and operators spend less time chasing files. Try it with your usual users and the kinds of jobs they submit.

Should You Use 3DPrinterOS?

I’d shortlist 3DPrinterOS for a school, makerspace or team where managing access and submissions has become a job in itself. Its documented permissions and queues address that problem directly, and institutional use supports that recommendation.

For a small team, the decision rests on how much coordination you actually need. If everyone already submits suitable files and knows which machine to use, another service may add administration without removing much work. For an individual, I’d start with the printer’s existing workflow or evaluate OctoPrint if browser control is missing.

The deciding step is a demonstration using your printer, firmware, typical file and intended user permissions. Include file export and connection-loss recovery. If an essential step can’t work on that setup, keep your current workflow. If the full process fits, 3DPrinterOS deserves a trial before you commit the whole lab.