> ## Documentation Index > Fetch the complete documentation index at: https://docs.layarva.com/llms.txt > Use this file to discover all available pages before exploring further. # Player Device Requirements > Choose hardware for Cloud, Edge, Offline, Kiosk, and Operator deployments without mixing browser and Android requirements. ## Choose the runtime first Layarva has more than one Player runtime. Select the row that matches what will actually run on the device. | Runtime | Runs on | Requirement source | | --------------------------- | --------------------------------------------------------------------------- | --------------------------------------------------------------------- | | **Cloud Player** | A supported desktop, TV, or embedded browser | Browser requirements on this page | | **Layarva Android Player** | The Layarva APK on an Android TV or box | [Android Player requirements](/screens/android-player) | | **Layarva Edge** | A Windows branch PC serving local Screens | Edge host requirements on this page | | **Offline Player** | A supported Player importing a signed `.lvapkg` | The runtime's requirements plus enough space for the complete package | | **Queue Kiosk or Operator** | A supported browser; Windows launcher recommended for silent Kiosk printing | Browser and Queue requirements on this page | Do not apply the browser RAM or engine floor to the Android APK. Android has its own measured requirements, bundled display engine, and in-app device check. ## Cloud Player and browser minimums | Component | Minimum | Recommended | | ------------------ | ------------------------------------------------------------ | ----------------------------------------------------------------- | | Browser engine | Chrome or Edge 111+, Firefox 111+, or Safari 16.4+ | A current Chromium-based browser with automatic updates | | Memory | 2 GB | 4 GB for long playlists, video, or animated Designs | | Display | 1280×720 | 1920×1080 | | Video | H.264 playback for `avc1.42E01E` with AAC audio | Hardware H.264 decoding | | Persistent storage | 512 MB browser storage headroom | Enough capacity for the active and previous Publication resources | | Network | HTTPS to `app.layarva.com` and `cdn.layarva.com` on port 443 | Wired Ethernet or stable Wi-Fi | Designs use a 1920×1080 authoring canvas and scale to the configured Screen. Portrait displays are supported; the short edge must still meet the 720-pixel floor. ### Recommended capabilities * Hardware-accelerated WebGL for Lottie and animated backgrounds. * At least two CPU cores; a modern quad-core device is preferred. * Audio output for video sound and Queue chimes. * An Indonesian text-to-speech voice when the Screen announces Queue tickets. * Browser kiosk or full-screen mode so browser chrome is not shown on the display. ## Check a browser device before installation Open [https://app.layarva.com/device-check](https://app.layarva.com/device-check) **on the actual device and browser that will become the Screen**. The public check measures the rendering environment; it does not infer support from a product listing or user-agent claim. Unknown measurements do not automatically fail a device. For example, Firefox and Safari may not report memory. A successful capability check also does not replace a sustained test with the actual Playlist. ## Layarva Edge host The Windows PC running Layarva Edge requires: | Component | Requirement | | ---------------- | ------------------------------------------------------------------------------ | | Operating system | Windows 10 or Windows 11, 64-bit | | Browser engine | Bundled with Edge; no separate browser update is required for the host runtime | | Storage | Enough disk space for staged Publications and previous rollback content | | Platform network | Outbound HTTPS on port 443 | | Branch network | Screens, Kiosks, and Operator stations must reach the Edge host on port `7749` | | Power policy | Always on; sleep and unattended shutdown must be disabled | One Edge instance runs per machine. Local Screens still need a supported display engine, memory, resolution, video capability, and local storage; only their route changes from the Platform to the branch Edge. ## Offline deployment Offline playback removes the network requirement, not the rendering requirements. The device must: * Run a supported Player runtime. * Have enough free space for the complete signed package and its verified extraction. * Maintain a trustworthy clock for the package lease. * Support every media type included in the Publication. The Player refuses a package whose signature, checksums, target identity, renderer compatibility, or validity window cannot be verified. ## Queue Kiosk and Operator stations A browser Kiosk or Operator station needs a supported browser, HTTPS access to Layarva, and a display suitable for its workflow. * A Kiosk with a thermal printer should use the Windows launcher from [https://app.layarva.com/kiosk](https://app.layarva.com/kiosk) for full-screen operation and silent printing. * A Kiosk opened without the launcher can still work, but the browser print dialog appears for every ticket. * An Operator station signs in at [https://app.layarva.com/operator/login](https://app.layarva.com/operator/login) and needs an account assigned to a trusted Counter. * Physically verify the printer, paper size, speaker, touch screen, and remote control. A web capability check cannot prove that those peripherals are connected correctly. ## Related guides * [Use the Cloud Player](/screens/cloud-player) * [Install and Operate the Android Player](/screens/android-player) * [Check Device Compatibility](/screens/device-check) * [Configure a Queue Kiosk](/queue/kiosks) * [Use the Operator Console](/queue/operator)