1/ Chrome shipped passkey autofill in version 108 back in December 2022. Run that same build on Windows 10 and the autofill chip never appears. So why does your passkey login sometimes show nothing? Conditional UI browser support is a matrix, not a checkbox. 🧵
1/ Every passkey carries a 16-byte AAGUID that names the password manager that made it, resolvable through the community passkey AAGUID list. Most teams throw it away. Here is the passkey aaguid field, explained.
1/ Cross-browser passkey autofill only became real when Firefox 122 shipped conditional UI on Jan 23, 2024. Before that it was a Chrome-and-Safari feature. But "supported" hides 3 separate capabilities, and that gap breaks real deployments. The passkey browser support matrix
1/ Nine in ten consumers now recognize passkeys, but only 40% enable them across most of their apps (FIDO Alliance, State of Passkeys 2026). Awareness is not the problem. So why is your enrollment stuck below 10%? Five reasons, ordered by how often they're the real cause.