Does turning off Background App Refresh affect a third-party keyboard on iPhone?
Background App Refresh only ever reaches the app you would tap on the Home Screen, topping up content it has ready for the next time you open it. A keyboard extension does not sit around waiting for that kind of top-up — it starts the instant a text field asks for one and is gone the instant it does not — so the switch has nothing to reach even when it is pointed at a keyboard’s own app.
Somewhere in a battery-saving pass through Settings → General → Background App Refresh, a keyboard app’s name turns up in the list next to games, news apps and things barely opened in months. Flipping it off there feels harmless for most of that list. Flipping it off for the app behind the keyboard typed on all day is a different kind of decision, and a reasonable one to hesitate over — is this the same kind of invisible permission as Full Access, quietly holding something the keyboard needs to keep working?
What Background App Refresh actually refreshes
Background App Refresh lets iOS wake an app that is not currently open, briefly, so it can fetch new content ahead of time: a news app pulling in the morning’s headlines, a mail app collecting messages that arrived overnight, a podcast app downloading the next episode before it is asked for. The point is to make the app feel instant the next time it is actually opened, rather than starting with a spinner while it catches up. iOS decides when to grant that moment on its own, based on how often the app is opened and whether a decent connection is available, and the whole mechanism needs a network connection to have anything to do at all — it is a way of doing a fetch early, not a way of running code for its own sake.
Why a keyboard extension is not the app sitting in that list
The row in Background App Refresh belongs to the container app — the one with its own icon and its own page on the App Store — not to the keyboard extension that app publishes. iOS only ever lets a person address whole apps from that screen; an extension has no separate row of its own to switch off, the same way a keyboard extension has no separate line of its own on the Battery screen either.
That container app and its keyboard extension also do not share a life the way the name suggests they might. A keyboard extension has no dormant state for a background refresh to reach in the first place: iOS creates it the instant some text field elsewhere on the phone asks for a keyboard, hands it a view to draw into, and tears it down again the moment that field loses focus or the keyboard is dismissed. There is no version of it sitting quietly in between, with a cache going stale that a scheduled wake-up would otherwise top off — the same short lifecycle that keeps a keyboard extension from costing battery in your pocket also rules out the kind of standing-by-for-a-refresh behaviour Background App Refresh exists to interrupt.
What actually happens once the switch is off
Switching Background App Refresh off for a keyboard’s container app stops that app, specifically, from quietly fetching whatever it would otherwise have ready for its own screens — new content behind its own icon, not anything a keyboard needs to draw a key. Opening that app directly afterwards just means it fetches fresh in the moment instead of starting from something grabbed earlier, exactly as it would if the permission had never been granted at all. None of that reaches the next time a text field somewhere else asks for a keyboard: it loads the same way every time, from what is already installed on the device, whether the app it came from was allowed to refresh in the background a minute ago or has been blocked from doing so for months.
Where the setting genuinely matters, and where it plainly does not
- Turned off for something that actually leans on it — mail, news, weather, a podcast app — the effect is real and visible: nothing was preloaded, so the first open after a while starts with a fetch instead of already-fresh content.
- Turned off for a keyboard’s container app, nothing about typing changes, because the extension was never drawing on that mechanism to begin with. A keyboard reads from what is installed on the device, not from a rolling cache Background App Refresh keeps topped up somewhere behind it.
- Even a keyboard feature that genuinely does reach the network — an image search inside an emoji panel, say — makes that call in the moment it is used, through whichever permission that specific action needs. It does not depend on a dormant wake-up scheduled hours earlier by a setting built for a completely different kind of app.
Where Kibo fits
Kibo makes zero network requests, so there is nothing behind it for Background App Refresh to fetch in the first place — no server holding a newer theme, no queue of sounds waiting to sync down before the app is opened. Every one of its themes, key sounds, backlight effects, fancy text styles and 30 typing languages already lives on the device the moment the app is installed, which is also why switching Background App Refresh off for Kibo specifically, or for the whole phone, changes nothing about how the keyboard looks, sounds or types. Full Access is a separate matter entirely, read only for the Copy word, Copy line and Paste buttons on the keyboard’s toolbar. Kibo is free to download.
Frequently asked questions
Will turning off Background App Refresh break my custom keyboard?
No. Background App Refresh only reaches the app’s own screens — the ones behind its Home Screen icon — and a keyboard extension is a separate, on-demand process that iOS starts the moment a text field asks for one and tears down the moment it does not. There is nothing in that lifecycle for the setting to interrupt.
Why does my keyboard app show up in the Background App Refresh list if it doesn’t affect the keyboard?
Because that list addresses whole apps — the container app you would tap on the Home Screen — not the keyboard extension published inside it. iOS has no separate row for an extension there, the same way it has no separate line for one on the Battery usage screen.
Does turning it off save meaningful battery for a keyboard app?
Only in the ordinary sense that applies to any app: less background fetching for the container app itself, if it was fetching anything in the background to begin with. It does nothing for the keyboard extension specifically, since Background App Refresh was never what kept that extension running — nothing does, once its keyboard leaves the screen.
Try it on your own keyboard
Kibo is a free custom keyboard for iPhone with real mechanical key sounds, a wardrobe of themes and RGB backlight effects. No account, no ads, and it works with Full Access left off.