Advanced
Troubleshooting
Fix common Convert3D issues
Use this page to diagnose common problems.
Conversion fails
Check:
- The input format is supported.
- The output format is supported.
- The file extension matches the actual file type.
- Required sidecar files are included.
- The source file opens in the app that created it.
If the extension is wrong, rename the file to the correct extension and try again.
Textures are missing
Common causes:
- OBJ was uploaded without its
.mtlfile. - Texture image files were not uploaded with the model.
- The source file uses absolute local paths.
- The target format does not support the same material features.
For web display, try converting to glb because it can contain textures in one file.
The model looks wrong after conversion
Check scale, orientation, and material support. Some source formats store scene data that does not map cleanly to every output format.
Try converting to glb first and inspect the model in the viewer.
DWG or DXF output is not what I expected
First decide whether the next app expects a 3D object or a 2D drawing.
- Use
3D / Meshwhen the result should stay a 3D model. - Use
2D / Multiview drawingwhen the result should be front, top, and right-side drawing views. - Use
steporstpwhen the next app needs solid CAD exchange more than DWG/DXF.
See DWG and DXF for the full checklist.
Compression says the file is not GLB
The compressor expects a GLB file. Convert the model to glb first, then compress the GLB.
AI generation fails
Check:
- You are signed in.
- Your account has credits or available usage.
- The input image is clear enough for 3D generation.
- The prompt is specific and does not ask for incompatible details.
For image-to-3D, use a clear image with the main object visible.