Forking a GitHub project creates your own independent copy of someone else's repository under your account. Click the Fork button in the top-right corner of any public repository, choose your account, and GitHub creates a complete copy with a 'forked from' badge. You can modify your fork freely without affecting the original, and use the Sync fork button to pull in updates from the source project.
What Forking Means and Why It Matters
Forking is one of GitHub's most important features, and it is surprisingly simple. When you fork a repository, GitHub creates a complete copy of that project under your own account. Your fork includes every file, every branch, and the full commit history — but it belongs to you. You can modify it however you want without affecting the original project. The original repository and your fork remain linked: GitHub shows a 'forked from' badge on your copy, and you can use the Sync fork button to pull in updates from the source project whenever you want. Forking is the standard way to contribute to open-source projects — you fork, make your changes, then submit a pull request back to the original. But forks are also incredibly useful for non-technical founders: if you find a template, starter project, or open-source tool built with frameworks used by Lovable, V0, or Replit, you can fork it and customize it for your own needs.
Prerequisites
- A GitHub account (free plan works)
- A public repository you want to fork
- A modern web browser
Step-by-step guide
Navigate to the repository you want to fork
Navigate to the repository you want to fork
Go to github.com and find the public repository you want to fork. You can get there by searching on GitHub, clicking a link someone shared, or browsing GitHub Explore. Make sure you are on the repository's main page — you should see the repository name, the file list, and the README below. In the top-right area, you'll see three buttons: Watch, Fork, and Star. The Fork button shows a number indicating how many other people have already forked this repository.
Expected result: You are on the repository's main page and can see the Fork button in the top-right corner.
Click the Fork button and create your copy
Click the Fork button and create your copy
Click the "Fork" button in the top-right corner of the repository page. GitHub opens a "Create a new fork" page. You'll see your account name listed as the Owner (if you belong to organizations, you can choose one from the dropdown). The repository name field is pre-filled with the original name — you can change it if you want. The description is also pre-filled from the original. Leave the "Copy the main branch only" checkbox checked unless you need other branches. Click the green "Create fork" button at the bottom.
Expected result: GitHub creates the fork and redirects you to your new copy. You see 'forked from original/repository' below the repository name.
Verify your fork and explore the forked-from badge
Verify your fork and explore the forked-from badge
After forking, you land on your new repository page. Just below the repository name at the top, you'll see a small line that says "forked from username/repository-name" — this is the forked-from badge. Click it to go back to the original repository anytime. Your fork has the same files, README, and commit history as the original at the moment you forked it. Any changes you make from here on only affect your copy. The URL of your fork will be github.com/your-username/repository-name.
Expected result: Your fork shows the 'forked from' badge and contains all the same files as the original repository.
Sync your fork with the original project
Sync your fork with the original project
Over time, the original repository may get new commits that your fork doesn't have. To pull in those updates, go to your fork's main page on github.com. If your fork is behind the original, you'll see a banner that says something like "This branch is 3 commits behind original:main." Click the "Sync fork" dropdown button that appears above the file list. Then click the green "Update branch" button. GitHub fetches the latest changes from the original repository and merges them into your fork — all through the browser, no terminal needed.
Expected result: Your fork updates to match the original repository, and the 'behind' message disappears.
Make changes to your fork independently
Make changes to your fork independently
Now that you have your own fork, you can edit files freely. Click on any file, then click the pencil icon to edit it. Make your changes, scroll down, add a commit message, and click "Commit changes." Your edits are saved only to your fork — the original repository is completely unaffected. If you later want to suggest your changes back to the original project, you can open a pull request from your fork to the original by clicking "Contribute" above the file list and then "Open pull request." This is how open-source contributions work.
Expected result: Your edit is saved as a commit on your fork. The original repository remains unchanged.
Complete working example
1# My Forked Project23> Forked from [original-author/project-name]45## What I Changed67- Customized the landing page content8- Updated branding and colors9- Added my own API keys via environment variables1011## Why I Forked This1213I found this open-source template and wanted to build14my own version without affecting the original project.1516## Keeping in Sync1718I use the "Sync fork" button on GitHub to pull19updates from the original repository periodically.2021## Original Project2223See the original at: [link to original repo]2425## Built With2627- React + TypeScript28- Tailwind CSS29- Deployed on VercelCommon mistakes when forking a Project on GitHub
Why it's a problem: Forking when you should clone
How to avoid: If you just need a local copy to examine or run, clone or download the ZIP instead. Fork only when you want your own GitHub-hosted copy to modify independently.
Why it's a problem: Editing the original repository instead of your fork
How to avoid: After forking, make sure the URL in your browser shows your username, not the original author's. The 'forked from' badge confirms you're on your copy.
Why it's a problem: Forgetting to sync your fork with the original
How to avoid: If the original project is actively maintained, click the 'Sync fork' button periodically to pull in bug fixes and improvements.
Why it's a problem: Renaming or restructuring the fork in ways that break the link
How to avoid: GitHub maintains the fork relationship automatically. Avoid deleting and re-creating the repository — this breaks the fork link and you lose the ability to sync or submit pull requests.
Best practices
- Fork open-source templates to get a head start on your own projects
- Keep the 'forked from' badge visible — it gives credit to the original author
- Sync your fork regularly if the original project receives active updates
- Use your fork's README to document what you changed from the original
- Do not commit API keys or secrets to your fork — use environment variables instead
- Fork before customizing any open-source project used with AI tools like Cursor or Replit
- Submit pull requests back to the original if you fix bugs that would help everyone
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
I just forked a GitHub repository. Explain what I can safely change in my fork without breaking anything, and how I should keep it in sync with the original project.
Frequently asked questions
Is forking the same as copying?
Forking is a special kind of copy that stays linked to the original. GitHub tracks the relationship, lets you sync updates, and makes it easy to submit pull requests back. A regular copy (like downloading a ZIP) has none of these features.
Can I fork a private repository?
Only if the repository owner has enabled forking for private repos in their settings. By default, private repositories cannot be forked. You'll need to ask the owner to grant you access or enable the fork option.
Does the original owner know I forked their repository?
The fork count on their repository increases, and your fork appears in their repository's 'Forks' tab. However, they don't receive a notification unless they're watching the repository closely.
Can I delete my fork without affecting the original?
Yes. Deleting your fork only removes your copy. The original repository is completely unaffected. Go to your fork's Settings, scroll to the bottom, and click 'Delete this repository.'
How is forking used with AI tools like Lovable?
When you connect a Lovable project to GitHub, it creates a repository. If someone else built a Lovable project and shared the repo publicly, you can fork it to create your own version and connect it to your own Lovable account or Cursor workspace.
Can RapidDev help me customize a forked repository?
Yes. RapidDev's engineering team frequently helps non-technical founders fork open-source templates and customize them — including updating branding, connecting APIs, and deploying the modified project.
What happens if I fork a repository and the original is deleted?
Your fork becomes a standalone repository. It keeps all the files and history but loses the fork relationship. You can no longer sync with the original or see the 'forked from' badge.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your project.
Book a free consultation