Bambu Lab Authorization Control System

On January 16, 2025, the 3D-printer manufacturer Bambu Lab announced that future firmwares for its 3D printers would introduce an authorization and authentication mechanism for printer connection and control, in the name of security. The change restricted the use of third-party accessories and slicers such as Panda Touch and OrcaSlicer, and it gated print initiation, motion control, fan and hotend control, AMS configuration, calibrations, remote video, and firmware upgrade behind a Bambu-issued authentication path. Bambu Lab also publishes its own slicer, Bambu Studio, under the AGPL-3.0, while its Terms of Use § 3.4 forbid users to modify, copy, reverse engineer, or create derivatives of "the Product." In April 2026, this authorization system became the basis for a cease-and-desist demand against a Polish community fork maintainer who had restored direct printer control on top of the AGPL source.

Controversy regarding firmware updates

Bambu terms regarding printer functionality and potential for disrupted print jobs if users do not update to a new firmware that radically restricts the autonomy of the owner of the printer

Potential for remote disabling of printers

A concern raised by the community revolves around the wording in Bambu Lab's Terms of Service (ToS) and firmware update announcements. Critics and users argue^{[citation needed]} that the phrasing leaves open the possibility for the manufacturer to remotely disable printers that are not updated to the latest firmware. Specifically, Bambu Lab's ToS warns that printers may block new print jobs if updates are not applied, which some users interpret as a potential pathway for forced obsolescence. While defenders of Bambu Lab point out that offline modes such as SD-card printing and LAN-only setups would remain functional, others point out that the ToS do not explicitly limit this restriction to cloud-based printing. This ambiguity has led to speculation that Bambu Lab could enforce broader limitations, effectively rendering printers inoperable for users who choose not to update.

Editing of initial announcement

Bambu users were concerned they would not be able to use their printer if they did not install this update, due to the wording of the blog and the ToS. This caused confusion since users report that Bambu's blog post dated January 16, 2025 includes the FAQ entry:

What happens if I never upgrade to this firmware? You may continue using an older firmware version that does not include the new security updates; however, this means the printers may miss out on important security fixes or bug patches included in newer versions. We highly encourage updating to the latest firmware version for the best experience and enhanced security.

However, this was not present on the day of the announcement. A snapshot of their webpage from archive.is demonstrates this section did not exist on the day of the announcement, when community members voiced their concerns. Bambu's response to community feedback references "social media posts spreading baseless allegations and untrue claims about Bambu Lab", including "Firmware updates will block your printer's ability to print.", without mentioning the context for those allegations. The context for those allegations was the lack of inclusion of the "What happens if I never upgrade to this firmware?" in Bambu's initial announcement alongside their stated terms of service.

After the edit, the announcement header reads Updated: January 17, 2025 and notes that additional details and FAQs (including the "What happens if I never upgrade to this firmware?" entry) were added.

The earliest archive.is snapshot of the announcement, dated January 16, 2025 17:31 UTC, contains two passages about staying on the old firmware. Under "Important Information for End Users":

2. Old Firmware Option: Users who decide to use an older firmware version can still use the previous or new versions of Bambu Studio and Bambu Handy without restrictions.

Under "Information for OrcaSlicer users":

1. You can continue using your X Series 3D printer with the older firmware version (which does not include Authorization Features). 2. If you choose to upgrade to the firmware version with Authorization Features, you must download and install Bambu Connect (a printer control software).

The FAQ section was added after the initial blog post publication and is noted as an update in the announcement header.

Debate over "bricking" terminology

The debate has also extended to the definition of "bricking". Some community members assert that if a printer is unable to accept new print jobs without an update, it effectively becomes non-functional and qualifies as being "bricked." Others counter that as long as certain offline functionalities remain (such as SD-card printing) the term does not accurately apply.

Privacy policy issues

Bambu Lab's privacy policy describes that when a user submits a print job through Bambu cloud, Bambu may forward configuration information, printing settings, model picture, plate thumbnails and G-code files (referred to in the policy as "Printing Files"), and when the print history reprinting feature is enabled, may store started times, finished times, and filament consumption. The privacy policy webpage is not present in the Wayback Machine.

Community strategies to deal with risks

Users have discussed strategies to avoid possible disruptions, including:

• Operating printers exclusively in offline modes.
• Using LAN connections or VPN setups: this requires an access key from the printer (previously, you could use your cloud credentials over LAN).
• Exploring alternative firmware or third-party scripts to restore full functionality.

Bambu Lab's justification and rebuttal

Bambu Lab has stated that the authorization system is in place in order to protect against "remote hacks," "printer exposure," and "abnormal traffic or attacks". The cited security incidents have specific context:

• The "remote hacks" cited as an example in the article followed a reported security vulnerability in a 3D printer product; according to Bitdefender's reporting, the researcher infected machines to display a harmless message in order to publicize the unpatched flaw.
• In the article cited about printer exposure, the hack was carried out largely because of user misconfiguration.
• The "abnormal traffic" can be mitigated by steps Bambu has already put in place, as detailed in their own article on the matter.
• "Other malicious devices in the LAN" can be partially mitigated by steps Bambu has already put in place, as detailed in their own article on the matter.

Issues with LAN mode requiring authorization

📅This section may be outdated. Some information may no longer reflect the current situation.

Bambu Connect App - Lan Device Discovery without Bambu Login

Bambu Lab printers have the ability to be controlled over both cloud and LAN. This allowed users to integrate their printers into private networks and maintain full control without having to rely on the manufacturer's server while also allowing cloud access. The new authorization system mandates that even LAN-based operations must go through an authentication process using Bambu Connect to retain full control. Full local access is still possible and unchanged for those not using the cloud.

This change has drawn criticism for many reasons:

• Privacy concerns: Requiring authentication for LAN mode raises concerns about data being unnecessarily exposed to Bambu Lab's servers, even for local-only operations, though previously, the printer was also connected and could be controlled by the cloud even when sending prints locally.
  • Confidentiality required by US Law: this is in conflict with users that have to comply with internal U.S. government classified information handling regulations.^{[citation needed]}
• Loss of offline independence while also using cloud: Before, users could have hybrid offline setups. The requirement for authentication removes this option unless users revert to older firmware versions; Bambu Lab initially indicated rollback would not be permitted, though The Verge later reported that users could still downgrade and use LAN access keys while signed into the cloud.
• Increased complexity: The added authentication layer complicates workflows for users who built custom setups or relied on third-party integrations for LAN control while retaining cloud functionality.

• LAN-Only mode in Orca Slicer is implemented by passing API Calls to the installed proprietary Bambu Network Plug-In (unlike BTT and other solutions that did indeed communicate with printer directly via MQTT protocol).
• Plug-In provides controls for Printers "Critical Operations" (as classified by the Firmware Announcement article) and displays these controls within the window of Orca Slicer.
• Using intermediary Plug-In does not manifest as "direct access through network plugin". It is still a Proxy communication, even if user experience is presented as direct communication (same slicer window).
• Bambu Connect moves the Network Plug-In functionality outside of the window of Orca Slicer thus appearing as separate window and presents the appearance of "indirect" communication channel to the printer.
• While the user experience is different, the flow remains unchanged Orca Slicer slices model -> Orca Slicer Calls API of Bambu Proprietary Software -> Bambu Proprietary Software controls the printer.

Additionally, Bambu Connect software (downloaded and installed in January 2025, before the backlash response) supports adding LAN-Only printers without requiring Bambu Account authentication, the same behavior as the Network Plugin used in Orca Slicer.^{[citation needed]}

X1E firmware 01.01.02.00 LAN-mode connection failure

Newly received X1E printers with firmware 01.01.02.00 will not connect to the Bambu Studio using the Lan only method password. Bambu Studio identifies the un-logged printer but will not allow a connection to the printer. Only after connection / account pairing is done over the Bambu Handy app by giving internet access to the PC and Printer then using the cloud service connection will Lan only communication and login work.

Implementation timeline and requirements

📅This section may be outdated. Some information may no longer reflect the current situation.

The authorization system will be rolled out in phases, starting with the X1 series printers. A beta firmware (version 01.08.03.00) was released on January 17, 2025, with the full release scheduled for late January 2025. The P and A series printers will get similar updates at an unspecified future date.

To use printers with the new authorization system, users must update multiple pieces of software:

• Bambu Studio must be updated to version 01.10.02.64 or higher
• Bambu Handy mobile app must be updated to version 2.17.0 or higher
• The new Bambu Connect application must be installed for using third-party slicers

These software updates are mandatory for users who update their firmware. Failing to update all components simultaneously will result in certain printer controls becoming unusable. Users who choose to maintain third-party software compatibility can continue using older firmware versions, or downgrade the firmware for new printers that ship with the authorization system pre-installed.

Bambu Lab states these coordinated updates are necessary because the new authorization system changes how the printer validates and accepts commands. The older versions of Bambu Studio and Bambu Handy lack the authentication mechanisms required to interact with printers running the new firmware. The Bambu Connect application was created specifically to provide a controlled interface for third-party software, replacing the previous direct access through network plugins.

Impact on third-party integration and user choice

Changes to third-party access

The new authorization system replaces direct network API access with a more limited URL-based interface through Bambu Connect. Third-party software can only interact with the printer by sending specific URL commands to Bambu Connect. The interface requires three parameters:

• path: The absolute file system path to the 3MF file (e.g., /tmp/cube.gcode.3mf)
• name: The name of the file (e.g., Cube)
• version: A fixed value of 1.0.0 for compatibility

A complete command must be formatted as:

bambu-connect://import-file?path=%2Ftmp%2Fcube.gcode.3mf&name=Cube&version=1.0.0

This interface only allows basic file transfer and print initiation. All other printer-control functions previously available to third-party software are now exclusive to Bambu's own applications. The path and name parameters must be URL-encoded using encodeURIComponent or equivalent functions.

Reduced home-automation capabilities

While basic status monitoring remains available (e.g., print-progress updates in Home Assistant), the new firmware removes the ability for home-automation systems to control printer functions. Users can no longer:

• Start or stop prints remotely using Home Assistant, BTT Panda Touch, or other third-party accessories or software interfaces
• Control printer temperatures or cooling
• Automate printer behaviors based on sensor data or events
• Access camera feeds through third-party applications

Impact on functionality

📅This section may be outdated. Some information may no longer reflect the current situation.

While some functionality remains unauthenticated like in previous firmware versions (sending status information from the printer over the network, starting a print job using SD cards), the most important features now require authentication through a closed-source client called Bambu Connect. These restricted features include:

• Initializing prints via LAN or cloud mode
• Remote video access to monitor prints
• Controlling motion system, temperature, fans
• AMS settings and calibrations
• Home automation integration beyond basic status monitoring

Previously, third-party software such as OrcaSlicer could interact with Bambu Lab printers via the open-source Bambu Studio and proprietary network plug-ins. While Bambu Connect provides a limited URL-based API to initiate prints, most functionality previously openly available is now restricted to Bambu's ecosystem.

Additionally, third-party accessories such as Panda Touch used to allow users to control their printers with a standalone device. Panda Touch was especially popular amongst P series printer owners since P series printers contain a monochromatic screen with a D-pad by default for printer control whereas Panda Touch featured a full-color touch screen According to Big Tree Tech (BTT), the manufacturer of the Panda Touch, they urge users of Panda Touch not to update firmware any further since doing so would foreseeably permanently break compatibility with users' printers and their Panda Touch.

Communication with Panda Touch developers

As of late January 2025, no formal communication between Big Tree Tech (BTT), the manufacturer and developer of Panda Touch, and Bambu Labs had been reported. BTT stated in a Facebook announcement that they had contacted Bambu Lab and would publish updates if Bambu responded.

Communication with OrcaSlicer developers

Before the official announcement of the new authorization and authentication, Bambu Lab engaged with the OrcaSlicer development team regarding the changes.

Pre-announcement contact

Reports from OrcaSlicer demonstrate that Bambu Lab provided limited advance notice of the changes that would render their software incompatible with Bambu printers running the new firmware. The communication emphasized:

• The introduction of Bambu Connect as the only supported method for interacting with third-party slicers.
• The discontinuation of the network plugin API that OrcaSlicer and other tools relied on for printer control.
• An invitation for OrcaSlicer developers to adapt their software to integrate with the Bambu Connect URL scheme.

The communication lacked the detailed technical documentation that would be necessary for developers to be able to work with the new requirements.

How the community viewed these actions

Primary criticisms of Bambu were:

• Lack of transparency: SoftFever reported that the limited warning given to OrcaSlicer developers preceded community engagement with existing customers. Point to the contrary: the new firmware is in beta and Bambu Connect middleware contains temporary compromises to allow third-party slicers to work as before.
• Lack of follow-through: As of January 2025, SoftFever, OrcaSlicer's lead developer, did not have API keys for Bambu Connect, a necessary layer of Bambu software that would need to be integrated into OrcaSlicer. Some community members questioned whether Bambu Lab's outreach to OrcaSlicer was a substantive collaboration effort.
• Disregard for open-source collaboration: OrcaSlicer is open-source software developed under the AGPL-3.0 license. The decision to restrict network APIs in favor of proprietary systems such as Bambu Connect removes customer choice in how the printer is operated.
• Token support for third-party tools: While Bambu Connect provides a workaround for third-party slicer use, it restricts functionality and complicates workflows, leading many to question the sincerity of Bambu's stated support for open-source tools.
• Power imbalance: As the hardware manufacturer, Bambu Lab has the ability to dictate how its products can be used; often to the detriment of third-party developers and users.

Community-driven workarounds and technical alternatives

📅This section may be outdated. Some information may no longer reflect the current situation.

Community members have published workarounds for the firmware restrictions.

Custom firmware development

Discussions took place within the community concerning the development of custom firmware as an alternative to Bambu's official updates. One prominent project mentioned in forums is the development of custom firmware for the X1-series printers, such as the "X1Plus Custom Firmware". This firmware aims to:

• Restore direct network control and third-party slicer compatibility.
• Re-enable previously available features such as motion-system adjustments, temperature control, and AMS settings without requiring proprietary software.
• Provide users with greater flexibility in integrating printers with home-automation systems and workflows.

However, custom firmware development faces several challenges^{[citation needed]}, including:

• Limited documentation and proprietary hardware components, which complicate reverse-engineering efforts.
• The potential voiding of warranties and risks of bricking devices.
• Legal concerns regarding intellectual property and bypassing manufacturer-imposed restrictions.

Backup of current third party access enabled firmware and network plugins

A GitHub repository, Tzeny/bambulabs_plugins_firmware, contains a backup of the latest firmware released by Bambu Labs for their printers and of the network plugin used by slicers such as Orca Slicer to communicate with the printer.

LAN mode and blocked internet access

In January 2025, user Tzeny15 on Reddit authored a five step guide to blocking internet access for the Bambu P1S as a precaution in case the manufacturer attempts to limit functionality for printers without the newest firmware.

Bambu Lab LAN mode guide

Community tools and scripts

In addition to firmware alternatives, some users have come up with custom scripts and software tools to interface with Bambu Lab printers indirectly. These tools often rely on:

• Reverse-engineering the URL-based commands required by Bambu Connect to enable partial functionality with third-party slicers like OrcaSlicer.
• Creating local server emulations to replicate the network API previously available before the update.

While these tools provide temporary solutions, they do not fully replace the open access that existed before the firmware update.

Re-engineering printer-control electronics

ChazLayyd's Bambu Lab Klipper Conversion project is currently in an incomplete stage. While the project was not made in response to Bambu's announcement, there has been a wave of new public interest in this specific project. ChazLayyd's documentation instructs P1S owners to non-destructively remove the old control electronics that run Bambu's proprietary software and instructs P1S owners to install off-the-shelf control components so that the existing motor connectors and other critical electronics can communicate with the newly-installed off-the-shelf control components.

Advocacy for open-ecosystem support

Community members have also organized to advocate for open-source support and rollback options. Suggestions include:

• Allowing an opt-out option for existing users who prefer local network control without cloud dependency.
• Providing an official API for third-party slicers under specific licensing agreements that allow secure authorized usage.

X1Plus and other alternative firmware

X1Plus is an open-source custom firmware version for Bambu Labs printers (more details on the GitHub page). It instructs the printer's auto-update mechanism that the device is on a future version (numbered 99 or higher) so the official firmware does not overwrite the modification.

• Installation tutorials are available for users who have not yet updated. Installing third-party firmware will void the warranty. Users are advised to consult the GitHub documentation before installation.
• X1Plus on GitHub
• The Bambu Labs website offers consumers the ability to request a rootable firmware to be sent to their printers. As of January 26, 2025, the feature (in the EU at least) is broken such that you cannot finalize the process of requesting such a firmware.
  • The result of accepting the terms of the page titled "Third Party Firmware Plan Guideline" and clicking "Next" takes you to a page titled "Important Notice and Risk Warning" which, when accepting the terms leaves you with an "I got it" button that takes you back to the previous page.

Impact on professional users and privacy concerns

Impact on professional users and print farms

The restrictions imposed by the new authorization system create operational challenges for professional users who kept their printers signed into the cloud:

• Print farms can no longer use custom automation systems to manage multiple printers
• Workflows built around third-party software have to be completely redesigned
• The requirement to manually export and import files through Bambu Connect creates additional labor
• Integration with existing business systems and workflows becomes more difficult or impossible
• Print-farm operators report that the new workflow disrupts their fleet-management workflows

Print-farm operators can avoid these restrictions by operating their printers in LAN-only mode rather than signing them into Bambu Cloud.

Privacy and data-collection concerns

The shift toward mandatory use of Bambu Studio and Bambu Connect raises several privacy and data collection concerns:

• All printer operations must now pass through Bambu's cloud infrastructure when using cloud mode
• User print data, including file names and print settings, becomes visible to Bambu when cloud is used
• Operational data is processed through Bambu's servers while on a different network. The camera feed, on the other hand, is always peer-to-peer.
• Users have limited visibility into how their data is collected, stored, and used in the cloud
• The system creates dependence on Bambu's cloud services availability for basic printer functionality

While Bambu Lab maintains that cloud processing is necessary for security and functionality, community members argue this represents unnecessary data collection that could be handled locally. Users who do not require cloud-based features can disable cloud connectivity and operate the printer through LAN mode.

Users who do not want their print data routed through Bambu's cloud infrastructure can operate their printers in LAN-only mode.

Customer reactions

Customer reactions on community forums and Reddit were negative. Bambu Lab has historically pushed cloud-based printer interaction while offering limited LAN mode functionality. Many customers argue that the security issues this locked-down firmware claims to address are actually consequences of the company's cloud-based design choices rather than inherent risks of local network control. After the announcement, Bambu Lab's Trustpilot page recorded a wave of one-star reviews citing the firmware restrictions as the reason for the rating.

As of publication, no changes have been announced for owners who never sign their printers into the Bambu cloud service. Past firmware updates allowed pairing the slicer via IP address and access key and performing offline firmware updates without ever signing the printer into the cloud, keeping local functionality unchanged.

Comparisons to similar practices by other companies

Bambu Lab's new authorization and authentication requirements have been compared to a number of practices by traditional printer manufacturers, such as HP and Epson, who have faced backlash and litigation over digital rights management (DRM) practices in 2D printers.^{[citation needed]}

A parallel from the 3D-printing industry is the 3D-printer manufacturer MakerBot, whose 2012 shift from open-source, DIY-focused machines to closed-source, proprietary machines drove customers to less-expensive open-source competitors, as documented by Hackaday's 2016 obituary of the company. MakerBot was also accused of asserting ownership over publicly available, open-source designs uploaded to its 3D print repository, Thingiverse.

TOS restricting development of third party devices and accessories

Archived discussion threads from January 2024 confirm that a clause restricting the development of third party devices and accessories - § 3.1 - has been part of the Bambu Lab Terms of Use at least since then. Community reaction was split: some readers argued the clause is intended to restrict third-party development, while others characterized it as standard boilerplate in vendor terms.

Bambu Lab's Terms of Use § 3.1 states:

3.1 You may not use Bambu Lab technology or Bambu Lab intellectual property to develop software or design, develop, manufacture, sell, or licence third-party devices/accessories associated with Bambu Lab Product without Bambu Lab's prior consent.

See also

• Bambu Lab cease and desist against OrcaSlicer fork developer
• Forced account
• Right to repair
• Terms of Service
• Software Freedom Conservancy v. Vizio
• GNU Affero General Public License
• Software Freedom Conservancy
• Reverse Engineering Bambu Connect