Open DICOM studies, edit metadata, and explore MPR, 3D volume rendering and cine on Mac and Windows. OmniDICOM includes PACS/DICOMweb transfer and exports; Professional adds stacked filters and analysis tools. A 14-day trial starts at first launch. Trial exports have limitations. Paid plans start at US$10/month per machine. For research and education, not diagnosis.
Hi, I'm Youngrak, the creator of OmniDICOM.
I built it around DICOM workflows for research and teaching: opening studies, comparing series, editing tag values, exploring MPR and 3D, and exporting results from one desktop app.
Metadata editing is a central part of the workflow. You can inspect a tag, change its value, save, then reopen the study to verify the result. Work on a copy if you need to preserve the original files.
The Mac download supports Apple silicon on macOS 13 or later; the Windows download supports 64-bit Windows 10/11. A 14-day Professional trial starts at first launch, with export limitations. Basic costs US$10/month or US$99/year per machine; Professional costs US$45/month or US$449/year. Taxes may apply.
OmniDICOM is for research and education only, not diagnosis or clinical decision-making.
If you work with DICOM for research or teaching, which repeated task would you most like to simplify? I would appreciate specific workflow feedback.
niche but clearly built by someone who actually deals with DICOM files, not a generic image viewer with a medical skin on it. the "work on a copy" advice for metadata edits makes sense given studies can't really be un-anonymized once you overwrite the wrong tag, but is there any built-in guardrail, like a warning before saving over the original file, or is that entirely on the user's own backup discipline right now?
OmniDICOM
Dial
niche but clearly built by someone who actually deals with DICOM files, not a generic image viewer with a medical skin on it. the "work on a copy" advice for metadata edits makes sense given studies can't really be un-anonymized once you overwrite the wrong tag, but is there any built-in guardrail, like a warning before saving over the original file, or is that entirely on the user's own backup discipline right now?