> ## Documentation Index
> Fetch the complete documentation index at: https://support.lumafield.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Choosing a Computer for Voyager

> Minimum and recommended specs for running Voyager in the browser

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.

<Note>
  These recommendations are for viewing scans in Voyager — opening a Project, orbiting, zooming, and scrubbing slices. [Integrity Analysis](/voyager/voyager-porosity-analysis) and heavy [GD\&T](/voyager/voyager-auto-dimensioning) work can ask more of the machine.
</Note>

<h2 id="recommended-spec">
  Recommended spec
</h2>

Comfortable day-to-day use. A typical scan is usable in about 30 seconds, with orbit at 60 fps.

| Component   | Spec                                                                       |
| ----------- | -------------------------------------------------------------------------- |
| **CPU**     | Apple M1 / Intel 11th-gen i5 or newer                                      |
| **RAM**     | 16 GB                                                                      |
| **GPU**     | Any hardware GPU with WebGL2 and about 1 GB free VRAM (integrated is fine) |
| **Display** | 1440p or lower for a solid 60 fps                                          |
| **Network** | 100 Mbps or faster                                                         |
| **Browser** | Current Chrome, Edge, Firefox, or Safari                                   |

<h2 id="minimum-spec">
  Minimum spec
</h2>

Works, with waiting. A typical scan is usable in about 50–80 seconds; orbit still stays near 60 fps.

| Component   | Spec                                                                         |
| ----------- | ---------------------------------------------------------------------------- |
| **CPU**     | Intel 8th-gen desktop i5 / 2019–2020 laptop i5 class                         |
| **RAM**     | 8 GB                                                                         |
| **GPU**     | Any hardware GPU with WebGL2 (integrated is fine; software rendering is not) |
| **Display** | 1080p                                                                        |
| **Network** | 25 Mbps (50 Mbps to stay under about a minute)                               |
| **Browser** | A current version of Chrome, Edge, Firefox, or Safari                        |

<Warning>
  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.
</Warning>

<h2 id="what-actually-matters">
  What actually matters
</h2>

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.

<Tip>
  4K displays use more GPU memory and can cut frame rate. 1440p or 1080p is smoother.
</Tip>

<h2 id="windows-dual-gpu-laptops">
  Windows dual-GPU laptops
</h2>

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

<h2 id="related-pages">
  Related pages
</h2>

* [Browser Graphics Optimization for Windows](/voyager/voyager-windows-graphics)
* [Welcome to Voyager](/voyager/voyager-intro)
* [First Steps](/platform/first-steps)