i tried automating my screenshots with apple shortcuts — here's why it wasn't enough.

I had 847 screenshots in my Desktop folder. Every single one named some variation of "Screenshot 2026-02-09 at 3.42.17 PM.png". This is the digital equivalent of having a drawer full of unlabeled photos from the 1970s.

I'm not alone. If you take screenshots on macOS regularly, you know the cycle. You capture something important. You tell yourself you'll organize it later. You never do. Three months later, you're scrolling through hundreds of identically-named files trying to find that one Slack conversation about the database schema.

Then Apple released macOS Tahoe with Apple Intelligence built into Shortcuts. The promise: your Mac can now automatically rename screenshots with AI-generated descriptive names. No apps, no subscriptions, just built-in automation.

I decided to try it. This is what happened.

attempt 1: apple shortcuts + apple intelligence

The setup is surprisingly straightforward. macOS Tahoe added folder automation triggers to Shortcuts, which means you can create a Shortcut that automatically runs whenever a new file appears in a specific folder.

Here's what I built:

1. //Create a new Shortcut in the Shortcuts app
2. //Set the trigger to "When files are added to" → select your Screenshots folder
3. //Add the action "Get file from input"
4. //Add "Generate description of image using Apple Intelligence"
5. //Add "Rename file" using the generated description

Five actions. Three minutes to set up. I saved it, took a test screenshot of my Slack window, and watched.

About four seconds later, Finder refreshed. "Screenshot 2026-02-09 at 2.14.33 PM.png" had become "Slack-conversation-about-API-redesign.png".

I took another screenshot. This time, a code editor showing a Python traceback. "VS-Code-Python-error-module-not-found.png".

One more. A browser tab with a Figma mockup. "Safari-Figma-design-mobile-dashboard-dark-theme.png".

I'm not going to lie, this felt like magic. My screenshots were naming themselves. Descriptively. Accurately. For free. No third-party app, no subscription, just a five-minute Shortcuts workflow leveraging Apple's own on-device AI models.

I went back through my folder and let the Shortcut process about 50 old screenshots. It worked on all of them. Login screens became "Chrome-login-form-email-password.png". Terminal windows became "Terminal-git-commit-command-output.png". Even screenshots of random tweets got renamed to something like "Twitter-post-about-React-Server-Components.png".

For the first time in years, I could actually scan my Screenshots folder and have a decent idea of what each file contained without opening it.

This was it. Problem solved. Right?

attempt 2: adding hazel to the mix

After a week of auto-renaming bliss, I realized I still had a problem. My Screenshots folder now contained 900+ files with descriptive names, but it was still just one giant folder. Finding anything required scrolling through hundreds of filenames.

I'd heard about Hazel for years. It's a Mac automation tool that watches folders and runs rules when files appear. People love it. The kind of love usually reserved for text editors and programming languages.

I installed the trial and set up three rules:

Rule 1: Date-based archiving Move screenshots older than two weeks into date-based subfolders: "February 2026", "January 2026", etc. This keeps the main folder manageable while preserving older captures in a sensible structure.

Rule 2: Project-based sorting If the filename contains certain keywords ("figma", "design", "mockup"), move to ~/Screenshots/Design. If it contains "slack", "discord", or "teams", move to ~/Screenshots/Conversations. Terminal, VS Code, and Xcode screenshots go to ~/Screenshots/Code.

Rule 3: Cleanup Delete screenshots older than six months that haven't been opened or modified. This one felt risky, but I figured if I haven't looked at a screenshot in half a year, I probably never will.

Combined with the Shortcuts auto-rename, this was beautiful. I was now capturing screenshots that named themselves and sorted themselves into project folders automatically. The whole system ran in the background. I didn't have to think about it.

I showed this setup to a designer friend. She immediately built the same workflow on her machine. We both felt like we'd discovered some secret Mac power user technique that should be talked about more.

For two weeks, this felt like the complete solution.

the five limitations nobody talks about

Then reality started showing cracks in the system.

1. AI renaming is descriptive, not contextual

Apple Intelligence is excellent at describing what it sees in an image. It can identify that a screenshot shows "Slack conversation between three people about API endpoints" with impressive accuracy.

But it has no idea why you took that screenshot.

That particular Slack conversation was the one where we decided to drop Redis from the architecture and go with Postgres for everything. That decision changed the entire backend implementation plan. It's a screenshot I've referenced five times since taking it.

The AI-generated filename is "Slack-conversation-three-people-about-API.png". Which is technically accurate. But when I search for it later, I'm searching for "redis postgres decision" or "architecture change conversation". The visual description doesn't match my mental model of what the screenshot represents.

This happens constantly. A screenshot of a Figma mockup becomes "Figma-mobile-interface-dark-theme.png". What I needed was "Dashboard redesign final version approved by Sarah". A terminal error becomes "Terminal-npm-build-error-red-text.png" when what I actually need to remember is "the CORS issue that broke production".

The AI can see. It can describe. But it can't read your mind about why this particular screenshot mattered enough to capture.

2. no way to add personal context at capture time

This is the most frustrating limitation. I know what the screenshot means the moment I take it. That knowledge is fresh, immediate, and accurate. But there's no mechanism in the Shortcuts workflow to pause and let me add a note.

I could manually add a Finder comment after the fact. Or rename the file again to include my context. But now we're back to manual work. The whole point of automation was to eliminate manual work.

Shortcuts can show notification prompts, but having a modal pop up every single time I take a screenshot would be incredibly disruptive. Especially during rapid capture sessions where I'm taking 5-10 screenshots in two minutes while debugging something.

What I needed was a lightweight way to optionally add context without breaking my flow. Voice note. Quick text field. Something. Neither Shortcuts nor Hazel provides this.

The automation handles the mechanics but ignores the most valuable piece of information: the human intent behind the capture.

3. renamed files are still just files in finder

Let's say the system works perfectly. Every screenshot is accurately renamed. Everything is sorted into sensible folders by date and project. Your Screenshots directory is a masterpiece of organization.

You still have to use Finder to browse them.

Which means:

• //Navigate to ~/Screenshots/February 2026/Code
• //Scan through 40 filenames
• //Click to preview in Quick Look if the name isn't enough
• //Open in default image viewer if you need to zoom
• //Copy path if you want to reference it elsewhere

There's no visual gallery view that makes sense for screenshots. Finder's icon view shows tiny thumbnails. List view shows filenames but no previews. Column view is better but still clunky for browsing images quickly.

More importantly, there's no semantic search. You can't search for "the screenshot about database migrations" and get relevant results. You're still searching filenames, which only contain whatever the AI happened to describe plus whatever folder rules Hazel applied.

A well-organized file system is still a file system. It's organized, but it's not smart.

4. shortcuts triggers aren't built for high-volume workflows

The folder automation trigger in Shortcuts is essentially polling. It checks the folder periodically for new files. When it finds them, it runs the workflow.

During normal use, this works fine. You take a screenshot every few minutes, it processes quickly, everything stays in sync.

But when you take screenshots rapidly, things get weird.

I was triaging a bug that required comparing five different error states. I took six screenshots in about 45 seconds. The Shortcut queued them up and started processing. The first three renamed fine. The fourth one seemed to hang. By the time I checked back two minutes later, the last two hadn't been renamed at all.

I manually triggered the Shortcut. It processed them. Everything was fine. But the automation had silently failed for two of the six files.

This happens occasionally with other scenarios too. If the AI analysis takes longer than usual (maybe the screenshot is complex, or your Mac is under heavy load), subsequent screenshots can pile up. Sometimes they all process eventually. Sometimes one or two get skipped.

Shortcuts doesn't have robust error handling or logging. When something fails, it just... doesn't happen. There's no notification. No retry mechanism. No way to see which files didn't process.

For casual use, this is fine. For someone taking 20+ screenshots per day across multiple projects, this unreliability becomes a real problem.

5. none of this connects screenshots to your projects

Here's the scenario that broke the system for me.

I work on three client projects simultaneously. Let's call them Project A (a React dashboard), Project B (a Python API migration), and Project C (iOS app design review).

On a typical Tuesday, I take:

• //8 screenshots from Project A (Figma mockups, Slack feedback, browser DevTools)
• //6 screenshots from Project B (terminal errors, API documentation, database diagrams)
• //5 screenshots from Project C (iPhone simulator, Sketch files, App Store guidelines)

All 19 screenshots land in the same folder. The Shortcuts workflow renames them based on visual content. Hazel tries to sort them by keyword.

But the keywords overlap. "API documentation screenshot" could be Project B or reference docs for Project A. "Slack conversation about timeline" could be any of the three projects. "Terminal git output" happens in both A and B.

Hazel's date-based rules don't help because I'm working on all three projects on the same day. Keyword rules are fragile because technical screenshots have overlapping vocabulary.

What I actually needed was project-aware capture. Some way to tag or associate screenshots with the project I was working on when I took them. Some way to say "the next 5 screenshots are all Project B related" without manually sorting them afterward.

Neither Shortcuts nor Hazel can do this. They're file-based automation tools. They see files appear in folders and run rules. They have no concept of context switching or project boundaries.

So I ended up doing what I always did before: manually reviewing screenshots every few days and moving them into project folders. Which defeats the entire purpose of automation.

what a complete screenshot workflow actually needs

After three weeks of trying to make Shortcuts + Hazel work, I had a clear picture of what was missing.

A complete screenshot workflow needs:

Instant detection when a screenshot is taken. Not folder polling that checks every few seconds. Real filesystem events that trigger immediately. This prevents the queuing issues and ensures every screenshot gets processed, even during rapid capture.

Lightweight context capture that doesn't break flow. A small popup or overlay where you can quickly type a note or speak a voice memo about why this screenshot matters. Completely optional, for when you want it, dismissed with a single key when you don't.

AI analysis that understands content, not just describes visuals. Recognize text in the screenshot (OCR). Understand code snippets, error messages, conversation threads. Connect the visual description with the semantic meaning of what's actually in the image.

A searchable gallery interface with thumbnails, not Finder file lists. Something purpose-built for browsing visual content. Zoom, filter by date or project, search by content. See ten screenshots at once instead of one filename at a time.

Project awareness that understands you work on multiple things. Tag screenshots by project or client. Group related captures together. Search within a project scope. Let me switch contexts and see only the screenshots relevant to what I'm working on right now.

Automatic background processing for everything else. File organization, metadata extraction, duplicate detection, integrity checks. All the housekeeping that Hazel tries to do, but with awareness of the screenshot-specific use case.

And critically, all of this needs to be fast. Taking a screenshot is a split-second action. Any friction added to the capture process makes the whole system feel heavyweight.

there's an app for that (literally)

About a week after I gave up on my Shortcuts + Hazel setup, I found ohsnp.

It's a menu bar app that does exactly what I was trying to build, but as a purpose-built system instead of duct-taped automation rules.

Here's how it actually works:

FSEvents watcher monitors your Screenshots folder using macOS filesystem events. The moment a screenshot is created, ohsnp knows about it. No polling. No delays. No files getting skipped during rapid capture.

Five-second popup appears in the corner of your screen. You can type a quick note, press Enter to record a voice memo, or press Escape to skip. If you do nothing, it auto-dismisses after five seconds and processes the screenshot anyway. Zero friction when you don't need it, instantly available when you do.

AI vision analysis runs automatically using the same models that power tools like ChatGPT's vision capabilities. It doesn't just describe what it sees. It recognizes text, understands code snippets, identifies UI elements, and extracts semantic meaning. A screenshot of a Slack conversation gets analyzed for the topic being discussed, not just "three people in a chat interface".

Cmd+K search palette that works like Spotlight but for your screenshots. Search by visual content, by your context notes, by date, by project tags. See thumbnail results instantly. The interface is designed for keyboard-first workflows.

Lives in your menu bar like all the best Mac utility tools. Click the icon to browse recent screenshots. Right-click for quick actions. No separate app window to manage. It's always there but never in the way. (I wrote about why menu bar tools work so well if you're curious about this design pattern.)

Local-first architecture means your screenshots never leave your Mac. The AI analysis runs using cloud APIs (because on-device vision models aren't good enough yet for this use case), but the images themselves stay local. Database is SQLite in your Application Support folder. You can back it up. You control the data. (More on why local-first matters for tools like this.)

The difference is night and day. Instead of fighting with Shortcuts triggers and Hazel rules, I just take screenshots. The app handles everything else. The popup appears when I want to add context. It disappears when I don't. Search finds things based on what I'm actually looking for, not just filename keywords.

It's the workflow I was trying to build with automation tools, but designed as a cohesive system instead of separate pieces fighting each other.

so should you use shortcuts at all?

Here's my honest take after trying both approaches:

If you take fewer than 10 screenshots per week, the Shortcuts auto-rename workflow is probably enough. Set it up once, let it run in the background, enjoy slightly better filenames. You don't need project tagging or semantic search for occasional captures.

If you already use Hazel for other automation, adding the Shortcuts rename is a nice enhancement. Your existing rules will work better with descriptive filenames. Just know you'll hit the limitations I described if your screenshot volume increases.

If you're a heavy screenshot user (20+ per day, multiple projects, screenshots as actual work artifacts), you need something purpose-built. The Shortcuts + Hazel approach will get you 60% of the way there, but the missing 40% is the stuff that actually matters: context capture, smart search, project awareness, reliability.

The broader lesson here is that automation tools like Shortcuts and Hazel are incredible for general file management. But screenshots have specific needs that general-purpose tools weren't designed to handle.

It's the same reason people use dedicated password managers instead of just storing passwords in encrypted text files with automation rules. Sure, you could build that system. But the dedicated tool handles edge cases, provides better UX, and actually gets used consistently.

If you want to see what other tools people are using for screenshots, I wrote a comparison of the best screenshot apps for Mac that covers the full landscape.

closing

The screenshot problem isn't about capture. macOS nailed that years ago with Cmd+Shift+4.

It's not even about renaming anymore. Apple Intelligence in Shortcuts handles that well enough for many use cases.

The real problem is the complete lifecycle: capture, context, organization, and retrieval. Every screenshot you take represents a moment you decided something was worth remembering. The system should make it effortless to record why it mattered and trivially easy to find it again later.

I spent three weeks trying to build that system with Shortcuts and Hazel. I learned a lot. The automation worked, sort of. But the friction points made me realize that sometimes you need a tool designed specifically for the job instead of general-purpose automation duct-taped together.

If you're struggling with screenshot chaos and want something that actually handles the full workflow, join the waitlist for ohsnp. It's currently in private beta, and we're letting people in gradually.

Your future self, frantically searching for that one screenshot from three weeks ago, will thank you.