GitHub
How to Keep Two GitHub Accounts Apart on One PC with Browser Profiles and Git Settings
Can separate browser profiles keep two GitHub accounts apart?
Yes for the website, and only the website. Chrome Help (read 3 October 2026) says profiles let you keep information such as bookmarks, history, passwords and other settings separate, and it names keeping work and personal accounts apart as a use. Chromium's documentation says profile data such as history, bookmarks and cookies lives in a profile subdirectory of the user data directory, so a github.com sign-in made in one profile stays in that profile.
Git, the GitHub CLI and GitHub Desktop sign in on their own, so a browser profile does not decide which account they use. And GitHub itself recommends one personal account for all your work, so profiles suit legitimate pairs, such as a personal account next to an employer-managed one. See the rules guide.
What does a profile separate, and what does it leave alone?
| Item | Separate per browser profile? | Note |
|---|---|---|
| github.com sign-in | Yes | Cookies live in that profile's own folder |
| The account-switcher list | Per browser | GitHub says it remembers the accounts in your browser |
| Bookmarks, history, saved passwords | Yes | Named on Chrome Help's profile page |
Git credentials, SSH keys, gh sign-in | No | They are set up outside the browser; see the Git section below |
| The computer and its network connection | No | Every profile runs on the same machine |
| Protection from people at your keyboard | No | Chrome Help warns that anyone with your device can switch to another profile |
Firefox offers Containers, which Mozilla describes as lightweight persistent contexts that isolate sites, separating cookies, localStorage, IndexedDB and caches. Its own example is work and personal accounts side by side in one window. Edge and Firefox also have profile features with different menus, so follow each browser's current help page.
How do you set up one Chrome profile per GitHub account?
- Plan the names first. One line per account, for example
Acme - client - GitHub. - Open Chrome, select Profile at the top right, then Add Chrome profile.
- Choose a name, photo and color scheme. Give each account its own color so you can tell the windows apart at a glance.
- Sign in to github.com inside that profile, with only that profile's account.
- Be ready for a check. If the account has no 2FA, GitHub may ask you to verify the new browser profile by email; the sign-in checks guide explains it.
- Repeat for each account. To move between profiles, select Profile and choose one. Check the icon before you act.
- Use the account switcher only inside one profile, for accounts that belong together, such as a personal account and its machine account.
How do you keep Git and the terminal on the right account?
| Need | What GitHub's pages describe |
|---|---|
| A different commit email per project | git config user.email "YOUR_EMAIL" inside the repository, without --global, overrides the global value for that repository only |
| HTTPS | A credential helper, git config --global credential.https://github.com.useHttpPath true, and a dedicated personal access token per account |
| SSH | One key per account, with host entries in ~/.ssh/config and IdentitiesOnly yes; ssh -T git@github.com shows which account a key reaches |
| GitHub CLI | gh auth login for each account, then gh auth switch |
| GitHub Desktop | Sign-in happens through your default browser; the page does not describe two GitHub.com accounts |
GitHub warns that handling two or more accounts makes it likelier you will expose internal code by mistake, so check which account a repository uses before every push. It also says to treat access tokens like passwords.
How should you name, hand over and back up each profile?
| Practice | What to do | Why |
|---|---|---|
| Naming | Account, role and purpose in that order; one color per account | You spot the wrong profile before you click |
| Hand-over | Do not pass on a signed-in profile; add the next person to the organization with their own account | The Terms reserve each login for one person |
| Retiring a profile | Remove it only after access has moved | Chrome Help says removing a profile wipes its bookmarks, history, passwords and other settings from the computer |
| Recovery codes | Under Password and authentication, next to Recovery codes, choose View; download or print the set of 16 and keep it in a password manager | Each code works once, and GitHub says not to share them |
| Tokens | Treat them like passwords and give each an expiration | GitHub recommends an expiration, and says tokens are tied to the user who made them |
| Where profiles live | Chromium lists %LOCALAPPDATA%\Google\Chrome\User Data on Windows and ~/Library/Application Support/Google/Chrome on macOS | Knowing the location helps; a folder copy is no substitute for being able to sign in |
What if something still lands on the wrong account?
- Check the profile icon, then the avatar at the top right of github.com.
Permission to user/repo denied to other-user. The key you push with belongs to an account without access; the owner can add that account as a collaborator.- Commits show another author. GitHub matches the commit's email to an account. Fix the local setting, and add the address to the account you meant.
- A verification email you did not request. GitHub says your password may be compromised: change it now and secure the account.
- Repeated prompts in one profile. GitHub says clearing cookies, or using another browser on the same device, can trigger device verification again. Keep each account in its own profile and avoid wiping its cookies.
When do ordinary profiles stop being enough?
| Sign | What helps |
|---|---|
| The profile list no longer fits in a spreadsheet or in your head | Opening, stopping and organising profiles in bulk |
| Accounts need their own network settings | A proxy per profile; see proxy types explained |
| You are comparing incognito windows, VPNs and profiles | Antidetect browser vs VPN vs incognito |
None of these changes GitHub's rules, and none replaces each person's own account.
Where ADSSPEED fits
ADSSPEED is a desktop app for Windows and macOS that manages many browser profiles in one place. Each profile keeps its own cookies, local data and browser settings, so accounts you own or are authorised to manage can stay signed in side by side without signing each other out. Profiles can be opened, stopped and organised in bulk, a proxy can be set per profile and assigned to many profiles at once, and profile data stays on your own computer. See how to install ADSSPEED on Windows. ADSSPEED is not affiliated with GitHub.
Frequently asked questions
Can I use two GitHub accounts on one computer with different Chrome profiles?
For the website, yes. Chrome Help says profiles keep bookmarks, history, passwords and other settings separate, and Chromium's documentation says profile data such as cookies lives in a profile subdirectory. GitHub still recommends one personal account for all your work, so use this for legitimate pairs such as a personal and an employer-managed account.
How do I use multiple GitHub accounts on the same computer on Windows or Mac?
Use one browser profile per account for github.com, then set up Git separately. GitHub's page on managing multiple accounts has steps for macOS, Windows and Linux: HTTPS with a personal access token per account, or SSH with one key per account in the ~/.ssh/config file, plus a per-repository commit email. The GitHub CLI adds gh auth switch.
Does a browser profile also separate my Git credentials?
No. GitHub's pages show Git over HTTPS, Git over SSH, the GitHub CLI and GitHub Desktop each signing in on their own, so a browser profile does not choose the account they use. Set credentials, keys and the commit email per repository, and test with ssh -T git@github.com.
Will GitHub ask me to verify a new browser profile?
It may. GitHub's device verification page says that when 2FA is not enabled, an unrecognised device can include a new browser or a new browser profile, with a code sent by email. It says GitHub does not ask for this when 2FA is enabled or when you sign in with a passkey.
How do I set a different commit email for each GitHub account?
Run git config user.email with the address inside the repository, without --global, to override your global setting for that repository only. GitHub links a commit to a user by matching the commit's email address to an email address on a GitHub account.
What happens if I delete a Chrome profile that holds a GitHub sign-in?
Chrome Help says removing a profile erases its bookmarks, history, passwords and other settings from the computer. Before you do, make sure you hold the account's 2FA recovery codes, because GitHub Support will not restore a 2FA-protected account if you lose your credentials.
Sources
- Google Chrome Help: Set up a profile (Manage Chrome with multiple profiles)
- Chromium docs: User data directory and profiles
- Mozilla wiki: Contextual Identity Project, Containers
- GitHub Docs: Managing multiple accounts
- GitHub Docs: Personal account management
- GitHub Docs: Verifying new devices when signing in
- GitHub Docs: Switching between accounts
- GitHub Docs: Setting your commit email address
- GitHub Docs: Troubleshooting commits
- GitHub Docs: Testing your SSH connection
- GitHub Docs: Using the GitHub CLI across GitHub platforms
- GitHub Docs: Configuring two-factor authentication recovery methods
- GitHub Docs: Recovering your account if you lose your 2FA credentials
- GitHub Docs: Managing your personal access tokens
Related guides
Run Android devices and browser profiles on your own PC
ADSSPEED manages many browser profiles and Android phone profiles from one app, each with its own device configuration, proxy and automation.