From reference image to indexed, downloadable 3D object
How the app.nz image-to-3D gallery connects reference images, reconstruction recipes, OBJ downloads, and production generation jobs.
A useful image-to-3D system needs more than one upload box. It needs examples you can inspect, stable recipes you can reproduce, and geometry you can download before committing a production generation job.
The new image-to-3D gallery pairs reference-image descriptions with live reconstructed Three.js meshes. Product footwear, furniture, collectibles, ceramics, helmets, and soft goods cover different silhouette and material problems instead of pretending one reconstruction preset works equally well for every object.
Indexed from input to output
Every entry includes a stable ID, source prompt, reconstruction stages, target polygon budget, expected PBR outputs, license note, JSON recipe, and preview OBJ. That means an agent can find a relevant starting point without reading UI markup:
app animation search product --kind image3d
app animation download image3d-sneaker --format obj --output sneaker.obj
app animation image-to-3d --image-url https://example.com/reference.webp --target-polycount 50000The public REST contract is GET /api/animation-library?kind=image3d, GET /api/animation-library/{id}/download?format=obj, and POST /api/animation-library/image-to-3d. Authenticated production jobs use the existing POST /v1/3d/generations route.
The open object kit owns the recipe, deterministic OBJ fixture generator, and stage vocabulary. Generated-asset rights still depend on the source image; the API says that directly rather than making a blanket ownership claim.