Pipeline explained · Last reviewed October 4, 2026
Image-Blaster: One Image, a 3D World, Meshes, Physics and Audio
Image-Blaster turns an image into coordinated environment, object and sound assets. Its contribution is joining those layers into a workflow, rather than treating the entire picture as one 3D object.
This is a source-based explanation of a third-party project, not an Image3D hands-on test. Image3D has not added Image-Blaster, Marble or world-generation integrations.
Why the object layer still matters
Imagine a room where a chair needs to move. The room’s appearance and the chair’s editable geometry solve different problems. Keeping them separate lets a downstream application treat the chair as an object while retaining the surrounding environment.
The World Labs Showcase identifies Neilson Koerner-Safrata’s Image-Blaster as a Claude Code toolkit. It describes removing dynamic objects from the source image to build a static environment while generating those subjects as standalone meshes. This illustrates the object-versus-world distinction.
Follow the handoffs, not just the final demo
Image cleanup → static plate → Marble world → splat and collision assets
Object references → separate 3D meshes → placement and interaction
The project’s README describes GLB/OBJ objects, an SPZ environment and MP3 sounds. Its model list assigns Marble 1.1 to the world, Hunyuan3D through fal to object meshes, Nano Banana or GPT Image to cleanup, and ElevenLabs SFX to sound. It also names downstream engines and DCC tools; that list does not establish that every generated scene imports perfectly into each application.
| Layer | Documented role | Check before delivery |
|---|---|---|
| Scene preparation | The Showcase describes separating dynamic subjects from the static image. | Look for duplicates or traces of removed objects in the background. |
| Environment | The world workflow source tracks local splat, collider and panorama assets. | Load the representation in a compatible viewer and inspect intended viewpoints. |
| Objects | The object workflow source names Hunyuan as its default mesh provider. | Inspect backs, thin parts, materials, scale and object origins. |
| Physics and assembly | Viewer dependencies include Three.js, React Three Fiber and Rapier integration. The Showcase describes interactive physics. | Test collision shapes and physical behavior separately from appearance. |
| Audio | The Showcase attributes ambient and object-effect generation to ElevenLabs SFX. | Check looping, timing, levels and usage rights before sharing. |
Hunyuan3D is not Hunyuan World
Tencent’s Hunyuan3D asset project describes shape and texture generation. HunyuanWorld 1.0 is a separate scene-generation project. Image-Blaster’s documented stack names Hunyuan3D for objects and Marble for the environment. It would be incorrect to say Hunyuan World powers that scene branch.
The broader category also includes Hyper3D WorldGen’s scene workflow. Similar names do not establish shared models, identical exports or integrations.
What an engine handoff leaves to check
The World Labs listing names Unity, Unreal and Three.js destinations. The repository additionally names Blender and other DCC tools. Treat these as handoff environments: a splat renderer, mesh importer and physics runtime are not interchangeable.
- Open environment and object files independently, then verify the assembled scene.
- Check origins, units and alignment; a convincing screenshot cannot establish them.
- Test object collisions instead of assuming a visual splat supplies collision geometry.
- Confirm textures and audio travel with the package and meet applicable service terms.
- Measure performance on the target device. This article supplies no speed, cost or quality benchmark.
For representation choices, consult Marble’s export explanation. A rendered video is something to watch, not a replacement for the underlying interactive assets.
Where Image3D fits
Image3D does not reproduce the entire Image-Blaster pipeline. It is relevant when your job is one object: a product, prop or character delivered as GLB, OBJ or STL. A complete world-generation pipeline may be unnecessary for that task.
This does not mean Image3D extracts objects from an Image-Blaster scene. Start with your own suitable reference and inspect the generated object. Use image-to-3D object generation, GLB output or STL preparation for that separate workflow.
Create an individual object