Pick a username you won't regret in five years

Your GitHub username is the name that appears on every repository you create, every contribution you make, and every project you share with employers or collaborators. Unlike an email address, you cannot change it without losing all the history attached to it — your contributions, your stars, your followers. Choose something professional enough that you would not be embarrassed to put it on a resume, but specific enough that it actually describes who you are or what you do.

The simplest rule: use your real name or a close variation of it if it is available. If your name is taken, add a number or a word that describes your field. Avoid inside jokes, slang, or references that made sense last year but will confuse people next year. GitHub is not a social media platform where you reinvent yourself every few months — it is a permanent record of your work.

Key Takeaways

  • Your GitHub username is permanent and appears on every project you create, so choose something you would put on a resume.
  • Real names or variations of your real name are the strongest choice because they are memorable and professional.
  • If your name is taken, add a number, year, or field-specific word rather than using slang or inside jokes.
  • Check that your chosen username is not already in use on other platforms where you want to build a presence.
  • Avoid usernames with numbers at the end that look like you were the 47th person to try that name.

Start with your real name or a professional variation

Search GitHub for your first name, last name, or full name. If it is available, use it. This is the easiest name for colleagues, employers, and collaborators to remember and find. It also signals that you are serious about your work — you are not hiding behind a persona.

If your exact name is taken, try these variations in order: first name plus last initial (like jsmith), first initial plus last name (like jsmith), or first name plus middle initial. If you have a common name like John Smith, you might try johnsmith1985 (your birth year) or johnsmith-dev (your field). The goal is to stay recognizable while making it unique.

Avoid adding random numbers at the end like johnsmith47 or johnsmith123. These usernames signal that you were not the first person to try that name, and they are harder to remember and type. A number that means something — your graduation year, a significant date — is better than a random sequence, but a descriptive word is better still.

Make it straightforward to spell and pronounce

Your username will be typed into search boxes, spoken aloud in meetings, and written in emails. If someone has to ask you how to spell it, it is too complicated. Avoid replacing letters with numbers (like j0hn5m1th), unusual capitalization, or hyphens in the middle of words unless they serve a real purpose.

If you use a hyphen, use it to separate two words: john-smith is clear, but j-ohnsmith is confusing. GitHub usernames are case-insensitive, so JohnSmith and johnsmith point to the same account, but lowercase is the standard and easier to type.

Check availability across platforms where you want to work

Before you commit to a username on GitHub, search for it on LinkedIn, Twitter, your personal website, and any other platform where you want to build a professional presence. You do not need the same username everywhere, but having a consistent name across platforms makes you easier to find and more memorable.

If your top choice is taken on GitHub but available on other platforms, decide whether consistency matters more than your first choice. Many developers use a slightly different username on each platform because perfect consistency is rare, but try to keep them close enough that someone who knows you can find you.

Avoid usernames that will age poorly

Do not use current slang, memes, or references to trends. A username like covidcoder2020 or skibididev will look dated within months. The same applies to inside jokes with friends or references to shows and games — they will not mean anything to an employer reviewing your GitHub profile in three years.

Avoid usernames that reference a specific technology or framework you are learning right now. pythonprogrammer or reactdev locks you into that identity. If you move to a different language or framework, your username no longer describes what you do. A name based on who you are rather than what you currently know stays relevant.

Keep it short and memorable

Shorter usernames are easier to type, easier to remember, and easier to share verbally. Aim for under 20 characters if you can. If your name is long, use initials or a shortened version. jsmith is better than johnalexandersmith.

Test your username by saying it aloud and having someone else type it from hearing you say it. If they get it wrong, it is too complicated. If you have to spell it letter by letter, consider a simpler option.

Understand GitHub's username rules

GitHub usernames can contain letters, numbers, and hyphens. They must start with a letter or number, cannot end with a hyphen, and cannot have consecutive hyphens. Usernames are 1 to 39 characters long. These are technical limits, not style guidelines — just stay within them.

GitHub reserves certain usernames like admin, api, and support. If you try to create an account with a reserved name, GitHub will reject it and suggest alternatives. This is rare for personal names, but it is worth knowing if you get an unexpected error.

Frequently Asked Questions

Can I change my GitHub username later?

Yes, GitHub allows you to change your username in your account settings. However, your old username becomes available for someone else to claim, and old links to your repositories will break. Changing your username is possible but disruptive, so choose carefully the first time.

Should I use my full name or a shortened version?

Use whatever version you would put on a resume or business card. If you go by John Smith professionally, use johnsmith. If you go by J. Smith, use jsmith. Consistency with how people know you matters more than using your legal full name.

What if my name is very common and every variation is taken?

Add a number that means something to you — your birth year, graduation year, or a significant date. johnsmith1990 is better than johnsmith47 because it is less random. Alternatively, add a descriptor: johnsmith-dev, johnsmith-engineer, or johnsmith-io.

Is it okay to use a nickname instead of my real name?

Only if the nickname is how people actually know you professionally. If your name is Jonathan but everyone calls you Jon, use jon or jonsmith. If you have a nickname that is not widely known, stick with your real name — GitHub is not the place to introduce yourself by a new identity.

Should I include my location or field in my username?

No. Your location and field belong in your GitHub profile bio, not your username. A username like bostondev or pythonprogrammer locks you into that identity and looks dated if you move or change focus. Keep your username about who you are, not where you are or what you currently do.