Question 1

What metadata is required to create a valid DICOM from a JPG?

Accepted Answer

To convert a JPG to a valid DICOM, you must include both image and patient/study metadata: core identifiers like SOPClassUID (e.g., Secondary Capture Image Storage), SOPInstanceUID, and Study/Series Instance UIDs; patient/study context such as PatientName, PatientID, PatientSex (optional but common), PatientBirthDate (if known), StudyDate, StudyTime, AccessionNumber (optional), StudyID, ReferringPhysicianName (optional), Modality (e.g., “OT” for other or “SC” for secondary capture), SeriesNumber, and InstanceNumber; image pixel descriptors including Rows, Columns, SamplesPerPixel (3 for color, 1 for grayscale), PhotometricInterpretation (e.g., YBR_FULL_422 or RGB for color, MONOCHROME2 for grayscale), BitsAllocated, BitsStored, HighBit, PixelRepresentation (usually 0), PlanarConfiguration (0 if RGB interleaved), plus TransferSyntaxUID supporting JPEG encapsulation and the actual PixelData; recommended additions include BodyPartExamined, PatientOrientation, BurnedInAnnotation (“YES/NO”), and LossyImageCompression to indicate JPEG compression.

Question 2

How is patient-identifying information handled or anonymized during conversion?

Accepted Answer

We automatically strip or mask patient-identifying metadata (e.g., names, IDs, device serials, GPS, EXIF/XMP tags) during conversion. Only the image pixels are processed; identifiable headers and sidecar fields are removed or overwritten with safe defaults to help prevent re-identification.
All transfers use encrypted connections, and files are handled transiently for the purpose of conversion. We do not scan or repurpose content, and access is limited to the processing pipeline required to generate your output.
For extra control, you can pre-sanitize files before upload and choose output settings that exclude embedded metadata. If compliance is required (e.g., HIPAA/GDPR), disable metadata retention and verify outputs with a metadata viewer to ensure no identifying fields remain.

Question 3

Will image quality or resolution change when converting JPG to DICOM?

Accepted Answer

By default, converting a JPG to DICOM does not improve the original image’s fidelity; the pixel data is embedded as-is, so any compression artifacts or resolution limits from the JPG remain. If the converter is configured to keep the original pixel matrix and avoid recompression, the visual quality will be unchanged. However, if you choose to recompress or change color space, minor differences can occur.
What can change is the metadata and how viewers display the image. DICOM adds headers (e.g., patient/study tags, photometric interpretation, pixel spacing if provided), which can affect scaling or windowing in medical viewers, but not the underlying resolution. To preserve quality, use lossless options and keep the same dimensions and bit depth as the source JPG when creating the DICOM.

Question 4

Can I batch convert multiple JPGs into a single multi-frame DICOM series?

Accepted Answer

Yes, you can batch convert multiple JPGs into a single multi-frame DICOM series, but you’ll need a tool that supports stacking images into one DICOM object and adding the required DICOM metadata (Patient, Study, Series, and Image attributes). Ensure all JPGs share the same dimensions, bit depth, and color space, and are ordered correctly to reflect slice or frame sequence before conversion.
Common approaches include using DCMTK (e.g., dcmj2pnm/dcmmkdir workflows) or Python with pydicom and numpy to assemble a Multi-frame Image Module and set Per-frame Functional Groups if needed. After conversion, validate with a DICOM viewer (e.g., Weasis, RadiAnt) to confirm frames, orientation, and tags are correct.

Question 5

Which DICOM tags (e.g., Modality, StudyInstanceUID) are populated automatically and which can I edit?

Accepted Answer

By default, many core DICOM tags are filled automatically by the exporter or PACS when a file is created. Common auto-populated tags include StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID (unique identifiers), Modality (e.g., CT, MR, US), TransferSyntaxUID, InstanceCreationDate/Time, and system-generated fields like ImplementationClassUID and SOPClassUID. If the source data lacks some identifiers, tools typically generate valid UIDs on the fly to ensure DICOM compliance.
User-editable fields usually include descriptive or workflow-related metadata: PatientName, PatientID, PatientBirthDate, PatientSex, AccessionNumber, StudyDescription, SeriesDescription, ReferringPhysicianName, InstitutionName, and image-level tags like ImageComments. Depending on the tool, you can also adjust StudyDate/Time, SeriesNumber, InstanceNumber, and orientation/position tags if reformatting images. Always follow privacy rules when editing patient data.
Some tags should not be edited because they affect object identity and consistency: StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID, SOPClassUID, and TransferSyntaxUID. Changing Modality is also discouraged as it alters semantics. If you need to “anonymize,” use a proper DICOM de-identification profile that safely replaces or removes PHI while preserving required UIDs, or generates new consistent UIDs across related objects.

Question 6

What is the maximum file size or dimensions supported for JPG to DICOM conversion?

Accepted Answer

The maximum file size and dimensions for JPG to DICOM conversion depend on the specific converter and DICOM viewers used. As a general guideline, many online tools support images up to 50–100 MB and dimensions up to around 8,192 × 8,192 pixels, but limits vary due to browser memory, upload constraints, and server policies.
For clinical interoperability, DICOM itself can store very large images, but practical limits arise from pixel data memory, bit depth, and whether compression (e.g., JPEG Baseline) is applied. Extremely large images may require tiling or multiframe approaches to remain responsive in viewers and PACS systems.
If your JPG is rejected or downscaled, try reducing resolution (e.g., to ≤ 8K on the long edge), decreasing file size (optimize/compress), or converting to 8-bit color. For exact limits, check the converter’s upload cap and your DICOM viewer’s documentation, then test with a small sample before full batches.

Question 7

What’s the difference between a JPG file and a DICOM file?

Accepted Answer

A JPG is a common image format optimized for photographs, using lossy compression to reduce file size. It stores only pixel data and basic metadata (like size, color profile, and simple EXIF tags). It’s widely supported, lightweight, and ideal for web and general image sharing, but repeated edits and saves can degrade quality.
A DICOM is a medical imaging file format and standard that bundles the image data with extensive clinical metadata (patient info, modality, acquisition parameters, timestamps, study/series IDs). It supports multi-frame images, 3D/4D datasets, and precise measurement scales, ensuring interoperability across medical devices and PACS systems.
In short: JPG = compact, universal, minimal metadata, lossy; DICOM = clinical context, rich metadata, may be lossless or lossy, and suited for diagnostics. Converting DICOM to JPG removes medical metadata and may reduce fidelity, while JPG to DICOM won’t recreate missing clinical context.

Question 8

Will the resulting DICOM be compatible with PACS and standard DICOM viewers?

Accepted Answer

Yes—our output is a standards-compliant DICOM file that preserves required metadata and image encoding according to the DICOM specification, making it compatible with most PACS systems and standard DICOM viewers; however, if your workflow requires specific tags (e.g., patient/study identifiers, modality, or transfer syntax), ensure those fields are correctly populated to maximize interoperability.

Convert JPG to DICOM Online & Free

More online JPG converters to transform your images

Frequently Asked Questions about converting JPG to DICOM