SSH Keys with Multiple GitHub Accounts

Craig Russell
Aug 10, 2016 · 6 min read

This article explains how to manage multiple SSH keys for different accounts so that you can access multiple accounts and projects, each with different credentials.

Image for post
Image for post
So many keys (Image attribution:

These instructions focus on Mac OSX and specifically; be warned if you are using another OS or a different hosted git repository.

If all goes well, you’ll likely be up and running within 30 minutes if you follow this guide.

Who Has Multiple SSH Keys?

What’s the Problem with Multiple SSH Keys?

When you attempt to pull or push code to a repo, the system will attempt to pick an SSH key to use and it won’t always match up. Often, it will just try the first key and for some projects you’ll see authentication problems as it is trying to connect with the wrong user.

The Solution

  1. Register the correct SSH keys with the correct account
  2. Create a git config file

The first two steps are the standard process; create an SSH key locally on your machine and then copy the public key information into your account settings.

The ✨magic✨ happens when you create the git config file in step 3.

Backup Existing Keys

Creating SSH Keys

Viewing Existing Keys

If you’ve followed SSH key creation steps before, you’ll likely have a file called id_rsa and another called; these are your private and public keys, respectively.

If you already have all of the SSH keys you want, you can skip the creation steps. Otherwise, read on for instructions for creating one or more new keys.

Creating a New SSH Key

ssh-keygen -t rsa -b 4096 -C “

You’ll be prompted to “Enter file in which to save the key”. You should use the standard id_rsa prefix followed by a descriptive name for your key.

So let’s assume you need to make accounts for a personal SSH key and a work one.

  1. Call the first key id_rsa_personal
  2. Repeat the process again to create id_rsa_work

⚠️ Note that the prompt expects you to enter the path to the file as well; failing to add this will create the file in the current terminal directory which may not be what you want.

The final step is to secure the keys with a passphrase. Do so.

Registering your new SSH Keys

eval "$(ssh-agent -s)"

Once running, you can then add your new keys. Repeat the following command for all new keys you have added, substituting the correct path to the private key. For example:

ssh-add ~/.ssh/id_rsa_personal

Add your SSH Keys to

To copy the public key to the clipboard, run the following, substituting for the correct filename:

pbcopy < ~/.ssh/

⚠️ Note, you want to be really careful that you match up the correct key with the correct GitHub account otherwise you are in for a world of confusion. You see now why I recommend descriptive names for them?

When signed in to (with the right account!) click on your avatar and choose settings. Choose SSH and GPG Keys from the menu, and click the New SSH Key button.

Image for post
Image for post
Registering an SSH Key on

Give it a descriptive title and then paste the contents of your clipboard (containing your public key information).

Once done, you’d want to login to your other account and register the other public key. Repeat this for as many different accounts as you are managing.

Create a Git Config File

A git config file lives at ~/.ssh/config
If the config file doesn’t yet exist, go ahead and create it:

touch ~/.ssh/config

Here is an example from my ~/.ssh/config file

PreferredAuthentications publickey
IdentityFile ~/.ssh/id_rsa_personal
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_rsa

Note that, although subtle, the first and fourth lines differ for each entry. By defining each account with a different Host value, you can specify which git URLs use which SSH key.

Above, I specify that:

  • any git URL that uses should use id_rsa_personal
  • any git URL that uses should use my id_rsa key.

I have an SSH key for personal projects, and another key for everything else. You might need to add more than two entries into your config if you have additional accounts to manage.

Cloning Projects

When cloning a project from GitHub using SSH, the URL format is

You can replace with your custom specified Host from your config, depending on which account you are wanting to use.

For example, let’s look at this project from GitHub.

Image for post
Image for post

GitHub tells us that we should use this URL:

To use our personal SSH key, we remember our setting from the ~/.ssh/config file:

PreferredAuthentications publickey
IdentityFile ~/.ssh/id_rsa_personal

which tells us to use instead of Therefore, we can use that URL instead to clone the project using the personal SSH key. For example:

// uses standard SSH key
git clone
// uses personal SSH key
git clone


It is undoubtedly a little tricky to setup but now that you’ve done it, you won’t have to think too much about it again; just remember to clone the url with the correct format depending on which account you want to use.

Image for post
Image for post
Tell a friend about this article. Or just scream into a tin can. (Image attribution:

Then when you have to repeat the process again in a few months, I’ll see you right back here! Perhaps do us both a favour. “Recommend” this post using the big ol’ heart button and share this blog post; you’ll find it easier again in future and you’ll be helping others to find it.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store