Free tool
GitHub Badge Generator
Show your repository's stars, forks or followers at the top of its README with a live badge that updates itself.
Type owner/repository (for example octocat/Hello-World). A followers badge needs only the account name.
Preview
Markdown
HTML
Runs in your browser. Nothing you type here is sent to Reachism.
How it works
-
1. Enter the repository
Type owner/name or paste the repository's GitHub address.
-
2. Pick a badge and a style
Stars, forks, watchers, followers, last commit or license — in five shields.io styles. The preview shows the real badge.
-
3. Paste it in your README
Copy the Markdown for README.md, or the HTML for a page. The badge links to the matching GitHub page.
README badges in short
The badges are images served by shields.io, a free and open-source badge service. Each time someone opens your README, shields.io reads the current figure from GitHub, so the number on the badge keeps itself up to date.
The social style looks like GitHub's own Star button and suits star and follower counts; flat and flat-square are the usual choice for a row of status badges.
Badges only work for public repositories and accounts: shields.io cannot see private ones, and shows "repo not found" instead.
Questions about the GitHub Badge Generator
Either the repository is private, or the owner or name is misspelled. Copy owner/name straight from the repository's address bar.
shields.io and GitHub both cache images for a short while, so a new star can take some minutes to appear on the badge. Nothing needs to be changed in your README.
Yes. Create a public repository named exactly like your username; its README is shown on your profile page. A followers badge fits well there.
No. The Markdown is written in your browser. Only the preview image is loaded, straight from shields.io, as it would be from your README.
Want more reach on GitHub?
When you are ready to grow, our GitHub Stars packages come in several sizes. No password needed — only the public link.