Bambu has begun manufacturing its own filament, and patterns of behavior we can observe in the Bambu Studio GitHub repository point toward a gradual lock-out of third-party filament vendors.
Not in the “Bambu will lock down their printers to Bambu filament” way people have feared, but by removing convenience, withdrawing validation, and letting vendor support quietly decay.
This is a step in a gradual process that will likely end with Bambu offering a licensing scheme: “pay us, and we’ll let you use Bambu RFID tags and get your profiles into Studio.”
Here’s how I arrived at that conclusion.
Background #
In mid-November, I noticed that Bambu removed all third-party filament profiles (Polymaker, Overture, eSun, etc.) from Studio for the H2C and P2S, leaving only Generic and Bambu profiles.
I opened an issue asking why.
The given reason was that the profiles hadn’t been tested or validated specifically for the H2C.
That’s a departure from the norm. Many of those profiles have been in Studio for a long time, well before the second generation printers were released. This suggests that Bambu either tested and validated them at some point and has since stopped, or that the historical bar for validation was lower than what is now being expected for H2C, P2S, and future printers.
The response makes it clear that Bambu wants filament vendors to take over testing and validation of their profiles from now on.
I asked a follow-up about what testing or validation Bambu now expects from filament vendors. That question has gone unanswered for weeks, even after I followed up again.
Languishing profiles #
On top of the removals, there are open pull requests from multiple filament vendors attempting to add or update profiles in Bambu Studio. Some of these have been sitting untouched for months.
- CookieCAD (CookieCAD employee)
- Overture (Overture employee)
- PolyMaker (PolyMaker employee)
- Numakers (Orca dev? unclear)
- Coex3D (Coex3D employee)
- Eolas (unclear)
- Valment (unclear)
This feels a little weird; in February 2025, Bambu merged a PR for Sunlu profiles. The submitter does not appear to have been a Sunlu employee, and the profiles were reportedly based on TDS data rather than extensive validation. There was active engagement from Bambu employees, and the PR was merged.
In August 2025, Bambu merged a Polymaker/Fiberon filament profile PR where a Bambu employee actively reviewed the changes and fixed issues internally rather than pushing them back onto the submitter. I read this as a sign that third-party profiles were still being treated as a shared responsibility at that point.
That pattern of engagement no longer exists. Vendor PRs now sit without feedback, requests for changes, or even acknowledgment.
That looks more like a deliberate lack of engagement, or at least a conscious deprioritization.
A shift in strategy? #
So, it seems clear that somewhere in the second half of 2025, Bambu has changed their approach to third-party filament vendors.
What would cause a change like this?
Bambu has always sold filament. Until recently, all of it was manufactured by third parties and sold under the Bambu name, paired with RFID and AMS integration.
Bambu now manufactures some of their own filament.
Now that Bambu is a filament manufacturer, third-party filament profiles inside Bambu Studio become less neutral. They become profiles for competing products, shipped by default in Bambu’s own slicer, sitting next to Bambu’s own SKUs. Identical parameters might even expose which third-party makes a given Bambu-branded filament.
From that perspective, the current behavior makes sense. Shipping competitor profiles as first-class defaults is no longer aligned with Bambu’s interests.
“Bambu will lock down their printers to Bambu filament” has long been a bogeyman in the Bambu community. I don’t think they’ll ever do that; it’d be a disaster worse than the Auth Control debacle.
But they don’t have to do that. All they have to do is remove the convenience and validation that third-party profiles in Studio provide.
The convenience lever #
Bambu’s core value propositions have always been quality and convenience.
Third-party filament profiles in Studio lower friction and provide confidence, especially for Handy users and anyone not comfortable creating Custom Filaments. Their presence signals that these materials work well with Bambu printers.
Removing those profiles doesn’t stop anyone from using third-party filament. It adds friction. It removes validation. It shifts blame for failures onto “unsupported material.”
Over time, that makes Bambu filament the default choice without ever requiring it.
Following a pattern #
In January 2025, Bambu rolled out its Authorization Control system, restricting what software can send prints to Bambu printers. On Generation 2 printers, that system is mandatory. LAN mode and dev mode exist, but they are clearly not the intended default.
The justification was security and reliability. It was probably required because of the laser in the H2 series.
The implementation didn’t fit the stated goals. Bambu could have chosen to implement Auth Control in a way that didn’t lock out all but their own software, but chose not to. Bambu Connect, the middleware they promised to “open access” to your own printer, is still a messy beta and doesn’t seem to be a priority; the H2C is still not supported (as of 12/12/2025).
The significance is precedent. Bambu has already demonstrated a willingness to restrict ecosystem access when it aligns with their goals in ways that do not benefit users.
RFID makes the next step easy #
At this point, I’m shifting from what we have observed to what we can infer about what’s next.
Bambu already has RFID-tagged spools, AMS integration, automatic profile selection, and telemetry hooks (the Customer Experience Improvement Program). From a technical standpoint, almost everything required for a licensing program already exists.
What’s missing is a policy decision to use it that way.
Once that decision is made, official filament profiles become something vendors pay Bambu for rather than something the ecosystem collaborates on. Third-party filaments continue to work, but only Bambu filament, or licensed filament, receives first-class treatment in the slicer.
What’s next? #
I expect Bambu to remove the remaining third-party filament profiles from Studio soon, citing staleness and lack of validation. That justification will be reasonable on its face; some of those product lines no longer exist (e.g. Polyterra).
After that, I expect a materials partner or licensing program. They’ll let vendors pay for RFID access, submit their filament for validation, and their profiles can be added to Studio.
What else could it be? #
There are other explanations. The slicer could simply be under-resourced. This could be prioritization or internal process churn.
If that were the case, some communication would be expected. A response on the issue or profile PRs. Validation criteria. Guidance for vendors.
So far, there’s been silence.
And silence, in cases like this, usually isn’t accidental.
OK, but why’s it even matter? #
Because it’s fucking frustrating as a user to have Bambu continually making it inconvenient to get the most out of my printer. If Auth Control hadn’t happened, or was done in a different way (which was viable!), this would be a non-issue.
Other slicers (really, OrcaSlicer) used to be the ’escape hatch’ for users who didn’t need or want to be hand-held by Bambu. Bambu has closed that avenue1. It’s frustrating to have to argue with Bambu to even allow the full suite of calibrations for their printers, after locking out software their own wiki used to recommend2 to get more out of their printer.
They try to position their filament with their profiles as not needing tuning, but that’s an obvious marketing ploy and isn’t true. If it was true, they wouldn’t have spent so much money and effort developing automatic tuning systems in their printers. Sure, they’ve got automated Flow Dynamics, but we had to fight to get access to any calibration other than Flow Rate in Studio.
Bambu makes excellent hardware capable of making near-perfect prints, and then pairs it with a slicer that they keep making harder to achieve those results with. It’s maddening.
I can surmise that a lot of this is caused by the split in Bambu’s customer base; some people just want to print dragons from Handy. Some customers need to print advanced materials that need extreme fine-tuning. Bambu needs to figure out how they use one slicer to serve both needs. They put us in this position.
But back to the filament: I see a lot of Bambu owners who only buy non-Bambu for three reasons:
- They want a particular material/color/finish that Bambu doesn’t offer.
- They want faster shipping than Bambu offers.
- They want to pay less. Bambu charges a premium for their ecosystem experience.3
Bambu should compete on those things, not make exclusionary or ecosystem-hostile changes in Studio policy.
If this isn’t the plan, now would be a good time to say something #
If Bambu isn’t moving toward a more closed filament ecosystem, the fix is straightforward: explain the strategy, publish validation requirements, and engage with vendors again.
Until that happens, the direction seems clear.
This doesn’t look like neglect, prioritization, or just being busy. It looks like preparation.
Add your voice #
If you’d like to add your voice to the conversation, I’d appreciate you leaving a polite comment on the issue in Studio asking what’s going on with third-party filament profiles. It’s important to us users, not just vendors, that we understand what’s happening. Thanks!
-
I know there are workarounds. They shouldn’t be needed. ↩︎
-
Bambu has blocked archive.org from including the wiki in the wayback machine, as far as I can tell; you can’t ask the wayback machine to archive it. As a result, I can’t prove this. I’m 95% certain it used to include references to using other slicers for more advanced calibrations. ↩︎
-
Although Bambu’s sales do often reduce the price significantly when bought in bulk. ↩︎