Your .dcm is not a DICOM file
Two completely different files ended up sharing the same extension. That single collision is why your viewer rejects the scan, and why the converters you found on Google cannot help.
A 3Shape intraoral scan saved as .dcm is an HPS file, not DICOM.
It is XML with the mesh packed inside it. DICOM readers reject it because it has no DICOM
header, and DICOM converters cannot read it at all.
The two files that share the extension
| Real DICOM | 3Shape scan | |
|---|---|---|
| What it holds | An x-ray, a CT or a CBCT study, stored as image slices | A finished 3D surface mesh of teeth and gums |
| Actual format | DICOM, a binary medical imaging standard | HPS, HIMSA Packed Standard format 501, which is XML |
| First bytes | 128 bytes of padding, then the letters DICM |
XML text, with HPS near the top |
| Written by | Radiography and CBCT machines | TRIOS scanners and 3Shape software |
| Typical size | Tens to hundreds of megabytes for a study | Roughly 0.1 to 10 MB for one scan |
Check yours in ten seconds
Make a copy of the file and open the copy in any plain text editor. Notepad, TextEdit and VS Code all work.
- You can read XML tags, and the letters
HPSappear near the top. It is a 3Shape scan. - You see a wall of unreadable characters. It is almost certainly a real DICOM image.
Work on a copy. Some editors will offer to re-save the file and change the bytes, which breaks it.
Why the wrong tools fail the way they do
A DICOM viewer looks for the marker DICM at byte 128 and stops when it is not there.
That is where the "invalid file" or "not a DICOM file" message comes from. Nothing is wrong with
your scan.
A DICOM to STL converter fails for a deeper reason. Its job is to stack image slices and build a
surface out of them. A 3Shape .dcm already contains a finished mesh, so there is no
stack of slices to work with, and the converter cannot read the container in the first place.
What the file actually contains
Inside the XML there are two payloads that matter, both base64 text. Vertices are three little-endian 32-bit floats each, in millimetres. Facets are not a plain list of triangles. They are a one byte per step instruction stream that rebuilds the mesh by walking an edge list, which is where the file gets its compression.
Because the numbers are already in millimetres, a correct reader does not need to scale anything. A scan that opens at the wrong size has been converted wrongly.
Questions
Is a 3Shape .dcm file a DICOM file?
No. It only shares the extension. A 3Shape .dcm is an HPS file, which stands for HIMSA Packed Standard, format 501. It is an XML document with the mesh packed into base64 text. DICOM is a different binary format for medical images. No DICOM reader will open a 3Shape scan, and no 3Shape tool will open a radiograph.
Why does my DICOM viewer say the file is invalid?
Because it is looking for the DICOM header and there is not one. A real DICOM file carries the four letters DICM at byte offset 128. A 3Shape .dcm starts with XML instead. The viewer reads the first bytes, finds no marker, and rejects the file. The file is not corrupt.
How do I tell which kind of .dcm I have?
Open a copy in any plain text editor. If the first line looks like XML and you can see HPS near the top, it is a 3Shape scan. If it is unreadable binary, it is most likely a real DICOM image. Size is a second clue: intraoral scans usually run from a few hundred kilobytes to about ten megabytes.
Can a generic DICOM to STL converter handle it?
No. Those tools build a mesh out of stacked CT or CBCT slices, which is a different job. A 3Shape .dcm already contains a finished mesh, so there is nothing to reconstruct, and the converter cannot read the container anyway.
Open the scan and save it as STL
If the text editor showed you XML, ScanLoupe will open the file. Drop it in and save an STL or PLY. It runs in this browser tab, so the scan stays on your computer.