Free online FBX to 3DS converter

An older 3D application, game editor, or visualization tool may accept .3ds but not Autodesk's .fbx format. Converting the file creates a compact legacy mesh file for sharing or archiving, but it cannot preserve every feature in a modern FBX scene.

What the FBX format is

FBX is an Autodesk 3D interchange format stored as binary or ASCII data. Depending on the exporting application, it can contain polygon meshes, transforms, cameras, lights, materials, texture references, scene hierarchy, skeletal rigs, skin weights, and animation.

Autodesk 3ds Max, Maya, and MotionBuilder use FBX for exchanging scenes between modeling, animation, rendering, and game-development tools. Blender and many other 3D applications can import or export it, although each application supports a different subset of FBX features.

What the 3DS format is

3DS is the legacy binary scene format associated with the original Autodesk 3D Studio software. Many older modeling, visualization, level-editing, and asset-import programs support it.

A 3DS file can store polygon meshes, object transforms, basic materials, texture references, cameras, lights, and limited scene information. Its broad legacy support and often small file size are useful when the receiving application does not accept FBX. The format has strict mesh and naming limits and is not a suitable replacement for a full modern scene interchange format.

How to convert FBX to 3DS

Using Autodesk 3ds Max

1. Open 3ds Max and choose File → Import → Import.
2. Select the source .fbx file and confirm the FBX import settings. Import only the cameras, lights, animation, and other scene elements required by the destination workflow.
3. Check the model's units, scale, axis orientation, transforms, smoothing, materials, and texture paths. Correct the scene before exporting; changing units after export can produce an incorrectly sized model.
4. Choose File → Export → Export, or File → Export → Export Selected if only part of the scene is required.
5. Select 3D Studio (*.3ds) as the output type, enter a filename such as model.3ds, and confirm the export.
6. In the 3DS export options, export the required objects, preserve smoothing groups when available, and split meshes that exceed the format's limits.
7. Open the exported file in the target program and verify geometry, scale, normals, materials, and texture paths.

Using Blender

1. Use a Blender version that includes the 3D Studio import/export add-on. Enable it under Edit → Preferences → Add-ons if it is disabled.
2. Import the source with File → Import → FBX (.fbx).
3. Remove unwanted objects and check units, orientation, scale, materials, and textures. For a static export, apply the required rotation and scale with Object → Apply → Rotation & Scale; do not apply transforms blindly to an animated rig.
4. Split or triangulate meshes that exceed the 3DS limits, then choose File → Export → 3D Studio (.3ds).
5. Set the output name to model.3ds, configure texture paths if the exporter provides that option, and export.
6. Open the result in the destination application or a 3D viewer and check its size, orientation, mesh integrity, materials, and textures.

The converter on 101convert.com can process the file for free without installing desktop software. Inspect the downloaded result before using it in a production scene.

Quality and compatibility limitations

• Animation and rigs: 3DS is mainly used for static scenes. Skeletal animation, skin weights, constraints, blend shapes, and many FBX animation features are normally discarded.
• Materials: PBR shaders, node graphs, advanced transparency, and vertex colors usually become basic 3DS materials. Rebuild materials in the destination application when visual accuracy matters.
• Textures: 3DS commonly stores texture paths rather than reliably embedding image data. Keep the referenced image files with the exported model and relink them when necessary.
• Mesh limits: 3DS uses 16-bit mesh indices. Keep each exported mesh within the receiving program's limit, typically no more than 65,535 vertices, and split large objects before export.
• Names and hierarchy: Legacy 3DS implementations can truncate object or material names and flatten or simplify nested hierarchies.
• Coordinates and scale: FBX files may use different units, up-axis conventions, and handedness. Confirm the units and orientation after import and again after opening the 3DS file.
• Application differences: FBX importers and 3DS exporters do not implement identical feature sets. A successful file conversion does not guarantee identical shading, animation, hierarchy, or viewport appearance.