GitHub username generator

Get a GitHub username that recruiters can read and teammates can type. Describe your name, stack or project, and the generator returns developer handles that follow GitHub's rules: up to 39 characters, only letters, numbers and single hyphens. Below are 120 ideas, from professional names to tiny handles and open-source project names.

1 credit per search

Try an idea

GitHub username ideas

Every handle below uses only letters, numbers and single hyphens and stays within 39 characters.

Professional

  • maya-codes
  • jlee-dev
  • priya-builds
  • sam-okafor
  • dana-ruiz-dev
  • tomas-k-eng
  • leah-writes-code
  • arjun-mehta
  • nina-park-ml
  • ben-carter-ops
  • sofia-lin-data
  • omar-haddad-dev
  • grace-ng-sre
  • felix-weber
  • hana-sato-web
  • dev-ravi-iyer
  • chloe-martin-ux
  • kwame-asante
  • ines-costa-dev
  • lucas-moreau
  • ellie-brooks-qa
  • ryan-tan-infra
  • zara-ali-codes
  • noah-fischer-io
  • meera-rao-dev
  • jonas-berg
  • amelia-hart-js
  • victor-nunez
  • tara-quinn-sec
  • ethan-cole-api

Short

  • kxn
  • rho-io
  • zvk
  • mjl
  • ark-io
  • tly
  • qrv
  • vex-dev
  • oza
  • nyx-io
  • jxo
  • kit-sh
  • lumo
  • pyx
  • brk-dev
  • ezra-x
  • dlt
  • rnx
  • oko
  • vyn
  • ido-io
  • fjx
  • yel-dev
  • qbit
  • axl
  • mox-io
  • tzk
  • zeo
  • wyn-dev
  • hix

Hacker & fun

  • null-pointer-pam
  • segfault-sam
  • rubber-duck-rita
  • off-by-one-otto
  • sudo-sandwich
  • git-push-gwen
  • merge-conflict-max
  • stack-trace-stan
  • regex-wrangler
  • ctrl-z-zoe
  • 404-brain-found
  • kernel-panic-kai
  • cache-miss-cleo
  • infinite-loop-lu
  • semicolon-sid
  • byte-me-bob
  • hotfix-hailey
  • yaml-yeller
  • bit-flip-billie
  • lambda-larry
  • heap-of-hugo
  • dev-null-diva
  • bug-whisperer
  • refactor-rae
  • async-awaits-al
  • localhost-lou
  • curl-up-cora
  • ship-it-shay
  • race-condition-rex
  • tabby-the-linter

Open-source project

  • tiny-lint
  • quick-parse
  • envy-config
  • logline
  • slim-router
  • tidy-json
  • fastglob-lite
  • mini-queue
  • patchwork-cli
  • cron-buddy
  • yaml-tidy
  • tiny-cache
  • md-preview
  • shellkit
  • color-tokens
  • pocket-db
  • retry-wrap
  • emoji-picker-js
  • dotfile-sync
  • port-finder
  • schema-guard
  • icon-forge
  • test-tamer
  • git-tidy
  • feed-reader-go
  • typo-hunter
  • snap-diff
  • auth-lite
  • task-runner-rs
  • docs-garden

GitHub username rules

GitHub's documentation sets a few rules for usernames. Every idea on this page and every name the generator returns follows them.

Up to 39 characters

A GitHub username can be at most 39 characters long. That is plenty for a first and last name with a role, such as ellie-brooks-qa. Shorter is still better: your username appears in every clone URL, every commit and every mention, so a handle under 15 characters saves you typing for years.

Letters, numbers and single hyphens only

You can use letters, numbers and hyphens. Underscores, periods, spaces and other symbols are not allowed. If your name on other sites uses an underscore or a dot, swap it for a hyphen here: jane_doe becomes jane-doe, and j.doe becomes j-doe or jdoe.

No hyphen at the start or end

A username cannot begin or end with a hyphen. Names such as -maya or maya- are rejected. Put the hyphen only between two words or between a name and a role, as in maya-codes.

No consecutive hyphens

Two hyphens in a row are not allowed, so maya--codes fails. Use one hyphen to separate words. If you want a visual break between three parts, a single hyphen between each part works: tara-quinn-sec.

How to pick a good GitHub username

Your GitHub username ends up on your résumé, in your portfolio links and in other people's code. Choose it as you would choose a work email address.

Use your real name if you want to be hired

Recruiters and hiring managers often open a GitHub link straight from a CV. A handle built from your name, such as sam-okafor or jonas-berg, connects your code to you without explanation. If your full name is taken, add a role suffix like -dev, -eng or -data before you reach for random numbers.

Keep it lowercase and easy to dictate

Lowercase handles look tidy in URLs and command lines. Avoid strings that are hard to say on a call, such as long runs of consonants or a mix of the letter l and the number 1. Test it by reading it aloud to a friend and asking them to type it.

Match the handle you use elsewhere

Developers find each other across GitHub, package registries, forums and social sites. Using the same handle on all of them makes you easy to look up and easy to credit. Before you settle, search for the name on the other sites you use and pick a version that is free on most of them.

Save jokes for side accounts and organizations

A handle like segfault-sam is memorable and fine for hobby work. For a profile you will show employers, a pun can read as unserious or date quickly. Many developers keep a plain personal handle and give the fun name to an organization, a bot or a side project.

5 tips for choosing your GitHub handle

Think about clone URLs

Your username sits in front of every repository name in a clone URL. A short handle keeps those paths readable when you paste them into docs, issues and README files.

Leave the stack out of your personal name

A suffix such as -js or -rails ties you to one technology. If you might move from frontend to data work, a neutral role such as -dev or -codes ages better.

Name projects for what they do

For an open-source project or organization, describe the job in two words: tidy-json, retry-wrap, port-finder. People search for the problem they have, so a plain name helps them land on your repository.

Avoid birth years and dates

Numbers such as a year make a handle look like a fallback and reveal personal details. If you need a number to make a name unique, choose one that means something only to you.

Check how it looks in a mention

Type the handle with an @ in front, the way teammates will tag you in a pull request. If it reads clearly in a sentence, it will work in code reviews, issue threads and commit messages too.

Want names made for yours? Describe what you're naming and Nomi finds names that fit.

GitHub username questions

No. GitHub usernames allow only letters, numbers and single hyphens. If you use an underscore or a period on other platforms, replace it with a hyphen or remove it. For example, maya_lee becomes maya-lee or mayalee. Every idea on this page already follows that rule, so you can use any of them as they are.

Add a short role or field to the name, such as -dev, -eng, -data or -ux, or use your middle initial. These keep the handle readable and professional. Avoid adding long strings of numbers. You can also type your name and stack into the generator and get a list of fresh variations to try.

It helps. When your GitHub handle, email address and professional profiles share the same name pattern, recruiters and collaborators can connect them quickly. It also makes your work easier to credit in talks and blog posts. Exact matches are not required, but a recognizable pattern across all of them is worth aiming for.

Give organizations and projects the same kind of handle as the ideas on this page. Describe what the project does in one to three words, keep it lowercase and join words with single hyphens. Check that the name is free on the package registry you publish to, so users can install it under the same name.

Yes. Every name it returns is checked against the rules: up to 39 characters, only letters, numbers and single hyphens, no hyphen at the start or end and no two hyphens in a row. It cannot tell you whether a name is free, so search for it on GitHub before you sign up.

Nametastic is an independent name generator and is not affiliated with GitHub.

More name generators

Browse all 314 generators →