MeshOdyssey 1.1.0 · Technical release

3D format compatibility

Use this matrix before converting a model. “Supported” is never shorthand for lossless, slicer-ready, or compatible with every extension.

FormatImportExportImportant limits
STLASCII and binary meshesBinary geometryUnits, materials, textures, hierarchy, and metadata are not standardized.
OBJGeometry, groups, normals, UVs, material namesGeometry-only OBJCompanion MTL and textures are not loaded or generated.
GLBSelf-contained uncompressed glTF 2.0Binary GLBDraco, KTX2, and Meshopt decoders are not bundled; STL conversion loses scene features.
GLTFSelf-contained JSON with embedded resourcesNot providedExternal BIN and image resources are rejected rather than fetched.
PLYASCII and binary triangle meshesBinary mesh PLYPoint-cloud-only data and custom properties are not supported; textures are not saved.
3MFCore meshes, components, base materials; partial material propertiesSTL geometry onlyAdvanced extensions, production metadata, and complete material fidelity are not promised.
PNG/JPEGBrowser-decoded raster pixelsSTL relief or silhouetteThis is sampled extrusion, not AI depth or 360-degree object reconstruction.
SVGSupported filled paths and holesExtruded STLStrokes, live fonts, filters, masks, scripts, linked images, and complex browser rendering are unsupported.

Validation boundary

What version 1.1 means

  • Anonymous file processing remains inside the browser path; analytics excludes filenames and model content.
  • Repository fixtures, round trips, builds, E2E routes, Cloudflare readback, and selected Chromium flows are automated or directly observed.
  • External slicers, Blender, printed parts, broad device memory, custom-domain indexing, GSC, and real-user demand remain separate gates.