A source model contains a lid, base and fittings, yet the exported STL appears as one object in another application. Confirm whether the recipient needs the overall surface or individually editable parts before choosing this delivery format.
One file is not a fused solid
Three.js documents STLExporter as merging geometry from multiple children into a single mesh in the file. FileMyLove uses its binary export path, so do not expect the original named part hierarchy.
This operation does not perform a Boolean union, weld touching surfaces or repair the model. Physically separated surfaces can remain disconnected within one file.
Agree on the handoff
| Recipient's need | Suggested preparation |
|---|---|
| Review the overall shape | STL, reopened and inspected |
| Move or edit individual parts | An original with separate parts and a compatible application |
| Print parts as separate jobs | Separate exports from the source application, checked in the slicer |
| Identify assembly locations | Reference pictures with part labels |
Reference pictures help communication but do not restore assembly structure inside STL. Converting it back to another format does not guarantee recovery of the original part names.
Inspect the exported copy
- Load the source in Convert 3D and check that the shape loaded completely.
- Export a separate STL copy, keeping the original.
- Open it in View 3D; inspect small components, gaps and placement.
- Open it in the recipient's application and test whether part selection meets the actual task.
- If separate parts are required, prepare them from the original before delivery.
Some applications can split disconnected surfaces. Do not assume that recovers the original names or hierarchy, especially where surfaces intersect or touch.
Current tool boundaries
The converter has no per-part STL export option, and previewing a model does not certify manufacturing readiness. See models that open but are not printable. Appearance is a separate issue covered in colors disappearing after STL export.
