Convert OBJ to FBX in your browser
This local converter reads a supported standalone OBJ mesh. File conversion happens in your browser. Check the format limits below before using the result.
Choose a file to convert.
Local mesh input up to 50 MiB. Unsupported features are rejected; read the format limits before converting.
A quick visual guide
OBJ to FBX converter
01Input
Use the source files or project information described below.
02Adjust
Change the relevant controls, then compare against your source.
03Check the result
Inspect the result and the stated limits before you use it.
Open each step for the practical check. Diagram, not a generated result.
OBJ to FBX converter
Convert a supported standalone OBJ into a static FBX mesh with a neutral grey material, locally in your browser. OBJ textures and materials are not carried over, and neither are UVs. Select the units your source was modelled in, then check the downloaded file in your target application. Need the original materials? Export FBX from your modelling application instead.
What this converter accepts
| Input | One standalone .obj file, up to 50 MiB: a static polygon mesh (OBJ geometry) made of triangles and quads |
|---|---|
| Output | One ASCII FBX 7400 file: static geometry and normals with one neutral grey material |
| Limits | Up to 250,000 vertices, 500,000 triangles and 1,000 meshes; the FBX is capped at 100 MiB |
| Rejected | Points, lines and free-form curves or surfaces; faces with more than four corners; zero-area triangles and non-finite coordinates |
| Not read | MTL files and texture images. This is a single-file route |
Two choices are required before the Convert button works: the units your source was modelled in, and the box accepting a static mesh with a neutral material.
What transfers and what you lose
FBX can carry much more than this converter writes. Treat the result as a static geometry hand-off and keep the OBJ as the master.
| OBJ information | FBX result | Action to take |
|---|---|---|
| Vertex positions | Written, scaled from the units you choose and stored in centimetres | Check one known dimension after import |
| Normals | Written per face corner | Check the shading for flipped or faceted areas |
| Faces | Triangles kept; each quad written as two triangles. Larger polygons are rejected | Triangulate larger polygons in the modelling application first |
| Transforms | Baked into the vertices | Expect each mesh at the origin with no rotation or scale of its own |
| Materials, UVs and textures | Not retained: one neutral grey material replaces them | Export FBX from the modelling application when textures matter |
| Vertex colours | Not retained | Keep the OBJ if the colours are needed |
| Object names and hierarchy | Not retained: meshes are named Mesh_1, Mesh_2 and so on, side by side | Rename or regroup the parts in the destination if needed |
| Size budget | An estimate can reject the file before the 100 MiB cap is reached | Reduce the mesh in the modelling application |
Units and orientation: a worked example
OBJ stores numbers without a unit, so the converter cannot tell millimetres from metres. You have to know what your source used. An illustrative example, not a run result: an object measures 100 in its modelling application, and its author knows that means centimetres. Select Centimetres, convert, and after import check that the object is 100 cm across. If you had selected Millimetres instead, the same object would arrive ten times too small.
The FBX declares Y as the up axis, and the converter does not turn the model. If the static mesh (OBJ geometry) was modelled with a different up axis, it may arrive lying on its side: rotate it in the source or the destination application. There is no automatic axis correction.
For more on units across formats, see mesh hand-off formats and units.
Why did conversion fail?
Save a copy of the source before you change it. Then match the message to the fix.
| Problem | What to do |
|---|---|
| Source units not chosen | Select millimetres, centimetres, metres or inches in the converter |
| Loss box not ticked | Tick it to accept a static mesh with a neutral material, or use a full export from the modelling application |
| Faces with more than four corners | Triangulate those polygons in the modelling application and export the OBJ again |
| Points, lines or curves | Export a polygon mesh only |
| Zero-area triangles or invalid coordinates | Clean up the source geometry, for example by merging duplicate vertices, then export again |
| Too many vertices, triangles or meshes | Simplify the mesh or split it into parts, and convert each part |
| Output over the 100 MiB budget | Reduce the mesh; ASCII FBX is a large text format |
| File over 50 MiB | Reduce or split the OBJ before converting |
Triangulating or cleaning a mesh can change it, so compare the result with the original. If the job needs textures or a full scene, export FBX with its companion files from the modelling application and check it in the target application.
Recommended workflow
- Choose a OBJ file. Select a supported standalone .obj mesh in the converter above. External texture sidecars and unsupported extensions are not part of this route.
- Convert to FBX. Run the conversion locally, then download the result when it is ready. If it fails, check the source in your modelling application.
- Reopen and inspect. Open the download in its destination application. Verify a known dimension, orientation and the parts that must survive the handoff.
After download: check the FBX
When the conversion finishes, the status line names the downloaded file, its size, the number of meshes and the number of triangles. That confirms what was written; it is not a test in your target application.
- Open the FBX in the application where it will be used.
- Check one known dimension against the source.
- Check the orientation: which way is up.
- Check the normals and shading.
- Check that every part you need is there, as Mesh_1, Mesh_2 and so on.
- Expect a grey material: original UVs, materials and textures are not in the file.
How the file is processed
The page's converter script reads the OBJ you choose in your browser and builds the FBX there, so the conversion does not need an upload. It reads only that one file: it does not look for an MTL file or textures beside it. The converter also reports usage events, such as a conversion starting, finishing or failing, with the converter pair but not the file. This describes the conversion code; it is not a full network audit.
Converting the other way or to another format? See FBX to OBJ, OBJ to GLB, GLB to FBX and all the 3D file conversion guides.
Guides for this tool
Frequently asked questions
What does this tool do?
It converts a mesh to FBX: one standalone OBJ in, one static ASCII FBX out, built in your browser. Geometry and normals are written with a neutral grey material. UVs, materials, textures, vertex colours and object names are not kept.
Can I convert OBJ to FBX with textures?
No. This route writes a grey static mesh: OBJ textures and materials are not carried over, and it does not read MTL files or texture images. When textures matter, export FBX from your modelling application instead.
How do I convert an OBJ to FBX accurately?
Choose the units your OBJ was modelled in before converting, because OBJ does not store them. After import, check one known dimension against the source and check which way is up: the FBX declares Y as up and the converter does not rotate the model.
Why is my FBX grey?
Because the converter replaces every material with one neutral grey material and does not write UVs or textures. That is expected. Use a full export from the modelling application if the materials must travel.
Why is the size wrong?
Usually because the wrong source units were chosen. OBJ stores plain numbers, so the converter uses the units you select and writes centimetres into the FBX. Convert again with the right units and check a known dimension.
Can this make a rig or animation?
No. The output is static geometry only. An OBJ holds no rig or animation, and this converter does not create one.
What are the limits?
One OBJ up to 50 MiB, made of triangles and quads, with up to 250,000 vertices, 500,000 triangles and 1,000 meshes. The FBX is capped at 100 MiB, and an estimate can reject the file before that.
Related conversions
This converter is free to use. Check the downloaded file in its destination application. Use the 3D File Format Converter Guide to plan the handoff, or discuss a production brief with XO3D.