How to share dicom medical imaging as a universal pdf
- Step 1Pick the representative image to share — Choose the single frame that best answers the request — the key slice, the diagnostic view, the relevant film. This converts one frame to one page, so select rather than dump the whole study.
- Step 2Export it as uncompressed DICOM — Export the single instance from PACS, preferably uncompressed (Implicit/Explicit VR Little Endian). Compressed pixel data (JPEG2000/JPEG-LS/RLE) will not render correctly in this tool.
- Step 3Drop it onto the converter — Upload the
.dcmor.dicomfile. One file per run;application/dicomaccepted. Over 2 MB on free tier? Upgrade to Pro (50 MB) or export a smaller representation. - Step 4Let it render automatically — No options to set — it renders on a fixed A4 page using the file's stored window the moment it's read.
- Step 5De-identify if sharing externally — The caption prints the patient name and ID. Before sending to an insurer or third party who shouldn't see identifiers, run the result through the PII redactor, or de-identify the DICOM beforehand.
- Step 6Share via portal, email, or print — Download the PDF and attach it to the patient portal, email it, or print it. Always retain the original DICOM for clinical use — the PDF is a shareable copy, not the diagnostic source.
Who you're sharing with, and what to send
Matching the recipient to the right precaution. The tool always renders identifiers into the caption unless you remove them.
| Recipient | Typical need | Recommended step |
|---|---|---|
| The patient (their own image) | A copy they can view on a phone | Convert and share as-is; identifiers are their own |
| Insurer / claims | Visual evidence for a claim | Redact name/ID with the PII redactor unless the claim requires them |
| Administrative staff | Image for a record without PACS | Share internally; keep the original DICOM as source of truth |
| External clinician (second opinion) | A viewable representative image | Convert, optionally merge several views with PDF Merge |
| Public / unverified channel | Should not contain PHI | De-identify the DICOM before converting |
What gets shared vs what stays private
The conversion is local; the privacy of the output is in your hands.
| Item | In the output PDF? | Notes |
|---|---|---|
| Rendered image | Yes | One frame, grayscale or RGB, file's window |
| Patient name / ID (caption) | Yes — printed onto the page | Redact with the PII redactor if needed |
| Full DICOM tag dump | No | Only the captioned fields are surfaced |
| Original pixel resolution | Reduced | Scaled to page, JPEG q0.95 — not diagnostic-grade |
| Server copy | No | All processing is in your browser; 0 bytes uploaded |
Cookbook
Sharing scenarios across patient, insurer, and admin audiences. Identifiers are illustrative.
Patient wants a copy of their scan
Convert the representative frame and the patient can open it on their phone. Their own identifiers in the caption are fine.
Input: scan_key.dcm 1.2 MB, CT, 512x512 Output: scan_key.dicom-to-pdf.pdf 1 page Share: email or patient-portal upload
Insurer claim — de-identified image
An insurer needs the image but not the patient's name. Convert, then redact the caption before sending.
Convert: film.dcm -> film.dicom-to-pdf.pdf (caption: name+ID) Redact: PII Redactor -> film_for_claim.pdf Attach the redacted PDF to the claim form.
File over 2 MB on free tier
A higher-resolution frame is blocked on free; Pro renders it.
Input: hi_res.dcm 3.3 MB Free: blocked - "... Free handles files up to 2 MB ..." Pro: renders to a one-page PDF (cap 50 MB)
Bundle a few images for a second opinion
Convert each representative frame, then merge into one PDF the external clinician can open.
Convert: img1.dcm -> img1.dicom-to-pdf.pdf
img2.dcm -> img2.dicom-to-pdf.pdf
Merge: PDF Merge -> second_opinion.pdf (2 pages)Image-free object → placeholder
If you accidentally export a report object instead of an image, you still get a PDF — a placeholder with patient and modality.
Input: report.dcm (no pixel data)
Output: "DICOM file imported - pixel data could not be
rendered" + Patient + ModalityEdge cases and what actually happens
Patient identifiers printed into the share
PHI exposureThe caption renders Patient name and ID onto the page. That's appropriate when the patient receives their own image, but a privacy risk when sharing externally. Redact with the PII redactor, or de-identify the DICOM first — the metadata scrubber clears document properties, not the rendered caption.
Sharing a whole study
By designThe tool converts one frame to one page — ideal for a representative image, not a full study export. To send several images, convert each and combine with PDF Merge.
File over the tier cap
BlockedFree allows 2 MB; Pro 50 MB. Higher-resolution frames exceed the free cap and are blocked with a size message. Upgrade, or export a smaller representation (not a compressed transfer syntax, which won't render).
Compressed pixel data
Renders incorrectlyEncapsulated (JPEG2000/JPEG-LS/RLE) pixel data isn't decompressed and renders as noise. Export uncompressed before converting.
Reduced resolution in the shared image
ExpectedThe image is scaled to fit the page and JPEG-encoded, so it's lower fidelity than the original DICOM. That's fine for sharing and viewing; keep the original for clinical use.
Recipient on mobile
SupportedThe output is a standard PDF that opens in any phone's built-in viewer or browser — the whole point of converting away from DICOM. No app install required.
Wrong file exported (report, not image)
PlaceholderAn image-free object produces a placeholder PDF with patient and modality rather than failing — a hint that you exported the wrong instance.
Renamed image file
ErrorA JPEG/PNG renamed to .dcm throws "Could not parse DICOM file". For ordinary images use Image to PDF.
Colour ultrasound looks off
Color shiftRGB renders fine; YBR colour spaces aren't converted, so YBR ultrasound shows shifted colours. Export as RGB if your workstation supports it.
Frequently asked questions
Can patients view the shared PDF on their phone?
Yes — it's a standard PDF, viewable in any mobile device's built-in viewer or browser. That's the main benefit over sharing a .dcm, which needs a specialist viewer.
What patient data is visible in the shared PDF?
The caption renders Patient name, Patient ID, Modality, Study Date, and Study/Series description onto the page. Confirm your privacy policy before sharing identifiable data externally; redact with the PII redactor if the recipient shouldn't see it.
Can I share an entire study this way?
Not in one file — it converts one frame per page. Convert each representative image and merge them with PDF Merge into a single shareable PDF.
Should I include the clinical report too?
Yes, for context. Convert the report or include the clinician's letter as a separate PDF, or append it to the image PDF with PDF Merge so the recipient gets image plus interpretation.
How do I de-identify before sharing with an insurer?
Convert, then black out the name and ID in the caption with the PII redactor; or de-identify the DICOM at the source. Clearing PDF document properties won't hide the rendered caption.
Is the image uploaded to a server?
No. Parsing and rendering happen in your browser with dicom-parser and pdf-lib. The image and identifiers never leave your device; the result panel shows 0 bytes uploaded.
Why won't my file convert?
Most likely it's over the free 2 MB cap (upgrade to Pro for 50 MB), it's compressed pixel data (re-export uncompressed), or it's not actually DICOM (a renamed JPEG/PNG — use Image to PDF).
Is the shared PDF good enough for diagnosis?
No. It's a reduced-resolution JPEG reproduction at a single window setting — for communication and records. Always keep the original DICOM for clinical interpretation on a calibrated display.
Are there any settings to choose?
No. The tool auto-runs on drop with the file's stored window on a fixed A4 page. Adjust page size afterward with PDF Resize if needed.
What's the file naming on download?
The output keeps your source name with a .dicom-to-pdf.pdf suffix — e.g. scan_key.dcm becomes scan_key.dicom-to-pdf.pdf.
Can the recipient extract the original DICOM from the PDF?
No. The PDF embeds a rendered JPEG of one frame, not the DICOM dataset. There's no way to recover full pixel data or the complete tag set from the shared PDF — another reason to keep the original on file.
Can I batch this for many patients?
The web tool is single-file. For automation, use the @jadapps/runner (Pro, runner-builtin): GET /api/v1/tools/dicom-to-pdf for the schema, pair the runner, then POST each file to 127.0.0.1:9789/v1/tools/dicom-to-pdf/run, processed locally.
Privacy first
All PDF processing runs locally in your browser using PDF-lib and pdf.js. No file is ever uploaded — only metadata counters are saved for signed-in dashboard stats.