How Much Does GitHub Sponsors Pay? Developer Earnings Explained (2026)

GitHub Sponsors takes nothing from personal sponsorships. 100% of what a developer's supporter pays goes directly to that developer — GitHub does not charge a platform fee for personal account sponsorships.

That is unusual. Most creator platforms take 10–30% before money reaches the creator. GitHub's 0% fee on personal sponsorships makes it one of the most transparent monetization structures in the creator ecosystem, and it's the fact that most developers asking "does GitHub take a cut?" don't expect to find.

The 0% fee on personal sponsorships

GitHub Sponsors launched in 2019 with a clear policy: for personal account sponsorships, GitHub charges no service fee. The full amount the sponsor pays transfers to the developer.

This stands in contrast to most monetization platforms:

Platform	Platform fee
GitHub Sponsors (personal)	0%
Ko-fi free plan	5%
beehiiv	0% (subscription revenue)
Patreon	10% (new creators)
Substack	10%

The 0% isn't a promotional offer or a first-year incentive. It's the standing policy for personal account sponsorships. GitHub's business model is built around enterprise GitHub subscriptions and platform services — not taking a cut of developer earnings.

The caveat is organization sponsors. When a company sponsors a developer through an organization account, GitHub charges up to 6%: a 3% credit card processing fee plus a 3% GitHub service fee. Organizations can eliminate the 3% GitHub service fee by switching to invoiced billing, leaving only the unavoidable payment processing cost.

For most individual developers, the majority of sponsors are personal accounts. The 0% fee applies to those.

How GitHub Sponsors earnings actually work

GitHub Sponsors is not a payout pool. GitHub does not distribute a shared fund based on views, engagement, or algorithm scoring. You earn exactly what your sponsors choose to pay you, on the tiers you define.

You set up sponsorship tiers — monthly or one-time — at whatever amounts make sense for your project and audience. A typical setup might include a $5/month individual supporter tier, a $25/month active user tier, and a $100+/month commercial user tier for companies depending on your project. Sponsors choose their tier and payment frequency.

GitHub sends your earnings monthly to your connected bank account, after you've completed bank information and tax forms. The 100% pass-through means the math is direct: 50 sponsors at $10/month = $500/month, no percentage deducted.

What GitHub does not do: show your Sponsors profile to people who don't know you exist. Discovery is entirely on the developer. The most common driver of GitHub Sponsors income is a README badge linking to your Sponsors page, followed by active promotion on social channels, newsletters, and in your project documentation. Maintainers who earn meaningful income from GitHub Sponsors typically spend intentional effort making their Sponsors profile visible to people who already use their work.

What developers actually earn on GitHub Sponsors

GitHub publishes no official average earnings figure. Income reports from developers across forums, open source communities, and creator income newsletters suggest a wide range:

• Smaller libraries and individual tools: $50–$500/month, driven by a handful of sponsors who depend on the project
• Mid-tier maintained projects: $500–$3,000/month, with a mix of individual and organizational sponsors
• Widely-depended-on open source infrastructure: $5,000–$20,000+/month, particularly for projects that companies use in production

The single largest variable is not code quality — it's whether your users know your Sponsors page exists and feel a direct relationship with funding your continued work. Many high-quality, widely-used open source projects earn nearly nothing on GitHub Sponsors because the maintainer hasn't actively promoted the profile. Many smaller projects earn disproportionately more because the maintainer has made their funding situation part of their project's communication.

Organizational sponsors tend to have higher per-sponsor values ($100–$1,000+/month) but require a more active outreach and sponsorship rationale — a company needs to internally justify the expense. Individual developer sponsors are easier to convert but pay less per sponsor.

Who qualifies for GitHub Sponsors

GitHub Sponsors has no follower count minimum, no repository star threshold, and no view count requirement. Eligibility centers on:

1. Open source contribution history — GitHub requires meaningful contributions to open source projects. These include code, documentation, bug reports, issue triage, community leadership, mentorship, business development, and project management. You don't have to be a code author; documentation maintainers and community managers qualify.
2. Supported region — GitHub Sponsors is available in a specific list of countries where GitHub can process bank payments and comply with tax regulations. Check your region's eligibility in your GitHub account settings before applying.
3. Two-factor authentication — 2FA must be enabled on your GitHub account.
4. Bank and tax information — You submit bank account details and tax forms (equivalent to a W-9 for US developers, or equivalent forms for international contributors).
5. Sponsored developer profile — You create a profile, write a description of your work and why supporters should fund you, and set up your sponsorship tiers.

The application goes through GitHub's review process. There's no stated timeline, but most contributions from active developers in supported regions are approved.

GitHub Sponsors vs other creator platforms

GitHub Sponsors occupies a distinct niche: it's monetization built specifically for open source developers, not content creators in the traditional sense. A developer whose project is depended on by thousands of users is in a fundamentally different position than a YouTube creator building a viewership audience.

That difference cuts both ways. Your potential sponsor base is limited to people who already use and value your work — but those people have a more direct financial incentive to support you than a casual subscriber does. A company saving engineering time because of your open source library has a concrete reason to fund your continued maintenance.

For developers who also create educational content, GitHub Sponsors pairs naturally with YouTube's Partner Program (if you teach development tutorials) or Ko-fi for one-time tips. For developers building developer tools specifically, the Cursor Ambassador Program covers a different angle: promoting AI coding tools versus direct project support.

More developer-oriented programs and tools across design and devtools programs are listed if you want to compare the field.

Setting up GitHub Sponsors: what actually matters

The technical setup is straightforward — GitHub walks you through it. What matters more is the strategy around the profile itself.

Developers who earn meaningfully from GitHub Sponsors consistently do a few things:

Make the link unavoidable. A Sponsors badge in your README, visible at the top where it's seen before any documentation, is the single highest-converting change most maintainers make.

Explain the funding rationale. "I spend 15 hours a week maintaining this project while working full-time" is more compelling than "consider supporting me." Make the cost of maintaining the project concrete.

Define tiers with specific value. "Individual supporter" and "commercial use ($X/month)" tiers with clear descriptions convert better than undifferentiated tiers. Companies especially want a reason that maps to their use case.

Promote on each major release. A release notes post that includes a note about GitHub Sponsors reaches exactly the people using your software at the moment they're most aware of its value.

The 0% GitHub fee means every incremental sponsor goes entirely to you. The investment is in building the funnel, not in working around the platform's take.