How to get paid for open source with GitHub Sponsors

How do I get paid for open source contributions with GitHub Sponsors

GitHub Sponsors pays open source contributors through a sponsored profile. You qualify by contributing real value to an open source project, then setting up your profile, tiers, bank details, and tax information. GitHub sends the sponsorship to you, but you remain responsible for your own tax obligations and payout setup.

The part people get wrong is thinking any kind of activity counts the same way. GitHub’s own guidance includes code, documentation, issue triage, mentorship, design, project management, business development, and leadership, but the payment flows to a real sponsored developer or sponsored organization profile, not to a casual mention of helping out.

Start by checking whether you are eligible in a supported region. GitHub says anyone who contributes to an open source project and lives in a supported region can become a sponsored developer, and organizations can also participate if they legally operate in a supported region. If your region is not supported yet, GitHub says you can join the waitlist.

Next, set up the sponsored profile itself. For a personal account, GitHub says you need to complete the sponsored developer profile, create sponsorship tiers, submit bank and tax information, and enable two-factor authentication. That is the point where many people stall, because the profile is not just a badge, it is the payment setup.

Choose sponsorship tiers that are simple enough to maintain. GitHub lets sponsored accounts define the tiers and benefits, and sponsors choose a one-time or monthly amount. Keep the tiers tied to something you can actually deliver, such as early access to roadmap notes, maintainer updates, or acknowledgment, because the sponsor is paying for the relationship around your open source work, not for a fake service bundle.

Then make the sponsorship visible where people already see your work. GitHub says you can add a sponsor button to the open source repository you contribute to after you join GitHub Sponsors, which helps people find the funding path from the project itself. If you maintain more than one repository, place the sponsorship link where your actual maintenance work lives, not only on a personal profile nobody visits.

Payout setup is where the money becomes real. GitHub says sponsored developers and organizations must submit tax information, and U.S. taxpayers must submit a W-9 before they can publish a personal GitHub Sponsors profile. GitHub also says it does not withhold tax from sponsorship payments, so you need to plan for taxes yourself instead of assuming GitHub will handle them for you.

The inconvenient part is that sponsorships are not the same as a salary, and they are not tax-free. GitHub says the responsibility for evaluating and paying taxes stays with the sponsored contributor or organization. GitHub also says it may issue tax forms through Stripe, and in some cases sponsors need to know whether the work is being done for a tax-exempt entity.

If you work across borders, check the tax side before you publish the profile. GitHub’s docs say sales tax can apply based on the recipient’s location in many places, and they give examples where a maintainer in one country can trigger tax in another country. That is not a reason to avoid Sponsors, but it is a reason to record what you are offering and what your local rules require.

For sponsors, the payment flow is straightforward, which helps your pitch. GitHub says people can sponsor a developer or organization from a personal account or an organization account, choose one-time or monthly amounts, and use the same billing date, payment method, and receipt they already have on GitHub. That low-friction checkout is one reason Sponsors works better than asking people to leave GitHub and fill out a separate form.

GitHub also says personal-account sponsorships do not carry a GitHub fee, while organization-account sponsorships can have a fee of up to 6 percent. If you are explaining why you want sponsors to use a personal account instead of an organization account, that fee difference is the concrete reason to mention.

A useful workflow is to pair sponsorship with visible maintenance. Publish releases, answer issues, keep the README current, and show a stable history of work in the repositories you maintain. Sponsors are more likely to pay when they can see ongoing contribution, and GitHub’s contributor categories make clear that paid open source work includes more than merged code.

If you are an individual maintainer, think in terms of one clear page: who you are, what you maintain, what support funds, and which tier fits a supporter. If you are an organization, GitHub says you can publish sponsorship tiers and manage members on the organization profile. That makes the setup suitable for maintainers who share work across a team, not only for solo projects.

A concrete example helps. Suppose you maintain a library used by small teams. You set up a personal Sponsors profile, add a monthly tier, connect your payout and tax details, then add the sponsor button to the repository README. A user who depends on the library can sponsor you without leaving GitHub, and the payment lands in the payout flow you configured.

If you want a place to point collaborators toward your testing work or broader builder network, DevConnect is free and stays free, and it is designed around mutual testing rather than paid promotion. For that kind of exchange, use your own profile and repos, then keep GitHub Sponsors for the money side. https://devconnectplatform.com

The main mistake is treating sponsorship like a one-time setup. The profile needs maintained tiers, current tax and payout details, and visible contribution history. If your work goes quiet, sponsors have less reason to keep paying. If your tax or bank information goes stale, the payout path can stall even when the sponsorships still exist.

The other mistake is promising more than your open source work can support. GitHub says the claims are the responsibility of the developer receiving the funds, and sponsors should trust the person before offering support. Keep your public promise close to the work you already do, and make the sponsorship page reflect that work honestly.

If you are ready to do this now, the order is simple: confirm eligibility, set up the sponsored profile, add tiers, complete bank and tax information, enable two-factor authentication, then link the sponsor button from the repositories where you actually contribute. That path is what turns open source work into paid sponsorship on GitHub.