The download page at [mieza.ai/download](https://mieza.ai/download) lists releases of the Mieza desktop assistant. It shows the newest release for every platform and release channel, along with the metadata you need to verify what you downloaded.

## What the Page Shows

Release metadata is public: you can read it without an account. For each current release the page lists:

- **Version** and **platform** (Windows or Linux)
- **Channel** — stable or beta; beta builds carry a *Beta* label
- **Size** and **published** date
- **System requirements**, when the release declares them
- **Release notes**, when the release includes them
- **SHA-256** of the installer, with the command to verify it

Withdrawn releases are not shown. When no release has been published for a platform and channel, the page says so: *No releases are available yet.*

## Downloading

Downloading requires two things: being **logged in**, and a plan that **includes the desktop assistant**. Release metadata itself is not restricted.

Click **Download** on a release card. The platform issues a short-lived, HTTPS-only download link for that exact artifact and starts the download; if it does not start automatically, a fallback link is shown. Before the link is handed to your browser, the page checks that the link's SHA-256 and size match the release you clicked. A mismatch is treated as an error rather than a download.

Three outcomes can stop a download, and the page names each:

| What you see | What it means |
|---|---|
| *Log in to download this release.* | You are not logged in. Release metadata stays visible. |
| *Your current plan does not include this download.* | Your account is not entitled. The required plan is shown with a link to plans. |
| *This release is no longer available.* | The release was withdrawn after the page loaded. |

An expired session shows a login prompt on the card instead of an error.

## Verifying Your Download

Every release card shows the installer's SHA-256 digest. After downloading, compute the digest locally and compare:

```bash
# Linux
sha256sum <file>
```

```powershell
# Windows (Command Prompt or PowerShell)
certutil -hashfile <file> SHA256
```

The output must match the SHA-256 on the release card. If it does not, do not run the installer.

### Windows SmartScreen

Some Windows builds are not yet code-signed. For those, the release card shows a note: Windows SmartScreen will display *"Windows protected your PC"* when you run the installer. Verify the SHA-256 first, then choose **More info** and **Run anyway**.

## See also
- [Plans and Billing](/docs/plans-and-billing) — which plans include which features
- [Uploading Your First Game](/docs/uploading-a-game) — analyzing recorded games on the web platform