Component instances - SketchUp components, FBX mesh node references, Collada instance_geometry, STEP assembly occurrences - are efficient for storage and editing but create problems in workflows that require flat, non-hierarchical geometry. Some rendering engines, physics simulators, and CAD tools cannot process instanced geometry; some formats simply have no instancing concept. Exploding instances means expanding each reference into a full independent copy of its geometry at its placed position.
Autoconverter explodes component instances automatically when converting to formats that don't support instancing. Understanding when this happens, which formats trigger it, and what the file size implications are helps you choose the right output format for your workflow.
When You Need to Explode Component Instances
Instanced geometry causes problems in specific situations:
- Target format has no instancing - OBJ, STL, and PLY have no instancing concept; all geometry must be flat. Converting SKP or FBX to these formats always explodes instances.
- Tool requires unique geometry per object - some physics engines, UV unwrappers, and mesh analysis tools require each object to have its own independent geometry buffer rather than a shared definition
- Per-instance material overrides - when individual instances of the same component need different materials, the shared geometry definition must be duplicated so each copy can have its own material assignment
- Downstream editing in tools that don't support instances - some 3D editors (older game engine importers, certain DCC tools) don't recognize instancing and import only the first instance or produce errors
- STL export for 3D printing - STL requires a single merged triangle mesh; all instances must be flattened and optionally merged before export
How to Explode Instances Using Autoconverter
The most reliable method is to export to a format that forces flattening. OBJ is the recommended intermediate because it is flat by specification, universally supported, and preserves materials via MTL:
-
Open the Source Model
Open your source file in Autoconverter - SKP, FBX, DAE, 3DS, 3DM, STEP, or any supported format containing component instances.
-
Export to OBJ Format
Go to File > Save As… and choose OBJ (*.obj) as the output format.
-
Flatten Component Instances
Click Save. Autoconverter expands every component instance into an independent geometry group in the OBJ output. Each instance appears as a named OBJ group at its correct position, rotation, and scale in world space.
-
Verify the Flattened Geometry
Open the OBJ file to verify the Groups Panel shows all instances as independent mesh groups. Each group is fully independent - no shared definitions, no instance references.
-
Convert to Other Formats (Optional)
If you need the flat geometry in a different format, use File > Save As… from the OBJ to convert to your target format (FBX, SKP, DAE, STL, etc.). The geometry is now flat in all subsequent exports.
Which Formats Explode Instances and Which Preserve Them
| Format | Instances in Output | Notes |
|---|---|---|
| OBJ | ❌ Always exploded | No instancing concept in the spec; each instance becomes a named group |
| STL | ❌ Always exploded + merged | Single triangle mesh; all instances flattened and merged into one |
| PLY | ❌ Always exploded | No instancing; each instance written as separate geometry |
| FBX | ✅ Preserved | FBX mesh nodes referenced multiple times with transforms |
| DAE | ✅ Preserved | Collada instance_geometry and instance_node elements |
| GLTF/GLB | ✅ Preserved | GLTF mesh instancing |
| SKP | ✅ Preserved | SketchUp component definitions and instances |
| USD/USDZ | ✅ Preserved | USD scenegraph instancing |
| STEP | ⚠️ Partial | Non-scaled instances preserved as STEP occurrences; scaled instances exploded |
| 3MF | ✅ Preserved | 3MF component references |
File Size Impact of Exploding Instances
Exploding instances increases file size proportionally to the number of instances. A SketchUp model with 100 chair instances storing one chair geometry definition becomes 100 independent chair geometry sets in OBJ output - 100× the geometry data for just those chairs.
Practical implications:
- A 2MB SKP with heavily instanced furniture may produce a 40–100MB OBJ after instance explosion
- An FBX with game asset prop instances may expand similarly when converted to OBJ for flat editing
- If the expanded OBJ is large, consider using FBX, DAE, or GLTF as the intermediate instead - these preserve instances and keep file sizes manageable
Frequently Asked Questions
Is the original file modified when I export to OBJ?
No. Autoconverter's Save As operation writes a new output file - the source file is unchanged. Keep the original SKP, FBX, or DAE file as the editable master. The exploded OBJ is a flat derivative for workflows that need it.
Can I choose which instances to explode and which to keep?
Not selectively within Autoconverter - the format determines whether instances are preserved or exploded. To selectively flatten specific components, open the file in its native tool (SketchUp, Maya, Blender), explode the specific components there, then re-export.
Why is my OBJ file 10× larger than the source SKP?
The SKP used component instances - geometry stored once with many placement references. OBJ has no instancing, so every instance is expanded to a full geometry copy. This is expected. If file size is a concern, use FBX, DAE, or GLTF as the conversion target instead.
Is there a free trial?
Yes. The free evaluation version of Autoconverter supports up to 10 file conversions. The full licensed version provides unlimited conversions.
Summary
Component instances are exploded automatically when converting to formats with no instancing support - OBJ, STL, PLY. Each instance becomes an independent geometry group at its correct world position. Formats that support instancing (FBX, DAE, GLTF, SKP, USD) preserve instances through conversion. Exploding instances increases file size proportionally to instance count - a 100-instance model produces 100 geometry copies in OBJ output. Use OBJ as the intermediate when flat geometry is specifically needed; use FBX or DAE when preserving instances matters for file size or downstream editing.
👉 Ready to convert? Download Autoconverter and try it free for up to 10 conversions.