How to get paid for open source work with GitHub Sponsors

How can I get paid for open source work through GitHub Sponsors

You get paid by publishing a GitHub Sponsors profile, adding payout and tax details, and making your open source work easy to evaluate. GitHub says sponsored developers and organizations can receive compensation for open source work directly on GitHub.

The part people get wrong is thinking sponsorship starts with a donation button. It starts with eligibility and setup. GitHub requires tax information before you can publish a profile, and U.S. taxpayers must submit a W-9. Non-U.S. taxpayers must submit a W-8 BEN or W-8 BEN-E.

After that, you choose how payouts arrive. GitHub says you can receive payments in a Stripe Connect account you control, or through a fiscal host you already work with. That choice matters because it decides who handles the money flow and the administrative overhead around it.

Your profile needs to tell sponsors what they are supporting. GitHub asks you to describe the open source work you contribute to, and you can publish sponsorship tiers with prices and a welcome message. The goal is to make the sponsorship decision understandable without forcing people to guess what they are funding.

A useful setup looks like this: one personal or organization profile, one clear summary of your maintainer work, and a few tiers that map to real support levels. GitHub lets you add tiers and customize the sponsor button in your repository through a FUNDING file, which can also point to external funding platforms or a custom funding URL.

If you maintain more than one repository, put the sponsor entry where contributors already look. GitHub supports a sponsor button in the repository itself, and that button can surface sponsored developers in GitHub Sponsors. That is useful because sponsors usually discover funding opportunities while reading issues, release notes, or the README.

Do not frame the profile like a paywall. GitHub Sponsors is for support, not gated access. GitHub describes it as a way for people and organizations to financially support the developers and organizations that design, build, and maintain open source projects. The work stays open source, the money supports the labor behind it.

The inconvenient part is taxes. GitHub says it does not withhold tax from sponsorship payments, and sponsored developers are responsible for evaluating and paying their own taxes. That means sponsorship income is not the same as a simple tip jar, because you still need to account for reporting and any sales tax or withholding issues that apply to your situation.

The part people also miss is that sponsorship is not automatic just because your code is popular. GitHub’s additional terms say it can review applicants or participants for eligibility and terms compliance. In practice, that means your profile, your activity, and your offer need to line up with GitHub’s rules and with the way you actually work.

A simple path is: finish the sponsor profile, add tax and payout details, write a plain description of the work you maintain, create a few tiers, and connect the repository button to the profile. If you already use a platform like DevConnect for coordination, use it for finding contributors and testing workflows, then send people to the GitHub Sponsors page for money. DevConnect itself is free to use, and that keeps the funding ask separate from the coordination layer. https://devconnectplatform.com

When you write the offer, be specific about what sponsors are supporting. Good examples are bug triage, release engineering, documentation, security fixes, and maintenance time. GitHub explicitly lists contributions such as bug reports, issue triage, code, documentation, leadership, business development, project management, mentorship, and design as part of open source contribution. That gives you room to describe real labor, not vague gratitude.

If you are part of an organization, the same idea applies, but the payout path and tax handling need to match the account type. GitHub says organizations can also receive sponsorships, and its docs on fiscal hosts explain that payout choice can be made during signup. The cleanest setup is the one where the legal owner of the work is the same person or entity that receives the money.

A practical example helps. If you maintain a security library, your profile can say that sponsorship funds release management time for reviews, patches, and advisories. Then your repository button points to that profile, and your tiers can reflect support for small, medium, or sustained maintenance. That is easier for sponsors to understand than asking them to pay for “support” without saying what support buys.

What happens when it goes wrong is usually boring, not dramatic. Missing tax information blocks publication, unclear tiers lower trust, and a profile that does not show real open source work makes it harder for sponsors to justify paying. GitHub’s own setup flow puts the profile, tax, payout, and tier steps in sequence for a reason: each one is required before the money starts moving.

If you want the shortest answer, it is this: create a sponsor profile, complete the required tax and payout setup, describe your open source work clearly, publish tiers, and connect the profile from the repository. GitHub Sponsors is the payment layer. Your job is to make the work legible enough that someone can support it without guessing.

FAQ

Do I need a company to use GitHub Sponsors No. GitHub supports both individuals and organizations. Individual contributors can receive sponsorships, and organizations can also be sponsored if their profile and payout setup are complete.

Can I make my sponsors pay for access to my code No. GitHub Sponsors is described as support for open source work, not a paywall for source code access. The cleaner model is to keep the project open and ask for financial support for maintenance.

What tax form do I need GitHub says U.S. taxpayers must submit a W-9 before publishing a profile, while non-U.S. taxpayers must submit a W-8 BEN or W-8 BEN-E.

Can I route GitHub Sponsors money through a fiscal host Yes. GitHub says you can receive payouts in a Stripe Connect account you control or through a fiscal host you already work with.

How do people find my sponsorship page GitHub lets you add a sponsor button in your repository with a FUNDING file, and the sponsor button can also point to GitHub Sponsors or external funding links.

Does GitHub withhold taxes for me No. GitHub says it does not withhold tax from sponsorship payments, and sponsored developers are responsible for evaluating and paying their own taxes.