DICOM MIME Type

What does application/dicom mean?

The application/dicom media type identifies data in the Digital Imaging and Communications in Medicine standard. A .dcm file can carry an image from CT, MRI, ultrasound, X-ray, or another modality together with the structured information needed to interpret it. DICOM also defines non-image objects, including structured reports, radiotherapy plans, waveforms, and presentation states, so it is more accurate to think of DICOM as a medical information format than as another photo format.¹

The IANA registration recommends .dcm for files saved to disk, except for the special DICOMDIR directory file. It describes the intended use as interchange of biomedical images and identifies application/dicom as a binary media type.²

Where did DICOM come from?

The American College of Radiology (ACR) and the National Electrical Manufacturers Association (NEMA) formed a joint committee in 1983 to make medical images and related information portable between equipment from different manufacturers. ACR-NEMA 1.0 appeared in 1985 and 2.0 in 1988. In 1993, the committee substantially revised that work and replaced it with the standard named DICOM.⁴

That 1993 revision added support for TCP/IP networks, offline file exchange, service-oriented operations, and formal conformance statements. The DICOM Standards Committee now maintains the multipart standard, which NEMA publishes and updates continuously.⁴

The file format predates its MIME registration. IANA records application/dicom through RFC 3240, published in February 2002.²⁵ The registration also defines an id parameter for a DICOM File ID when a multipart message represents a file set. It is not a generic filesystem path, and it may be absent when no DICOMDIR is included.²

How do you identify a .dcm file?

A DICOM PS3.10 file begins with a 128-byte preamble followed by the four ASCII characters DICM. In hexadecimal, the prefix is 44 49 43 4D at byte offset 128. File Meta Information follows the prefix and identifies the SOP Class, SOP Instance, transfer syntax, and implementation that wrote the file.³

The prefix is a useful signature, but a robust validator must also parse the meta elements and data set. DICOM explicitly warns readers not to use the preamble contents to decide whether the file is DICOM.³ A .dcm extension alone is likewise not proof of a valid or safe file.

DICOMDIR is a related special case. It is an index for a DICOM file set and also uses application/dicom, but its reserved filename distinguishes it from the referenced instances.² It should stay with the directory structure and files it indexes.

Why is a DICOM file not just a JPEG?

JPEG describes compressed pixels. DICOM describes a clinical object, its metadata, and how its values are encoded. The Pixel Data element inside a DICOM object may be uncompressed or encapsulated with a codec such as JPEG or JPEG 2000. The Transfer Syntax UID tells a DICOM reader which encoding rules and pixel codec apply.³⁶

Extracting a JPEG-compressed frame does not preserve the surrounding DICOM object. Conversely, changing .dcm to .jpg does not make a browser understand the file.

How do you open an application/dicom file?

General-purpose browsers do not provide a native DICOM study viewer. The IANA registration anticipates that generic applications may save DICOM data without being able to interpret it.² Use a DICOM-aware application instead:

• 3D Slicer imports files into its DICOM database and then loads supported objects through its DICOM browser. Its documentation notes that DICOM has many information-object types, so extensions may be needed for specialized objects.⁷⁸
• OsiriX MD reads DICOM images and fields, organizes them in a database, and provides 2D, 3D, and 4D medical-image viewing on macOS.⁹
• A PACS workstation or a healthcare provider's supplied viewer may be the right choice for a clinical study, especially when presentation states and series relationships matter.

Import the whole folder when possible. Opening one arbitrarily selected slice can omit the rest of the series, and moving files without their DICOMDIR can break a portable file set's index.

Support in Poly

Poly recognizes .dcm filenames as application/dicom and classifies them in its archive category. It can store, sync, share, version, download, and find the outer file by name.

Poly currently treats the payload as opaque:

• It does not parse DICOM tags, transfer syntaxes, frames, or pixel data.
• It does not index patient, study, series, modality, report text, or image content.
• It does not generate a medical-image thumbnail or provide an in-app DICOM viewer.
• The Poly agent cannot read or reason about the DICOM object's contents.

This classification is an internal processing choice. A DICOM object is not an archive of member files like ZIP. Download it and use a trusted DICOM application when you need its clinical data. If you export a non-sensitive rendered image or report and add that separately, Poly can process the exported format through its normal image or document pipeline.

Converting DICOM to a common format

Choose the output according to what must survive:

• PNG or TIFF can preserve a rendered frame without adding another lossy generation. They do not preserve the complete DICOM metadata model or study relationships.
• JPEG is convenient for a small reference image, but it may introduce loss and usually reduces high-bit-depth medical pixels to a display-ready rendering.
• NIfTI or NRRD is often more useful for volumetric analysis, but conversion combines a series and changes the metadata model. Verify orientation, spacing, units, and coordinate conventions in the destination tool.
• DICOM-to-DICOM transcoding changes the transfer syntax while retaining the DICOM data model. This is preferable when the recipient still needs a clinical DICOM object.

Use export features in a DICOM-aware application rather than renaming the file. 3D Slicer, for example, treats DICOM as an import-and-load workflow and supports exporting selected data from its scene to other formats.⁷

Privacy and security considerations

DICOM commonly carries identifying and sensitive medical information. The media-type registration specifically calls out individual demographic information and recommends protecting exchanges according to applicable confidentiality policy.² Patient identity can appear in standard attributes, private attributes, text, overlays, and pixels burned into an image.

Deleting a few obvious tags is not reliable anonymization. DICOM PS3.15 defines confidentiality profiles and options for replacing or removing attributes, cleaning pixel data, handling recognizable visual features, and maintaining consistency across related instances. It also warns that applying attribute rules alone does not guarantee that an information object is de-identified.¹⁰

The file structure itself needs defensive parsing. PS3.10 notes that the 128-byte preamble can contain malicious executable content and recommends validation or sanitization appropriate to the application.³ Open untrusted files only with maintained DICOM software, and validate both structure and declared transfer syntax before further processing.

Before sharing a study outside its clinical system:

1. Use a DICOM de-identification tool with a documented conformance profile.
2. Review private attributes and free-text fields.
3. Check pixels, overlays, and derived images for burned-in identifiers.
4. Preserve consistent replacement UIDs across the complete study when relationships matter.
5. Validate the result and transfer it through an access-controlled channel.

How does application/dicom relate to DICOMweb types?

application/dicom represents a binary PS3.10 instance. DICOMweb also defines representations for particular web-service resources, including application/dicom+json for the DICOM JSON Model and application/dicom+xml for the Native DICOM Model. Rendered resources may be delivered as ordinary image types such as image/jpeg.¹¹

These are adjacent representations, not alternate names for the same bytes. A server must serialize or render the DICOM information for the requested media type. Merely changing the HTTP Content-Type header does not convert a binary .dcm file to JSON, XML, or JPEG.