Guide · 10 min read

iPhone Shortcuts automations for grayscale: the full guide + where they break

Every menu, in the order iOS 26 actually presents them. Two automations per app, built by hand, and the ways the whole thing stops firing.

The easy way: let Dwindle do it

Dwindle is the easiest way to get exactly what this guide builds: per-app grayscale, with the automations pre-built and installed in a tap, the escape hatch built in, and self-repair when an automation misses. One app free.

The rest of this page is the manual path, for people who would rather build it themselves. It works, and it is fiddly and fragile in the ways the “Where they break” section below sets out: a dozen menus in a strict order, an escape hatch you have to build before anything else, two more automations for every app you add, color flooding back mid-scroll when an interruption or a link-out counts as a close, and a gray camera when a close never fires.

Grayscale is the rare screen-time trick with actual research under it. Across published field studies, switching an iPhone to gray reduces objectively measured screen time by roughly 20 to 40 minutes a day^{1 2 3}: logged time, not self-reported. The catch is that iOS ships grayscale as a single global switch. Flip it on and Instagram loses its pull, but so do your camera, your photos, and the map you’re trying to read.

There’s no toggle for “gray, but only for the apps that eat my evening.” There is a way to build one out of the Shortcuts app, free and reversible, out of two automations per app and a dozen menus that have to be visited in the right order. This is the complete walkthrough (every menu, in the order iOS 26 actually presents them), followed by where the whole thing breaks. Because it does break, in a handful of predictable ways, and you’re better off knowing them before you rely on it than discovering them mid-scroll.

What you’re building

Two automations per app. Open the app, the screen goes gray. Close it, color comes back. Every other app is untouched. Before any of that, you’ll set up a manual override, because the very first rule of automating your screen color is having a way to fix it by hand.

You need an iPhone on iOS 26 with the Shortcuts app (it ships with iOS), and a walk through a dozen menus in a strict order for every app you target. No jailbreak, no third-party app, nothing that touches a warranty.

Step 1: Prime the color filter

1. Open Settings → Accessibility → Display & Text Size → Color Filters.
2. Toggle Color Filters on and choose Grayscale. Your whole screen drains to gray. That’s expected.
3. Toggle Color Filters back off. Color returns.

That on-then-off dance isn’t busywork. It tells iOS which filter to apply whenever something switches filters on later. Your automations only flip the master switch; this step decides what the switch does. There’s an intensity slider on this screen too: on iOS 26.6 it’s an unlabeled track with no percentage markings, so any partial setting is by feel. Leave it at full for now.

Step 2: Set up the escape hatch first, not last

Before a single automation exists, give yourself a manual override. Go to Settings → Accessibility → Accessibility Shortcut (it’s at the bottom of the Accessibility page) and check Color Filters. Now a triple-click of the side button toggles grayscale on or off, anywhere, any app, any time.

Do this first. If anything downstream misbehaves (and the last section of this guide is a list of ways it can), the triple-click is how you undo it in one second instead of spelunking through Settings. It’s genuinely useful on its own, too: plenty of people skip the automations entirely and just triple-click a colorful app into gray the moment they feel a doomscroll starting.

Prefer not to use the side button? You can add Color Filters to Control Center instead and tap it from there.

Step 3: The “gray on open” automation

This is the step where older guides, including earlier versions of this one, stop matching your screen. iOS 26 reorganized automation triggers into four groups: Event, Travel, Communication, and Setting. The old flat list with an “App” row at the top is gone. The App trigger still exists; it just moved.

1. Open Shortcuts → Automation tab → + (New Automation).
2. Scroll to the Setting triggers group. The App trigger lives there now.
3. Do not use the search box to find your app. On iOS 26, typing an app’s name into this flow surfaces that app’s donated actions (things like “Open Instagram”), not the trigger. It’s a genuine trap: pick one of those and you build a shortcut that opens Instagram rather than an automation that reacts to Instagram opening. It looks correct in the summary and does the exact opposite. We took that wrong turn ourselves the first time through. Ignore search; go through Setting triggers → App.
4. Tap App, then Choose, and select Instagram (or whichever app is the problem).
5. Leave Is Opened checked and make sure Is Closed is unchecked. One trigger per automation.
6. Critically, select Run Immediately, not “Ask Before Running.” Ask-before turns the whole system into a permission prompt every time you open an app, which defeats the point of an ambient tool.
7. For the action, add Set Color Filters, configured to Turn Color Filters On.

Use Turn On, never Toggle. Toggle looks equivalent and isn’t: it flips whatever the current state is, so the first time reality and its assumption drift apart, you get color where you wanted gray and gray where you wanted color. “Turn On” states an intent; “Toggle” makes a guess.

Step 4: The “color on close” automation

Repeat Step 3 with two changes: check Is Closed instead of Is Opened, and set the action to Turn Color Filters Off. Run Immediately again.

That’s one app fully wired. Open Instagram and the screen should drain to gray within a beat; close it and color returns. Now repeat both automations for every app you want to target: TikTok, YouTube, Reddit, X, whichever ones you actually lose time to. Two automations each. It’s repetitive, and there’s no shortcut around the repetition; the trigger is per-app by design.

The inverse setup: gray by default, color for the apps that earn it

Everything above assumes a colorful phone with gray exceptions. Some people, often after living with the per-app version for a while, flip the logic. They leave Color Filters on permanently and build automations that turn filters off when Camera or Photos opens and back on when it closes. The phone rests in gray; color becomes something specific apps earn for the moment you need them.

The mechanics are identical, just mirrored: Camera / Is Opened → Turn Color Filters Off, Camera / Is Closed → Turn Color Filters On. The inverse setup is the more forgiving of the two, because when an automation misfires it fails toward gray, annoying but harmless, rather than toward color, which quietly defeats the whole exercise. The cost is a more monastic phone. Both are worth knowing; start with the per-app version if you’re not sure.

Where they break: read this before you rely on it

What you’ve built is a set of independent automations with no awareness of each other and no memory of what you’re doing. That’s fine until it isn’t, and here are the failure modes, so they don’t surprise you. None of them are dealbreakers; all of them are why this feels like a clever hack rather than a finished thing.

Interruptions can reset a session. A phone call, a notification you tap away to, locking the screen: iOS can read any of these as the app closing, and the close automation fires. Color floods back mid-scroll even though you never really left. Coming back can register as a fresh open. It’s visually noisy and occasionally just confused; a clean close-and-reopen sets it straight. Treat any interruption as a possible silent reset.

A link-out flips the color back. Tap a link that bounces you to Safari or another app and the same thing happens: the source app counts as closed, color returns, and returning counts as a new open. It’s most jarring exactly when you’re reading something, which is when links appear.

A force-quit can leave you stuck in gray. Every so often a close automation simply doesn’t fire (swiping an app away in the app switcher at the wrong moment is the usual cause), and later you open your camera to a gray viewfinder. This is precisely what the Step 2 triple-click is for. It will happen eventually; it’s a one-second fix when it does. (This is the single best argument for setting up the escape hatch first.)

Filter-type drift. The automations control the master switch, not what the switch does. If you, or someone borrowing your phone, changes the selection in Settings from Grayscale to some color tint, every automation now toggles that tint instead. The plumbing keeps working; it’s just pushing the wrong filter. Worth a periodic glance at Step 1’s screen.

Timers outlive their sessions. The basic build here has none, but the tempting extension (“gray me a few minutes after I open the app,” via a Wait action) has a sharp edge. A pending Wait doesn’t cancel just because you closed the app. Abandon a session early and the timer can still fire later, graying your screen in the middle of something else entirely. If you go down the timed road, expect the occasional ghost.

That’s the full list of the common ones. Each is a consequence of the same root fact: these automations don’t know about each other, don’t remember the last thing that happened, and can’t tell a real exit from an accidental one.

What Shortcuts can’t do at all

No amount of cleverness in this app gets you: gradual desaturation over a session (the action is binary, on or off, nothing in between), a different intensity per app (intensity is one global slider), or anything happening inside an app. Those limits are baked into iOS, not into your patience. Within them, per-app grayscale is still the rare screen-time intervention with published evidence behind it that never blocks you from anything and never nags. Grayscale produced an immediate, significant drop in measured screen time against a self-monitoring control in Zimmermann and Sobolev’s pre-registered field experiment¹, and in Dekker and Baumgartner’s study daily screen time fell by around 20 minutes while the number of daily unlocks held steady²: the reach survives, the sessions shrink. It just quietly stops paying out.

Or don’t maintain it yourself

Building it is only the start. The upkeep is the tax: two automations per app, redone as your problem apps change, plus the failure modes above with nothing to catch them.

Related guides: the per-app grayscale setup, the triple-click trick, the stimulation stack, and the science of grayscale.