> ## Documentation Index
> Fetch the complete documentation index at: https://docs.evox.wraithesports.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Installation

> Install evoX on Windows, macOS or Linux and complete the first run.

evoX is the same app on Windows, macOS and Linux: your profiles, key assignments and Market
content work the same on all three systems. The differences are only in how it is installed, the
permission steps on first launch and how updates arrive.

## Supported systems

| System  | Requirement                  | Package          |
| ------- | ---------------------------- | ---------------- |
| Windows | 64-bit Windows 10/11         | `.exe` installer |
| macOS   | Apple Silicon (M1 and later) | `.dmg`           |
| Linux   | x86\_64                      | AppImage         |

On every system you need a working USB connection for evoX and enough disk space for installation
and updates.

<Info>No build is published for Macs with Intel processors. The manufacturer does not provide an
Intel version of the device's connection library, so instead of shipping an app that installs but
can never see the device, nothing is published for that platform.</Info>

## Windows

<Steps>
  <Step title="Open the installer package">Run the evoX Windows package provided by Wraith. Do not use packages whose source you cannot verify.</Step>
  <Step title="Complete the user installation">The installation goes to your user account; no Windows Service is installed.</Step>
  <Step title="Launch evoX">On first launch the `%APPDATA%/evoX` data area is prepared.</Step>
  <Step title="Verify the device">If the official app is holding the device, [take over control](/en/application/device-connection).</Step>
</Steps>

Windows has no extra permission step and updates arrive automatically.

## macOS

<Steps>
  <Step title="Install the app">Open the `.dmg` file and drag evoX into the Applications folder.</Step>

  <Step title="Open the app manually on first launch">
    The package is not yet signed by Apple, so macOS shows a security warning on first launch.
    On macOS 14 and earlier, right-clicking evoX in Finder and choosing **Open** is enough.
    On macOS 15 and later, close the warning, then choose **Open Anyway** in
    **System Settings → Privacy & Security** and enter your password.
  </Step>

  <Step title="Grant Accessibility permission">
    macOS requires **Accessibility** permission for an app to send keyboard and mouse input.
    When you choose **Grant permission** in the welcome screen step, System Settings opens; once you
    turn evoX on in the list and return to the app, the status updates on its own.
  </Step>

  <Step title="Verify the device">
    No extra permission is needed for the device. On first launch the `~/Library/Application Support/evoX` data area
    is prepared.
  </Step>
</Steps>

You can also choose to continue without granting permission. In that case the shortcut, text and
mouse actions you assign to keys do not work; when you press a key, evoX shows a notification that
opens the permission pane. On the first use of keyboard and text actions, macOS also asks for an automation approval.

<Warning>Unsigned distribution has two more consequences: evoX cannot update itself, so you install
new releases manually from the [download page](/en/application/download); and you need to grant
Accessibility permission again for every new release. Once Apple approval arrives, a signed release
will be adopted; from that release on, updates will arrive automatically and permissions will be kept.</Warning>

Some Windows shortcuts are translated to different keys on macOS and four have no equivalent; the
**Coordinates** mode of **Mouse Event** also works only on Windows. Details are on the
[Assign actions](/en/application/assign-actions) page.

## Linux

<Steps>
  <Step title="Make the AppImage executable">
    Give the downloaded file execute permission and open it; there is no separate installation step.

    ```bash theme={}
    chmod +x evoX-*-x86_64.AppImage
    ./evoX-*-x86_64.AppImage
    ```
  </Step>

  <Step title="Set up device permission">
    On Linux, access to USB devices requires a system rule. On first launch evoX offers to install
    this rule and asks once for your administrator password. After installation you may be asked to
    log out and back in.
  </Step>

  <Step title="Launch evoX">On first launch the `~/.config/evoX` data area is prepared.</Step>
  <Step title="Verify the device">If the device does not appear, follow the order on the [Troubleshooting](/en/application/troubleshooting) page.</Step>
</Steps>

Two shortcut actions have no equivalent on Linux, and the **Coordinates** mode of **Mouse Event**
works only on Windows; details are on the [Assign actions](/en/application/assign-actions) page.

If you choose **Later** on the device permission prompt, the prompt is not repeated for the same
release. On distributions whose system configuration is read-only (for example NixOS), instead of
installing, evoX shows instructions explaining how to add the rule to your system configuration.

To sign in to your Market account, a system keyring (GNOME Keyring or KWallet) must be running in
your session; without a keyring the session cannot be stored securely, so it is not saved.
If the AppImage does not open, install your distribution's FUSE compatibility package (`libfuse2`).

<Note>Automatic updates on Linux depend on two conditions: you run the app as an AppImage file and
the folder containing the file is writable. The update replaces the file in place, so the file name
changes along with the version; if you created a shortcut tied to a fixed name, you may need to
recreate it after the update. Starting the app together with the system is not supported on Linux;
evoX does not install a separate system service.</Note>

<Info>Uninstalling the app does not automatically delete the user profiles and content in your data
area.</Info>