Migrate from KeyShot
Understand what carries over from KeyShot scenes and rebuild the rest as reusable Glossi setups.
Your KeyShot geometry and materials come across in a GLB export. Lighting, environment and cameras don't, so you rebuild them once in Glossi and save them as a template for every later model.
Why KeyShot files can't be uploaded
KeyShot saves scenes in two proprietary formats:
- .bip: the native scene file. It stores geometry, materials, cameras, and environment settings in a closed format only KeyShot can read.
- .ksp: a KeyShot package. A .bip bundled with its textures for sharing between KeyShot users. Equally closed.
No third-party converter reads these formats, so Glossi can't either. Glossi accepts GLB and 50+ other supported file types, and KeyShot exports GLB natively. That export is the bridge.
There's a second reason the export step matters: KeyShot materials are procedural. They're recipes evaluated by KeyShot's renderer, not texture images, so they can't be copied to another engine as-is. When KeyShot exports GLB it bakes those recipes into standard PBR texture maps (base color, roughness, metalness, normal), which any modern engine, including Glossi's Unreal-based Studio, understands.
What transfers and what you rebuild
| In KeyShot | Transfers in the GLB? | In Glossi |
|---|---|---|
| Geometry and UVs | Yes | Uploads as-is |
| Materials | Yes, baked to PBR textures | Fine-tune in the Studio material controls |
| Labels and textures | Yes, baked into the maps | Part of the material |
| Environment (HDRI) | No | Pick a backdrop or HDRI in the Studio |
| Physical lights | No | Build a light rig (save it as a workspace preset) |
| Cameras | No | Save shots in the project |
| Studios / Model Sets | No | Model variants and material swaps |
| Animations | No | Photo and video modes in the Studio |
| Render settings | No | Choose per render or bake into a template |
The right column is a one-time cost per look, not per model: lighting, backdrop, and camera setups are saved as templates you apply to every future upload.
Move a model
Use the Glossi Uploader script to export and upload in one step, or export File > Export > glb/gltf and upload the file yourself. Either way, prepare dense scenes first: KeyShot models often carry heavy NURBS tessellation and duplicate materials.
Rebuild your scene setup
After the model uploads, open it in a project in the Studio:
- Review the baked materials. Metals and simple plastics usually arrive right; adjust roughness or color where the bake drifted (materials).
- Choose a background and HDRI to replace the KeyShot environment (background).
- Build a light rig and save it as a workspace preset, so the next model starts lit (lighting).
- Save a shot for each view you rendered in KeyShot (shots).
- Save the setup as a template to apply to every later model, in the Studio, Render products or automations.
Migrate a whole library
KeyShot work lives one scene per .bip, so migration is per-scene: open, export or run the script, repeat. After the first few, the setup work is done:
- Build one template per look, then batch-render new uploads against it with Render products or an automation (Enterprise).
- Recreate KeyShot Model Sets and multi-materials as model variants and material swaps.