To fix a Discord passkey that is not working, sign in with your password first, then select Authenticate with security key and try your registered passkey again. Discord recommends this as the first troubleshooting step, and hardware security keys generally require this route. If it fails, check which device or password manager holds the credential before removing anything.
Keep any working Discord session and another authentication method available while you troubleshoot. The Windows settings below use Windows 11 menus. Sign in only through Discord’s own app or website, and never share a code, password, or remote access with someone who contacts you.
The short version
- Try password login first: Enter your credentials, then select Authenticate with security key.
- Find the saved credential: Choose the account, device, or password manager that holds your Discord passkey.
- Check phone handoff: Windows cross-device authentication needs Bluetooth and internet access on both devices.
- Keep another way in: Use an enrolled authenticator, previously enabled SMS MFA, or an unused backup code when needed.
| What happens | What to try | What you need |
|---|---|---|
| Passwordless login fails | Try the passkey after password login | Your password and registered credential |
| The passkey is missing | Check the original account or device | Access to its password manager |
| Phone authentication stalls | Check Bluetooth and internet | The phone holding the passkey |
| The wrong provider opens | Choose or enable the correct provider | Access to the saved credential |
| You need another way in | Use an existing authentication method | An enrolled factor or unused backup code |
| The saved passkey remains broken | Replace the credential on both sides | Another usable authentication route |
| A hardware key is blocked | Resolve its PIN or biometric block | The key and its FIDO2 PIN |
| The login interface freezes | Restart or update the client | A working internet connection |
| The failure keeps returning | Report the error to Discord | Error details and device information |
Try both Discord passkey login routes
Enter your Discord login credentials and continue to the multifactor authentication challenge. Select Authenticate with security key, then try the registered passkey or hardware key. This gives you another route when starting directly with passwordless login fails.
For direct passkey login in the desktop app, a desktop browser, or the mobile app, select Or, sign in with Passkey instead on Discord’s login screen. Choose the passkey for the correct Discord account and complete device verification. If the credential is missing from the selection prompt, check where you saved it next.
Find the device or account holding your passkey
In Chrome, use the Google Account that stores your Discord passkey. Open More > Passwords and autofill > Google Password Manager and inspect your saved credentials. A passkey saved only in Windows Hello or a local Chrome profile on a Mac does not automatically follow you to another computer, so use the original computer or profile for those credentials.
On Android 9 or later with a screen lock enabled, open Chrome and select More > Settings > Autofill and passwords > Google Password Manager. Use your device’s PIN, pattern, or password when requested. On a replacement Android device, sign in to the original Google Account and supply the old device’s screen-lock credential when prompted.
On iPhone or iPad running iOS or iPadOS 18 or later, open Passwords, unlock it, select All, and find Discord. Check the relevant shared group and Deleted too. Shared credentials require compatible software on every device.
If you recently deleted the credential on a Mac with the Passwords app, open Passwords > Deleted, select the Discord account, and click Recover. Apple retains deleted credentials for 30 days, and recovery restores them to the Mac and iCloud Keychain. The passkey must still be registered with Discord to work.
If your credential is missing on another Apple device using the same Apple Account, open Settings, or System Settings on Mac, and select your name. Open iCloud and turn on password and keychain syncing; the exact labels vary by OS release. Approve a new device using an existing approved device or the previous device’s passcode when requested.
Use a passkey saved on your phone
Start Discord passkey login in desktop Chrome, then select Use Passkey from Another Device or Use a phone or tablet in the browser prompt. Select Try another way when needed to reach that choice. Scan the displayed QR code with the phone holding your registered passkey and authenticate on that phone.
For Windows cross-device authentication, turn on Bluetooth on both the computer and phone and connect both devices to the internet. Retry the phone-based passkey prompt after restoring those connections. These requirements apply to cross-device authentication, rather than every passkey stored locally.
Check the password manager and passkey permissions
On Windows 11 version 24H2 or later with passkey-consent settings, open Settings > Privacy & security > Passkey access. Find Discord or the browser you are using and enable its access switch. On Windows 11 builds exposing provider controls, open Settings > Accounts > Passkeys > Advanced options and enable the provider holding the credential; for local credentials, enable Save passkeys to this Windows device.
If passkey access or provider settings are unavailable on a managed Windows computer, contact its administrator. Your organization can restrict provider integration, access to settings, or the Bluetooth transport used for phone authentication.
On current Apple systems with the Passwords app settings, open Settings, or System Settings on Mac, then select General > AutoFill & Passwords. Turn on AutoFill Passwords and Passkeys. Check this setting when saved credentials are not offered automatically.
With the 1Password browser extension, unlock the extension, start Discord passkey login, and select Use passkey. Select Other options to choose another credential, or select the security-key icon to use a hardware key or browser-held credential. If 1Password is intercepting a passkey saved elsewhere, open its account menu, select Settings > Autofill & save, and turn off Offer to sign in with passkeys before retrying with the correct provider.
For the Bitwarden browser extension, open Settings > Notifications and check Ask to save and use passkeys. If Discord appears among blocked or excluded domains, removing that entry allows passkey prompts for Discord again. Remove that entry if present, then retry.
On Android 14 or later, open Bitwarden and select Settings > Autofill > Passkey management > Continue, then select Bitwarden in the system provider settings. Use Discord’s direct passkey login for Bitwarden’s documented primary login route on Android. If the password-first challenge fails with that provider, try direct login or another enrolled authentication method.
For Bitwarden’s native Windows provider, use its appx or Microsoft Store distribution and open File > Settings > Passkey provider > Manage in system settings, then enable Bitwarden. On a supported Mac desktop app, open Preferences > Passkey provider > Manage in system settings and select Turn On. Disable duplicate extension passkey handling to avoid conflicts with the native provider.
Get back in with another authentication method
An authenticator app already enrolled for Discord gives you another route: enter your password and complete the authenticator challenge with the app’s current code. For previously enabled SMS MFA, select Verify with something else > Use a code sent to your phone, enter the received code, and select Confirm. Having a phone number linked to Discord alone is not enough to use SMS MFA.
To use a backup code, find your saved codes, including a file named discord_backup_codes.txt or a saved screenshot. After password login, select Verify with something else > Use a backup code. Enter an unused eight-digit code and select Confirm.
A desktop or browser session that is still signed in can also help you retrieve codes. Open User Settings, select My Account, then select View Backup Codes. Enter your password to access them; additional verification may apply.
Discord’s separate QR-code login is another option when the mobile app is already signed in. Display the Discord login QR code on your computer, then open Discord on your phone, tap your profile image and the cogwheel, and select Account Settings > Scan QR Code. Scan your computer’s code and tap Log in; this route uses your authenticated Discord mobile app rather than a phone-held passkey.
Replace a passkey that remains broken
Removing a credential takes away that saved passkey, so preserve a working session, another authentication method, and available backup codes before deleting it. Once you have another usable login route, confirm you can also complete the reauthentication needed to register a replacement passkey before removing the Discord credential from the password manager that holds it; a backup code may let you sign in but may not work for registering a passkey. Sign in using another enrolled factor, device, or unused backup code, then begin replacement enrollment in Discord, which may not accept a backup code. Enrollment includes a separate reauthentication step, so keep your other enrolled factors available.
For a passkey stored locally in Windows, deletion removes the local Discord credential. On Windows 11, open Settings > Accounts > Passkeys, find Discord, open its adjacent menu, and select Delete passkey. This path applies to locally stored Windows credentials, not credentials held by a separate synced provider.
Deleting the Discord credential from Apple Passwords removes that saved credential. In the current iPhone or iPad Passwords app, unlock the app, select Discord, and tap Edit > Delete. Continue with replacement enrollment in Discord.
Deleting the passkey from a Bitwarden item removes that saved passkey. In Bitwarden’s web app, extension, or desktop app, open the Discord item’s Edit screen, select the Passkey field’s delete icon, and select Delete. Select Save, then continue with Discord enrollment.
On Discord desktop or in a desktop browser, open User Settings, select My Account, then find Password and Authentication and select Register a Security Key. Reauthenticate, select Let’s go, and complete your provider’s enrollment. Your operating system and provider must support the enrollment method you choose.
In the Discord iOS or Android app, tap your avatar and the cogwheel, then select Account > Security Keys > Add. Reauthenticate, choose Other Options when needed, save the credential, name it, and tap Finish. If you cannot complete reauthentication, use another enrolled authentication route and follow Discord’s recovery guidance.
Deleting the old registration removes that passkey from your Discord account. After registering the replacement, remove the old registration in Discord’s account settings.
Resolve a hardware key block
If your FIDO2 YubiKey stops accepting PIN attempts after three incorrect entries, unplug and reinsert it before retrying with the correct PIN. This is the key’s PIN, not your Discord password. Eight incorrect entries block FIDO2 and require a destructive reset, so stop guessing if you do not know the PIN.
If a YubiKey Bio is blocked after unsuccessful fingerprint attempts, open Yubico’s setup page and select Unblock biometrics. Enter the security key’s PIN. When its green LED flashes, touch the key’s bezel ring.
Deleting a Discord passkey from your YubiKey removes that credential from the key, so establish another Discord login route first and confirm you can complete the reauthentication needed to register a replacement passkey; a backup code may let you sign in but may not work for registering a passkey. In desktop or Android Yubico Authenticator, open Passkeys, authenticate with the key’s PIN, select the Discord credential, and open Details > Actions > Delete passkey. Enter the PIN if requested, select Delete, then register a replacement through Discord. This view lists discoverable credentials; non-discoverable MFA credentials cannot be listed here.
A FIDO2 reset erases the key’s FIDO credentials, so establish another login route for every affected account, and confirm you can complete Discord’s reauthentication to register a passkey, before proceeding. For a supported permanently blocked key, connect it to desktop or Android Yubico Authenticator and open Home > DEVICE > Factory reset. Select FIDO2, then select Reset; for USB, unplug, reinsert, and touch the key when prompted. Register it with Discord again afterward.
A Bio Multi-protocol Edition reset also affects PIV credentials, so account for those before resetting that model. Customized keys can restrict reset transports or require a five-second touch. Follow the prompts for your key rather than assuming every model resets identically.
Fix a stalled login screen
When the interface freezes or requests fail to complete, fully quit Discord, including its background processes in Windows Task Manager. Wait 30 seconds and reopen it, then test another internet connection if requests still fail. These steps address client or connection faults; they do not repair a revoked passkey.
Try Discord in an updated supported desktop browser or update the Discord app. To update desktop Chrome, open More > Help > About Google Chrome, let the update check finish, and select Relaunch if offered. Chrome installations on Linux use their package manager instead.
Clearing Discord’s cache deletes its cached files; preserve any usable signed-in session elsewhere before proceeding. Quit the Windows or Mac desktop app, clear its cache at %appdata%/discord/Cache on Windows or ~/Library/Application Support/discord/Cache on Mac, then reopen Discord. Use this for a frozen login interface, not as a repair for the credential itself.
Check Discord’s official status page for active incidents when authentication requests keep failing. If authentication or API availability is affected, retry after service recovery. Replacing a credential is not the next step for a service outage.
Report a persistent passkey failure
Record the exact error, the steps that reproduce it, your Discord client or browser version, operating system, and passkey provider. Open Discord Support and select Submit a request to report the failure. Do not include passwords, backup codes, or private credentials.
If you cannot use any enrolled authentication method, follow Discord’s account recovery instructions. Support cannot bypass MFA or manufacture replacement backup codes.
Frequently Asked Questions
What if you forgot your Google Password Manager PIN?
On a non-Android computer where you previously used these passkeys, open Chrome and select More > Passwords and autofill > Google Password Manager > Settings > Change Google Password Manager PIN. Authenticate, enter the replacement PIN, and select Confirm. The option may be absent for a different account or an unauthorized device; Android uses its device screen lock instead.
Can you change a YubiKey PIN that you still know?
Yes, connect a supported FIDO2 key and open Passkeys in desktop or Android Yubico Authenticator. Enter the current PIN and select Unlock > Change PIN. Enter the current PIN and the new PIN twice, then select Save. This procedure requires the current PIN.
Why does a new YubiKey fail when you tap it with NFC?
Some NFC-capable YubiKeys ship with NFC temporarily disabled. Connect the new key to a powered USB port for at least three seconds, then retry NFC.
Can you troubleshoot Discord passkeys in a mobile browser?
Discord explicitly does not support mobile-browser use. Use the Discord mobile app or a supported desktop browser instead. Your passkey provider can require a newer operating system than Discord itself.
Why does Discord’s login QR code expire before you scan it?
Discord login QR codes last two minutes. Refresh an expired code and scan the new one with your already signed-in Discord mobile app. A compatible Camera app can also start the login handoff.
Can Siri open your saved Discord credentials?
On a Siri-enabled iPhone, activate Siri and say Show my passwords. Authenticate, then inspect the Discord entry in Passwords. This opens credential management and still requires authentication.