Dental scan file formats are the files a scanner generates when exporting a case—in dentistry, this almost always means STL, PLY, or DCM. The format dictates exactly what the next piece of software can read: bare geometry, geometry plus color, or a CAD-native container that carries the entire case context alongside the mesh.
This is why compatibility is the first real question any lab asks before booking a demo. It’s not just about how good the AI is; it’s about whether it will actually open your files, and how easily you can integrate it into your existing workflow.
What file formats do dental scanners export?
Three formats cover nearly everything a lab receives today. They aren't interchangeable, and the differences matter much more than the file extension implies.
- STL: Triangle mesh geometry, nothing else—no color, no case data. It's the common-denominator export on nearly every intraoral and desktop scanner. This is the safe interchange format: when two systems agree on nothing else, they agree on STL.
- PLY: The same mesh, plus color stored per vertex. This comes from scanners that capture surface color along with shape. It matters when color carries critical information—like reading soft tissue, or a margin the doctor marked in ink on the scan.
- DCM: A CAD-native container: mesh plus the case context stored with it. These usually come from desktop CAD systems a lab may already own, such as exocad or 3Shape. It matters when the case was already set up in a CAD seat and you don't want to rebuild that context by hand.
Which scan file formats does Dentscape accept?
To keep your workflow smooth, Dentscape relies on open formats. It natively reads STL, PLY, and DCM from any scanner or desktop CAD. These are the exact files your lab already receives, meaning there is no extra export step wedged into your process. The scanner brand, file type, and jaw are detected automatically, and if a doctor has already marked a margin (pts file), the system respects it rather than overwriting it.
Relying on open formats also keeps your current tools in play. If your lab has spent years mastering a specific CAD seat, you don't have to choose between that software and our AI layer. Since both systems read the same files, they run perfectly side by side.
Do I need to install anything to read these files?
No. Handling open formats seamlessly is only half the battle; the software itself needs to be just as accessible.
Because Dentscape is entirely web-based, you don't need a heavy desktop application to open your files. It runs securely in a browser, meaning there is nothing to install at the bench and no physical dongle to pass around the lab. This cloud-based approach eliminates the worst parts of software compatibility: checking workstation specs, updating drivers, or hunting down a USB license key. To load a scan and start designing, your bench PC only needs to open a new tab.
What comes out the other side — and will it open in my CAM?
The output format determines whether a design actually makes it to the mill. Finished batches from Dentscape are delivered straight into your milling software, sent to your printer, or provided as a structured download—with construction info and margin lines perfectly matched to each case. Nothing has to be re-exported, renamed, or reassembled by hand to move from review to production. (Why this half of the case matters just as much as the crown is a topic we cover in our guide: AI Crown Design With a Print-Ready Model, Included)
What if my scanner isn't on anyone's compatibility list?
Don't look at the brand; look at what it exports. The most important list isn't the roster of supported scanner manufacturers—it's the supported file formats. If your scanner exports STL or PLY, or your CAD outputs DCM, the file is readable regardless of the logo on the machine.
There is one caveat worth noting: some closed scanner ecosystems lock their native exports behind proprietary settings. If a native file refuses to open outside its home software, simply switching the export setting to STL or PLY works just as well, and the case loses nothing essential for the design phase. Compatibility is a property of the file itself, not the result of a corporate partnership agreement.
Being readable and being usable are two different things, however. Format compatibility and a cloud-based workspace get the case in the door instantly; what happens next depends entirely on the quality of the mesh. (We dive deeper into this in our article: How AI Crown Design Works.)