An open-source recompiler turns tested Windows programs into Apple silicon code
The project’s PuTTY and command-line results come with Wine dependencies, fallback execution and a deliberately limited compatibility claim.

A Windows executable can become an Apple silicon executable before it starts running. arm64-recompiler reads x86-64 machine code, translates it through LLVM and produces a native ARM64 program for macOS. The original program gets another machine language without arriving with its original source. That’s quite a translation assignment for a file ending in .exe.
The project README narrows the claim: “not a general” tool for arbitrary Windows binaries. The tested examples include PuTTY and its Plink command-line companion, jq and a restricted ripgrep run. Those concrete demonstrations are more useful than a promise that an entire software library has suddenly become Mac-compatible.
The distinction between native and hosted operation matters. A simple Plink version command runs through startup, argument handling, output and shutdown. GUI and network workloads need a hosted mode with Wine’s support layer and a Wine installation. The README says wineserver still runs under Rosetta. There is no standalone application bundle that makes those dependencies disappear.
Static translation also has limits inside a program. Runtime-generated code and some unrecovered indirect branches can fall back to an x86 interpreter. Several instruction families aren’t lifted. A translated binary can therefore contain native execution and supporting fallback behavior, rather than every possible path being converted in advance.
The headline performance result is particularly easy to overstate. The project reports a 42.31-millisecond median for Plink’s version command against 262.23 milliseconds under Wine plus Rosetta, across thirty runs per variant. It also lists the upstream native Mac build at 7.41 milliseconds. Translation beats one baseline in that test while remaining slower than software built directly for the platform.
The hosted results tell a different story. On the project’s M1 test, a cold SSH command was roughly level with Wine plus Rosetta, while a warm command improved. Reported resident memory was higher for hosted programs, including roughly twice the memory for the PuTTY configuration window. Faster startup and lower memory are separate claims, despite their frequent marriage in release announcements.
For a developer interested in compatibility machinery, the repository includes an account of failures involving callbacks, thread-local startup, imports, locks and pointer handling. Those are the details that decide whether a recompiled program can actually finish its work. A convincing opening window is only one stage of the exercise.
This article reports the maker’s tests and limitations, without claiming an independent benchmark or successful run of an additional Windows application. The opportunity is to inspect a working translation approach and its defined examples. Replacing an operational Windows environment would require broader compatibility evidence.
The next program can still find an instruction or API the current tests never reached. The project’s own list leaves that work visible.
PuTTY made it through customs.