Can an M1 Mac run WoW Forever? Check Blizzard’s minimum

M1 with 16 GB: the direct answer

Blizzard’s Forever store page lists Apple M2 as the minimum Mac processor, with 8 GB RAM, macOS 12 and 128 GB of free SSD space. The recommended Mac uses an M4 and 16 GB RAM. An M1 with 16 GB clears the memory line but still falls below the named processor minimum. Do not read “16 GB” as an M1 compatibility guarantee.

This is a published requirement, not a claim that the game can never launch on an M1. A player report about an M1 Pro beta session describes low frame rates, while replies describe different results. Those anecdotes cannot predict your frame rate or stability.

Check your exact Mac before installing

Open the Apple menu and choose About This Mac. Apple says the Chip field identifies an Apple silicon model. Compare that chip, macOS version, memory and free SSD space with Blizzard’s Mac tab rather than using the Windows GPU list.

1. 01

   Read the chip and memory

   Apple menu → About This Mac. Note whether the chip says M1, M2 or later and check installed memory.

2. 02

   Check Blizzard’s Mac tab

   The minimum shown on 28 September is M2, 8 GB RAM, macOS 12 and 128 GB free on an SSD; the recommended chip is M4.

Beta freeze reports from M1 to M5

From September 17, a Blizzard Mac Technical Support thread collected reports of the whole Mac freezing on Enter World, sometimes until a forced shutdown. Posters list M1, M1 Pro, M4, M4 Pro, M5, M5 Pro and M5 Max machines on macOS 15 and 26. Several later posts say build 1.60.1.69977 (September 23) stopped the crash for them; others still reported low frame rates or broken shadows. These are player reports, not a Blizzard count of affected Macs.

1. 01

   Lower Secondary Lighting before entering

   At character select, open Options → Graphics, set Secondary Lighting to Fair, then enter the world. Several players report this avoided the freeze.

2. 02

   If the Mac freezes before you can change it

   Quit the game and open Config.wtf in the WTF folder of your install (the beta used _classic_beta_). The player-documented version sets giQuality "1", RAIDgiQuality "1", graphicsQuality "2" and RAIDgraphicsQuality "2". In game, /dump GetCVar("giQuality") should return 1.

3. 03

   Match raid graphics settings

   On October 3, a Blizzard developer said Secondary Lighting was reading the raid setting outside raids and vice versa; his workaround was to enable raid settings and match them to the normal ones. He said build 70245 (October 6) fixed this bug.

What Blizzard fixed, and what was still open

In the Mac graphics thread, the same developer reported a shadow fix in the October 8 build, Stormwind water fixed in build 70338 around October 10, and a possible fix for the green/magenta tint in build 70374 on October 13. On October 21 he wrote that the next round of fixes would not deploy until Thursday, after the server stress test. We have not found a Blizzard confirmation that the tint is fixed, and the beta closed on October 23.

He also tied one camera-related crash to macOS 12 and 13, inside the Metal driver, and suggested macOS 14 or later may prevent it: a hypothesis, not a change to the requirements. None of this raises the M1 to Blizzard’s minimum. If the game freezes after the November 4 launch, update the client, try Secondary Lighting at Fair and report your chip, macOS version, build and exact symptom to Blizzard support.

What changed in the September 24 beta build?

Blizzard says the September 24 build fixed a water-display issue and other Mac visual artifacts, plus a memory leak affecting some players. That note does not change the M2 minimum or promise that every M1 crash is fixed.