SketchUp to Unity: Direct SKP Import vs FBX vs GLB

Unity can read SketchUp data directly, but direct import is not always the best production choice. The decision depends on whether you need a quick architectural preview, a controllable engine asset, or a lighter handoff through FBX or GLB.

What Unity Supports from SketchUp

Unity's own SketchUp importer documentation says the engine can read textures, materials, groups, components, and scene camera data, but it also lists clear limitations around unsupported SketchUp features.

That is the reason to treat direct import as an option, not as a default. Review the official Unity SketchUp import settings and SketchUpImporter API reference before you commit to a direct engine workflow.

When Direct SKP Import Is Good Enough

Direct SKP import can be useful for early architectural reviews, quick iteration, or when the model mostly needs to show up in the scene without a lot of downstream asset cleanup.

When FBX or GLB Is Safer

Use SKP to FBX when the Unity project needs a more conventional engine-oriented handoff. Use SKP to GLB when the same asset must also move into web viewers or lightweight runtime previews.

Import Checklist

• Check scale before building prefabs or physics.
• Review backfaces and materials immediately after import.
• Decide early whether this is a one-off import or a reusable asset pipeline.