Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

Lock and Home Screen Wallpapers turn black after iOS 27 update?

After updating my iPhone 17 Pro to iOS 27.0, my lock screen and home screen wallpapers will often show a black background as opposed to an image when unlocking the device


The lock screen is set to shuffle a specific photo album. The home screen is paired to match the lock screen.


Setting up a new lock screen with the album does not resolve this issue


The issue did not exist prior to iOS 27


Anyone else experiencing this? How do I resolve it?

6 replies

Since recreating the Lock Screen didn’t help and this started right after iOS 27.0, I’d try one thing to narrow it down.


Set a single photo as the Lock Screen wallpaper instead of Photo Shuffle and use it for a while. If that stays visible, but an album set to Photo Shuffle turns black again, the problem is likely specific to Photo Shuffle rather than your photos or wallpaper setup. Apple does support using an album with Photo Shuffle, so what you’re doing is valid.

→ Change your iPhone wallpaper - Apple Support


I’d also force restart the iPhone once. If the problem continues with Photo Shuffle after that, I’d report it to Apple Support since it may be an iOS 27.0 issue.

Check Focus l, particularly Smart Activation. It is normal for wallpaper to be black if Focus is activated

Have the same issue on ios27. Blank photo but only for few from photo shuffle. I think only happen when the photos are taken from iCloud.

Hey, in my case it is red. Actual photo is opened, but on backtound you can see same blurred image as is on lovk screen. It looks like shuffler drastically zooms on tissue under the coffee.

Happens to me repeatedly; I get a plain-color lock screen, change to the picture I like -- and a while later it goes plain again.


No photo shuffle.

Same, and I can't figure out the link between which photos it is. But it's driving me crazy. I reported it through the feedback app weeks ago. It wasn't fixed with 27.2 sadly.