How to Add SSH Keys to GitHub Account

Add SSH Keys to GitHub is one of the most secure and efficient ways to authenticate your system with your repositories. Instead of typing your username and password every time you push or pull code, SSH keys allow passwordless authentication between your computer and GitHub. This improves both workflow efficiency and account safety, making it an essential setup for developers managing multiple repositories.

In this guide, you’ll learn everything about SSH keys — from generating them to adding them to GitHub and testing the connection. By the end, you’ll be able to securely connect Git using SSH, ensuring fast, reliable, and secure code deployment across your projects.

What Are SSH Keys and Why Do They Matter?

SSH keys are cryptographic credentials that let your computer prove its identity to servers without using a password. They consist of two parts — a private key (stored securely on your device) and a public key (shared with platforms like GitHub).

When you add SSH Keys to GitHub, you establish a trusted connection, eliminating repeated password prompts. Unlike HTTPS, SSH authentication uses encryption-based validation, making it more secure and efficient. It’s also ideal for automation, CI/CD pipelines, and working with private repositories.

Steps to Add SSH Keys to GitHub Account

Setting up SSH keys involves generating a new key pair, adding it to your local SSH agent, and linking it to your GitHub account. Follow these simple steps to complete the setup.

Step 1 – Generate a New SSH Key Pair

Open your terminal and use the following command to create a new SSH key:

ssh-keygen -t ed25519 -C "your_email@example.com"

If your system doesn’t support ed25519, you can use RSA instead:

ssh-keygen -t rsa -b 4096 -C "your_email@example.com"

When prompted, specify the file path (default: ~/.ssh/id_ed25519) and optionally add a passphrase for extra protection. Once complete, two files are created — a private key (id_ed25519) and a public key (id_ed25519.pub). The public key is what you’ll later add to GitHub to enable secure access.

Step 2 – Add Your SSH Key to the SSH Agent

Next, start the SSH agent and add your private key so your system can use it automatically during Git operations. Run the following commands:

eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_ed25519

This step ensures your SSH key is available for authentication without manual input.
For Windows users, you can perform the same using Git Bash or PowerShell with similar commands. Once added, your system is ready to connect securely to GitHub.

Step 3 – Add the SSH Key to Your GitHub Account

Now that your SSH key is ready, it’s time to add SSH Keys to GitHub.
First, copy the public key content using this command:

cat ~/.ssh/id_ed25519.pub

Log in to your GitHub account and navigate to Settings → SSH and GPG Keys → New SSH Key.
Give your key a recognizable title — for example, “Work Laptop” or “Home PC.”
Paste the copied key into the “Key” field and click Add SSH Key.

Once saved, your GitHub account recognizes your device as a trusted source, allowing secure Git operations without asking for a password every time.

Step 4 – Test the SSH Connection

To confirm that your setup works correctly, run the following command in your terminal:

ssh -T git@github.com

If everything is configured properly, you’ll see a message like:

“Hi username! You’ve successfully authenticated, but GitHub does not provide shell access.”

If you encounter a “Permission denied” message, double-check that your public key is correctly added to GitHub and your SSH agent is running. Successfully establishing this connection ensures your key is active and valid.

Step 5 – Use SSH for Git Operations

Once you’ve successfully added SSH Keys to GitHub, you can start using SSH for cloning, pulling, and pushing repositories. For example:

git clone git@github.com:username/repo.git

If you previously used HTTPS, switch your remote URL to SSH using:

git remote set-url origin git@github.com:username/repo.git

This switch makes your workflow passwordless and more secure. All future Git commands — like git push or git pull — will authenticate automatically using your SSH key.

Troubleshooting SSH Key Issues

Sometimes, SSH key setups can fail due to permission or configuration errors.
If you see “Permission denied,” ensure your private key has the correct permissions:

chmod 600 ~/.ssh/id_ed25519

You can also debug using:

ssh -vT git@github.com

This command shows detailed output to help identify issues like missing keys or incorrect file paths. If problems persist, try regenerating and re-adding your key to GitHub.

Conclusion

Adding SSH keys to GitHub improves security, simplifies authentication, and creates a faster workflow for developers. Instead of typing credentials repeatedly, your SSH setup ensures smooth and encrypted communication with GitHub servers.

Once you add SSH Keys to GitHub, you can safely access, manage, and automate repository operations from any trusted device — ensuring a secure and efficient development environment.