Wintty on Windows on ARM

The ARM64 build of the same Ghostty-core terminal, on its own channels. This page tracks where it stands, what experimental means, and where reports from ARM machines go.

Where the ARM64 build stands

The ARM64 build ships on two channels: arm64-stable for released builds and arm64-tip for development builds. Sponsor at any amount, sign in with GitHub on the download page, and take the installer below.

The installer routes check your sponsor session, so sign in first: a click without one lands on a refusal, not a file.

Sponsor and Pro desktop carry it. OSS ships no binary at all, and Pro Legacy and Pro Enterprise have no ARM64 build.

What experimental means

ARM64 builds are experimental: there is no ARM hardware here to test them properly yet, so treat them as early builds even on the stable channel. Reports from Windows on ARM machines are welcome.

The word stable in arm64-stable names the release process, not a promise about ARM hardware: those builds get the same checks and signing as every other cut, and they are still early builds, because nobody here has run them on the hardware they are for.

Channels and access

Architecture is a channel dimension: the ARM64 build of a channel is its own channel, named by putting the arm64 segment in front.

ChannelWhat it isUpdate feed
arm64-stableThe released ARM64 build./releases/arm64-stable/releases.win.json
arm64-tipThe development ARM64 build./releases/arm64-tip/releases.win.json

The same sponsorship covers both architectures. A sponsor entitled to stable is entitled to arm64-stable, with no separate tier, no new signup, and nothing extra to buy. Installed builds poll their channel's feed for updates, the same mechanism as x64.

Installing on an ARM machine

Sponsor at any amount, sign in with GitHub, and take the installer above. It installs and updates in place, the same mechanics as the x64 build. Building from source is still documented for x64 only.

Reporting what you find

Run Wintty on your machine and tell us what breaks. Open an issue on GitHub with the device, the Windows version, and what you saw, and say it is a Windows on ARM machine. Reports from Windows on ARM machines are how the experimental label comes off.

Requirements

  • Windows 10 or 11 on an ARM64 machine for the ARM64 build; the x64 installer covers 64-bit Intel and AMD machines.
  • A DirectX 12 capable GPU for the standard renderer. Machines that cannot run DirectX 12 take Pro Legacy, the build against DirectX 11.
  • No WSL, no X server, and no Linux environment: Wintty installs like any other Windows application.

FAQ

Is there a Wintty build for Windows on ARM?

Yes. Wintty ships a native ARM64 build for Windows on ARM on its own channels, arm64-stable and arm64-tip. It is experimental, and it installs and updates the same way the x64 build does.

Are the ARM64 builds stable?

No. ARM64 builds are experimental: there is no ARM hardware here to test them properly yet, so treat them as early builds even on the stable channel. Reports from Windows on ARM machines are welcome.

Do I need a separate sponsorship for ARM64?

No. The ARM64 build of a channel rides the same sponsorship as its x64 twin: a sponsor entitled to stable is entitled to arm64-stable, with no new tier and nothing extra to buy.

Which editions have an ARM64 build?

Sponsor and Pro desktop. OSS ships no binary at all, and Pro Legacy and Pro Enterprise have no ARM64 build.

Wintty is built on the Ghostty terminal core and is not affiliated with the Ghostty project. We are big fans of Ghostty and hope this work lands in official Ghostty for Windows.