Project guide · Updated
Image Blaster: what it is, setup and outputs
Image Blaster, also written Image-Blaster, is an open-source toolkit for Claude Code. It coordinates World Labs environments, separate object meshes and sound from one image. You run the project locally with your own API credentials; generation uses external services.
This guide reviews the project's documentation and source. We have not run its generation pipeline. Image3D has not added Image-Blaster, Marble or world-generation integrations.
What do you need to run Image Blaster?
The official quickstart starts in a terminal with Claude Code. The project also uses Node.js helpers and a Bun workspace for its viewer; see its setup and file conventions and workspace scripts.
- Prepare the local tools. Have Git, Claude Code access, Node.js and Bun available. Clone the official repository and open its directory in your terminal.
- Configure two API credentials. Copy the environment template to a private local
.env. SetWORLD_LABS_API_KEYfor environments andFAL_KEYfor object meshes, image editing and sound. Keep the keys out of shared files. - Stage the image and review the plan. Put your source image in
input/, startclaudein the project directory, and ask it to confirm each stage. Review the selected objects and cleaned background before approving generation. - Open the included viewer. The project documents
bun install, thenbun run devfrom the repository root. Open the local URL printed by the development server. This starts the viewer; the generation steps create its assets separately.
Open-source code does not include API usage. The repository uses an MIT license. Generation depends on your provider accounts: check World Labs API billing and fal usage pricing. World Labs states that Marble web-app credits cannot be used for its API. We have not measured a total cost or completion time for this workflow.
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.
What files does Image Blaster produce?
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 | .spz Gaussian splats, with separate collider .glb and panorama assets when returned, tracked by the world workflow source. | Use a compatible splat renderer for appearance; check collision geometry separately. |
| Objects | The README lists .glb/.obj meshes for dynamic 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 README lists .mp3 ambience and object effects; the Showcase attributes sound generation to ElevenLabs SFX. | Check looping, timing, levels and usage rights before sharing. |
Projects live under worlds/<slug>/. The file conventions separate source images, generated assets and scene.json placement state. Keep these together when reopening a project. The viewer reads local asset files, so a provider URL recorded in JSON is not enough if the corresponding download is missing.
An SPZ environment and a GLB object are different deliverables. World Labs provides specific SPZ rendering guidance for third-party engines. A normal mesh import path alone does not establish splat compatibility. For an individual exported GLB, use the existing Blender import and inspection guide.
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.
Public examples are free to view. New accounts need a paid pack or plan before generating their own model; existing credits and purchased access remain unchanged. Open Studio, upload your image, sign in when prompted and check the available plan before generating.
Open Studio for one object