UltiMaker Cura is a Python shell on the Uranium framework, and building it starts with a Conan remote
3D printer / slicing GUI built on top of the Uranium framework
At a glance
- What is it?
- UltiMaker Cura is described as a 3D printer slicing GUI built on top of the Uranium framework, with hundreds of settings and community-managed print profiles. The build, the printer profiles, and the version story each carry their own friction.
- Who is it for?
- UltiMaker Cura suits people who want to slice on their own machine with settings contributed by other users, and who accept that printer support arrives through a reviewed profile rather than a menu click. Building it from source is a different proposition entirely, involving a Conan remote that recently moved, a CMake and Python build, and version metadata generated from templates.
- Can I use it commercially?
- Yes, with conditions. LGPL-3.0 is a weak copyleft licence: you can use it inside commercial and closed-source software, but if you distribute changes to its own files, you must publish those changes under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 4 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- Ultimaker/Cura7,082 ★ · +37
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| Ultimaker/Cura | 7k | 7.1k |
37 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The first instruction aimed at builders is a Conan config fix
Before any description of the application, the README opens with an important callout: the project switched to a new remote server for its Conan artifacts, and the configuration on your machine needs updating to match. The command given is a single line.
conan config install https://github.com/ultimaker/conan-config.gitThat is the whole fix, and it is telling that a slicer application leads with a build system problem. The repository ships a conanfile.py and a conandata.yml at the top level, so binaries for the non-Python parts of the build are fetched through Conan rather than vendored. Anyone with a Conan config from before the move resolves dependencies against a remote the project no longer uses. If you are cloning this to build, run that command first, before anything else in the file.
The application is Python, but the build is not a single pip install
The primary language listed for the repository is Python, and the tree backs that up with a cura/ package directory, a cura_app.py entry point at the root, a resources/ directory, and pytest.ini alongside tests/. Alongside that sits CMakeLists.txt, conanfile.py, conandata.yml, and a scripts/ directory. Read those together and the picture is clear: a Python application whose build pulls native pieces through Conan and drives part of the compilation through CMake. There is no one command in this README that produces a working Cura, and the file does not attempt to give one. Instead it points builders at a Getting-Started page on the project wiki. That page is the actual build documentation, and the README's role is to route you there.
Adding a printer means passing a linter, not flipping a config toggle
The project describes its print profiles as community-managed, and the contribution path for adding a machine leads with an instruction to read a wiki page first: Adding new machine profiles to Cura. The repository carries that gate in code. There is a printer-linter/ directory and a .printer-linter configuration at the top level, alongside a scripts/ directory. So a printer definition is not simply dropped into a folder. It has to satisfy a linter that the project maintains, and it arrives through a contribution workflow rather than through an import inside the running application. For a user, that is a reason to check the wiki for your machine before you buy hardware around it.
Your settings come from whatever somebody contributed
The README advertises hundreds of settings and community-managed print profiles, and it links two separate wiki pages for where those live: one on Profiles and Settings, one on Plugins and Packages. The tree includes a plugins/ directory at the top level, so the feature set of a given installation is assembled from contributed parts rather than fixed by the core. This is the single most important thing to understand before you start tuning prints, and it cuts both ways. Before spending an evening on a profile, find out who maintains the profile for your printer and read the profiles and settings page rather than guessing from the interface.
Version and packaging files are jinja templates, not checked in values
Two files at the top level are templates rather than plain files: CuraVersion.py.jinja and UltiMaker-Cura.spec.jinja. A jinja template inside a Python project means the version string is injected during the build instead of being edited by hand, and the spec template does the same for packaging metadata. Alongside them sit packaging/, a cura.sharedmimeinfo file for desktop file type registration, and a .run_templates/ directory for editor run configurations. The consequence for anyone automating a Cura build is that you cannot simply read a version out of the tree and expect it to be the version you will ship. The version you run is decided at build time.
The newest tag is a June alpha while main keeps moving
The release history is short and recent: 5.13.0 on 2026-05-28, 5.14.0-alpha.0 on 2026-06-25, and 5.14.0-beta.1 on 2026-10-15. The last push to the main branch came on 2026-11-02, and the most recent tag is a beta rather than a stable release. There is no homepage listed for the project, so the release page is the address that matters, and the downloads badge in the README points straight at the latest release. No version of this README tells you which build a given machine or profile was validated against, so if you are chasing a print problem, check which release you installed before you start changing settings.
Reporting a problem has a documented path and an undocumented one
The repository routes several things outward: a report link aimed at docs/Report.md, a security policy through SECURITY.md at the root, contribution guidance in CONTRIBUTING.md, funding through FUNDING.yml, and a citation file in CITATION.cff. Worth verifying one of those paths before you rely on it. The report link resolves to docs/Report.md, while the top level of the repository lists a doc/ directory. The README does not explain the difference, so treat the exact location as something to confirm. Third-party licensing is handled in-repo through a licenses_thirdparty entry, which is where to look if you need the full dependency inventory for your own compliance review.
Editorial conclusion
UltiMaker Cura suits people who want to slice on their own machine with settings contributed by other users, and who accept that printer support arrives through a reviewed profile rather than a menu click. Building it from source is a different proposition entirely, involving a Conan remote that recently moved, a CMake and Python build, and version metadata generated from templates. Before you commit, download a tagged binary from the releases page instead of building main, read the profiles and settings wiki for your machine, and confirm the Conan config command still points at the current remote.
Frequently asked questions
What is UltiMaker Cura used for?
It is a 3D printer slicing GUI built on top of the Uranium framework, described as a slicer app to prepare your 3D models for your 3D printer. The README advertises hundreds of settings and community-managed print profiles.
Is UltiMaker Cura free to use?
The source is published under the GNU Lesser General Public License version 3, with the license text in the LICENSE file at the repository root. The README itself makes no claim about pricing or accounts.
How do I download UltiMaker Cura?
The README's downloads badge points at the latest release page on GitHub, and the releases include tagged builds such as 5.13.0 from 2026-05-28. The most recent tag is 5.14.0-beta.1 from 2026-10-15.
how to install ultimaker cura on linux
The README contains no Linux installation command. What it does contain is the build fix for the moved Conan remote: conan config install https://github.com/ultimaker/conan-config.git, plus a pointer to the Getting-Started page on the project wiki for building from source.
Is UltiMaker Cura good for beginners?
The README does not address that question. What it does say is that Cura ships hundreds of settings with community-managed print profiles, and it points configuration questions at a Profiles and Settings wiki page rather than a quick start guide.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/ultimaker-cura)Star history chart for your README
[](https://hysenlabs.com/projects/ultimaker-cura)Was this useful?