Skip to content

dcmview documentation

Inspect DICOM where the data already live, without setting up a permanent viewer or sending files to a third party.

dcmview is a fast, temporary DICOM viewer for developers, data scientists, and medical imaging researchers. Give it one or more local files or directories and it starts an embedded browser viewer for pixels, tags, logical series, cine playback, references, and rectangular ROI annotations. Stop the process and the unauthenticated local server, caches, and in-memory edits disappear.

Chest CT cine playback in dcmview

DICOM SEG semantic overlay in dcmview

Chest radiograph in dcmview

Mammography study in dcmview

PET cine playback in dcmview

Ultrasound cine playback in dcmview

RT Dose semantic context in dcmview

DICOM whole-slide microscopy context in dcmview

Source imagery attribution

If you want to… Start here
Open a file or study directory from a shell Install dcmview and inspect a first image
Inspect data on a remote server Forward the loopback viewer over SSH
Launch from a script or notebook Use dcmview from Python
Stay inside your editor Open DICOM data in VS Code
Load, edit, and export rectangular ROIs Work with annotations
Understand what the viewer can and cannot render Review DICOM support boundaries
  • Recursive file discovery with metadata filters and progressive results.
  • Study, series, logical-frame, and local DICOM-reference navigation.
  • Server-rendered PNG and client-side raw-frame paths with consistent windowing.
  • Pan, zoom, scroll, window/level, presets, flips, rotation, and cine controls.
  • Lazy tag browsing with sequence expansion and selective retrieval.
  • Conservative context for SEG, Parametric Map, RT Dose, and positioned WSI tiles, including validated geometry-aligned SEG composition.
  • In-memory EMBED-style rectangular ROI editing and CSV export.
  • The same self-contained Rust viewer through the CLI, Python package, and VS Code extension.

dcmview has no database, user accounts, persistent viewer state, or configuration files. The HTTP API is an internal debugging surface, not a stable public integration API. Semantic panels do not establish clinical correctness: ambiguous SEG or RT Dose geometry disables overlay eligibility, and WSI support positions one selected tile without stitching a whole slide.

This site documents the stable v0.2.12 release. See the documentation source for the exact commit.