DICOM Metadata Viewer

View metadata from DICOM (.dcm) medical imaging files: CT, MRI, X-ray, ultrasound. Extract patient, study, series, equipment, and image tags. No desktop DICOM viewer required.

1.0.0
Version
Auth
Batch
PHI warning: DICOM files often contain Protected Health Information (PHI). Files are parsed in memory and deleted immediately after the response. Still, for production PHI workflows, consider running this tool locally.

Upload a .dcm file

CT, MRI, X-ray, ultrasound, PET — any DICOM modality • Max 30MB

Requires login • 2 credits

DICOM Metadata Viewer Tutorial

What is DICOM?

DICOM (Digital Imaging and Communications in Medicine) is the standard for medical imaging. Every CT slice, MRI, X-ray, and ultrasound you see in hospitals is stored as a .dcm file. Each file bundles the image data with hundreds of metadata tags describing the patient, study, equipment, and acquisition parameters.

What You'll See

  • Modality — CT, MR, CR (X-ray), US (ultrasound), PT (PET), etc.
  • Patient info — ID, name, DOB, sex (often anonymized in teaching/research sets)
  • Study details — date, description, referring physician, accession number
  • Equipment — manufacturer, model, station, institution, software version
  • Image parameters — resolution, bit depth, slice thickness, pixel spacing
  • All tags — full dump of every non-pixel tag with its VR (Value Representation)

Why This Tool Exists

Installing a DICOM viewer just to check a file's metadata is overkill. Researchers, medical imaging engineers, radiology IT staff, and students often just need to see what's inside a .dcm file — where it came from, which machine, what modality. This tool does exactly that, no install, no 4GB software package.

Pixel Data

We deliberately do not decode or display pixel data — that would require a full imaging pipeline and is a different product. For viewing actual images, use RadiAnt, Mango, or OsiriX.

Tags Format

Each DICOM tag is a (group, element) hex pair: (0010,0010) is PatientName. The VR column shows data type: PN person name, DA date, UI unique identifier, IS integer string, etc.

Privacy

Files are parsed in RAM only. The temp file is deleted in the finally block. Nothing is persisted. Still — for clinical or research PHI, run this locally with pydicom directly.