Skip to content

Help

Most questions come down to one of three things: whether a title is ready to use, whether the file you downloaded is the file we published, and how to tell us something is wrong. Those are covered first.

Starting out

  1. Open the product page and read the status badge before anything else.
  2. In development means there is no release to install yet. There is nothing to download, and nothing is being hidden from you.
  3. When a release exists, the downloads page lists the real file size, release date and — if we hold one — the SHA-256 digest.
  4. The changelog lists every published release with its notes and any warnings.

Checking that a download is genuine

Compare the file size first. Then, where a digest is published, compare the SHA-256 value on your machine against the one on the downloads page. If the digests differ, stop and discard the file.

The security page > has the exact commands for macOS, Linux and Windows.

When something does not work

  • A download that stalls is usually local: try a different browser or network before treating it as a fault on our side.
  • If a platform entry is marked unavailable, we know that build cannot be served right now. Nothing is silently substituted for it.
  • When reporting a problem, include the product name, the version shown on the downloads page, your operating system, and what you expected to happen.

Product-specific support

No per-product support channel is published yet

No product currently has a support link on record. Rather than inventing one, we leave this empty — the general contact below is the route in the meantime.