Which 3D File Format Should You Export From CLO: OBJ, FBX, glTF, Alembic, or USD?

Choose the format by where your garment goes next. Send a static mesh as OBJ, an avatar with joints and cameras as FBX, a web or real-time model as glTF, simulated cloth motion as Alembic, and a shared multi-app scene as USD.

CLO imports and exports OBJ, FBX, and Alembic files, and it supports glTF and USD too. So the question is which one saves you the most cleanup in the next app.

Which CLO Export Format Fits Your Workflow?

If you need to… Export Why
Move a garment mesh into another 3D app OBJ Contains geometry and material information, plus an MTL file with material properties
Send avatars, joints, cameras, or animation FBX Contains mesh, material, joint, animation, and camera information
Publish to web or real-time viewers glTF / GLB Can include lights, animation, and embedded textures
Deliver simulated cloth motion Alembic Saves vertex and animation information in an interchange format
Take an animation to 3ds Max or Maya Animation cache (MC, PC2, MDD) Vertex animation data in point cache format
Work across several 3D apps in one scene USD Layers and Prim Paths keep each asset organized

All of them live under File ▶ Export in the top menu. Pick one, set a save path, then adjust the options in the export window.

When Should You Export OBJ From CLO?

Use OBJ when you need a clean mesh to open in other 3D software. OBJ carries geometry and material information. Go to File ▶ Export ▶ OBJ (or OBJ (Selected) to export only what you pick). CLO creates an MTL file next to it that stores the material properties.

These export options matter most:

  • Single Object / Multiple Objects: Decide whether the garment leaves as one mesh or as separate pieces.
  • Unweld / Weld: Choose whether sewn pattern edges export as separate vertices or one merged point.
  • Thin / Thick: Include the garment’s thickness or leave it flat.
  • Combined UV Coordinates: Export a combined UV layout with the file.
  • Save with Texture Files (ZIP): Bundle the textures with the OBJ.
  • Save Colorway: Export your colorways along with the mesh.

OBJ is also the format you mainly use to bring avatars and related sources into CLO. You can import an OBJ as an avatar, a trim, a garment (for example a mesh built in Maya or 3ds Max), or a morph target. Two details to know before you import:

  • OBJs imported as trims do not calculate collision.
  • Arrangement Points generate properly only when the avatar is in an A-pose or T-pose.

When Is FBX the Better Choice?

Choose FBX when the file needs more than a static mesh. An FBX file contains mesh, material, joint, animation, and camera information, so it suits avatars and scenes with motion.

Go to File ▶ Export ▶ FBX and look at these options:

  • Animation: Saves the animation information in the file.
  • Cache Animation (MC): Saves your recorded garment animation as cache data.
  • Entire Region / Play Region Only: Export every animation key, or only the frames inside your playback range.
  • Relative Texture Image File Path: Saves only the texture name, so textures load automatically when the FBX and the images sit in the same folder.
  • Diffuse Color Combined on Texture: FBX files cannot hold every texture image and color value, so this option bakes the applied color into the texture.

On import, set the Object Type to Avatar or Trim. Among avatar skinning types, Dual Quaternion and Eblend are not compatible with CLO. If an import throws a character error, make sure the file name and the entire folder path use English characters.

What Does glTF Give You for Web and Real-Time Use?

Pick glTF 2.0 (GLTF/GLB) when your garment is headed to a viewer or a real-time scene. Go to File ▶ Export ▶ glTF 2.0 (GLTF/GLB). The export window gives you:

  • Light: Export lights along with the garment (render lights are excluded).
  • Garment Animation and Avatar Animation: Export garment motion, plus joint or cached avatar animation.
  • Save Colorway and Combine to One File / Multiple Files: Put all colorways in one file or give each its own.
  • Save with glTF-Embedded (GLTF only): Save textures inside the glTF file.
  • Save with Zip Files (ZIP): Package the export for sharing.
  • Save with MetaData (XML): Keep pattern mesh, physical properties, and sewing information.

Watch the Scale setting. The common default unit for glTF is meters, so confirm your unit before you export.

Why Choose Alembic for Garment Animation?

Alembic is an interchange file format for computer graphics that saves both vertex and animation information. In CLO, it stores the object, cache, normal, and animation data, so you send the simulated drape frame by frame instead of rebuilding it in the next app. Go to File ▶ Export ▶ Alembic.

  • File type: Choose OGAWA or HDF5.
  • Unweld / Weld and Thin / Thick: Same logic as OBJ.
  • Include Avatar Shape: Save the avatar as part of the file.
  • FPS and Scale: Set the cache frame rate and the output size.

When you import an Alembic file, Garment Position moves the garment to the location of the first frame.

When Does USD Make Sense?

USD is a graphics standard format built for collaboration across 3D software. You can export garments, avatars, and trims with meshes and materials. Go to File ▶ Import / Import (Add) / Export ▶ USD.

  • Prim Path: Choose whether to export meshes and materials, and set the Prim Path they depend on. Materials are stored in a textures folder inside the saved USD folder.
  • USD Layer window: Open it from Settings ▶ Display ▶ Windows ▶ USD Layer. Select assets in the 3D or 2D window, right-click, and choose Export to USD Layer to send them to the Authoring Layer.
  • Omniverse Connector: With a session connected in Omniverse USD Composer, Export to USD Layer sends your CLO work straight into it.

The CLO Help Center also has step-by-step guides for CLO to MetaHuman: USD Garment Integration Workflow and CLO to Twinmotion: FBX Workflow.

Which Other 3D Formats Does CLO Support?

Beyond the five main formats, CLO handles three more file types for specific jobs:

  • **Animation cache (*.mc, .pc2, .mdd): Vertex animation data that CLO can import and export. Use it to take an animation made in CLO to 3ds Max or Maya in point cache format.
  • COLLADA (*.dae): Import only. Export the file from software such as 3ds Max, Maya, or DAZ Studio. It contains geometry and material, plus rigging, skinning, and animation data. When you export COLLADA from 3ds Max or Maya, install the OpenCOLLADA plugin so you can use the file as an avatar.
  • LXO (*.lxo): Export only. It contains geometry and material information and sends apparel and avatars to Modo.

How Do You Save Export Settings as a Preset?

Set your options once and reuse them. Presets arrived in CLO 2025.1 and work for OBJ, FBX, glTF 2.0, Alembic, USD, Maya Cache, Point Cache 2, MDD Cache, and OBJ Sequence.

  1. Click File ▶ Import/Export and select the 3D file.
  2. Set your import or export options.
  3. Click Add under Preset.
  4. In the Create Configuration window, set the Preset File Path and Name.
  5. Click Save.

Each file type needs its own JSON preset file, so an FBX preset cannot be reused for glTF. You can share preset files with teammates, which gives your studio or class one set of export standards.

Wrap-Up

Match the format to the destination, set the options once, and save them as a preset. Open any garment in CLO, run one export in each format you use, and check the result in the receiving app. You can try this with a free trial of CLO.


Sources:

Leave a Reply