Apple Intelligence File Renaming: What It Can (and Can't) Do

Why People Assume Apple Intelligence Renames Files

It is a reasonable thing to expect. Apple Intelligence can already rewrite a paragraph in Mail, summarize a long email thread, and generate an image from a description, so "read this scan and give it a sensible name" sounds like it should already exist somewhere in System Settings. It does not, and searching for it in Finder's preferences will not turn anything up.

What actually exists is one level down from that: a model you can call, not a feature that calls itself. This guide covers what that model is, how to point it at your files yourself using Shortcuts, and the specific places that approach breaks so you are not left guessing why forty files went in and only thirty came out renamed.

What You Need Before Any of This Works

Apple Intelligence is gated by hardware, not just software. You need an Apple Silicon Mac, M1 or later; Intel Macs cannot run it at all, no matter how current the OS is. On top of that, you need macOS 26 Tahoe or later, roughly 7GB of free storage for the on-device model files, and Apple Intelligence switched on under System Settings > Apple Intelligence & Siri. Full functionality is currently most reliable with the system language set to English.

The "Use Model" Action, and Its Three Sources

This single Shortcuts action is the entire bridge between Apple Intelligence and anything you build yourself, file renaming included. It gives you a choice of three places to actually run the request.

How to Build Your Own Renaming Shortcut

None of this requires writing code, only assembling five actions in the Shortcuts app in the right order. It takes about ten minutes the first time.

Where the DIY Version Breaks Down

The shortcut above genuinely works, and for a small, occasional batch it is a reasonable free option. It also has real limits worth knowing before you point it at anything you care about.

• Scanned documents with no text layer get skipped, not warned about. A conditional check that tests for extracted text will treat an empty result as "nothing to do" rather than "something went wrong," so a folder of photographed receipts or fax-quality scans can go through a batch run and come out mostly untouched with no error message telling you why.
• On-device image descriptions are hit or miss. The on-device model is compact by design, built for fast, private text tasks rather than richly describing a busy photo. It will usually produce something, but "something" is not always a useful filename.
• The output format needs constant babysitting. Models tend to add filler ("Sure, here's a name:") unless the prompt aggressively rules it out, and even a well-worded prompt occasionally slips. Every version of this shortcut in circulation includes some form of cleanup step for exactly this reason.
• There is no preview and no undo. Shortcuts renames the file the moment the action runs. If a name comes out wrong on file 12 of 40, you find out by looking at file 12 afterward, not before, and fixing it means renaming it back by hand.
• The ChatGPT option adds a dependency you don't control. It works without an account for casual use, but you are now relying on OpenAI's uptime and rate limits inside what was supposed to be a simple Mac automation, and your file content is going to a company other than Apple.

DIY Shortcut vs. a Dedicated Renaming App

Both routes can end up using the same underlying idea, a language model reading a file and proposing a name. Where they differ is everything wrapped around that core step.

When the Shortcut Is Enough, and When It Isn't

If you rename files rarely, want to keep the whole thing free, and don't mind spending ten minutes building it once, the Shortcuts route is a genuinely good option. It is also a reasonable way to learn what "Use Model" can do before deciding whether you want more than that.

It stops being enough once renaming becomes a routine chore rather than an occasional one, once the files involved are financial or otherwise consequential enough that a silent skip or a wrong guess is actually costly, or once you find yourself wanting a folder watched automatically instead of running a shortcut by hand every time. That is the gap a purpose-built tool is meant to close: the same idea, a model reading your files and proposing names, but with a batch preview before anything changes and a history you can roll back afterward. Files Magic AI's Magic Rename works this way, using Apple Intelligence, a built-in local model, or an optional Rename LLM depending on what your Mac supports, with everything processed on-device.

Sources & Further Reading

Frequently Asked Questions

The Bottom Line

Apple Intelligence gives you a real, capable language model to work with, not a finished renaming feature. Shortcuts lets you point that model at your files yourself, and it genuinely works for light, occasional use once you know to save the file extension separately and give the model a tightly worded prompt. Where it runs out of road is scale and consequence: no preview, no undo, and scanned documents that fail without telling you. That gap between "a model you can call" and "a tool that previews, applies, and lets you undo a rename" is exactly what a dedicated app like Magic Rename is built to close, using the same Apple Intelligence option under the hood when your Mac supports it.

For the fuller picture of this category, including cloud and BYOK renamers beyond just Apple's own model, see how AI file renaming works on Mac. For hands-on workflows built on Magic Rename specifically, read how to rename invoices, scanned receipts, and OCR-scanned documents. For naming conventions once your files are readable again, see our file naming conventions guide, or browse every 1dot.ai guide.