Photo and video exports don't pay for an M5 Max Mac Studio. Matt Talks Tech tallied two weeks of its own workloads. The machine earns itself back in about 21 months only when Blender time is billed at a 3D artist's hourly rate and a local AI agent stands in for two hours a week of a human assistant.
Time saved over a year of work, per the video
| Lightroom AI Denoise, 250 batches | 17.7 hours against an M4 Max |
|---|---|
| Lightroom export, 250 batches of 500 RAW files | 2.3 hours against an M4 Max |
| Blender, 1,000 renders | 120.5 hours against an M1 Max |
| Payback, M5 Max with 128GB | About 21 months, all workloads combined |
Where the M5 Max pulls away
- Blender. Its median benchmark score lands at about 8.2 times the M1 Max and close to double the M3 Max, which the video credits to the AI accelerators in the M5 Max's GPU cores.
- AI Denoise. One batch of Sony A7 IV RAW files took 3 minutes 55 seconds against 8 minutes 10 seconds on an M4 Max.
- Local image generation. Flux 2 Klein 4B in Draw Things makes an image in about a second, all on the Mac.
- Local agents. Models in LM Studio run with Wi-Fi off, tidying a cluttered desktop every hour and finding a file from a plain-English description.
Where it barely shows
- Final Cut Pro. An H.264 export of a six-and-a-half-minute project stays ahead of the M4 Max by a smaller margin than in Blender.
- Lightroom export. A 500-file RAW batch takes 47 seconds against 1 minute 20 on the M4 Max, 33 seconds saved.
- Language models. Answers come back only seconds sooner than on older Max chips; the gap widens against Pro and base chips with fewer GPU cores.
The channel's own verdict on photo and video work is blunt:
I still think just a standard Pro or even the standard M chip is good enough for most people's scenarios out there.
The payback assumes the top M5 Max with 128GB of memory, the ceiling before the M5 Ultra. It holds for a freelancer who bills renders by the hour; iPhoners who edit photos for fun should start from the M5 Pro the video itself points to.
