MetalSharp Windows → Metal

1.1.0macOS 15+Free

Run Windows games on Apple silicon.

One library for your Windows games. MetalSharp translates DirectX and OpenGL into Metal and picks a graphics route for each title. Version 1.1.0 runs two Wine runtimes, a native Arm64 Wine with FEX or an x86_64 Wine under Rosetta 2, and you can switch between them from the header.

Download 1.1.0 Try the renderer
or brew install --cask metalsharp/tap/metalsharp

The download above starts on the x86_64 runtime. Get the Arm64 FEX build to start on FEX. Both run on macOS 15+ and can switch to the other.

MetalSharp 1.1.0 library with God of War Ragnarök featured on the Mullion route, the FEX | x86_64 runtime toggle, a carousel of installed games, and the Stream to phone or tablet control.
  • One librarySteam, Epic, GOG, Battle.net, Ubisoft, Rockstar
  • Two runtimesFEX or x86_64, switch any time
  • Per-game routespicked from tested rules
  • Browser demono install required

A few of the 75+ titles confirmed playable by players and the developer. See the full list

Try the renderer

See the library before you install.

A browser recreation of the MetalSharp 1.1.0 app. Flip through the library, pick a game's route, switch between the FEX and x86_64 runtimes, and open game settings, Settings and Logs. Nothing launches on your Mac.

Controls are easier to read in the full demo. Open full demo
Graphics routes

Two runtimes. Four routes to Metal.

MetalSharp gives each tested game a route from its rule set, and you can save another one in the game's settings. Switch runtimes from the FEX | x86_64 toggle in the header: prefixes are shared, so games and saves come with you. Check your title first.

FEX runtime

MetalSharp-1.1.0-arm64-FEX.dmg

A native Arm64 Wine. x86 games run through FEX, with no Rosetta. Built from MetalSharp Wine 6.0.

Wine
11.20 arm64
macOS
15+ · 32-bit 26.4+
Routes
3

x86_64 runtime

MetalSharp-1.1.0-arm64.dmg

An x86_64 Wine under Rosetta 2, with Apple's D3DMetal. One signed app from MetalSharp Wine 6.0; Rosetta installs itself if it's missing.

Wine
11.17 x86_64
macOS
15+
Routes
4
How a frame reaches the GPU

Pick a route to trace its path.

Graphics routes from Windows APIs to Metal D3DMetal takes Direct3D 12 and 11. Mullion takes Direct3D 12, 11 and 10. VKD3D-Proton with DXVK takes Direct3D 12 down to 8 and goes through MoltenVK. WineMetalGL takes OpenGL. Every route ends in Metal. Windows API Route Vulkan layer Apple GPU Direct3D 12 Direct3D 11 Direct3D 10 Direct3D 9 · 8 OpenGL 1.0–4.6 D3DMetalx86_64 only · GPTK Mulliona DXMT fork VKD3D-Proton + DXVKD3D12 · D3D11–8 WineMetalGLOpenGL on Metal MoltenVK METAL
What each route runs, and where. MetalSharp 1.1.0 ships every route below with MetalSharp Wine 6.0.
Route APIs Runtimes Version
D3D12D3D11D3D10D3D9 · 8OpenGL FEXx86_64
MullionDirect to Metal. A DXMT fork, also built for 32-bit games. metalsharp-2.1f5dad40e
VKD3D-Proton + DXVKThrough Vulkan and MetalSharp's MoltenVK, with Apple's Metal Shader Converter. VKD3D-Proton 5.3DXVK 2.7.1
D3DMetalApple's translator from the Game Porting Toolkit, shipped unmodified. GPTK 4.0 beta 33.0 below macOS 27
WineMetalGLOpenGL 1.0 through 4.6 drawn with Metal, in place of Apple's deprecated OpenGL. 3.9.0

Supported Not on this route

Picked for each game

Tested games get the route that worked in testing; others get one from the DirectX they load. Change it any time from the game's settings.

DLSS on MetalFX

Games that ship DLSS get Super Resolution on every route, Ray Reconstruction on macOS 26 and Frame Generation on macOS 27. MetalFX upscaling at 1.5x, 1.75x or 2x works on every route too.

Fitted to your macOS

Below macOS 27, Mullion uses Metal 3.2 shaders, Direct3D 9 on VKD3D uses shader model 3, and D3DMetal comes from Game Porting Toolkit 3.0.

What it handles

A friendly interface for all of your games.

Easily change artwork, launch options, and settings all within one interface.

  • Stores

    Every library, one shelf.

    Steam installs sync in automatically. Epic, GOG, Battle.net, Ubisoft Connect, Rockstar, and Game Jolt games download and launch from the same place, and each launcher gets its own page.

    • Steam
    • Epic
    • GOG
    • Battle.net
    • Ubisoft Connect
    • Rockstar
    • Game Jolt
  • Launchers

    Every launcher, managed.

    Battle.net games start the way its Play button does, and Rockstar Games Launcher titles run too. Pick the drive a launcher installs to, and uninstall a game or a whole launcher from its menu.

  • Bottles

    Per-game settings.

    Each game gets its own bottle with its own route, msync, and MetalFX. The x86_64 runtime adds controller input and x87 acceleration; the FEX runtime adds a Metal HUD, frame rate limits, and ray tracing.

  • Sharp Library

    Not just games.

    Import standalone Windows programs, installers, and launchers. Installers run in their own bottle.

  • Steam Art

    Your covers, your way.

    Set custom artwork for any game in any of your Steam libraries.

  • Streaming

    Play on the couch.

    Stream to a phone or tablet with Sunshine and Moonlight. MetalSharp installs Sunshine and walks you through pairing.

Under the hood

Built from our own runtimes.

MetalSharp 1.1.0 ships three MetalSharp projects of its own. Each is open source and can be used without MetalSharp.

Start with docs

Find the right answer next.

Short guides for setup and compatibility, plus a full technical reference if you want to go deeper.

  1. 01Install and launchInstall, pick a runtime, play, and fix a game's setup.
  2. 02Check a gameTested titles and the route each one uses.
  3. 03Ubisoft ConnectInstall it, add games on external drives, and launch them.
  4. 04Fix a broken updateRecover when an in-app update fails.
  5. 05ArchitectureThe two runtimes, routes, rule sets, and bottles.
  6. 06Build from sourceBuild, test, package, and sign MetalSharp yourself.
Get MetalSharp

Install when you're ready.

Download MetalSharp 1.1.0 for Apple silicon Macs. Both DMGs come from the same release and differ only in the runtime they start on; switch from the header any time. Already on 1.0.0? The in-app updater brings you to 1.1.0 and keeps your library.

Download 1.1.0 · x86_64 Download 1.1.0 · Arm64 FEX

Both run MetalSharp Wine 6.0 on macOS 15+: x86_64 Wine 11.17 under Rosetta 2, or native Arm64 Wine 11.20 with FEX (32-bit x86 games on FEX need macOS 26.4+). Read the install guide.

brew brew install --cask metalsharp/tap/metalsharp
Version
1.1.0
Chip
M1 – M5
x86_64
macOS 15+
Arm64 FEX
macOS 15+
Disk
~12 GB
Price
Free
Before you install

Questions before you start.

Which DMG should I download?

Either one: they differ only in the runtime they start on. The x86_64 runtime is an x86_64 Wine under Rosetta 2 with Apple's D3DMetal; the FEX runtime is MetalSharp Wine's native Arm64 Wine, which runs x86 games with FEX instead of Rosetta. Both run on macOS 15 and later. Switch any time from the FEX | x86_64 toggle in the header: prefixes are shared, so your games and saves come with you.

What can I do in the browser demo?

Browse the library and each launcher's page, choose a graphics route, switch between the FEX and x86_64 runtimes, change a game's settings, try the themes, and open Settings, the collection and Logs. It's a recreation of the MetalSharp 1.1.0 app running in your browser: it doesn't install MetalSharp or launch any games.

How do I choose a graphics route?

Usually you don't have to: tested games use the route in their build's rule set, and other games get one from their DirectX imports. If a game doesn't run, pick another route from its bottle dropdown, and check the supported games list for what worked for others.

Is D3DMetal included in the download?

On the x86_64 runtime, yes: it carries Apple's D3DMetal unmodified, from Game Porting Toolkit 4.0 beta 3 on macOS 27 and 3.0 below. The FEX runtime doesn't use D3DMetal; those games run on Mullion or VKD3D-Proton instead. The architecture guide explains both.

Do games with anti-cheat work?

Not if they use kernel-level anti-cheat. That can't run under Wine, and MetalSharp flags those titles in the library.

Where should I report a problem?

Open a GitHub issue for a bug you can reproduce. Use Discussions or the Discord for questions and setup help.