PORTABLE 3D MODEL EXPORT

Texture-baked 3D exports to USDZ, GLB, and OBJ

Standard 3D exporters drop custom surface finishes, uploaded logos, and true-scale wood or fabric tiling when saving a file. Aircada bakes live surface finishes and decals into portable 2D textures in the browser and exports the customer's exact configured build to USDZ, GLB, GLTF, or OBJ.

Texture-baked 3D exports to USDZ, GLB, and OBJ

Why standard 3D exports lose custom finishes and decals

When a customer configures a bespoke pendant fixture, a custom-wrapped cornhole board, or a modular lab bench in the browser, the live 3D viewport relies on dynamic procedural shaders, world-scale UV projections, and canvas-rendered customer logos. Running a naive 3D exporter directly on that live scene fails because external AR viewers and desktop CAD tools cannot evaluate browser shader graphs, leaving buyers with blank white models or missing artwork.

Aircada solves this with an isolated preparation and baking pass before serialization. Through procedural shader-to-texture baking and client-side USDZ and GLB synthesis, the exporter clones only the customer's visible configured parts, flattens active surface effects and decals into standard 2D texture maps, applies viewer-specific calibration (including wall-mount alignment and iOS AR roughness tuning), and outputs a self-contained file ready for instant download, mobile AR launch, or upload alongside Shopify and headless quote or order workflows.

EXPORT PREPARATION SPEC

How live 3D customizations become portable CAD and AR files

Aircada clones the active 3D scene into an isolated buffer, bakes dynamic finishes into 2D textures, and serializes the target format on demand.

USDZ (iOS AR)Binary GLBJSON GLTFWavefront OBJ
LIVE CONFIGURED 3D SCENE
Bespoke leather and oak lounge chair with live procedural node shaders and dynamic fabric weave in the browser viewport

Procedural shaders, world-space UVs, and dynamic decals

PORTABLE 3D ASSET PACKAGE
Exported 3D lounge chair asset alongside its baked 2D base color, normal, and roughness texture maps

Self-contained USDZ, GLB, GLTF, or OBJ with baked 2D PBR maps

Supported Export Formats

Apple USDZ (.usdz), Binary glTF (.glb), JSON glTF (.gltf), and Wavefront OBJ (.obj), loaded lazily on demand

Shader & Texture Baking

Inspects active PBR channels and bakes live procedural finishes and decals into standard 2D texture maps with diffuse caching

Scene Sanitization & Orientation

Clones visible assemblies, strips hidden variants and helpers, preserves animations, and supports Z-up or wall-mount alignment

Target Calibration Profiles

Apple AR Quick Look profile (1.15x roughness compensation) and Web-optimized GLB profile (1.0x standard PBR)

All scene cloning, texture baking, and binary serialization execute directly on the client device with mobile memory yields between sub-assemblies.

Two export adaptation profiles for AR and CAD/Web

Tailor material sheen, orientation, and texture packing to the destination viewer.

Apple iOS AR Quick Look (USDZ)

Apple's native iOS AR Quick Look renderer evaluates specular highlights glossier than standard browser viewports. When exporting for iPhone AR, Aircada applies a 1.15x roughness calibration multiplier, bakes custom finishes and decals, and supports automatic vertical wall-mount rotation so wall-hung products snap flush to vertical room planes.

  • Generates self-contained USDZ archives directly in Safari on iPhone and iPad with zero server wait
  • Applies a 1.15x roughness multiplier so satin wood, leather, and brushed metal stay natural in iOS AR
  • Automatic wall-mount alignment (-90 degree rotation with back contact snapped to plane) for wall signage and fixtures
  • Launches straight into {{@link:capabilities.3d-technology.ar-room-placement|label=room-scale AR placement}} without installing a native app
Apple iOS AR Quick Look (USDZ)
DEPLOYMENT WORKFLOWS

How brands use real-time 3D model export

Bridge browser customization with mobile augmented reality and architectural specification.

Responsibility Tiers

  • 1 Native Aircada layer
  • 1 Aircada Configuration layer
  • 1 Custom Implementation layer
  • 1 External layer

Responsibility Boundaries Across 3D Model Export

How Aircada's export pipeline, Studio export triggers, custom quote/order routing, and external viewers divide responsibilities.

Scene sanitization, shader-to-texture baking, roughness calibration & USDZ/GLB/GLTF/OBJ serialization

  • Native Aircada
  • On-demand exporter loading, isolated hierarchy cloning, dynamic finish baking to 2D textures, 1.15x AR Quick Look roughness adjustment, wall-mount and Z-up orientation, and browser binary/file generation.

Target format selection, permissions & export action bindings

Gated B2B lead-capture forms & order-record file upload

  • Custom Implementation
  • Wrapping the browser export file behind an architect registration modal or uploading the exported 3D package to your CRM, quote builder, or Shopify order storage.

Downstream third-party viewer lighting (iOS Quick Look, SketchUp, Revit)

  • External
  • How external software environments light and shade the exported USDZ, GLB, or OBJ file once opened outside the browser.

Frequently Asked Questions

Why do custom 3D finishes and decals need to be baked before exporting to USDZ or GLB?
External viewers like iOS AR Quick Look or desktop 3D software only read standard static 2D texture maps rather than live browser shader graphs. Aircada's procedural shader-to-texture baking renders your active finishes, world-scale UVs, and customer decals into flat 2D PBR maps during export so the model looks consistent outside the browser.
Why does Aircada adjust material roughness when exporting to Apple USDZ?
Apple's native iOS AR renderer evaluates PBR roughness differently than browser viewports, which can make matte wood or satin metal look overly shiny in a customer's room. Applying a 1.15x roughness calibration multiplier during USDZ export keeps surface sheen natural in iOS AR Quick Look.
Which 3D file formats can be exported live in the browser?
Aircada exports Apple USDZ (.usdz), binary glTF (.glb), JSON glTF (.gltf), and Wavefront OBJ (.obj) directly on the client device, loading each exporter lazily on demand so initial page load stays fast. Project owners control which export formats are allowed via Studio's publishing and export permissions.
Are hidden accessories or inactive option meshes included in the exported file?
No. During the preparation pass, Aircada clones only the active visible hierarchy into an isolated export scene and strips out hidden variants, helper gizmos, and inactive cameras. It also supports optional center-origin alignment, Z-up axis conversion, and wall-mount orientation before saving.
NEXT STEP

Keep large 3D catalogs fast with automated model compression

Reduce polygon counts with quadric error metrics and compress vertex buffers for instant mobile loading.

CONNECTED CAPABILITIES

Related capabilities

Explore the adjacent capabilities and integrations that pair with this workflow.

Engineering CAD to web-ready 3D conversion
CAD TO WEB PIPELINE
CAPABILITY

Engineering CAD to web-ready 3D conversion

Explore
Split one 3D model into customizable parts
MULTI-MESH DECOMPOSITION
CAPABILITY

Split one 3D model into customizable parts

Explore
Browser-rendered 4K and 8K product proof exports
production and fulfillment
CAPABILITY

Browser-rendered 4K and 8K product proof exports

Explore
Place customized 3D products at true scale in any room
3d technology
CAPABILITY

Place customized 3D products at true scale in any room

Explore

Sean Chenoweth
WRITTEN BY
Sean Chenoweth
Co-founder, Aircada
Published Updated