Missing textures, broken rigs, flipped normals — why these happen and how to fix them
Converting a 3D file rarely goes perfectly wrong or perfectly right — most of the time, the mesh comes through fine but something specific breaks: a texture doesn't show up, a rig stops deforming correctly, or the model looks inside-out. Almost all of these issues trace back to the same root cause: the source and target formats don't support the same features, so something has to be dropped or reinterpreted during conversion.
This is the most common issue, and it's almost always a path problem, not a data problem. Formats like OBJ and FBX reference texture images by file path rather than embedding them directly. If those texture files aren't in the expected relative location when the model is opened, the material shows up blank or magenta.
Fix: Keep texture files in the same folder as the exported model, or use a format like GLB that embeds textures directly into the file so there's nothing to lose track of.
Rigs break during conversion when the target format either doesn't support skeletal animation (like OBJ or STL, which are static-only) or interprets bone hierarchies differently than the source format did. Converting an animated FBX character to OBJ, for example, will always produce a static mesh — the rig data simply has nowhere to go in that format.
Fix: Only convert rigged models between formats that both support skeletal animation — FBX and GLTF are the safest pairing for this. If you only need the mesh shape, converting to OBJ or STL is fine, but expect to lose the rig entirely.
If a model looks inside-out or has patches that appear invisible from certain angles, its normals (the direction each face is "facing") were likely flipped during conversion. This usually happens when converting between formats that define winding order (the order mesh vertices are listed in) differently.
Fix: Most 3D software has a "flip normals" or "recalculate normals" tool that can fix this in seconds once you've identified the affected faces.
A model that imports at 100x the expected size (or 1/100th) usually comes down to a units mismatch — some formats and tools default to centimeters, others to meters or inches, and the conversion process doesn't always carry that unit information forward correctly.
Fix: Check your source software's export unit settings before converting, and verify scale immediately after import rather than after building on top of the model.
Convert3D preserves geometry, materials, and textures wherever the target format supports them — free, with no signup.
Convert a File →