How to Export 3DS Files from SketchUp: Step-by-Step Guide

Exporting 3DS from SketchUp: Best Settings for CAD & 3D Apps

Exporting a clean, compatible 3DS file from SketchUp requires attention to geometry, materials, units, and export settings. Use the checklist and step-by-step workflow below to reduce errors, preserve scale, and ensure smooth import into CAD, game engines, and rendering apps.

1. Prepare the model in SketchUp

1. Purge unused: Window → Model Info → Statistics → Purge Unused. Removes unused components/materials to reduce file size.
2. Fix geometry: Select the model and use SketchUp’s Eraser or Solid Inspector (extension) to remove stray edges, reversed faces, and non-manifold geometry. 3DS imports struggle with open meshes and internal faces.
3. Explode groups/components when needed: Some target apps expect a single mesh or specific grouping. Decide whether to export grouped objects or a single merged mesh.
4. Simplify complex geometry: Reduce high-polygon details (e.g., overly subdivided curves) or bake them into normal maps for game engines.
5. Apply transforms: Right-click components and choose Reset or make sure scales/rotations are applied so objects export with correct orientation.

2. Set units and scale

1. Model units: Window → Model Info → Units. Choose the unit most compatible with the target app (millimeters for CAD, meters for architectural renderers).
2. Check model scale: Use Tape Measure to verify key dimensions. 3DS has a limited numeric range and can clip very large or tiny scales—keep models within realistic ranges (e.g., 0.001–1,000 units).
3. Export scale: If the target app expects different units, either change SketchUp’s model units or apply a uniform scale factor before exporting.

3. Materials and textures

1. Use simple materials: SketchUp materials should be basic (diffuse color + texture) because 3DS supports limited material channels. Avoid complex SketchUp procedural materials.
2. Bake textures: If a material uses multiple layers or procedural effects, bake to a single texture in SketchUp (or an external renderer) and apply it to the faces.
3. Texture paths: Ensure textures are saved in the same folder as the exported 3DS or in a relative path. 3DS stores bitmap references—missing textures are a common issue.
4. UVs check: SketchUp doesn’t expose full UV tools; check that textures tile and align correctly on faces. For advanced UV needs, export to an FBX/OBJ workflow with UV editing.

4. Naming and hierarchy

1. Clean names: Rename components/groups with short, ASCII-only names. 3DS has filename/identifier length limits and may fail on special characters.
2. Hierarchy: 3DS supports a simple hierarchy. Flatten overly deep nesting if the target app expects flatter structures. Preserve logical grouping so imported objects are manageable.

5. Export process (SketchUp native/exporter or plugin)

SketchUp’s native 3DS exporter (or third-party exporters) will present options—use these recommended settings:

• Export Format: 3DS (.3ds)
• Exclude hidden geometry: Yes (unless intentionally needed)
• Export texture maps: Yes (ensure “Export texture maps” or similar is enabled)
• Triangulate faces: Enable (3DS requires triangles; triangulation avoids shading artifacts)
• Export edges/lines: Disable (for mesh-only exports; enable if target needs SketchUp edges)
• Preserve component hierarchy: Yes (if needed by the target app)
• Scale: Match model units to target app (or apply explicit scale factor)

If using a plugin exporter (e.g., SimLab, Skimp, Transmutr), follow plugin-specific recommendations for better material and UV handling.

6. Post-export checks

1. Open in target app: Immediately import into the destination software and verify geometry, scale, normals, and textures.
2. Check normals: Flip normals if faces appear black or invisible. Triangulation during export may change smoothing—adjust