3D Foundations & AI Asset Cleanup

3D is no longer only for specialists with years of modeling experience. Text-to-3D and image-to-3D tools can turn a prompt or a picture into a model in minutes. But the results are raw material, not finished assets. They often arrive with messy shapes, odd scale and lighting baked in. To sell 3D work, you need enough basics to know what usable means and how to get a model there.

The basics in plain words

• Mesh: a surface made of points (vertices), lines (edges) and faces, usually triangles or quads. The number of polygons drives file size and speed.
• Topology: how the faces flow. Clean, even topology bends and shades well. Messy, auto-made topology does not.
• UVs: a flattened map of the surface, used to place textures. Overlaps and stretching cause texture problems.
• Materials (PBR): a physically based material uses maps such as base color, roughness, metallic and normal. They describe how light interacts with a surface.
• Scale and origin: real-world units, and the model's pivot point. The wrong scale ruins AR and game use.
• Lighting and camera: how the model is lit and viewed. Renders need both, and real-time viewers bring their own.

File formats you will really use

• GLB and glTF: the JPEG of 3D, for the web and many real-time tools. GLB puts everything in one file.
• USDZ: Apple's format for augmented reality quick look on iOS.
• FBX and OBJ: long-standing formats for swapping between game engines and 3D tools.
• STL and 3MF: for 3D printing. STL holds shape only, with no color.
• Blend and other native formats: keep these as your editable source files.

What AI 3D generators are good for

• Concept props and background assets, single objects with simple outlines, stylized characters, quick prototypes and previsualization.
• Starting meshes that you will clean up, rebuild and re-texture.
• Quick exploration of shapes before you commit to hand modeling.

Typical problems to fix

• Dense, irregular triangle meshes that are heavy and hard to edit.
• Textures with shadows and highlights baked in, which look wrong under your lighting.
• Holes, broken geometry, flipped normals and floating fragments.
• Lopsided shapes or mushy detail where the source image was unclear. The back side is guessed.
• Wrong scale and origin, and unreadable text and small details.

A cleanup pipeline in Blender, or similar

1. IMPORT      Bring in the generated model; check scale against a reference (1 unit = 1 meter in many pipelines).
2. INSPECT     Look for holes, loose parts, flipped normals (face orientation overlay), intersecting geometry.
3. REPAIR      Merge by distance, fill holes, recalculate normals, delete floating pieces.
4. REDUCE      Decimate for a quick fix, or retopologize for clean quad topology when it will be animated/deformed.
5. UVs         Check for overlaps/stretch; re-unwrap if the generated UVs are poor.
6. TEXTURE     Re-bake or repaint base color without baked lighting; add roughness/metallic/normal maps if needed.
7. ORIGIN      Set the pivot at the base or center; apply scale/rotation so values are clean.
8. TEST        Drop it into the target (web viewer, engine, AR) under neutral lighting.
9. EXPORT      GLB for web; USDZ for iOS AR; keep the .blend source and a record of the generator + settings.

When to model by hand

Use AI generation for speed and exploring. Model by hand when you need exact sizes, such as products with real specs. Also model by hand for clean topology for animation, hard-surface accuracy, brand-accurate logos and parts, or guaranteed rights. Clients who buy a product visualization usually need the real product's exact shape. A text prompt cannot guarantee that.