Cloud viewer software
that speeds you up

Sirona runs in Chrome on a business-class connection — we recommend more than 50 Mbps. Lower latency is better; most U.S. wired and Starlink connections perform well. Your implementation team tests each site before go-live.

Any modern workstation with a current browser version and 16GB+ RAM is sufficient. Sirona runs browser-based with server-side image processing, so workstation requirements are minimal relative to legacy on-prem viewers. For tomosynthesis review we recommend a 5MP+ display at 60 Hz.

We do support multi-monitor, up to 4 distinct monitors at a time. These can be placed in any combination of landscape or portrait. For monitor configurations: • 2MP minimum resolution. • We recommend a minimum 5MP display for tomosynthesis review, and support 6MP. • 60 Hz refresh rate minimum.

Our browser-based caching is currently supported. We are exploring various caching strategies that take increasingly into account client behavior and available bandwidth to further optimize performance.

Yes, the viewer architecture leverages these discrete GPUs effectively. Our rendering engine uses WebGL 2.0 today, with work in progress for WebGPU. The calls we need for rendering image data do eventually route through ANGLE, but are appropriately mapped to the proper discrete GPU commands and run on GPU, not the CPU or integrated GPU (as long as the device is not on a deny-list). We verify this by checking with Chrome’s telemetry (“chrome://gpu”) to ensure that WebGL is marked as “Hardware accelerated” and has the appropriate GPU marked as the active GPU.

Network related timings can be observed through the Chrome developer tools. GPU utilization can be observed via profiling. Correct GPU assignment can be viewed in “chrome://gpu”.

Sirona’s performance strategy emphasizes server-side processing — including frame extraction, compression and browser caching — rather than pushing computational load (like pixel decoding) to the browser. This architecture inherently minimizes reliance on local GPU capabilities, and instead focuses on fast, efficient delivery of already processed and compressed frames to the viewer.

While older versions of Chrome could be limited to 2-4GB depending on whether you ran a 32- or 64-bit operating system, new Chrome instances running on Windows OS are capable of supporting 16GB per tab, providing sufficient space to run our viewer application.

Once image data is loaded into the browser, scrolling is rendered client-side, so there is no network round-trip per frame. Scroll lag is typically a function of viewers that use “server-side rendering”; Sirona’s Edge Streaming engine gets data to the browser faster and more reliably, but the rendering engine itself is client-side, making it the best of both worlds. When scrolling through images prior to having them in browser memory, we adjust the prioritization of image downloading appropriately to target the desired frame and those around it.

While the default browser bit depth is 8-bit, Chrome does offer support for higher bit depth with proper settings enabled and a monitor which supports 10-bit display.