GuideIntermediate11 min

Export FBX 7.5 for DCC and real-time tools

Choose an FBX consumer profile, scene structure, origin, instances and appearance, then validate the static scene in its destination.

Choose the receiving profile

Use Binary FBX 7.5 for the normal compact interchange path; choose ASCII only when a receiving or diagnostic requirement needs readable records.
Select General DCC, Blender, Unity or Unreal according to the actual downstream application.
Use the profile as a tested baseline, then change units, axes, origin or structure only when the destination project requires it.

Decision table
Decision	Choose	Effect
Structure	Source model, element or merged	More merging reduces nodes but sacrifices element selection and property granularity.
Origin	Federation center, Preserve world or Explicit coordinate	Smaller coordinates improve downstream float behavior; preserve world only when required.
Instances	Preserve or expand	Preserving can reduce file size when the receiver handles shared geometry correctly.
Appearance	Original or Persistent overrides	Persistent live overrides require Standard Export; Fast reads saved appearance.

FBX v1 writes triangle meshes only; curves and points are not exported.
A receiver can reinterpret axes, units, pivots or material transparency; verify rather than assuming its profile defaults.
Merged structure cannot preserve the same per-element navigation as an element hierarchy.

Open in the exact consumer version
Importer behavior changes by release and project template.
Check axes, unit and origin
Measure a known length and compare a control point or aligned source.
Check hierarchy and selection
Confirm the chosen structure exposes the objects the team needs.
Check repeated geometry and appearance
Inspect instances, normals, opacity and representative colors.
Retain the report
Record the consumer profile and any custom overrides with the delivered FBX.