What you need to know
- The latest developer beta of macOS Monterey contains a reference to "High Power Mode."
- The new mode would allow Macs to run at peak performance regardless of being plugged in.
The latest developer beta of macOS Monterey makes reference to a "High Power Mode."
As reported by 9to5Mac, code found within. macOS Monterey beta 8 contains a reference to the new feature, which would act as the opposite to Low Power Mode.
A "High Power Mode" could let MacBook Air and MacBook Pro users clock the CPU and GPU at the highest performance possible regardless of the hit to battery life. It would be a helpful feature for those who need to eke out even more performance for demanding tasks.
It would be interesting to see how this kind of "Pro Mode" would work across Apple's Mac lineup, especially since the M1 MacBook Air removed fans from the Mac completely. The MacBook Pro models are currently the only portable Macs to feature fans.
It could also be a feature reserved for Apple's rumored 14-inch and 16-inch MacBook Pro refreshes which are expected to be announced at an October event. The new Macs are anticipated to feature the M1X processor, a souped-up version of the M1 chip that was released last year.
Get the best of iMore in in your inbox, every day!
Joe Wituschek is a Contributor at iMore. With over ten years in the technology industry, one of them being at Apple, Joe now covers the company for the website. In addition to covering breaking news, Joe also writes editorials and reviews for a range of products. He fell in love with Apple products when he got an iPod nano for Christmas almost twenty years ago. Despite being considered a "heavy" user, he has always preferred the consumer-focused products like the MacBook Air, iPad mini, and iPhone 13 mini. He will fight to the death to keep a mini iPhone in the lineup. In his free time, Joe enjoys video games, movies, photography, running, and basically everything outdoors.
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.