3mf merge — merge Bambu Studio / OrcaSlicer projects

[ 02 · BILL OF MATERIALS ]

MERGE BEHAVIOR

01 Slicer Settings — from row 01 only

✓ Objects & Meshes — retained from all files

✓ Per-Object Settings — retained from all files

ITEM FILE SIZE

— NO FILES ADDED —

[ 03 · OUTPUT ]

— ADD 1 MORE FILE —

OUTPUT FILE — click to rename

combined .3mf

[ 04 · DETAILS ]

WHAT IT DOES

Each .3mf file you drop in is a slicer project containing one or more plates of arranged objects. The merge combines every plate from every file into a single project — objects stay exactly where they were, and each plate keeps its identity.

The first file’s print profile and slicer settings are used for the output. G-code is dropped — your slicer will regenerate it when you slice.

Only Bambu Studio and OrcaSlicer project files are supported. PrusaSlicer and Cura use a different .3mf dialect and will be rejected.

UNDER THE HOOD

This page is a static HTML file plus a WebAssembly module compiled from Rust. When you click Merge, your files are passed to Rust code running inside your browser — nothing is uploaded, because there is no server to upload to.

Inner object IDs and UUIDs are regenerated globally so meshes from different files don’t collide. Plates are laid out on a virtual grid and renumbered sequentially.

The merge engine is the same mf3-combine crate used by the CLI, compiled to WebAssembly. Source is on GitHub.