.glTF (and .glb), .obj, and .fbx are the only 3D formats that can be imported into a Spatial Editor project. To use 3D objects in other formats, convert them to .gltf or .glb using a tool like Blender.

The glTF format includes extensions that support additional features and effects in your 3D models. glTF extensions supported in Spatial Editor include:

Find out more about materials and textures in Spatial Editor.

Compositions can be exported as glXF files, which are arrangements of glTF assets. Find out more about glXF files or targeting individual meshes in your Spatial SDK project.

To export a composition as a glXF file, you can use the Command Line Interface (CLI) or select File>Export glXF in Spatial Editor. For more information on how to use the Spatial Editor CLI, refer to the documentation.

The .metaspatial file extension is used for saving and loading projects in Spatial Editor. A .metaspatial file brings together all the essential elements of your project, including 3D models, materials, textures, and other assets.

Ensure that the .metaspatial file and all related project files are placed in the Spatial Editor folder of your Spatial SDK project:

With the files saved in the correct directory, use the Spatial SDK Gradle plugin to prepare your build. Alternatively, the Spatial SDK template includes an empty Spatial Editor file for you to get started from.

Find out more about adding a Spatial Editor project to a Spatial SDK app.

In the Spatial Editor, there is no strict limit on the size of textures you can use. However, for optimal performance, it’s advisable to:

Key points to remember:

Find out more about working with materials.