# SpoolEase tracks 3D printing filament by weight, tag and slot > SpoolEase is a locally hosted filament manager that combines NFC tags for spool identification, weight tracking through a scale or print usage, storage location records and printer slot configuration, with tight integration for Bambu Lab printers and Bambu Studio. The firmware is Rust, the hardware is a console and a scale you build yourself, and the licence is a custom one. **yanshay/SpoolEase** — 3d printing filament manager that brings weight and location tracking, slots configuration, slicer integration, NFC and more to your 3D printer. - Repository: https://github.com/yanshay/SpoolEase - Website: https://www.spoolease.io/ - Stars: 566 · Forks: 41 - Language: Rust - License: NOASSERTION - Published: 2026-10-22 · Updated: 2026-10-22 · Language: en - Canonical page: https://hysenlabs.com/projects/yanshay-spoolease ## What SpoolEase actually is SpoolEase is described as a comprehensive filament manager solution that tracks spool inventory, remaining weight, storage locations and printer slots in one locally hosted filament manager. That last phrase carries weight. A locally hosted manager means the inventory data stays on your own hardware, which for a device that sits next to your printer and talks to it over the network is a reasonable default rather than a selling point, but it does mean there is no account to create and no service that could disappear. The purpose it serves is narrow and concrete. SpoolEase helps manage any filament brand, monitor printers, and avoid running out of filament mid-print, powered by NFC/RFID. The project is two physical products rather than one piece of software, and the README describes them separately. SpoolEase Console is the main hub with a display, managing inventory, weight tracking, AMS and external slot configuration, and showing AMS and external filament status. SpoolEase Scale measures spool weight and feeds data to the Console. That split is the core idea. A scale that knows the weight of a spool and a hub that knows which spool is where and which printer slot it is in can answer the question that matters, which is whether there is enough filament left to finish the print you just started. Neither half can do that alone. The firmware is Rust, and the repository layout is small and consistent with that: core/, shared/ and readme/ at the top level, with a CHANGELOG.md, a LICENSE.md and a README.md. The homepage is spoolease.io, and the README says that for the most up to date information you should check that site, with a documentation and flashing page linked at the end. The last push was on 2026-08-10 and the most recent release is 0.7.0 from 2026-06-22. ## Three ways to know how much filament is left The weight tracking feature is the part of SpoolEase that solves the problem the project exists for, and the README describes it as using three methods. It is a precise filament weight tracking system using, one, weight scale, two, print usage monitoring, and three, a smart workflow, so you can tell how much filament is available in every spool. The scale is the direct measurement. The SpoolEase Scale sits under the spool, measures it, and sends the number to the Console. That is unambiguous, and it is also the method that requires the physical hardware, since the scale is one of the two products. Print usage monitoring is the derived method. If the printer reports how much it has consumed, and you know the starting weight, then the remainder is arithmetic rather than measurement. That works without the scale, which matters for anyone who does not want to weigh every spool. The third is described as a smart workflow, and the README does not unpack it in the text shown here, so the documentation site is the place to read what it actually is. Given the framing of the other two, it is likely a way of combining the two signals rather than a third independent sensor, and it is worth confirming in the docs before relying on it. The printer monitoring feature follows from the same design. It covers the essentials for monitoring printers, prints progress and AMS units status, and the Bambu integration is what supplies the print progress data in the first place. ## NFC identification and the tag ecosystem Spool identification is handled with NFC, and the README is specific about which tags work. It supports most common NFC tags, NTAG with 215 and above recommended, and Mifare Classic, with Mifare not yet supported for the virtual label feature. That recommendation about NTAG 215 and above is not arbitrary. NTAG 215 is a larger tag with more memory and better read characteristics than the smaller NTAG 213, and if the system stores spool information on the tag itself then the capacity matters. The Mifare caveat is a reminder that tag support is not uniform across the two families. On the data side, the project imports and supports Bambu Lab spools RFID tags, and it also has software support for OpenPrintTag, with the README pointing at a documentation page on registering OpenPrintTag spools and asking the reader to check the support scope there. That pointer matters, because OpenPrintTag is an open alternative to a proprietary tag scheme and the degree of support varies. There is also a Virtual Spool Label for viewing spool info on your mobile device, so you can read a spool's identity with a phone rather than walking over to the Console, with the caveat that Mifare Classic is not yet supported for that feature. The physical counterpart to all this is the SpoolEase NFC tag holder, a 3D printable model on MakerWorld that supports easily swappable NFC tags and printed labels for the type and spool id, with the stated purpose of spool reuse. The reason that matters is that a spool is often reused with different filament on it, so the tag needs to be swappable and the printed label needs to be swappable too. ## Storage locations, slots and the Bambu Studio integration The storage system management feature uses NFC based location tracking so you can find where your spools are, with a workflow intended to keep the location information up to date. The mechanism is that a tag read at a location records that spool as being there, so the inventory knows where things are rather than only what exists. The printer side is handled by automatic slot configuration for filament type, color and pressure advance, and the last of those is the one with an unusual angle. The README says SpoolEase even serves as backup for your pressure advance settings, for when the printer loses them, and yes, it happens. Pressure advance is a per-filament calibration value that printers store locally, and losing it means a first-layer problem on a filament you have already tuned. Compatibility is listed precisely. It supports Bambu Lab X1, P1, A1, H2, P2 and X2 product lines with AMS-Lite, AMS, AMS2-Pro and AMS-HT and the Filament Track Switcher, and it supports multiple printers simultaneously within resource limits. The slicer integration is a separate product rather than a plugin. A custom Bambu Studio is described as an enhanced Bambu Studio with new features to take advantage of SpoolEase information, with the SpoolEase application hosted inside the slicer. The README links a video demonstration for it and separately notes that the Console videos are outdated, since SpoolEase now offers far more features than those videos show. The compatibility with your slicer filament settings is the item that ties it back to the printer, since the point of tracking filament accurately is that the slicer can then pick the right profile for the spool you have loaded. ## Building it yourself, and the risk notice The project is open source and the README makes a point of the hardware being approachable. Even though it's an open-source project, it's fun and easy to build and surprisingly simple to set up. The documentation and flashing instructions are at spoolease.io, and the README links that page under the name SpoolEase Web Site - Documentation & Flashing, which tells you the repository is the firmware and the site is the build guide. Community support runs through a Discord server and a subreddit at r/SpoolEase, and the README says that for discussions, support and general discussions the best route is the Discord server. The risk notice at the end is the most important paragraph for an evaluator. It says this is a new project, that while it has been installed by many happy users, new users should be aware that there are no warranties, liabilities or guarantees, and that they assume all risks involved. That is a more direct statement than most projects make, and it fits the shape of the project. The hardware is DIY, the firmware is written by an individual, and the integration with a proprietary printer ecosystem depends on behaviour that the vendor can change. A user flashing firmware onto a printer has no vendor warranty to fall back on if something goes wrong, and the project is clear about that. The licence is recorded as a custom one that GitHub cannot classify, with the LICENSE file in the repository as the authoritative text. Since this is firmware that runs on hardware people own and that touches their printers, reading that file before building is worth the few minutes it takes. The release history is short and shows a single meaningful tag, 0.7.0 from 2026-06-22. The other tag, SpoolEase-Desktop-r0.1.0 from 2025-03-10, is labelled Obsolete in its own release name, which suggests an earlier desktop application approach was tried and dropped in favour of the console and scale hardware. ## Where SpoolEase fits, and where it stops The comparison worth making is with the inventory tracking your printer already does, and with the commercial filament management systems. Against the printer's own tracking, the difference is that Bambu Studio and the AMS units know what is loaded, and possibly how much is left in the loaded spool, but they generally do not know what is sitting in your storage boxes. The location tracking and the virtual label are the parts that fill that gap, and the scale is what makes the weight number trustworthy for a spool that is not currently in a printer. Against a commercial filament management system, the difference is ownership and cost. A commercial product gives you a supported device and a vendor to call, and SpoolEase gives you firmware you can inspect, modify and flash onto hardware you built. The README's own framing of the trade-off is that there are no warranties, liabilities or guarantees and that you assume all risks involved. The limits are worth naming plainly. The weight scale is a physical accessory, so without it the tracking depends on print usage reporting and whatever the third method turns out to be. The printer integration is concentrated on Bambu Lab, and the AMS variants and product lines are enumerated, so a different printer brand is out of scope. OpenPrintTag support has a scope the README asks you to check rather than describing. And the whole system is firmware for two devices plus a phone app plus a modified slicer, which is a lot of moving parts for something whose failure mode is a printer that does not behave as expected. For a hobbyist with many spools, a storage area that is not a filing cabinet and a printer that will happily start a six-hour print with 40 grams of filament left, this is a coherent answer. The NFC tag holder that makes spool reuse practical and the pressure advance backup are the two features that suggest the author built it around the annoyances rather than around the feature list. The last push was on 2026-08-10, the repository is not archived, and the licence is the custom one in LICENSE.md, so anyone deploying this should read that file and decide for themselves what the terms are before they flash anything. ## Conclusion SpoolEase suits a 3D printing hobbyist with enough spools that running out mid-print has become a real problem, since the weight tracking, the NFC identification and the location records are the parts that actually stop that from happening, and the Bambu Studio integration means the slicer sees the same inventory. It is the wrong tool if you have a handful of spools, and it is the wrong tool if you need a supported commercial product, because the README states plainly that this is a new project with no warranties, liabilities or guarantees and that users assume all risks. Before you build, read the documentation and flashing pages at spoolease.io, since the README points there for the most up to date information and the repository itself is mostly firmware for two pieces of hardware. ## FAQ ### What is SpoolEase? It is a locally hosted filament manager for 3D printing that tracks spool inventory, remaining weight, storage locations and printer slots in one system, using NFC/RFID identification so you can avoid running out of filament mid-print. It includes a console with a display and a scale that measures spool weight and feeds data to the console. ### How does SpoolEase track how much filament is left? The README describes three methods: weight scale, print usage monitoring, and a smart workflow. The SpoolEase Scale measures the spool directly, print usage monitoring derives the remainder from what the printer reports consuming, and the third method is not unpacked in the README, so the documentation site is the place to read how it works. ### Which NFC tags does SpoolEase support? Most common NFC tags, with NTAG 215 and above recommended, and Mifare Classic, although Mifare Classic does not yet support the virtual label feature. The project also imports and supports Bambu Lab spools RFID tags and has software support for OpenPrintTag, with the support scope documented on the SpoolEase site. ### Which printers does SpoolEase work with? Bambu Lab X1, P1, A1, H2, P2 and X2 product lines, with AMS-Lite, AMS, AMS2-Pro and AMS-HT and the Filament Track Switcher, and multiple printers simultaneously within resource limits. The slicer side is a custom Bambu Studio with the SpoolEase application hosted inside it. ### Is SpoolEase open source and what licence does it use? The project is open source and the firmware is written in Rust, but the licence is a custom one that GitHub cannot classify, so the LICENSE file in the repository is the authoritative text. The README also states that this is a new project with no warranties, liabilities or guarantees, and that users assume all risks involved. ### Where do I find the build and flashing instructions for SpoolEase? The README points to spoolease.io for the documentation and flashing pages, and says that is where the most up to date information is. The repository itself holds the firmware source, with core/, shared/ and readme/ at the top level, and support runs through the project's Discord server and subreddit. ## Sources - [Issues](https://github.com/yanshay/SpoolEase/issues) - [Project website](https://www.spoolease.io/) - [README](https://github.com/yanshay/SpoolEase/blob/main/README.md) - [Releases](https://github.com/yanshay/SpoolEase/releases) - [yanshay/SpoolEase on GitHub](https://github.com/yanshay/SpoolEase) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/yanshay-spoolease