Extensible 3D XML encoding MIME Type
model/x3d+xml identifies, how Extensible 3D XML encoding files are encoded, and how Poly supports them. MIME type details for model/x3d+xml
In active use| MIME type | model/x3d+xml |
|---|---|
| Extensions | .x3d |
| First standardized | Unknown |
| Created by | Web3D Consortium and ISO/IEC |
| Browser support | |
| Example applications | X3D-Edit, InstantReality |
| Poly support | Partial. Poly recognizes this 3D media type and processes supported files. |
| Indexed by Poly | Yes. Poly indexes filenames and visual similarity for processed geometry; scene counts are displayed in Details. |
| Preview in Poly | Partial. Poly provides an interactive preview for supported constructs. |
| Poly agent | Yes. An optimized rendition of the 3D object or scene is provided to the agent, allowing compact yet information-rich multimodal interaction with 3D files. |
What does model/x3d+xml mean?
X3D is an ISO-ratified, royalty-free open standard for representing and communicating 3D scenes and objects. Its XML encoding maps the scene graph to XML elements and fields. Web3D specifies .x3d with model/x3d+xml.1 Profiles and versions determine which nodes are available.
The associated extensions are .x3d. The media type identifies the format family; it does not convert bytes or guarantee that a reader supports every entity.
Poly support
Poly can recognize this type as 3D content and index filenames and visual similarity for processed geometry; scene counts are displayed in the Details panel. An optimized rendition of the 3D object or scene is provided to the agent, allowing compact yet information-rich multimodal interaction with 3D files.
| Construct | What to expect |
|---|---|
| Geometry and scene structure | Available when import succeeds. |
| Materials and textures | Depends on source constructs and supported rendition features. |
| Lighting, cameras, and animation | Available when present and supported. |
Opening and conversion
Use a format-aware application when preserving editability matters. Conversion to glTF or OBJ can improve interchange for 3D viewing, while CAD and BIM workflows should retain the original schema and exchange context.