Dental Scan Review

Review an intraoral scan in a browser and hand the case to whoever needs it next — a lab, a referring specialist, the patient — as a link with no login. Drop the upper and lower arch as STL, PLY, OBJ, 3MF or GLB from any scanner, or a crown/abutment design as STEP or IGES. MILLIMETRES ARE REAL HERE: an import keeps its own coordinates, and an intraoral scanner writes millimetres, so one world unit is one millimetre and the measure tool is set to mm rather than the engine default of metres. Distance, angle, radius, path and area all read in the units a clinician expects, and the camera is framed for a ~55 mm arch instead of a 5-unit debug cube. The dropzone deliberately authors no `center` or `fit`, because importers discards both for mesh imports — they are dead props on every plate that sets them. There is no ground grid, because an arch does not stand on anything. SECTIONS cut every mesh at once through the renderer global clipping planes, which is how you get inside a prep, look down an interproximal contact, or check a crown seated on a die — an upper and a lower arch therefore section together, not separately. FINDINGS are annotation pins: each carries a title, a description and a screenshot of the view it was placed in, so a note about a specific tooth still means something a week later. TOOTH LABELS are callouts, which park at the edge of the frame with a leader line rather than sitting on the surface, so labelling six teeth does not bury the thing being labelled. The numbering is text you supply — FDI, Universal or Palmer — because the plate ships no tooth dictionary and will not guess which system your practice writes in. THE ONE THING TO KNOW ABOUT ISOLATION: hide and isolate act on the current selection, and a scanner's STL export is a SINGLE unsegmented mesh with one object in the tree — so per-tooth show/hide does nothing useful until the file actually has per-tooth sub-objects. If yours does not, build the segmentation in the segment3d plate (rectangle, polygon and lasso region select, grow and shrink, named coloured classes, CSV or JSON label export) and bring the result back here. THE REVIEW PRINTS. A PDF findings report lists every pin with its title, author, date and the object it sits on, then gives each finding its own sheet carrying the description and the view it was placed on — those thumbnails are already in the track, so the report needs no live canvas and a published referral prints the same as the one you sent. NOT HERE, AND EACH FOR A DIFFERENT REASON. CBCT: a DICOM series is volume data rather than a mesh, and it loads on Dental Implant Plan — this plate declares no `volume`, so dropping a series here does nothing. Occlusal contact and clearance mapping: a real capability, wired on Dental Lab QA and Dental Ortho Staging; this plate does not declare `deviation`, because a referral view should stay a referral view. Automatic tooth segmentation and shade matching: genuinely absent — nothing in the catalog does either, and a scan carries no calibrated colour to match against. A dropped file lives in the session only — save it to the asset library from the header if you want the published track to reopen with the geometry as well as the camera, sections and findings.

Supported file formats: STL, PLY, OBJ, 3MF, GLB, GLTF, STEP, STP, IGES, IGS