Hi everyone,
I’ve been building an open-source tool around the U1, and with the Snapmaker Innovation Fund community vote now open, I thought this was the right time to finally introduce it properly to the community.
What is Snapmaker Studio?
Snapmaker Studio is a local pre-print intelligence tool for the Snapmaker U1.
The basic question it tries to answer is:
“I downloaded this 3MF/STL. Will it actually work correctly on my U1, what might go wrong, and what can safely be fixed before I slice it?”
It is not another slicer and it isn’t intended to replace Snapmaker Orca.
The workflow is:
Understand → Check against the printer → Prepare → Slice in Orca → Verify the sliced job
GitHub:
Independent community project — not affiliated with or endorsed by Snapmaker. Current installer: Windows 10/11 x64. MIT licensed.
The repository includes a 66-second demo, screenshots, documentation and a Windows installer.
What it currently does
Design / Project Health
Studio reads the real contents of a 3MF or STL and can inspect things such as:
-
Object and plate structure
-
Dimensions and bed fit
-
Geometry and mesh integrity
-
Watertightness / holes / normals
-
Stability and tip risk
-
Overhang/support indicators
-
Materials and colors
-
Project/slicer origin
-
Per-object and process information
The goal is to explain problems in normal language instead of just returning something like “out of bounds.”
For example, Studio can identify which object, which edge and how many millimeters are outside the printable area.
Printer-aware checking
One part I especially wanted to explore was taking advantage of how open the U1 ecosystem is.
Studio can communicate with a U1 over the local network through Moonraker and compare a project with the printer it can actually see.
Where the printer/firmware does not expose enough information, Studio deliberately reports that it cannot determine the answer rather than inventing one.
The U1 is the first printer target and is the printer against which the hardware integration has been tested.
Prepare a corrected copy — without touching the original
When Studio can justify a correction, it creates a new project copy.
The original file is never modified.
After preparation it produces a fidelity report describing:
-
What remained unchanged
-
What Studio changed
-
Why it changed it
-
What could not be carried across
-
What Studio could not verify
A conversion is not supposed to silently throw project information away.
Snapmaker Orca still performs the actual slicing.
Multi-material / painted-project analysis
Studio can read painted multi-material information before slicing, including which filament assignments appear in the project and information about the painted regions.
It can also help reason about projects containing more colors than available U1 toolheads and distinguish between things Studio can prove and things that will only be known after slicing.
Checking what Orca actually produced
The workflow doesn’t stop at the source project.
After slicing in Orca, Studio can read the G-code back and inspect what the printer will actually be asked to execute.
That allows checks to be based on both:
the design before slicing
and
the job after slicing
rather than treating them as the same thing.
Local-first and open source
This was important to me from the beginning:
-
No cloud account
-
No project uploads
-
No telemetry
-
Runs locally
-
MIT licensed
-
Original project is never overwritten
The project is intended to work with the existing open U1 ecosystem rather than replace it.
That includes Snapmaker Orca, OrcaSlicer, Fluidd, U1Hub and other community tools. Studio can even point users toward a community tool when it detects a project characteristic that another tool handles better.
Easy Windows installation
The current stable release is v0.9.0.
There is a normal Windows 10/11 x64 installer, so you don’t need Python, Node, Rust or a development environment just to try it.
The installer isn’t code-signed yet, so Windows may show an Unknown Publisher warning. The repository publishes the SHA256 and explains how to verify the installer.
I especially want people to try to break it 
The most valuable feedback for this project isn’t “looks good.”
It’s:
“Studio told me X, but my file/printer actually does Y.”
If you have an unusual 3MF, multi-material project, project from another slicer, broken model, or anything else that gives the U1 trouble, I would really appreciate you testing it.
Issues, discussions and pull requests are all welcome.
Snapmaker Innovation Fund
Snapmaker Studio is a Phase 1 Innovation Fund entry, and community voting is open until September 30 at 11:59 PM UTC.
Each voter selects 5 projects.
If you’ve looked through Studio and think the project is worth continuing, I’d really appreciate you considering Snapmaker Studio as one of your five choices.
How to vote
-
Open the voting gallery:
Innovation Fund - Phase 1Community Votes - Easypromos -
Find and select Snapmaker Studio, along with four other projects you want to support.
-
Submit your choices.
-
Enter your email address and confirm using the access code sent to you.
Official Snapmaker voting announcement:
If you find Studio useful, you can also help the project by:
Starring the GitHub repository:
Liking this post so more U1 users have a chance to discover it.
Most importantly, I’d love to hear what you think should come next.
The roadmap currently includes additional printer targets, OBJ/GLB support, further PrusaSlicer preservation and a stable API that other community projects could integrate with.
Thanks for taking a look — and thanks to everyone building around the U1 ecosystem.
Snapmaker Studio
The Intelligence Layer for Open 3D Printing
Windows only…
Linux support is already in progress and should be available shortly for testing.