Skip to content

Free GitHub Badge Generator

Free GitHub badge generator: pick a repository and get live shields.io badges for stars, forks, license and releases, or build a custom badge. Copy and paste.

Badges

The preview appears here.

Embed this tool

For AI agents: every setting is a query parameter of https://gitwow.org/embed/github-badge-generator (theme, accent, bg, radius), and the tool reads its own inputs from the address too. All tools are listed in llms.txt.

  1. A README badge is a picture from shields.io. The star badge reads the repository's current count whenever it is shown, so the number updates by itself.
  2. The Repository tab builds up to 11 badges at once, each linked to the page it describes. The Custom tab builds one from label, message, colour, style and a Simple Icons logo.
  3. A site button with a live counter and a profile achievement such as Starstruck are different things, and they are made elsewhere.
  4. Copy the result as Markdown, HTML or the image address. The form state sits in the address, and the page stores nothing.

Pick the right thing first: a README badge, a site button or a profile achievement

People who search for a star button on GitHub mean three different things. This generator makes the first one: a small picture for a README that reports a fact about your repository, such as its stars, license or latest release. You paste the Markdown it gives you into the README, and shields.io draws the picture. The other two have their own tools.

What you wantWhat it isWhere it comes from
A badge in a READMEAn image with a label and a value, served by shields.ioThis generator
A Star button with a counter on a websiteHTML or a React component that calls GitHubThe official buttons.github.io page for HTML, or a component such as the shadcn.io GitHub stars button
A profile achievement such as StarstruckAn award GitHub gives your account, shown on your profileNobody can generate it. See GitHub achievements

Our generator draws no interactive button, does not star anything and changes nothing on GitHub. What to do now: if you need a counter on a web page, open buttons.github.io, choose Star, tick Large button and Show count, and copy the HTML it prints.

Maintainers, course authors and newcomers each reach for a different badge

  • A maintainer about to announce a project ticks stars, license, latest release and last commit, so the README shows that the code is alive.
  • A junior developer with a portfolio repository adds top language and license, two badges that cost nothing to keep true.
  • A course author builds one custom badge per lesson, such as a label "lesson" with the message "3 of 8", and links it to the code.
  • A team lead puts a custom "docs" badge with a logo in front of the internal wiki address.
  • A DevRel engineer adds the owner's followers badge to an organisation's README.

Three steps: name the repository, check the preview, copy the code

Give it a repository or a badge text

On the Repository badges tab, paste owner/repository or a link, tick the badges you want and choose a style. Stars, forks, issues, license, release and last commit are ticked from the start. On the Custom badge tab, type a label and a message instead.

The badge generator with the Repository badges tab open, a repository typed in and badge checkboxes ticked
Step 1. Eleven repository badges, six of them ticked by default.

Check the preview

The preview is the real picture from shields.io, with each badge wrapped in its link. If shields.io cannot draw one, a message under the preview names it and suggests checking the repository name or the logo.

A row of rendered badges in the preview area with Markdown, HTML and image address fields below
Step 2. The preview shows what the README will show.

Three fields hold the result: Markdown for a README, HTML for a web page and the bare image address for anything else. The form state lives in the address of the page, so a filled generator is a link you can send. The Embed button builds an iframe of it for your own site.

The Embed window with theme, accent, background, corners and height settings, a live preview and the iframe code
Step 3. The Embed window carries your current badges.

Add live repository badges to your README in one line

Each repository badge is a shields.io address, and shields.io reads GitHub when the picture is shown. A number you typed by hand stays frozen. This one follows the repository, so a star badge always shows the current star count, shortened by shields.io once it gets long. The generator links each badge to the page it describes, with one exception explained under the table.

BadgeShowsLinks to
StarsCurrent star countThe repository
ForksFork count/forks
WatchersWatcher countThe repository
Open issuesIssues still open/issues
LicenseThe license nameThe LICENSE file
Latest releaseThe newest release tag/releases
Last commitHow long ago the last commit was/commits
Top languageThe main languageThe repository
ContributorsContributor countThe contributors graph
Repository sizeSize of the repositoryThe repository
Owner's followersFollowers of the accountThe follower list

A line in the Markdown field looks like [![GitHub stars](https://img.shields.io/github/stars/owner/repo)](https://github.com/owner/repo). The stars and watchers badges link to the repository itself. Since mid-2026 GitHub shows the stargazer and watcher lists only to admins and collaborators, so a link there would show most readers nothing. The repository page is where they can press Star or Watch.

GitHub's help says starring is a two-step process, open the repository and press Star at the top right, and that many of its repository rankings depend on the number of stars (GitHub docs). The badge puts that number in front of every reader, and the button is where it grows. If you want more stars on the repository, start free on the home page.

The Custom badge tab makes one static badge. The message is required, since it is the right half. The label is the left half and may stay empty. The colour comes from ten named choices or any hex value, with a separate colour for the label. A logo is a Simple Icons name, and twelve buttons fill the common ones, such as github, typescript, python, docker and vercel. The link is optional.

The result is an address of the form img.shields.io/badge/label-message-colour with the style, logo and colours as extra parameters. A dash or an underscore inside the text must be doubled and a space becomes an underscore, and the generator does that escaping for you. The page shows no catalog of its own: shields.io lists every badge type it serves, and Simple Icons lists the logo names.

A custom badge is plain text in a coloured box. It checks nothing and never updates, so keep it for facts that change rarely, such as a docs address or a lesson number, and never type "passing" for a build you do not run. Build and coverage badges come from the service that runs those checks, and its own badge Markdown is the one to paste.

Choose one style and keep it across all badges

shields.io has five styles and the generator offers all of them for both tabs.

  • flat is the default: a flat strip with rounded corners.
  • flat-square is the same strip with square corners.
  • plastic adds a glossy gradient.
  • for-the-badge is tall, with capital letters.
  • social looks like a button with the count beside it.

Mixed styles in one row look accidental, so choose one before you tick anything and keep it for the whole README.

A badge that leads nowhere wastes a click. Our badges link by default: forks to the fork list, releases to the release page, license to the LICENSE file. Up to five badges fit in one row. Beyond that, group them by category in a Markdown table, and centre a row with an HTML paragraph that has align set to center. Show what a visitor needs to decide and leave the rest out. What to do now: untick everything except the five badges that answer whether the project is alive, licensed and current.

Know the limits of shields.io and GitHub API counters

  • The count is fetched by shields.io when the picture is shown. If GitHub or shields.io cannot answer, the picture does not render and the alt text shows instead. Our page tells you which badge failed.
  • A badge for a user's total stars counts at most the 200 most-starred repositories of that account, according to shields.io. The generator's Stars badge is per repository.
  • Without authorization GitHub's API gives 60 requests an hour per IP. That limit matters to a button on your own website, which should cache the count. A README badge leaves the limit to shields.io.
  • Slack and HTML e-mail do not show SVG, so a badge in those places needs a raster picture.

The Embed button beside the heading offers a dark or light theme, an accent colour, a background, corner roundness and height, with a live preview and the iframe code. The code carries the badges you built, at /embed/github-badge-generator. Every setting is a parameter in the address. /embed/github-badge-generator?repo=owner/name&style=flat-square&badges=stars,forks,license builds three badges. For a custom badge use tab=custom with label, message, colour, style, logo and link. The label colour and logo colour are not stored in the address. The page /llms.txt lists all the free tools, and the free tools catalog shows them to people.

What sets this generator apart

Everything is free, needs no GitHub account and stores nothing: the page only assembles addresses, and shields.io draws the pictures. Repository badges carry real, current numbers and a link each. The generator works with the README stats cards for contribution numbers, the profile views counter for a views badge, the profile README generator for a whole profile and the README generator for a project. For a chart to put beside the badges, use the star history generator.

Frequently asked questions

How do I get the stargazer icon for a GitHub repo?

For a README, tick Stars on the Repository badges tab and paste the Markdown. For a website, the official buttons.github.io page makes an HTML Star button with a counter.

When does a star badge fetch the star count?

shields.io reads the count each time the picture is shown, which is why the number follows the repository without any action from you.

How do I avoid the request?

A README badge needs nothing from you, and shields.io makes the request. For a button on your own site, some components accept a count you pass in, and then they skip the call.

Will a badge hit GitHub's rate limit?

The limit sits on the shields.io side for a README badge. A live counter on your own site, calling GitHub without authorization, gets 60 requests an hour per IP and should cache the answer.

What happens when GitHub can't be reached?

The picture does not render, and a README shows the alt text. Our preview names the badge that failed and suggests checking the repository name.

How is the count shortened?

shields.io does it, so a large count appears as a short form such as 12.3k. You type nothing.

Where does the badge link to?

Each repository badge links to its own page: forks to the fork list, releases to the releases page, license to the LICENSE file. The stars and watchers badges link to the repository itself, because GitHub now shows those two lists only to admins and collaborators, and the repository page has the Star and Watch buttons.

How can I get the Starstruck achievement in GitHub?

Starstruck is a profile achievement for a repository you created that collects stars. A badge in a README does not earn it. The details and tiers are in the GitHub achievements article.

Related pages

PageSectionUpdated
Free GitHub Profile README GeneratorFree tools
Free GitHub README Stats GeneratorFree tools
Free GitHub Wrapped GeneratorFree tools
GitHub profile README: make it show, keep it short, keep it freshBlog
How to write a good README: four questions every visitor asksBlog
Free GitHub README GeneratorFree tools

GitWow

GitWow is a free community for growing your GitHub repositories and profile with help from other members.

47k members ยท 900+ actions a day

Create a free account