Product
How Slicebuild works
A project is not a zip of STLs. It is the printed parts, the hardware, the print notes, and a step-by-step assembly manual — one record you can follow at the bench.
Four pieces, one record
-
01
Printed parts
STLs live on the project, not in a sidecar zip. Each part can carry print notes so a builder is not guessing walls, infill, or material from a forum thread.
-
02
Hardware on the step
Vitamins are attached to the instruction that uses them — M3×12, an insert, a bearing — then rolled into a bill of materials on the public page.
-
03
A guide you can step through
Studio writes the manual. The public build page is crawlable HTML; “Start the guide” opens the player for the bench.
-
04
Publish when it can stand alone
Drafts stay private. Publishing lists the project on Explore and in the sitemap. Creators can unpublish later without deleting the files.
Voron 0.2 · Lower gantry
Who it is for
Builders
People assembling a machine who need quantities, print specs, and an order of operations — not a folder named final_final_v3.
Creators
People shipping a revisioned project. The manual is part of the release, not a PDF you forget to update.
Designers
CAD stays the source. Slicebuild is the distribution layer: parts, vitamins, notes, and assembly in one place builders can find.
Questions
- How is Slicebuild different from Printables or YouMagine?
- Those sites are strong at hosting files. Slicebuild is built around the assembly layer: each step knows which printed parts and hardware are in your hand, and the public page is a readable manual — not only a download button.
- Do I need an account to follow a guide?
- No. Published projects are public. Open the build page, start the guide, and step through it. An account is only required to create or edit a project in Studio.
- What has to be true before a project can be published?
- The manual needs at least one real step. Drafts stay private. Publishing lists the project on the homepage and Explore, and puts it in the sitemap for search engines.