On this page
The essentials
- A passkey can replace SMS, but not your cloud password.
- Check credential storage and recovery before losing a device.
- Keep your registered number active and under your control.
What changes when you sign in
A passkey lets you sign in to Telegram by approving the request on a device, using a fingerprint, face recognition or a PIN, for example. Instead of waiting for an SMS, you use a saved credential. That is particularly useful when traveling with internet access but unreliable carrier messages.
A passkey is not a new short password to dictate to someone. Compatible devices and credential managers create and store it. An enabled Telegram cloud password remains an additional sign-in requirement, however. If you have forgotten that password, creating or using a passkey is not a shortcut around two-step verification recovery.

Choose where the key will live
Start on a device already signed in to the intended Telegram account. If you use several numbers, check the profile first. Make sure you know the device unlock code and can access your password manager. Do not create your primary passkey on someone else’s phone, a shared work computer or a device you will soon return.
Local storage and synchronization have different consequences. A key stored only on one device may become inaccessible if that device is lost. A synchronized key depends on access to its credential-manager account. Check the destination offered by the system dialog before approving it. Do not assume a backup was created automatically.
On a shared family tablet, consider who knows the unlock code. Biometric approval is convenient, but system authentication may also allow a backup PIN. If several people know that code, the device is not an exclusively personal access method. Prefer your own phone and a credential store you understand. Decide this before creating the key; after a loss, you usually have less time to investigate where it was saved.
Create the key and verify the entry
In Telegram settings, open Privacy and Security, then Passkeys. Start creation and read the system dialog carefully. Choose a suitable credential store if a choice is offered, then approve using your normal device-unlock method.
Return to Telegram’s passkey list afterward. Find the new entry and creation date; the interface also provides usage information. This is a better confirmation than a dialog simply disappearing. If the entry is missing, do not sign out to test it. First check whether creation completed or was canceled in the system prompt. Button labels vary by Telegram client and operating system.
Test without sacrificing access
To test a passkey on a second personal device, keep the first device signed in. Start an official login and select the available passkey method. The system request should correspond to your own action, not a stranger asking you to “confirm a gift.” Enter your cloud password afterward if Telegram requests it.
Do not remove your older access methods after a single successful test. Confirm the second client opened the intended profile and your normal cloud chats. Secret chats do not move to another phone through this login. If the key is not offered, check system compatibility and access to the correct credential store instead of blindly creating new accounts.
Example: traveling without incoming SMS
You previously stored a key in a manager available on your personal laptop. While traveling, your SIM cannot receive messages, but Telegram on your phone works over Wi-Fi. You sign in on the laptop using the key and, if required, your cloud password. Here the passkey solves a specific SMS-delivery problem.
Now consider a lost phone with a key stored only on that phone and no accessible backup manager. The key will not magically appear on a replacement device. Finish setup by asking “How would I access this key after losing my phone?”, rather than stopping at a successful-creation badge.
What to keep under your control
Keep the active phone number registered with Telegram under your control. Passkeys add a login method; they do not remove the number or SMS fallback. Update account details before giving up a number. Protect your credential-manager account and recovery mailbox so synchronization does not depend on a weak link.
When a device is no longer yours, review both passkeys and active sessions. Removing a key and terminating an existing session solve different problems. Remove an outdated key only when you know where working access remains. Decline an unexpected authentication prompt and investigate, rather than automatically touching the fingerprint sensor.


