3D model creation for AR app

Creating 3D Models for AR Application

A 3D model for AR isn't the same as one for film or game engines. Different requirements for polygon count, textures, formats, and scale. A model that looks perfect in Cinema 4D might deliver 5 FPS on iPhone and incorrect scale in ARKit.

Creating AR-ready 3D models is an entire pipeline: from references to optimized USDZ or GLB on CDN.

Technical Requirements for AR Model

Polygon count. For mobile AR—maximum 50,000–100,000 polygons per object. Multi-object scene: up to 300,000 total. Higher and FPS drops on non-PRO devices. For simple objects (box, glass)—500–3,000 polygons.

Textures. Maximum size—2048×2048 pixels. For small objects—1024×1024. Formats:

• iOS/USDZ: PNG or JPEG for diffuse, separate maps for normal, roughness, metallic
• Android/GLB: prefer JPEG for diffuse (smaller), PNG for transparency

UV unwrap. No overlaps, no stretching. Critical for AR: models are examined close-up; UV artifacts are visible.

Scale. 1 unit = 1 meter. Mandatory for correct ARKit/ARCore display. A 2.2-meter sofa is 2.2 units in scene. Check dimensions in Blender via N-panel before export.

Pivot point. Rotation and placement point—center of base for furniture, geometric center for others. ARKit places model relative to pivot. If pivot is wrong, object floats above floor or sinks through it.

AR Model Creation Pipeline

References → Low Poly modeling → UV → Texturing → Optimization → Export

Work primarily in Blender (free, powerful, Python API for automation). For organic shapes—ZBrush with retopology in Blender. Textures—Substance Painter for PBR materials.

Geometry optimization: Decimate modifier in Blender with quality control—removes polygons invisible at normal viewing angles. For round objects (vases, wheels)—shading via normal map, not geometry: 16-gon with normal looks like cylinder but 5x fewer polygons.

Baking. If source is high-polygon model (photogrammetry, CAD import), bake normal map, ambient occlusion, curvature in Substance Painter. This delivers high-polygon detail at low-polygon count.

Export to AR Formats

USDZ for iOS:

# Via Apple's reality-converter or usdz_converter
xcrun usdz_converter model.usda model.usdz
# Or via Python USD library
from pxr import Usd, UsdGeom

USDZ—ZIP archive with USD files and textures. Important: textures inside USDZ must be PNG (not JPEG) if transparency needed. Size: optimize via Apple's TextureConverter, ASTC compression for textures.

GLB for Android: Blender natively exports GLB with materials. Verify via Khronos glTF Validator—glTF errors often only manifest on device. Draco geometry compression via gltf-pipeline:

gltf-pipeline -i model.glb -o model_compressed.glb --draco.compressionLevel 7

Reduces geometry size 60–80%, no noticeable quality loss.

Working with CAD and Suppliers

Manufacturers provide STEP, IGES, SolidWorks files—precise CAD models with millions of polygons. Direct AR import = 2 FPS. Conversion pipeline:

1. Import STEP into FreeCAD or Fusion 360
2. Export to OBJ/FBX
3. Retopology in Blender (automatic via Remesh modifier, manual for important details)
4. UV and texturing
5. Export to USDZ/GLB

Time per CAD model: 4–16 hours depending on complexity.

Timeline

Cost calculated after reviewing references and required texture quality. Batch work (10+ models)—separate pricing.