How to Import 3D Models into Daz Studio: FBX, OBJ and the GLB Detour

Daz Studio is built around figures: it poses, morphs, clothes and renders Genesis characters, and its own content arrives as DSON assets carrying rigs, morph dials and material presets. A mesh from anywhere else brings none of that context, so importing one is largely a decision about what you are willing to rebuild by hand.

Three problems cover almost every failed import: the mesh loads invisible, it loads at the wrong scale, or it loads grey. Each has a specific cause and a specific fix.

This tutorial follows the order the questions arrive: what Daz Studio reads, which format to use, how to land on the right scale the first time, and how to repair opacity, materials and rigging afterwards.

What Daz Studio imports, and what it silently refuses

Open File > Import in your build and you get the real list: OBJ, FBX, DAE (Collada) and the older Poser-era formats. Those importers are plug-ins, so the set depends on your installation. What is missing matters more: no glTF or GLB, no USDZ, no .blend, no STL. That is inconvenient, because GLB is what AI generators and marketplace downloads usually hand you. The conversion belongs in another application, before you open the import dialog.

Pick the carrier: FBX for rigs and hierarchies, OBJ for static props

FBX is the better container when the asset has several parts or a skeleton: a binary FBX 7.x file holds node hierarchy, joint transforms, skin weights, UV sets and material names, so a multi-part prop arrives as separate nodes you can move individually. OBJ holds geometry, UVs and material groups, and its MTL lists colours and texture paths, but there is no hierarchy or skeleton. For a single static mesh, OBJ is enough.

The GLB-to-Blender-to-FBX route, step by step

1. Blender: File > Import > glTF 2.0, then check the object size in the N panel.
2. Apply the object transform with Ctrl+A and All Transforms; leftover scale or rotation usually causes a wrong-size import.
3. Scale the mesh so a human-sized asset measures about 1.8 m, the height of a Genesis figure.
4. Name the object and every material slot; those names appear in the Daz panes.
5. Export FBX with Path Mode set to Copy so textures are written beside the file, and keep Apply Modifiers on.

Scale: one Daz unit is one centimetre

Daz Studio works in centimetres, which is why a Genesis figure stands roughly 180 units tall, about 1.8 m. Blender, Unity and most glTF exporters think in metres, so an asset exported at one unit per metre arrives about 100 times too small, and one authored in millimetres ten times too large. Larger errors are common, because unit metadata in exported files is inconsistent. Keep a Genesis figure in the scene as a ruler: a mesh reaching its ankle instead of its shoulder is off by about three, and one that shrinks to a speck by 100.

Repairing scale without wrecking the scene

• Fix scale in the modelling application: export a Genesis OBJ from Daz, match your mesh to it, then export again.
• If you must correct on import, use the scale field in the dialog; a non-default node scale misbehaves when you transfer rigging later.
• Node scale is harmless on a plain prop, but reset it to 100 percent before saving it as a support asset.
• Check rotation too: Daz expects Y up, so a Z-up export arrives on its back.

An invisible OBJ is almost never a geometry problem

The usual OBJ complaint is a mesh that appears in the Scene pane and then renders see-through. The geometry imported fine; the surface arrived with its opacity turned down. A low dissolve value in the MTL, or an opacity map pointing at a texture the importer could not resolve, is enough to make a surface fully transparent. The older Daz default shader calls that value Opacity Strength, a percentage, while Iray Uber Base calls it Cutout Opacity, from 0 to 1. Check that number before blaming normals or a damaged file.

1. Select the node in the Scene pane and open the Surfaces pane.
2. Read Opacity Strength or Cutout Opacity; at 0 or 0 percent, set it to 1 or 100 percent.
3. Clear any opacity map slot pointing at a missing image; a broken reference can hold a surface transparent.
4. Still invisible? Measure it against Genesis; a mesh 100 times too small is easy to miss.
5. Then rebuild the material: assign Iray Uber Base and reapply base colour, roughness and normal maps.

Grey or missing textures: the MTL stores paths, not pixels

An OBJ file contains no pixels. The MTL beside it lists paths, usually relative ones such as textures/body_diffuse.png, so moving the OBJ without its folder structure breaks every one of them. That is why a model that looked right in the vendor's preview arrives grey and untextured. Keep the three together in the same relative layout, and treat absolute paths from another machine as broken. GLB avoids this because textures travel inside the file, but Blender's FBX exporter set to Path Mode Copy writes them out again.

Rigging, posing and morphs for a mesh from outside Daz

An imported mesh is static geometry. When an FBX carries a skeleton and weights, Daz can build a figure with bones from it, but rig transfer between applications is the least dependable part of this pipeline: helper joints and corrective shapes usually arrive as plain bones needing weight rework. Two tools matter. Edit > Figure > Transfer Utility copies a rig from a source figure onto a target mesh, and the target must fit that figure in the zero pose; a mesh authored for Genesis 9 follows a pose correctly, while one that merely looks close tears at the shoulders and hips. Edit > Figure > Morph Loader Pro loads an OBJ as a morph target whose vertex count and order must match the base figure. FBX blend shapes rarely become morph dials.

Where AI-generated meshes fit, and what to clean first

Generators such as Hunyuan3D, TRELLIS 2, Tripo, Meshy and Rodin typically return one textured mesh in the tens of thousands to a few hundred thousand triangles, depending on the engine. Open3DAI (a Open3DAI product) covers text-to-3D and image-to-3D generation, multiview input, AI texturing and export to GLB, glTF, OBJ, STL, PLY and 3MF; the same deployment can compare the available engines side by side on one prompt before you export, and it ships 48 format converters, 12 browser tools and a REST API. Its limits matter here too: it does not rig, animate, retopologise or unwrap UVs, and it does not promise watertight output. A generated character needs the same cleanup as any marketplace mesh.

• Scale to centimetres against an exported Genesis reference and apply the transform.
• Check that normals point outward and no faces are loose or zero-area; Meshmixer handles both.
• Split the parts before export: separate nodes stay separate in Daz and move individually.
• Keep the textures beside the exported file and open each map once.

Run it yourself in Open3DAI

Send the same prompt or image to several engines, compare the meshes side by side, then export GLB, glTF, OBJ, STL, PLY or 3MF. Creating an account grants free credits and needs no card.