Mac.apk

The idea

Mac.apk runs Android apps directly on Apple Silicon Macs at full native speed.

Not an emulator. Not a virtual machine. No Linux running underneath, no Docker, no Rosetta, no Wine. Android apps launch the same way a Mac app does, render with the Mac's own graphics stack, and use the CPU at its full native speed.

The result is an Android app that feels and performs like a Mac app, because that's what it has become.

What makes it different

Why it matters

Current status

Mac.apk is in public alpha. The first public release, v1.0.1666, shipped on October 2, 2026; the latest, v1.0.1732, shipped on October 6, 2026, and it improves with every build. Some apps run beautifully, some run partially, and some do not run yet.

Of 65 apps tested so far, 52 work, 10 partly work, and 3 do not run yet. See the compatibility list for the details, and the release notes for known issues.

Part of Mac.apk is open source: dex2jvm, the converter that turns Android app code into Java bytecode.

The project is open to acquisition, licensing, or strategic partnership.

Use at your own discretion

Mac.apk runs unmodified Android APKs as native code on your Mac. By installing or using it, you accept that:

• You are responsible for the Android apps you choose to load.
• Voltare cannot test, audit, or vouch for any third-party APK, and we make no guarantee about the behavior of code we did not write.
• Mac.apk is provided "as is", with no warranty of any kind, express or implied.
• Voltare is not liable for damages, data loss, malware, security incidents, copyright disputes, or any other consequence of code that runs through Mac.apk.
• Some APKs may behave incorrectly, crash, or trigger unexpected system behavior. This is the nature of running software outside its original target platform.
• You are responsible for only running APKs that you have the legal right to use.
• An Android app running under Mac.apk runs as ordinary native code with your macOS user account's permissions. There is no phone-style app sandbox around it, so only install APKs you trust, from a source you trust.

If you do not agree, do not install Mac.apk. The full terms are in the End User License Agreement.

License

Mac.apk is free for personal, non-commercial use. For commercial use, white-labeling, bundling, or distribution agreements, please email Kaleb@voltare.us.

Download

Free for personal use. Requires an Apple Silicon Mac (M1 or newer) running macOS 26.4 (Tahoe) or later. macOS 26.4 is a hard requirement: native Android code depends on a platform capability Apple introduced in that release. Intel Macs are not supported.

Check the box above to enable the download. The button opens the latest release on GitHub; download the disk image and drag Mac.apk into Applications. Setup steps are in the installation guide.

For developers and publishers

Mac.apk runs your Android app on macOS, but two things that work on Android do not work here: advertising SDKs and in-app purchases. This is by design, not an oversight, and we want to explain why.

Ad networks (Google AdMob, Unity Ads, AppLovin, IronSource, Vungle, and others) require apps to be distributed through approved channels and to run on attested Android devices. Their terms of service prohibit ad serving in modified runtimes, and their fraud-detection systems are aggressive about flagging traffic that doesn't match a real Android device fingerprint. Attempting to serve real ads through Mac.apk would risk getting your AdMob account terminated for facilitating fraud, which would harm you, not help you. So Mac.apk itself serves, counts and fakes no ads: no impression, click, or paid event is ever fabricated. Mac.apk's own stand-in for Google's ad SDK, used when an app does not ship that SDK itself, answers every ad request with no fill, exactly as a real device with no reachable ad configuration does. An ad SDK that an app ships inside its own code runs as part of that app, though, so some free games do show their full-screen ads on Mac.apk. Apps keep running either way.

In-app purchases are blocked for the same structural reasons. Google Play Billing requires a connection to Google Play Services and an attested device, neither of which Mac.apk provides. We stub the billing SDK so apps don't crash on init, but purchase flows will fail gracefully rather than complete. Users cannot buy anything through Mac.apk, and you receive no revenue from Mac.apk users through the standard Android monetization paths.

We recognize this means Mac.apk users currently play your game for free. We don't want this to be the long-term answer. If your app is running on Mac.apk and you'd like to be compensated for it, we're genuinely interested in working out a partnership. Possible structures include:

• A licensed Mac distribution where users purchase a one-time unlock through a payment flow you control, with you keeping the majority of revenue.
• A subscription or storefront model where Mac.apk acts as a sanctioned distribution channel for your catalog on Mac.
• A revenue share on a developer-specific in-app currency or premium content unlock.
• Whatever structure makes sense for your business. We're flexible.

We'd rather build a small number of real publisher relationships than run an unlicensed pile of your games. If you publish an Android app that runs on Mac.apk (whether it's in our compatibility list or you've tested it yourself), please reach out to Kaleb@voltare.us. Even if a partnership doesn't materialize, we want to know which developers are paying attention.

If you'd prefer your app not run on Mac.apk, also reach out and we'll add it to a runtime block list. We'd rather honor that request than fight about it.