Microsoft delivered a blockbuster stat this week: roughly 90% of the time users spend on Arm-based Windows PCs now happens inside apps compiled natively for the Arm architecture. The metric, published in a corporate blog post by customer experience engineering VP Mike Adams, flips the long-running script that Windows on Arm is a compatibility minefield. For the first time, the platform can credibly tell mainstream buyers that the apps they live in—browsers, office suites, creative tools—will run at full speed, not through a sluggish translation layer.

The figure is usage-weighted, not a raw count of available titles. Microsoft focused on the apps that eat the most minutes: Chrome, Edge, Microsoft Office, Adobe Photoshop, Premiere Pro, DaVinci Resolve, Blender, Spotify, WhatsApp, Telegram, and dozens more. That matters far more than a giant catalog of niche utilities, because it directly predicts the experience you’ll actually have when you open an Arm laptop.

The Milestone Microsoft Just Dropped

On March 27, 2025, Mike Adams laid out the numbers in a post that felt part victory lap, part buyer’s guide. “The Arm app ecosystem continues to expand, with native Arm versions available for apps representing 90% of total user minutes,” he wrote, “thus providing efficient, high-performance experiences across the scenarios that matter most to our customers.”

The company pointed to concrete examples across every major category. Browsers: Google Chrome (finally native since early 2024) and Microsoft Edge. Productivity: the full Office suite, LibreOffice, 7-Zip, Dropbox, Todoist, Trello. Creative: Adobe’s flagship apps—Photoshop, Premiere Pro, Audition, and more—plus DaVinci Resolve, Blender, CapCut, Djay Pro, Paint.NET, Camtasia. Communication: WhatsApp, Slack (via native Arm builds), Telegram, Apple Music, Apple TV. Endpoint protection: several major security vendors have shipped native agents.

That list covers the vast majority of what a student, office worker, or content creator does in a day. And because these apps are native Arm64 binaries, the CPU doesn’t burn cycles translating x86 instructions; the result is snappier responsiveness and, crucially, longer battery life.

What’s Actually Running Natively Today

To be clear, “native” can mean a few different things in 2025. Some apps are pure Arm64 builds, compiled from source for ARMv8/ARMv9. Others use Arm64EC, a hybrid model that lets developers ship a mostly native process while still calling a few x64 components for compatibility. Both deliver the core benefit: most of the execution stays on Arm-native code paths, avoiding the overhead of full emulation.

Microsoft and its OEM partners have also smoothed the path for independent software vendors. Visual Studio and CMake now produce Arm64 binaries with minimal fuss. MSIX packaging supports Arm-native distribution in the Microsoft Store and through enterprise channels. And frameworks like Electron, Flutter, and .NET MAUI—which underpin many modern apps—have matured their Arm toolchains, so recompiling a cross-platform app requires less heavy lifting than it did even two years ago.

The result is that the apps you’re most likely to install today are already native. For a quick spot check, here’s a representative sample of what runs natively:

  • Browsers – Google Chrome, Microsoft Edge, Firefox (Arm64 version available).
  • Productivity – Microsoft Office, LibreOffice, Notepad++, Todoist, Trello.
  • Creative & Media – Adobe Photoshop, Premiere Pro, DaVinci Resolve, Blender, Paint.NET, CapCut, Camtasia, Audacity, Luminar Neo.
  • Communication – WhatsApp, Telegram, Slack, Discord (native Arm build in testing), Zoom (native Arm preview).
  • Cloud & Utilities – Dropbox (Arm64 client), Google Drive, 7-Zip, Figma, Apple Music, Apple TV.
  • Developer Tools – Visual Studio, VS Code, Python, Node.js, WSL, Docker (through WSL2).

This is not an exhaustive list; Microsoft’s blog name-checks dozens more. The point is that the “long tail” of apps you rarely open is now the only real island of emulation—and Prism, the built-in x86/x64 emulation engine, has gotten good enough that many of those simpler apps run transparently.

Why This Changes the Buying Equation

For the everyday user—someone who lives in a browser, streams media, edits documents, and occasionally touches up a photo—an Arm PC is now a no-brainer if you value battery longevity and cool, silent operation. You’ll rarely, if ever, notice the difference between an Arm-native app and the same app on an Intel or AMD machine.

Home users gain the most. A Copilot+ laptop like a Surface Pro 11 or a Samsung Galaxy Book4 Edge will run all the key apps natively, often with better battery life than comparable x86 ultrabooks. Streaming 4K video, scrolling through social feeds, or joining a video call all happen on Arm-optimized pathways that sip power. The days of “it works, but feels a little off” are largely over for this group.

Professionals and creators need to check their toolchains, but the picture is far brighter than a year ago. Adobe’s core apps are now native, though some plugins may still be x86 and run under emulation. DaVinci Resolve’s native Arm build is performant enough for many editing workflows, but high-end color grading or GPU-accelerated effects may still favor a discrete GPU on an x86 machine. For coders, Visual Studio and VS Code run natively, and WSL2 gives you a full Arm Linux environment—great for cloud-native development, but local x86 containers remain a hiccup.

Gamers and anti-cheat purgatory remain the clearest caution. While Prism emulation handles many indie and older titles, most modern multiplayer games rely on kernel-level anti-cheat drivers that haven’t been ported to Arm. Titles like Valorant, Call of Duty, or Fortnite at competitive settings may not run at all, or run with significant performance gaps. Microsoft is working with anti-cheat vendors, but until they publicly commit, a Windows on Arm device cannot be your primary gaming rig.

IT administrators evaluating Arm laptops for a fleet should prioritize device models with strong OEM firmware support. Kernel drivers for printers, scanners, VPN clients, and DLP agents can be the hidden deal-breaker. Test your golden image on a pilot device, including any legacy 32-bit helpers, and confirm that your endpoint protection and management tools have native Arm agents. Many now do—CrowdStrike, SentinelOne, and Microsoft Defender run native—but check.

The Road to 90%: How We Got Here

Windows on Arm’s first iteration in 2017 (with the Snapdragon 835) was an expensive science experiment. A thin app catalog and x86-only emulation that was painfully slow meant few buyers, which starved the developer ecosystem. Microsoft’s second attempt, the Surface Pro X in 2019, brought a custom SQ1 chip and x64 emulation later, but app support stayed sparse and the experience remained uneven.

Everything shifted in mid-2024. Microsoft rebranded the effort around Copilot+ PCs, a new class of devices anchored by Qualcomm’s Snapdragon X Elite and X Plus processors. These chips delivered not just competitive CPU performance but an on-device neural processing unit (NPU) capable of 45 TOPS, enabling features like Recall and Windows Studio Effects. More importantly, the launch was accompanied by a massive software push. Microsoft’s own apps were already native, but the company worked directly with high-profile ISVs—Google, Adobe, Spotify, WhatsApp—to get Arm builds into production before the hardware shipped.

Prism, the new emulation engine, was rewritten to support the full x86-64 instruction set, including AVX, AVX2, BMI, and FMA. That unblocked hundreds of apps that previously crashed on startup because they expected those instructions. It didn’t make emulation fast for compute-heavy workloads, but it turned a hard “this app won’t open” into “this app opens but isn’t as fast as you’d like.” That bought time for developers to compile native versions.

The 90% figure didn’t materialize overnight. It reflects a cumulative shift: as Chrome, Edge, Office, and Adobe apps went native, the average user’s daily timeline automatically skewed toward Arm code. Each new native release closed the gap. By early 2025, the combination of native browsers, office suites, and media apps covered the overwhelming majority of consumer minutes.

What to Do Before Buying an Arm PC

If the 90% stat has you eyeing a sleek new Copilot+ laptop, do three things before pulling the trigger:

  1. Inventory your must-have apps. Make a list of the software you open almost every day. Check Microsoft’s Windows on Arm compatibility page or the developer’s own site for a native Arm version. If it’s not native, search community forums for real-world Prism performance reports.
  2. Test on the hardware if you can. For enterprise buyers, pilot a device with your actual workflows, including any plug-ins, macros, or peripheral devices. Retail users: buy from a store with a generous return policy and spend a week hammering your daily routine.
  3. Keep the system fully updated. Windows Update and OEM firmware updates have delivered measurable Prism compatibility improvements and power-efficiency gains. Don’t defer the big feature updates; they frequently ship Arm-specific fixes.
  4. Validate gaming expectations. If you play competitive online titles, assume they won’t work until the publisher and anti-cheat vendor explicitly say so. For single-player and DRM-free games, check protondb-style community databases that track Arm emulation results.
  5. Consider your peripheral stack. Printers, scanners, external DACs, and specialized USB hardware often need Arm64 drivers. While Windows Update will fetch many automatically, niche gear might not have a driver at all. A quick visit to the manufacturer’s support page can save a headache.

What’s Next for Windows on Arm

Microsoft’s messaging suggests the platform is now on a sustained trajectory. The upcoming Snapdragon X2 chips (rumored, but not yet officially named or dated) are expected to raise CPU and NPU performance further, making Arm a credible choice for heavier creative and AI workloads. At the same time, Intel and AMD are readying their own Copilot+ silicon with NPUs that meet Microsoft’s 40+ TOPS requirement, so the NPU-driven features won’t be Arm-exclusive for long. The real differentiation will stay where it has always been: high native app performance paired with battery life that can realistically last a full workday.

Prism emulation will keep improving—Microsoft quietly pushes AVX/SSE coverage updates through the engine—but the industry incentives now align to make emulation a backup, not the main event. As anti-cheat vendors and hardware partners eventually certify Arm builds, even the gaming asterisk may shrink. For now, the 90% user-minutes figure is both an achievement and a promise: Windows on Arm has graduated from a curiosity to a platform you can confidently recommend to most people, so long as you know the few scenarios where it still needs a closer look.