Skip to Content
Platform Ontology

Passkey on a nearby phone (hybrid)

A computer shows a QR code and your phone approves the passkey sign in.

When you are signed inWhile you use it

Hybrid transport lets a passkey on a phone sign you in on another device. The computer shows a QR code, the phone scans it, and the two devices check they are near each other over Bluetooth before talking through a relay. It works on a browser with no passkey of its own. An unattended cloud browser or agent cannot finish it without a person holding the phone.

What it can and can't do

What the user does: Scan the QR code and approve on the phone

It can

  • Use a passkey that lives on a nearby phone
  • Sign in on a shared or new computer
  • Prove you are near the phone, which blocks remote phishing
  • Work without typing a password

It cannot

  • Run unattended; a person must hold the phone
  • Work without Bluetooth on both devices
  • Let an agent finish the step
  • Skip the phone's fingerprint or face check

How it differs between platforms: Needs Bluetooth, internet and a phone with a passkey. Firefox depends on the operating system. Cloud browsers and agents stop at the QR code.

Browser support

Version notes
  • Chrome: Desktop shows a QR code for a nearby phone
  • Edge: Chromium Edge
  • Firefox: Depends on the OS passkey dialog; check your platform
  • Safari: Safari 16 and later on Mac
  • Safari on iPhone: Phone side of hybrid; iOS 16
  • Chrome on Android: Acts as the phone (authenticator) side
  • Samsung Internet: Phone side depends on the password manager

How a site asks for it

APInavigator.credentials.get({publicKey}) with hybrid transport chosen in the browser's passkey sheet; transport value 'hybrid'
Permissions policypublickey-credentials-get
Browser compat keysapi.AuthenticatorAttestationResponse.getTransports
How access is grantedprompt
What the user seesBrowser passkey sheet with QR code, then phone prompt
Needs a secure context (HTTPS)Yes
Needs a user gestureYes
How long it lastsPer site and passkey
How to take it backDelete the passkey on the phone or in the password manager
Inside an iframeSame as top level; cross origin frames need a permissions policy where listed

Typical flow

  1. Site starts a passkey sign in
  2. Browser offers 'use a phone' and shows a QR code
  3. Phone scans, checks Bluetooth proximity and asks for biometrics
  4. Phone sends the signed answer to the page

Data you get

Shape: object
How often: per sign in

FieldTypeUnitRangePrecision
transportslistNoneincludes hybrid when the passkey can be used from a nearby phoneNot listed
authenticatorAttachmentenumNonecross-platform for hybrid sign insNot listed
signaturebinaryNonesigned challenge for the siteNot listed

Technical limits

  • Needs the phone to be near and awake
  • QR scanning is a human step
  • Support varies by browser and OS

The story

What it is

A QR code on the screen lets your phone vouch for you. The two devices check they are close so a far away attacker cannot use it.

For you

You scan a QR code with your phone and approve with your face or finger. Nothing is typed. It is the way to use a phone passkey on someone else's computer.

For makers

Do not assume the user is on a device with a passkey. Offer the phone path and an alternative. For agents and cloud browsers plan a human handoff step at the QR code.

Where you see it

TypeExampleApps
securityAn employee signs in on a shared kiosk using the phone's passkey.None named
bankingA bank customer signs in on a new laptop by scanning a QR code.None named
shoppingA shopper checks out on a borrowed computer with a phone passkey.None named
productivityA user opens a work account on a new machine with the phone.Google Workspace
enterpriseStaff approve admin sign ins on their phone.None named
developerAn agent team adds a person to approve the QR step in an automated flow.None named

Risks

  • Needs Bluetooth and a nearby phone
  • Blocks fully unattended agents

What the platform says

Good uses and abuse

Legitimate uses

  • Phishing resistant sign in on any computer
  • Human approval for agent hand offs

Known abuse

  • QR code social engineering at kiosks

Scores

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility5 of 5How useful it is to honest apps
Friction2 of 5How much the user has to do
Fingerprint bits0.5Rough identifying entropy, when known

History

  • 2022-09, Safari 16: Passkeys and cross device sign in in Safari 16
  • 2022-11, Chrome 108: Chrome desktop adds the phone QR code flow
  • 2024, Chrome: Hybrid transport value standardized

Sources

How well checked: Based on official documentation.

On this page