OHIF

OHIF is a customisable web-based medical imaging viewer.

  • AI
  • Media Applications
  • Tools & Utilities
OHIF is a customisable web-based medical imaging viewer. It allows doctors and researchers to access and analyse scans, such as MRIs and CTs, directly through any web browser. It simplifies viewing medical data from different sources without needing specialised software installed on individual computers.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

55/100 Fair

Maintained
74last commit 79 days ago
Popular
2313 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
75no serious findings

Based on 4 of 5 factors.

Availability: platform listings confirmed 2 days ago

GitHub stars
13
Open issues
1
Last commit
2026-09-03
Activity
stale

Checked 15 days ago - source: GitHub (OHIF/OHIF-Office-Hours)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Connect OHIF to a DICOM data server OHIF only shows images from a DICOM (medical image) server. If it is left pointing at the public cloud data server, your own studies will not appear. source
  • Start Orthanc and keep storage persistent Use Orthanc or another DICOM server to hold studies, and open port 4242 for its web/API and 8042 for receiving DICOM uploads. The Docker example uses temporary storage, so scans disappear when it stops. source
  • Make OHIF restart after a reboot If OHIF runs as a PM2 service (a program that keeps apps running), enable PM2 startup so it starts automatically after reboot. Otherwise the app may be down and nobody can open studies. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why do my own DICOM studies not appear after installing OHIF?

OHIF only displays images from a configured DICOM server. If it is still pointed at the public cloud data server, your local studies will not show.

Which Orthanc ports should be exposed for OHIF, and what storage gotcha applies?

Open port 4242 for Orthanc's web/API and 8042 for receiving DICOM uploads. Use persistent storage for the DICOM server, because the Docker example uses temporary storage and scans disappear when it stops.

How can OHIF be made to start after a server reboot?

If OHIF runs as a PM2 service, enable PM2 startup so it starts automatically. Without this, the app may be down and users cannot open studies.

Can an organization seek FDA clearance for a product built on OHIF?

The OHIF Platform license does not prevent a company or group from seeking FDA clearance for a product built using the platform.

Answers sourced from docs.ohif.org, github.com, github.com, github.com

Community

Collected 48 days ago - public community threads