Skip to main content
Voyager runs in your browser. Client demand is modest and does not grow with scan size — a large reconstruction is not a heavier computer. The usual wait is the network download when a scan first opens. A real hardware GPU is required; software rendering is not usable.
These recommendations are for viewing scans in Voyager — opening a Project, orbiting, zooming, and scrubbing slices. Integrity Analysis and heavy GD&T work can ask more of the machine.
Comfortable day-to-day use. A typical scan is usable in about 30 seconds, with orbit at 60 fps.

​
Minimum spec

Works, with waiting. A typical scan is usable in about 50–80 seconds; orbit still stays near 60 fps.
Below minimum: less than 8 GB RAM, no hardware GPU, or under about 10 Mbps. At 10 Mbps a typical scan can take about 3 minutes to open.

​
What actually matters

Ranked by how much they affect your experience:
  1. Network — most of the wait is downloading the scan. Faster internet shortens time-to-usable more than a faster CPU.
  2. CPU — sets how quickly the scan becomes interactive after the download. Once the volume is on the GPU, orbiting stays smooth even on a slower processor.
  3. A real GPU — any hardware GPU with WebGL2 is enough. Integrated graphics are fine. Software rendering is not.
8 GB of RAM is the floor because one Voyager tab can use about 2.4 GB. VRAM is rarely the limit.
4K displays use more GPU memory and can cut frame rate. 1440p or 1080p is smoother.

​
Windows dual-GPU laptops

On Windows, the browser may default to integrated graphics even when a discrete GPU is available. See Browser Graphics Optimization for Windows to point Chrome, Edge, or another browser at the high-performance GPU.