How to Get More Stars on GitHub: 7 Steps That Work
How to get more GitHub stars on your repository: a README that sells, the settings GitHub uses to surface projects, where to launch, and how to reach Trending.
A GitHub star is a bookmark with a side effect: it tells everyone else that a project is worth a look. Stars push repositories onto GitHub Trending and into search results, and they’re the main way people discover the developer behind a project. Most new followers start as someone who starred one of your repositories.
Getting stars comes down to the same two things every time: a project that makes a good first impression, and enough of the right people seeing it. Here’s how to get both.
1. Build something people search for
The repositories that collect stars steadily tend to share a shape: they solve one specific, annoying problem, and you can explain them in a sentence. A CLI that fixes one workflow, a small library that wraps a painful API, a template that saves an afternoon of setup, or a curated list of resources on a topic.
If you’re not sure what to build, look at your own week. Any script you wrote to save yourself time is a candidate, because someone else has the same problem and is searching for it right now.
2. Make the README do the selling
Most people decide whether to star within a few seconds of landing on the repository, and what they see is the README. Put these at the top, in this order:
- One sentence on what it does and who it’s for.
- A screenshot or short GIF of it working. This is the single biggest improvement for most projects.
- A copy-paste install or usage command. If trying it takes more than a minute, most visitors won’t.
- A short “why”: what it does better than the obvious alternative.
Below that, add the details: configuration, examples, how to contribute and a license. A few well-chosen badges (build status, version, license) signal that the project is maintained; a wall of them just adds noise.
3. Fill in everything GitHub uses to show your repo
These take five minutes and help both GitHub search and people browsing:
- About section: a clear description with the words people would search for, plus a website link if you have a demo or docs.
- Topics: add relevant ones (you can add up to 20). Topic pages are how people browse projects by subject.
- Social preview image: set one under Settings → General → Social preview (1280×640 works well). It’s the image that shows up when your link is shared on X, Slack, Discord or LinkedIn, and a good one gets far more clicks than the default.
- Releases: publish tagged releases with short notes. They show the project is alive, and people who watch your releases get notified.
- A license: without one, many developers and companies legally can’t use your code, so they won’t star it either.
4. Launch it where developers look
Stars come in bursts, and almost every burst traces back to a post somewhere else. The places that work best:
- Hacker News (Show HN): a plain title that says what it is, and be around to answer comments for the first few hours.
- Reddit: the subreddit for your language or tool, not just the general ones. Read the rules on self-promotion first.
- dev.to, Hashnode or your own blog: a post on the problem and how you solved it, with the repository linked.
- X, Bluesky, Mastodon and LinkedIn: a short demo video or GIF does most of the work.
- Weekly newsletters for your language or ecosystem. Many take submissions.
- Awesome lists: find the
awesome-*list for your topic and open a pull request to add your project, following its contribution guidelines.
Lead with the problem, not the stack. “I kept losing an hour to X, so I built Y” gets clicked; “A Rust + WASM + Tauri app” mostly doesn’t.
5. Aim for GitHub Trending
GitHub Trending shows repositories that are gaining stars quickly right now, overall and per language. Getting there puts your project in front of a lot of developers who browse it daily, which brings more stars, which keeps you there a bit longer.
The practical lesson: concentrate your launch. Posting in five places on the same day gives you a much better chance of trending than posting in one place a week for five weeks. Per-language Trending pages are much easier to reach than the overall page, so tag your repository’s language correctly.
6. Keep it alive
Stars keep coming long after launch day if the project looks maintained. Reply to issues quickly, even if it’s just to say you’ve seen it. Label a few issues good first issue so contributors can get started. Merge good pull requests and thank the people who sent them: contributors share projects they’ve worked on.
Your own activity matters here too. Visitors look at the commit history and at your profile, and a steady contribution graph says the project won’t be abandoned next month. A live GitArena stats badge in your profile README shows that activity at a glance.
7. It’s fine to ask
One line at the end of your README, like “If this saved you time, a star helps others find it”, is normal and works. Keep it to one line, and keep it out of the way of the actual content.
Don’t buy stars
Paid and traded stars are a real market, and researchers have found millions of suspected fake stars on GitHub. They’re easy to spot: a spike of stars from new, empty accounts, with no matching forks, issues or traffic. GitHub removes them and can take action against the repositories involved. Even when they stick, they don’t bring users, contributors or followers, which is what stars were supposed to get you in the first place.
Turn stars into followers
When someone stars a repository they like, the next click is often your profile. Make sure it’s ready: a photo, a bio that says what you build, your best projects pinned and a profile README that points to your other work. That’s how one popular project turns into an audience for everything you build next. Our guide on how to get more GitHub followers covers the rest, and how many GitHub followers is good shows how your count compares with the rest of GitHub.
Checklist
- A project that solves one clear problem.
- README with a one-line pitch, a GIF and a copy-paste install.
- Description, topics, social preview image and a license.
- A tagged release.
- Launch in several places on the same day.
- An entry in the relevant awesome list.
- Fast replies to issues, and a few good first issues.
- A profile ready for visitors, and a GitArena profile page that shows you’re still shipping.
Add live GitHub stats to your README
Generate an embeddable GitArena badge in seconds — customize the timeframe, theme, and color.
Generate your badgeKeep reading
How to Get More GitHub Followers for Free (Naturally)
We compared 471 GitHub accounts to see what gets developers followed. 7 free ways to get more GitHub followers, backed by data, and why to skip follower bots.
How Many GitHub Followers Is Good? Real Numbers for 2026
We counted GitHub followers across 165 million accounts. Only about 157,000 have 100 or more. See where your follower count ranks, tier by tier.
How to See Who Unfollowed You on GitHub
GitHub doesn't notify you about unfollows. Here's how to track who unfollowed you, find who doesn't follow back, and stay safe with unfollower apps.