Hitem3D 3.0: The Essentials

Last updated: August 21, 2026

Hitem3D 3.0 turns one photo, or up to four reference views, into a full 3D asset in a single pass. It generates at 2048-cube voxel resolution, roughly double the detail of the earlier 1536-cube standard, and lets you choose between a clean mesh-only output for pipelines that do their own texturing, or a fully textured PBR asset ready to drop into a scene.

How to Use the Model

Single Photo or Multiple Views

The simplest way to use Hitem3D 3.0 is a single, sharply lit photo of the subject on a plain background. That is enough for most props and objects.

Single-photo input, 2048 Quality, mesh + PBR texture · Open the 3D result on Scenario

For a sharper reconstruction, upload up to four views in this order: front, back, left, right. Testing surfaced an important caveat: when the views come from separate photos or separate generations rather than a real object on a physical turntable, front and back combine cleanly, but adding a left or right profile frequently deforms the mesh, especially on wings, limbs, or other asymmetric features. A profile view exposes the one axis the model has the least information about, and it is also the axis most sensitive to any small difference in pose or proportion between shots. If you cannot guarantee an identical camera distance, height, and lighting across all four shots (the setup a physical turntable gives you for free), stick to front and back.

Mesh Only or Fully Textured

Output Type controls whether you get a textured asset or bare geometry. Mesh + Texture (the default) returns a full PBR material alongside the mesh. Mesh Only skips texturing entirely and returns a clean, un-textured mesh, useful when the asset is headed into a retopology or hand-painting pipeline instead.

Single-photo input, 2048 Master, Mesh Only (no PBR) · Open the 3D result on Scenario

Quality or Master Resolution

2048 Quality is the default and balances detail against cost and speed. 2048 Master pushes for the highest geometry and topology quality the model can produce, at a noticeably higher cost and a longer runtime: in testing, a Master run took roughly four times as long as the equivalent Quality run.

Single-photo input, 2048 Quality, mesh + PBR texture · Open the 3D result on Scenario

Parameters

Every generation needs at least one image; the rest of the dials control output type, geometry budget, and material.

images

Required. Upload 1 to 4 images, starting with the front view. For multi-view input, add back, left, and right in that order. Front plus back alone gave the most reliable results in testing; see the multi-view note above before adding side profiles.

requestType

Output Type. Mesh + Texture (default) returns a full mesh with a PBR material. Mesh Only returns bare geometry with no texture, for pipelines that texture separately. See the Mesh Only example above.

resolution

Generation Resolution. 2048 Quality (default) balances geometry detail against cost and speed. 2048 Master maximizes geometry and topology quality and costs noticeably more. See the Quality vs Master example above.

face

Max Faces, from 100,000 to 5,000,000 (default 2,000,000). Pair roughly 2,000,000 with 2048 Quality; only push toward 5,000,000 when also using 2048 Master; a Quality pass will not resolve enough detail to use the extra faces.

pbr

true / false, default true. Generates a PBR material when Output Type includes texture. Has no effect when Output Type is Mesh Only, since there is no texture to apply a material to.

Use Cases

  • Game props: turn a concept render or reference photo of a weapon, tool, or hard-surface prop into a game-ready mesh with PBR materials.

  • Film and previz assets: block out set-dressing objects from reference photography without a manual modeling pass.

  • Product visualization: turn a single product photo into a spinnable 3D asset for an e-commerce page or configurator.

  • Collectibles and tabletop: convert a sculpt, miniature, or figure photo into a clean digital mesh for reprints or digital display.

  • Retopology and hand-painted pipelines: use Mesh Only to get clean base geometry, then texture it by hand or in a separate tool.

Tips for Better Results

  1. Light the subject evenly and keep the background plain. Harsh shadows get baked directly into the reconstructed geometry and texture.

  2. Frame the subject at 60 to 80 percent of the image. Extreme close-ups with cropped edges reconstruct poorly.

  3. For multi-view input, use front and back only unless you can shoot all views on a real turntable with identical distance, height, and lighting. Independently generated or photographed side profiles are the most common source of deformed limbs and wings.

  4. Use 2048 Quality for iteration, 2048 Master for the final hero asset. Master costs meaningfully more and runs several times slower, so save it for the shot that matters.

  5. Match Max Faces to your resolution mode. Around 2,000,000 faces suits 2048 Quality; only raise it toward 5,000,000 alongside 2048 Master.

  6. Choose Mesh Only when you plan to texture by hand. It skips PBR generation entirely and returns a lighter, cleaner mesh.

  7. Avoid reflective, transparent, or very glossy subjects. Glass, chrome, and mirrored surfaces reconstruct far less reliably than matte materials.

Known Limitations

  • Independently sourced side profiles can deform the mesh. When front, back, left, and right come from separate photos or generations rather than one rigid object on a turntable, any mismatch in pose or proportion is most visible in the profile views, and the reconstruction can warp wings, limbs, or other asymmetric parts trying to reconcile them. Use front and back only in that case.

  • No text prompt input. The model is conditioned purely on the uploaded images plus the four numeric and boolean parameters; there is no way to steer style or fix an issue with wording.

  • Mesh Only output defaulted to a private asset in testing, while Mesh + Texture output defaulted to public. If you need to share a Mesh Only result, check its privacy setting after generation.

  • Occasional transient errors shortly after a model launches. A generation can fail with a generic internal error under normal parameters; retrying after a short wait resolved every case seen in testing.