Posted on 16/11/26 01:05 pm
Reset a GitHub password by email. Lost two-factor access? Use a recovery code, a passkey or security key, or start account recovery with an SSH key or token.
| Option | What you need |
|---|---|
| Recovery codes | One of the codes saved when you set up 2FA |
| Passkey or security key | A registered key or device |
| Fallback SMS | If you added a fallback number |
| GitHub Mobile | If you signed in to the app before |
If none of those work, GitHub offers an account recovery request. It verifies you with something only the owner should have, such as:
GitHub reviews requests, which can take several days. Support cannot simply turn off two-factor without verification.
Organisation owners can remove a locked-out member and invite them again after recovery. They cannot reset your personal two-factor.
GitHub can use a registered SSH key or a personal access token from a computer you still have to help verify you during recovery. Check your machines for keys you added before contacting support.
See GitHub two-factor authentication and GitHub rate limits.
If GitHub Desktop, an IDE or the GitHub CLI is still signed in on one of your computers, that session can help. You may be able to download new recovery codes or add a new two-factor method from a browser that is still logged in. Check every device before starting a formal recovery request, which takes longer.
Recovery messages go to verified emails on the account. Keep at least two verified addresses, including one that is not a work email you could lose when changing jobs.
Use recovery codes, a passkey, or an account recovery request.
Only after verifying you through recovery.
SSH keys, tokens, verified emails or known devices.
Related: GitHub 2FA · GitHub rate limits · GitHub account suspended.
Receive SMS online · Non-VoIP numbers · Temporary phone numbers · Free numbers