Props on Pro. Characters that move on Studio.

Start with the prop

Name the object, the style, and the material, or upload the concept. The first result is a mesh with UVs and PBR maps. If the silhouette is right, stop regenerating.

Retexture when the material is wrong. Remesh when the density is wrong. A background prop can take a lower face budget than a hero asset.

Rig only what moves

A crate, a weapon on a rack, and a statue do not need a skeleton. Export GLB or FBX from Pro and drop them in.

A character that idles, walks, or runs needs auto-rig. That preview, and the rigged FBX, is on Studio. Unusual creatures still want a hand-authored rig in a DCC tool.

Hand off the file the engine expects

GLB is the safe real-time file. FBX is the better choice when the project already imports FBX, and it is the file a rig exports to.

Studio also includes API access, which is the path when a pipeline generates assets instead of a person clicking through one at a time. Enterprise is volume, SSO, and custom terms.

Limits to check before delivery

A generated prop is not automatically a production-ready game asset. Collision, LODs, shader conversion, and project-specific budgets remain separate tasks. A static engine import does not itself require Studio; rigging or API access is the reason to upgrade.

• Unity Manual — importing a model
• Godot documentation — available 3D formats
• Khronos — glTF 2.0 specification

Handoff checklist

Place the asset beside a scale reference in the project. Check triangle count, materials, bounds, pivot, and collision behavior. Test at the shipping camera distance. For an animated character, check deformation and root motion rather than treating an import success as final approval.