Does the iPhone Action Button run a Shortcut while the screen is off?
Chris Walsh
October 7, 2026
Yes. On an iPhone 15 Pro, an iPhone 16, or an iPhone 16 Pro with the Action Button set to a Shortcut, a press runs that Shortcut while the screen is off. You do not have to wake the Lock Screen first. The screen often lights a moment later to show what happened. Steps that need Face ID, a menu, or an app in the foreground stop and wait. Steps that only change a Focus, a light, or a local setting finish in the dark.
The button is a hardware trigger, not a Lock Screen widget. Widgets need the screen awake and a tap on glass. The Action Button needs a finger on the side of the phone. That is why it works in a pocket, which is both the feature and the bug.
Which phones is this even about?
The Action Button is the control that replaced the ring/silent switch. It is on the iPhone 15 Pro and 15 Pro Max, and on the iPhone 16, 16 Plus, 16 Pro, and 16 Pro Max. An iPhone 15 or 15 Plus still has the mute switch. That switch cannot run a Shortcut. If the phone in your hand clicks like a mute switch and Settings has no Action Button page, this article is not your hardware.
The button runs a Shortcut only if you assigned Shortcut in Settings, and then picked one. If it is set to Silent Mode, Camera, Flashlight, Voice Memo, Focus, Translate, Magnifier, or the control the newer phones call Visual Intelligence, a press does that instead. The screen being off does not matter. You never handed it a Shortcut. Check the assignment before you decide the Shortcut is broken.
One Shortcut is assigned, not a folder. If you wanted a menu of three night actions, that menu has to live inside the single Shortcut the button calls. A menu on a dark phone is a bad menu. Prefer one action that is safe to fire unseen, or a menu you only use when you are looking, and accept that the screen will come on.
What actually happens in the dark?
Press the button with the screen off and the phone locked. iOS starts the Shortcut. For a local action, the work happens without an unlock. A Home scene fires if the hub is reachable. A Focus changes. A flashlight turns on, if that is what the Shortcut does. You may feel a haptic. The screen may wake to a small confirmation and then go dark again. Waking the screen is not the same as requiring the Lock Screen. The Shortcut did not wait for you to tap a widget.
Low Power Mode does not block this press. You are the trigger. The throttle that delays a 6:30 automation does not sit between your finger and a hardware button.
What will not finish in the dark is anything that needs you. Choose from Menu, Ask for Input, and Show Alert bring the screen up and then sit there. Send Message often demands a confirmation or Face ID before it sends, which is the correct refusal. Health samples, passwords, and a photo picker stop at the lock. Open App brings you to the Lock Screen or to the app only after you authenticate. If your Shortcut ends in “open the train app,” the button woke the phone and then waited. That is a successful hardware press and a failed unattended Shortcut.
Why does it fire in a bag?
Because the screen does not have to be on, and the button does not check that you meant it. A press in a coat pocket, against a table edge, or in a bag next to a water bottle runs the same Shortcut as a press you intended at the door. There is no “only if the screen was already on” switch. The feature you wanted at night is the feature that toggles the hallway lights from inside a backpack.
Design the assigned Shortcut as if a stranger will press it. No send message. No unlock the front door unless you have a second confirmation you will actually see. No toggle that is disastrous in both directions. A Focus, a flashlight, or a scene that turns one lamp on are survivable accidents. A Shortcut that texts your boss is not.
If pocket presses are constant, the button is the wrong trigger for that Shortcut. Put the dangerous action on a Lock Screen control you have to aim at, or inside a menu as the second step, knowing the menu saves you only because it cannot complete while you are not looking. The first step, the one the button always runs, should be boring.
How is this different from a Lock Screen Shortcut?
A Lock Screen widget or control runs when the screen is already awake and you hit the right target. It is harder to do by accident in a bag, and it is useless when you do not want to light the room to find the icon. The Action Button is the opposite trade. It works from sleep. It is easy to hit without looking. Pick it when the point is speed in the dark: a lamp by the bed, silent mode because you gave the physical switch away, a voice memo you start without hunting an icon.
Silent mode is the assignment people miss. On these phones the old switch is gone. If the Action Button runs a Shortcut, it does not also mute the ringer unless the Shortcut does. A night Shortcut that sets a Focus may or may not silence the hardware ringer. Test with the screen off and a timer you can hear. Do not assume Focus and the silent state are the same switch. They never were. The Action Button just made you choose one of them per press.
What should the Shortcut contain if the screen stays off?
Keep it short and local. One or two steps that do not show UI. Set Focus. Toggle a Home scene through the hub. Set the flashlight if you can tolerate a pocket light. Start a specific playlist only if playing audio in a bag is acceptable, which it usually is not.
Leave out Get Contents of URL. A press can start a fetch, and the fetch can still stall if the phone is locked and the radio is stingy. The button did its job. The network step is a different kind of failure, and it is a bad thing to bind to a control you hit when you are not looking at errors.
Leave out anything you would be upset to run twice. The button has no debounce you control beyond how the Shortcut is written. A toggle is the classic mistake: press once in the dark, unsure it worked, press again, and you undo it. Prefer a Shortcut that sets a known state, lamp on, rather than lamp toggle, if the press is supposed to work while you cannot see the lamp yet. If you can see the lamp, a toggle is fine. The screen-off case is the one where you cannot.
How do you test it without lying to yourself?
- Settings, Action Button, Shortcut, and the specific Shortcut named there. Not last used.
- Lock the phone. Wait until the screen is fully off, not the dim Lock Screen.
- Press the button once. Do not pick the phone up and unlock it.
- Check a result that is not the screen: the lamp, the ringer, the Focus name you can see on a watch, the recording indicator if you started a memo.
- Put the phone in a jacket pocket and walk around the house. If the lamp changes, the Shortcut is too easy to fire and you should change what it does, not the laws of the button.
A test where you unlock first only proves the Shortcut’s steps. It does not prove the button runs them from sleep. The whole question is the sleep part.
Are you pressing the Camera Control instead?
On the iPhone 16 lineup there is a second control, the Camera Control, and it is not the Action Button. It sits on the other edge, it is built to open the camera, and a light press or a click there will not run the Shortcut you assigned on the Action Button page. In the dark the two are easy to swap. If the screen wakes into the camera and your lamp does nothing, you found the camera control. Move your finger to the button above the volume keys, the one Settings calls Action Button, and press that.
The Camera Control cannot be fully reassigned into an arbitrary Shortcut the way the Action Button can. Do not spend an evening debugging a Shortcut that the wrong piece of metal is launching. Name the control out loud once while you are looking at Settings, then test with the screen off. Muscle memory from a 15 Pro, which has only the Action Button, is how 16 owners hit the camera and decide Shortcuts is asleep.
Who should not put a Shortcut on that button?
Do not put one there if you still need a dedicated silent switch and you will not remember which Shortcut press mutes the phone. The mute assignment is boring and it is the one that matches the hole Apple left. A Shortcut is worth it when you press it daily for one physical outcome and you have made that outcome safe to repeat by accident.
Do not put a multi-step goodnight routine there if half the steps need the screen. You will get a phone that lights up and waits, which is a worse flashlight than the flashlight assignment. Split the routine. The button does the part that is safe in the dark. The rest waits until you are looking at the phone on purpose.
The Action Button runs a Shortcut while the screen is off. That is the reason to use it. It will not unlock the phone, it will not tap through a menu, and it will not decline to run because you are in a bag. Give it a Shortcut that can live with all three of those facts.
