create github account without phone number github account without phone number does github require phone number

Create a GitHub account without a phone number

Adrian Maverick · · 9 min read

No. GitHub's own documentation lists two things you need to start: a personal account and a verified email address. A phone number only comes up if you choose text messages (SMS) for two-factor authentication, and GitHub recommends an authenticator app over SMS anyway.

Everything below comes from GitHub Docs, checked on November 17, 2026.

What GitHub asks for when you sign up

GitHub's account creation guide says: "To get started with GitHub.com, you need to have a personal account and a verified email address." It also says that "during sign up, you'll be asked to verify your email address." The guide does not mention a phone number at any step.

You can also sign up with a Google or Apple account. GitHub calls these "the supported social login providers." If you'd rather not link either one, use the regular email sign-up.

How to create a GitHub account with just an email

  1. Go to github.com/signup in a browser.
  2. Follow the prompts to choose your account details. Your username becomes your public identity on GitHub, so pick one you're happy to have on every commit and profile link.
  3. Verify your email address when GitHub asks you to. If you need to resend the email later, go to Settings, then Emails in the "Access" section, and click Resend verification email.
  4. Click the link in GitHub's email within 24 hours. GitHub's troubleshooting page says "the verification link expires after 24 hours," after which you can request a new one.
  5. Set up two-factor authentication with an app (next section). GitHub "strongly" recommends 2FA for every account.

Two email rules worth knowing before you start:

  • Disposable addresses don't work. GitHub says: "You cannot verify email addresses from disposable email address services." Use a real, long-term inbox.
  • The noreply address is for commits, not sign-in. GitHub offers a noreply address to keep your email out of your commit history, but it "does not replace the need for a valid account email address."

If sign-up fails with "This email can't be used" or "We couldn't create your account," GitHub suggests a different browser or clearing cookies, disabling extensions, trying another device and network, or waiting and trying again. For "This email can't be used," it also suggests a different email address or domain.

Two-factor authentication without a phone number

This is where most people get stuck. Since March 2023, GitHub has required 2FA for users who contribute code, rolled out in groups. If your account is selected, you get an email and a 45-day window to enroll.

The good news is in GitHub's mandatory 2FA page: being selected "does not mean you have to provide GitHub with your phone number. You only have to provide your phone number if you use SMS for 2FA."

GitHub's first 2FA method must be one of two things: a TOTP app or SMS. TOTP stands for time-based one-time password, the six-digit codes an authenticator app generates. GitHub "strongly" recommends TOTP and says it is more reliable than SMS, "especially for locations outside the United States."

Set up 2FA with an authenticator app

From GitHub's 2FA setup guide:

  1. Install a TOTP app on your phone or computer. GitHub is "app-agnostic," so any app that supports TOTP works.
  2. Open Settings, then Password and authentication in the "Access" section.
  3. Click Enable two-factor authentication.
  4. Scan the QR code with your app. If you can't scan it, click setup key and type the code into your app by hand.
  5. Type the six-digit code from the app into the field under "Verify the code from the app."
  6. Download your recovery codes under "Save your recovery codes," store them somewhere safe, then click I have saved my recovery codes.

You don't need a phone for this at all. GitHub says TOTP apps "can be downloaded to your phone or desktop," and for people who don't want an app on a mobile device, it recommends KeePassXC on desktop or the 1Password browser extension.

After setup, GitHub runs a 28-day check up period. Sign in with 2FA once during those 28 days and you're done. Otherwise GitHub will ask you to perform 2FA on the 28th day.

Add backup methods after the app

Once your TOTP app is set up, you can add more ways to sign in. None of them need a phone number:

Method What it is Needs a phone number?
TOTP app Six-digit codes from an authenticator app on phone or desktop No
Passkey Signs you in "with a single step," covering password and 2FA No
Security key A WebAuthn hardware key, used with your password No
GitHub Mobile Push approval in the GitHub app, using public-key cryptography No
SMS Codes by text message, only in supported countries Yes

Passkeys, security keys and GitHub Mobile can only be added after you've set up TOTP or SMS. GitHub says it doesn't support passkeys or security keys as a primary method yet, because "they are easy to lose and do not support sync across a wide enough range of devices."

Why GitHub doesn't want you on SMS

GitHub's own warning is blunt: "SMS is susceptible to interception, does not provide resistance against phishing attacks, has unreliable deliverability, and is not supported in all countries."

SMS 2FA only works in the countries on GitHub's supported list. If yours isn't there, you have to use a TOTP app. Organizations and enterprises can also block content access for members who use SMS 2FA. So even if you have a number, an authenticator app is the safer default.

What your email does for your GitHub account

With no phone number on file, your email does a lot of work:

  • Password resets go to your email.
  • New-device checks. If you don't use 2FA, GitHub may send a device verification code to your email the first time you sign in from a new browser or computer. The code "is valid for one hour." GitHub skips this check once 2FA is on, or when you sign in with a passkey.
  • Account recovery. If you lose your 2FA app and your recovery codes, GitHub sends a one-time password to your email as the first step of recovery.

That's why GitHub says email verification alone "does not count as 2FA." In its words: "If an attacker has access to your email inbox, they can reset the password for your account and pass the email device verification check." Protect the inbox with its own 2FA.

How to stay recoverable without a phone

GitHub's warning about lost 2FA is clear: Support "will not be able to restore access to accounts with two-factor authentication enabled" if you lose your 2FA credentials and your recovery methods. Set these up early, from GitHub's recovery methods guide:

  • Recovery codes. You get 16 single-use codes. Find them under Password and authentication, next to "Recovery codes," and Download, Print or Copy them.
  • TOTP app backups. Most authenticator apps can back up your codes, so a lost device doesn't mean lost access.
  • SSH keys. An SSH key of type "authentication" can be used to verify your identity during recovery.
  • Personal access tokens. A token with the "repo" scope can be used the same way.
  • A second method. A passkey or security key gets you in if your TOTP app is gone.

If you lose all of these, GitHub says "you have permanently lost access to your account," though you can unlink your email from the locked account and use it on a new one.

Frequently asked questions

Does GitHub require a phone number?

No. GitHub's documentation says you need a personal account and a verified email address. A phone number is only needed if you pick SMS as your two-factor method.

Can I use GitHub 2FA without a phone?

Yes. You can run a TOTP app on your computer instead. GitHub recommends KeePassXC on desktop or the 1Password browser extension for people who don't want a mobile app, and any app that produces RFC 6238 codes works.

Can I add a passkey or security key instead of an authenticator app?

Not as your first method. GitHub requires TOTP or SMS first, then lets you add passkeys, security keys and GitHub Mobile as extra methods.

Can I remove my phone number from GitHub?

GitHub's docs say you can reconfigure your 2FA settings without turning 2FA off entirely, which keeps your recovery codes and your membership in organizations that require 2FA. That lets you move from SMS to a TOTP app without starting over.

Can I sign up for GitHub with a temporary email?

No. GitHub says it cannot verify addresses from disposable email services, and your account email is how you reset your password and recover your account.

Pick an email you'll keep for years

On GitHub, your email is the recovery path: password resets, new-device codes and the first step of 2FA recovery all go there. Use an address you control for the long term, with no phone number tied to it. If your current inbox needs a number, see how Gmail and Outlook handle it.

Secria Mail sign-up is a name, the address you want and a password, with no phone number and no card. You save a 12-word recovery phrase at sign-up, so getting back into your inbox doesn't depend on a number either. The free plan includes 2 aliases, so GitHub can get its own address.


GitHub doesn't need your number, and neither does your email: create a free Secria address.

Secria fact-checks every post against primary sources. Spotted something wrong or out of date? Email hq@secria.me and we will correct it.