Summarize this article with:
Every developer remembers their first clone. That moment when a remote project suddenly exists on your machine, ready to explore.
Learning how to clone a Git repository is one of the first real steps in any software development journey.
Whether you’re joining a team project, contributing to open source, or downloading code from GitHub, cloning creates your local copy of the entire project history.
This guide walks you through the complete process. You’ll learn HTTPS and SSH authentication, cloning specific branches, creating shallow clones for large repositories, and fixing common errors.
Five minutes from now, you’ll have the skills to clone any repository with confidence.
How to Clone a Git Repository
Cloning a Git repository is the process of creating a local copy of a remote repository on your computer.
This gives you full access to the project’s source code, commit history, and branch structure.
Developers need this when joining existing projects, contributing to open source software, or setting up a backup of their codebase.
This guide covers 6 steps requiring 2-5 minutes and basic familiarity with the command line.
Prerequisites
Before you start, make sure you have these ready:
- Git 2.x or later installed on your system (here’s how to install Git if you haven’t)
- Terminal access (macOS/Linux) or Git Bash on Windows
- The repository URL you want to clone (HTTPS or SSH format)
- Authentication credentials for private repositories (personal access token or SSH key)
- Read access to the target repository
Time estimate: 2-5 minutes depending on repository size.
Skill level: Beginner.
Step 1: How Do You Find the Repository URL to Clone?
The repository URL is located on the main page of any code hosting platform like GitHub, GitLab, or Bitbucket.
Click the green “Code” button, select HTTPS or SSH, and copy the URL to your clipboard.
Action
- Navigate to repository page: Open the project in your browser
- Locate Code button: Green button near the top right of the file list
- Select URL type: Choose HTTPS (easier) or SSH (more secure)
- Copy URL: Click the clipboard icon next to the URL string
Purpose
Getting the correct URL format prevents authentication errors during the clone process.
HTTPS works immediately; SSH requires a configured key pair on your machine.
Step 2: Where Do You Run the Git Clone Command?
Open your terminal application and navigate to the directory where you want the cloned project folder to appear.
The git clone command creates a new folder automatically, so pick a parent directory like “Projects” or “Code”.
Action
- Open terminal: Terminal (macOS), Git Bash (Windows), or any Linux shell
- Change directory: Run
cd ~/Projectsor your preferred location - Verify location: Run
pwdto confirm you’re in the right spot
Purpose
Choosing the right working directory keeps your projects organized.
Took me forever to figure out why I had random repo folders scattered everywhere. Pick one location and stick with it.
Step 3: What Is the Syntax for Git Clone?
The basic git clone syntax is git clone [repository-URL], which downloads all files, branches, and commit history from the remote server to your local machine.
Action
- Basic command:
git clone https://github.com/username/repo.git - With custom folder:
git clone [URL] my-folder-name - Expected output: “Cloning into ‘repo-name’…” followed by download progress
Common Flags
--depth 1creates a shallow clone with only the latest commit--branch [name]clones a specific branch instead of the default--single-branchfetches only one branch’s history
Purpose
Understanding the command structure lets you customize the clone for your specific needs.
Most developers just use the basic syntax. The flags matter when you’re dealing with massive repositories or slow connections.
Step 4: How Do You Clone Using HTTPS Authentication?
HTTPS cloning prompts for credentials when accessing private repositories.
You’ll need your username and a personal access token (not your password).
Action
- Run command:
git clone https://github.com/username/private-repo.git - Enter username: Your GitHub/GitLab username when prompted
- Enter token: Paste your personal access token as the password
Purpose
HTTPS works through firewalls and requires no local key setup. Best for quick access or shared machines.
Step 5: How Do You Clone Using SSH Authentication?
SSH cloning uses cryptographic keys instead of passwords, eliminating repeated credential prompts.
Requires a configured SSH key pair linked to your account.
Action
- Verify SSH setup: Run
ssh -T git@github.comto test connection - Run command:
git clone git@github.com:username/repo.git - Accept fingerprint: Type “yes” if prompted about host authenticity
Need to set up keys first? Learn how to add an SSH key to GitHub.
Purpose
SSH is more secure and faster for frequent operations. One-time setup, permanent convenience.
Step 6: How Do You Clone a Specific Branch?
By default, git clone fetches all branches but checks out the default branch (usually main or master).
Use the --branch flag to start on a different branch immediately.
Action
- Command:
git clone --branch develop https://github.com/user/repo.git - Short flag:
-bworks the same as--branch - Result: Working directory contains the specified branch’s files
Purpose
Saves time when you need a feature branch or release tag. Skip the extra branch switching step.
Step 7: How Do You Clone Into a Custom Directory?
Add a folder name after the URL to override the default directory name.
Action
- Command:
git clone https://github.com/user/repo.git my-project - Path options: Relative path (
./folder) or absolute path (/home/user/folder) - Result: Repository contents appear in “my-project” instead of “repo”
Purpose
Useful when repo names are generic or you’re cloning multiple forks of the same project.
Step 8: How Do You Create a Shallow Clone?
Shallow clones download only recent commits, reducing clone time and disk usage.
Perfect for large repositories or CI/CD pipelines where history doesn’t matter.
Action
- Depth 1:
git clone --depth 1 https://github.com/user/repo.git - Custom depth:
--depth 10gets the last 10 commits - Combined flags:
git clone --depth 1 --single-branch --branch main [URL]
Purpose
A full clone of the Linux kernel takes gigabytes. A shallow clone? Under 200MB.
Teams using continuous integration rely on this for faster build times.
Verification
Confirm your clone worked correctly with these checks:
- List contents:
ls(macOS/Linux) ordir(Windows) shows the new folder - Enter directory:
cd repo-name - Check status:
git statusconfirms you’re on a branch with a clean working tree - Verify remote:
git remote -vdisplays the origin URL
If all commands return expected output, your local copy is ready.
Troubleshooting
Permission denied (publickey)
Cause: SSH key not found or not added to your account.
Fix:
- Test connection:
ssh -T git@github.com - Add key to agent:
ssh-add ~/.ssh/id_rsa - Verify key exists in account settings under SSH keys
Repository not found
Cause: Wrong URL, typo, or insufficient permissions.
Fix:
- Double-check spelling and case sensitivity in the URL
- Confirm repository visibility (public vs private)
- Verify your token has
reposcope for private access
Clone speed is slow
Cause: Large repository or network limitations.
Fix:
- Use shallow clone:
--depth 1 - Add
--single-branchto skip other branches - Clone during off-peak hours if using shared bandwidth
Authentication failed
Cause: Expired token or wrong credentials.
Fix:
- Generate a new personal access token with correct permissions
- Clear cached credentials:
git credential-cache exit - For HTTPS, use token (not password) when prompted
Related Git Operations
After cloning, you’ll likely need these commands:
- git pull updates your local copy with remote changes
- git fetch downloads updates without merging them
- Creating a new branch for your feature work
- Pushing changes to GitHub when you’re ready to share
- Resolving merge conflicts when branches diverge
Understanding version control fundamentals makes all of these operations easier to grasp.
FAQ on How To Clone A Git Repository
What is the difference between git clone and git pull?
Git clone creates a brand new local copy of a remote repository, including all files and commit history.
Git pull updates an existing local repository with changes from the remote server. Clone once at the start; pull regularly to stay current.
Can I clone a private repository?
Yes, but you need proper authentication.
Use HTTPS with a personal access token or SSH with a configured key pair. Your account must have read access to the repository. Without credentials, you’ll get a “repository not found” error.
How do I clone a repository to a specific folder?
Add your desired folder name after the URL: git clone [URL] my-folder-name.
This overrides the default behavior of creating a folder matching the repository name. Works with both relative and absolute paths.
What is the difference between HTTPS and SSH cloning?
HTTPS requires username and token for each authenticated operation. SSH uses cryptographic keys stored locally, eliminating repeated prompts.
HTTPS works through most firewalls; SSH is faster for frequent operations after initial setup.
How do I clone only one branch?
Use git clone --single-branch --branch [branch-name] [URL].
This downloads only the specified branch’s history, reducing clone time and storage. Useful for large projects where you only need one feature branch or release.
Can I clone a repository without the commit history?
Yes, use a shallow clone with git clone --depth 1 [URL].
This fetches only the latest commit, dramatically reducing download size. Perfect for build pipelines or when you just need the current code.
Why is my git clone so slow?
Large repositories with extensive history take longer. Try shallow cloning with --depth 1 or add --single-branch to skip other branches.
Network speed and server load also affect clone times significantly.
How do I clone a forked repository?
Clone your fork the same way as any repository using its URL.
After cloning, add the original project as an upstream remote with git remote add upstream [original-URL] to fetch future updates.
What happens if I clone a repository twice?
Git creates a second folder (or fails if the folder name exists). Each clone is independent.
To update an existing clone instead of duplicating, use git pull from inside the existing directory.
Can I clone a repository from GitLab or Bitbucket?
Absolutely. The git clone command works with any Git hosting platform.
Just copy the repository URL from GitLab, Bitbucket, Azure DevOps, or any other service. The process is identical to cloning from GitHub.
Conclusion
You now know how to clone a Git repository using both HTTPS and SSH authentication methods.
The clone command is your entry point into any project’s source code and commit history.
Whether you’re downloading a public project or accessing a private repository, the process stays consistent across GitHub, GitLab, and Bitbucket.
Shallow clones and single-branch options give you flexibility when dealing with large codebases.
Master this skill and you’ve unlocked the foundation of source control management.
From here, explore branching strategies, committing changes, and Git workflows to level up your development environment.
The terminal is now your workspace. Start cloning.
Many of his resources are available on various design marketplaces and for free on Codepen.
Over the years, he's worked with a range of clients and contributed to design publications like Design Your Way, Designmodo, WebDesignerDepot, WPDean, Speckyboy, and Slider Revolution among others.
- What Happens When You Offload an App on iPhone - May 9, 2026
- How to Use Digital Wellbeing on Android - May 8, 2026
- Why Buyers Trust a Well-Built Data Room - May 7, 2026
