Does AutoFill work with a third-party keyboard on iPhone?
The little key-shaped suggestion strip for saved passwords and text-message codes is drawn by iOS itself, not by your keyboard, so switching to a custom one does not hide it — except for the one field where iOS takes the keyboard away from you entirely anyway.
You tap a login field expecting the small strip above the keys that offers a saved password, or the banner that lets you approve a passkey with Face ID, or the code that just arrived by text lifting itself straight off the screen and into the field. Switch from Apple’s keyboard to one you installed and it is reasonable to wonder whether any of that survives the change. It does, for almost all of it, and the one exception is not really about AutoFill at all.
What that suggestion strip actually is
AutoFill is Apple’s own system for offering saved credentials: passwords and passkeys from iCloud Keychain, or from a password manager you have installed and turned on as an AutoFill provider, plus one-time codes it has read out of a text message so you do not have to leave the app to go copy one. None of that data or logic lives inside a keyboard. It is stored in the Keychain, matched against the field you tapped by iOS itself, and presented in a thin strip that sits above whichever keyboard happens to be showing.
It shows up above a custom keyboard the same way
For an ordinary username field, an email field, or a one-time-code field, that AutoFill strip is drawn by the system as a layer above the keyboard, not by the keyboard extension itself. A third-party keyboard has no say in whether it appears and does nothing to build it — it simply sits underneath a bar that iOS was going to show regardless of which keyboard was active. That is why people who type on a custom keyboard every day still see “use password for [site]” or a six-digit code offered to them without ever switching back to Apple’s own.
The one field where iOS does swap the keyboard
The actual password field is a different case, and it is the same rule covered in why a custom keyboard disappears in some apps: a password field is marked as secure text entry, and iOS forces its own keyboard for as long as the cursor sits inside it — not just the suggestion strip above it, the keys themselves. Move the cursor to the username field just above it, or the one-time-code field just after it, and your usual keyboard is back immediately, because those fields were never secure to begin with. From the outside this can look like AutoFill is the thing breaking; what actually happened is the narrower, unrelated secure-field override, and it lets go the moment the cursor leaves.
Why iOS drew the line here
Saved passwords and passkeys are about the most sensitive data a phone holds, so Apple keeps the matching and the filling-in entirely inside its own system layer rather than handing any of it to code a third party wrote — the same caution behind sandboxing a keyboard extension away from the network by default. Letting the AutoFill strip render above any keyboard, rather than requiring Apple’s own, was a deliberate design choice in the other direction: it means adopting a custom keyboard never costs you password autofill for the fields that are not actually the password itself.
This has nothing to do with a keyboard’s Full Access switch
It is a reasonable guess that AutoFill ties into the same permission that gates a keyboard’s clipboard buttons, since that is the one switch iOS keeps asking about. It does not. Full Access is a keyboard extension permission, and it governs the network and the system pasteboard, not the Keychain. Whether AutoFill suggestions appear is controlled separately, in Settings under Passwords, and has nothing to do with which keyboards you have installed or whether any of them has Full Access turned on. A keyboard with Full Access off shows the same AutoFill strip as one with it on, and turning Full Access on for a keyboard does not hand it your saved passwords — the secure field it would need to reach stays forced to Apple’s own keyboard either way.
Where Kibo fits
Kibo is an ordinary keyboard extension in exactly the sense this depends on, so none of it changes with Kibo active: the AutoFill strip for saved passwords, passkeys and text-message codes still renders above it on every field that is not itself the password, and the password field still hands control to Apple’s keyboard for as long as the cursor is there, the same as with any other keyboard installed. None of it needs Full Access, which Kibo only reads for the clipboard buttons on its own toolbar. It is free to download.
Frequently asked questions
Do I need to switch back to Apple’s keyboard to use a saved password?
No. The AutoFill suggestion strip is drawn by iOS above whichever keyboard is active, so it appears the same way over a third-party keyboard. iOS only takes the keyboard away from you for the actual password field itself, and gives it back the moment the cursor leaves.
Why did my keyboard change to Apple’s right as I typed a password?
The password field is marked as secure text entry, and iOS forces its own keyboard for as long as the cursor sits in that specific field. It is the same restriction that applies to banking apps and payment sheets, and it is not something any keyboard, including Kibo, can opt out of.
Does a keyboard need Full Access to show AutoFill suggestions?
No. AutoFill suggestions come from Settings under Passwords and are controlled separately from any keyboard’s Full Access switch. A keyboard with Full Access off shows exactly the same AutoFill strip as one with it turned on.
Does turning on Full Access let a keyboard see my saved passwords?
No. Full Access grants network access and the system clipboard, not the Keychain. The password field itself is always handed to Apple’s own keyboard while the cursor is inside it, regardless of what any other keyboard is permitted to do.
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.