Importing Data

Bring meshes, point clouds, volumes (voxels), polylines, distance maps, and G-code into MeshInspector with predictable results.
Updated over 3 weeks ago

Start Clean

  • New: Clears the scene. Use to restart a workflow.

Ways to Import

  • Open Files: Load single files or a .zip that contains supported files.
  • Open Directory: Recursively loads all supported files from a folder and its subfolders.
  • CT tab: Required for volume-based inputs:
    • Open DICOMs (select a folder with the series)
    • Open RAW Voxels (specify dataset parameters)
    • Open Voxels from TIFF (desktop only; not available in web app)
  • Recent Files: Reopen items from the Open File dropdown.

Web vs Desktop differences

  • To open STEP/STP formats we ****use a web converter in the web app and on-device conversion on desktop app.
  • Import via CT → Open Voxels from TIFF is desktop only.

Special-format guidance

  • DICOM (.dcm)
    • Select the parent folder; MeshInspector groups slices by series.
    • Ensure the folder contains one complete series for consistent spacing and orientation.
  • RAW voxels
    • Must supply dataset dimensions and how data was saved (e.g., axis order, spacing). RAW has no embedded metadata.
  • TIFF stacks
    • Use CT → Open Voxels from TIFF on desktop.
    • Input voxel size for each axis.
  • OBJ
    • Keep .obj, .mtl, and texture images together in the same folder for robust material loading.
  • GLTF/GLB
    • Prefer .glb for a single-file package. .gltf may reference external textures.
  • Point clouds (E57/LAS/LAZ/PTS/ASC/PLY)
    • Color channels are read where supported; see tables in Article 4.
  • CSV/XYZ/TXT
    • Parsed as coordinates. Color is not supported for these inputs per the reference table.

Performance notes

  • Large point clouds and voxel volumes require ample RAM and GPU memory. Close unneeded objects to conserve resources. Though they can be viewed and opened in the web app, we recommend using our native desktop app.
  • Prefer binary formats where available (e.g., .ply binary, .ctm) to reduce load times and disk footprint.

Table of Contents