FBX to OBJ Converter
Convert an FBX model into an OBJ that almost anything will open. Upload the file, convert, and download the OBJ. No account, no watermark, and the upload is deleted after processing.
FBX and OBJ are both 3D formats, but they are not equivalent, and the gap between them decides whether this conversion gives you what you need.
What each format can hold
FBX is Autodesk's interchange format and it carries almost everything a 3D scene can contain: meshes, materials, embedded textures, UV layouts, a scene hierarchy with parents and transforms, skeletons, skin weights, blend shapes, animation take, cameras and lights.
OBJ is from Wavefront Technologies in the 1980s, and it is deliberately plain. It holds geometry — vertices, faces, texture coordinates, normals — together with group names and a reference to a companion material file. That is the whole format.
OBJ's narrowness is also its strength. It is plain text, it has no version drift worth speaking of, and it is read by essentially every 3D program ever written. When something refuses your FBX, OBJ is the thing that works.
What the conversion discards
Everything OBJ cannot describe is dropped, and it is better to know in advance than to discover it in your viewport.
Animation. OBJ stores a single static pose. Every take, every keyframe and every camera move goes. A character arrives frozen in whatever position the file described.
Rigs and skinning. The skeleton, joints and skin weights go with the animation. The mesh survives; its ability to be posed does not.
Blend shapes and morph targets. Facial expressions and shape variations are not representable in OBJ.
Cameras and lights. OBJ describes objects, not scenes. These simply do not exist in it.
The hierarchy. FBX records parents, children and their transforms. OBJ has flat groups. Parts keep their positions, because transforms are baked into the vertex coordinates on the way out, but the structure that related them is gone.
If the model is animated or rigged and you need that to survive, OBJ is the wrong destination. glTF is the modern interchange format that keeps animation and skinning while still being widely supported, and it is worth converting to that instead.
Materials and textures
This is where most confusion with OBJ begins, and it is a property of the format rather than any converter.
An OBJ does not contain its materials. It references a companion file, conventionally with the same name and an .mtl extension, which lists material properties — colours, shininess, and the filenames of texture images. The texture images themselves are not contained either. They are ordinary image files that must sit alongside, named as the .mtl expects.
FBX, by contrast, can embed its textures inside the file. So a single self-contained FBX becomes an OBJ that refers to images which were inside the original and are not inside the output. The geometry opens perfectly and the model appears untextured.
The fix is to keep the textures from your source. Export them from the FBX using Blender or the Autodesk FBX Converter, place them in the same folder as the OBJ, and check that the filenames in the .mtl match. If the .mtl is missing entirely, most 3D programs let you assign materials by hand, which is tedious but reliable.
How to convert FBX to OBJ
- Upload your FBX, or drag it onto the upload area. Binary and ASCII FBX are both the same format.
- Convert.
- Download the OBJ.
There is nothing to configure — no axis conversion, no scaling, no texture options. The next section covers the two adjustments that are usually needed afterwards.
Orientation and scale afterwards
Up is not agreed. OBJ conventionally treats Y as up. FBX files may be authored Y-up or Z-up depending on what produced them — 3ds Max and most CAD tools use Z-up, Maya and Unity use Y-up. When the two disagree, your model arrives lying on its side or face down.
It is a one-step fix, not a corrupted file. Rotate 90 degrees about X in whatever opens it, then apply or freeze the transform so the correction is baked in rather than carried as a pending change.
Scale is not agreed either. FBX records its units; OBJ does not. A model authored in centimetres arrives as bare numbers that your target program may read as metres, making it a hundred times too large or small. Check the dimensions on import and scale once.
When OBJ is the right choice
Reach for OBJ when you want a static mesh that will open anywhere: sending a model to someone whose software you do not know, importing into an older or unusual tool, 3D printing workflows that want geometry only, archiving a shape in a format that will still be readable in twenty years, or feeding a renderer that does its own materials anyway.
Reach for something else when the model is animated, when you need PBR material definitions preserved properly, or when file size matters — OBJ is plain text, so it is several times larger than an equivalent binary format. glTF or FBX itself are the better answers in those cases.
FBX and OBJ side by side
FBX began at Kaydara in the 1990s, passed to Alias and then to Autodesk in 2006. It is proprietary, exists in binary and ASCII variants, and its specification has changed repeatedly, which is why a file written by one version is sometimes refused by an older importer.
OBJ was created by Wavefront Technologies for its Advanced Visualizer software in the 1980s. It is an open, human-readable text format that has barely changed since, and that stability is precisely why it remains the safe option for exchanging a static mesh.
Common problems and what causes them
The model has no textures. Expected. OBJ references textures rather than containing them. Extract the images from the FBX and place them beside the OBJ with names matching the .mtl file.
The model is lying on its side. Y-up versus Z-up. Rotate 90 degrees about X and apply the transform.
The model is enormous or microscopic. FBX carries units, OBJ does not. Scale once on import.
The animation is missing. OBJ cannot store animation at all. Use glTF if you need it.
The file is much larger than the FBX. Expected. OBJ is text, so every coordinate is written out as digits. Zip it for sending, or use a binary format if size matters.
Parts that were separate are now one object. OBJ has flat groups rather than a hierarchy. Most 3D programs can separate by loose parts or by group after import.
