Skip to main content
Back

Camera-to-Blender Turns One Phone Photo Into a 3D Asset in 60 Seconds

A new open-source tool from the creator of blender-mcp turns phone snapshots into Blender-ready 3D models in under a minute using Tripo3D.

Repo, Full Access
  • Siddharth Ahuja released camera-to-blender, an MIT-licensed tool that photographs objects and generates Blender meshes.
  • End-to-end time is 30 to 60 seconds per object, phone to viewport.
  • Stack: FastAPI relay server, Tripo3D API for generation, Gemini for optional background removal, ngrok for HTTPS phone access.
  • Blender add-on connects over WebSocket (wss://.../ws?client=blender) to auto-import finished models.
  • Requires a Tripo3D API key; Gemini key is optional; laptop webcam works without ngrok.
  • Known issue: hard-coded Tripo model IDs now return error 2015, needs v3 API patch.

Siddharth Ahuja, creator of the popular blender-mcp project, has released camera-to-blender, an MIT-licensed tool that sends a phone photo through an image-to-3D service and imports the resulting model into Blender. The process typically takes 30 to 60 seconds, giving developers and artists a fast way to create blockout assets without a scanning rig or manual file transfers. The repository has 34 GitHub stars.

From shutter to viewport

A local FastAPI server coordinates the workflow. A browser-based camera interface uploads the photo, Gemini can remove its background, and Tripo3D generates the 3D asset. The server then sends the finished model to a Blender add-on over a WebSocket connection.

  1. The phone captures and uploads one image.
  2. Gemini removes the background when an API key is configured.
  3. Tripo3D generates a preview and final model.
  4. The relay sends the result to Blender.
  5. The add-on imports the model into the active scene.

The approach avoids the overlapping photographs, camera calibration, feature matching, and reconstruction stages used by photogrammetry. Tripo instead infers a complete object from the visible surface, including geometry the camera never captured.

Three services, one thin relay

Component Role Requirement
FastAPI relay Accepts uploads, calls external APIs, and coordinates delivery