Convert OBJ assets to glTF 2.0.
Install Node.js if you don't already have it, and then:
npm install --save obj2gltf
node bin/obj2gltf.js -i model.obj
node bin/obj2gltf.js -i model.obj -o model.gltf
node bin/obj2gltf.js -i model.obj -o model.glb
var obj2gltf = ;var fs = ;;
var obj2gltf = ;var fs = ;var options =binary : true;
Traditionally the .mtl file format describes the Blinn-Phong shading model. Meanwhile glTF 2.0 introduces physically-based materials.
There are three shading models supported by
If the material type is known in advance, it should be specified with either the
In general, if a model is authored with traditional diffuse, specular, and shininess textures the
materialsCommon flag should be passed in.
The glTF will be saved with the
KHR_materials_common extension and the Blinn-Phong shading model will be used.
However if the model is created with PBR textures, either the
specularGlossiness flag should be passed in.
See the command line flags below for more information about how to specify PBR values inside the .mtl file.
If none of these flags are provided, the .mtl is assumed to contain traditional Blinn-Phong materials which will be converted to metallic-roughness PBR. There may be some quality loss as traditional materials do not map perfectly to PBR materials.
Commonly in PBR workflows the the .mtl file may not exist or its values may be outdated or incorrect. As a convenience the PBR textures may be supplied directly to the command line. See the options below.
||Path to the obj file.||✅ Yes|
||Path of the converted glTF or glb file.||No|
||Save as binary glTF (.glb).||No, default
||Writes out separate buffers and textures instead of embedding them in the glTF file.||No, default
||Write out separate textures only.||No, default
||Do a more exhaustive check for texture transparency by looking at the alpha channel of each pixel. By default textures are considered to be opaque.||No, default
||Prevent the converter from reading texture or mtl files outside of the input obj directory.||No, default
||Pack the occlusion texture in the red channel of metallic-roughness texture.||No, default
||The values in the mtl file are already metallic-roughness PBR values and no conversion step should be applied. Metallic is stored in the Ks and map_Ks slots and roughness is stored in the Ns and map_Ns slots.||No, default
||The values in the mtl file are already specular-glossiness PBR values and no conversion step should be applied. Specular is stored in the Ks and map_Ks slots and glossiness is stored in the Ns and map_Ns slots. The glTF will be saved with the
||The glTF will be saved with the KHR_materials_common extension.||No, default
||Path to the metallic-roughness-occlusion texture that should override textures in the .mtl file, where occlusion is stored in the red channel, roughness is stored in the green channel, and metallic is stored in the blue channel. The model will be saved with a pbrMetallicRoughness material. This is often convenient in workflows where the .mtl does not exist or is not set up to use PBR materials. Intended for models with a single material.||No|
||Path to the specular-glossiness texture that should override textures in the .mtl file, where specular color is stored in the red, green, and blue channels and specular glossiness is stored in the alpha channel. The model will be saved with a material using the KHR_materials_pbrSpecularGlossiness extension.||No|
||Path to the occlusion texture that should override textures in the .mtl file.||No|
||Path to the normal texture that should override textures in the .mtl file.||No|
||Path to the baseColor/diffuse texture that should override textures in the .mtl file.||No|
||Path to the emissive texture that should override textures in the .mtl file.||No|
Run the tests:
npm run test
To run ESLint on the entire codebase, run:
npm run eslint
To run ESLint automatically when a file is saved, run the following and leave it open in a console window:
npm run eslint-watch
Coverage uses nyc. Run:
npm run coverage
For complete coverage details, open
The tests and coverage covers the Node.js module; it does not cover the command-line interface, which is tiny.
To generate the documentation:
npm run jsdoc
The documentation will be placed in the
Developed by the Cesium team.