> For the complete documentation index, see [llms.txt](https://kb.mago.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.mago.io/mago-stage/device-requirements/controller-requirements.md).

# Controller requirements

Use these requirements when selecting a device that will control Mago Stage. Controller devices are used to create and manage Stages, add content, connect displays, and control presentations.

More demanding workflows, including high-resolution content, screen sharing, video conferencing, and several connected displays, may require more powerful hardware.

The specifications below are deployment baselines. They do not guarantee performance for every combination of content and connected displays.

### Windows controllers

| Component    | Minimum baseline                                               | Recommended                                      |
| ------------ | -------------------------------------------------------------- | ------------------------------------------------ |
| Processor    | 12th-generation Intel Core i5 or equivalent                    | Intel Core Ultra 5 or equivalent                 |
| Memory       | 16 GB RAM                                                      | 32 GB RAM                                        |
| Free storage | 64 GB                                                          | 128 GB                                           |
| Graphics     | Hardware-accelerated graphics and video decoding               | Hardware-accelerated graphics and video decoding |
| Display      | 1920 × 1080                                                    | 1920 × 1080 or higher                            |
| Software     | Current graphics, network, and Microsoft Edge WebView2 updates | Current vendor and operating-system updates      |

The controller must be able to reach the required Mago Stage cloud or on-premises services.

### Android controllers

Recommended baseline:

* Android 12 or later
* Quad-core processor or better
* 8 GB RAM
* Sufficient free storage for locally stored and cached content
* Rear camera with autofocus for QR codes, photographs, and document scanning
* 1920 × 1080 display resolution or higher
* Reliable Wi-Fi connection

### iPhone and iPad controllers

Recommended baseline:

* iOS or iPadOS 16 or later
* iPad 10th generation or newer for full-size tablet use
* Sufficient free storage for locally stored and cached content
* Rear camera with autofocus for QR codes, photographs, and document scanning
* Reliable Wi-Fi connection

Smaller phone-sized controllers support selected workflows. A phone controller can connect to a maximum of two displays during a session.

### Browser controllers

A browser controller requires:

* A supported desktop browser
* JavaScript and cookies enabled
* Permission to open required pop-up windows
* Access to the required Mago Stage services
* Screen-sharing permission when sharing the controller’s screen
* Camera and microphone permission when using conferencing features

Screen capture is not supported from mobile browsers or Safari on iPhone and iPad.

### General controller requirements

All controllers require:

* A supported operating system or browser
* Access to the required cloud or on-premises endpoints
* Correct system date, time, and time zone
* Current operating-system, graphics, browser, and network updates
* A stable network connection
* Local file access when uploading content

Depending on the features being used, controllers may also require:

* Camera permission for scanning QR codes
* Camera access for photographs and document scanning
* Microphone permission for conferencing
* Screen-recording permission for screen sharing

### Performance considerations

Controller performance may be affected by:

* The number of connected displays
* The complexity of the Stage layout
* High-resolution images and video
* Large locally stored or cached files
* Interactive websites
* 3D models
* Screen sharing
* Video conferencing

Test the intended device with representative content before a large deployment.
