img2threejs Tested: Can Codex Turn One Image into a Three.js 3D Model?
I tested img2threejs with GPT-5.6 SOL at medium reasoning. Complex subjects such as an F1 car failed quickly, while a simple NES controller produced clickable buttons, multiple views, and an exploded view. This article covers the results, practical limits, and Codex installation.
Introduction
The name img2threejs is very literal: give an agent a reference image and have it rebuild the object as an interactive Three.js 3D model in the browser.
It does not directly convert the photo into a mesh, and it is not photogrammetry. The agent first breaks down the silhouette, parts, materials, and details, then recreates them with Three.js geometry, materials, and code. In theory, the workflow moves through blockout, structure, form, materials, lighting, interaction, and optimization.
For this test, I used GPT-5.6 SOL with medium reasoning. I started with a complicated subject, an F1 car, and the result failed rather clearly. A few wrong curves, body proportions, tires, or aerodynamic parts are enough to make the final model look like a generic race car instead of the specific car in the reference.
I then switched to a much simpler NES controller. I ran one complete task and did not continue with repeated rounds of manual refinement. The result included the shell, D-pad, Select and Start controls, A and B buttons, and cable. It also supported view switching, part selection, and an exploded view. I would not call it polished, but it was acceptable as a rough demo.
The NES controller generated with GPT-5.6 SOL at medium reasoning
This video shows the complete test, including model rotation, clickable controls, and the exploded view produced by the agent.