Guide

How to Set Up GitHub Sponsors

A practical setup guide for GitHub Sponsors: eligibility, profile setup, tiers, payout setup, repository Sponsor buttons, and README funding copy.

Last reviewed: 2026-06-21 3 min read

Contents

To set up GitHub Sponsors, check eligibility, create a sponsor profile, connect payouts, add simple sponsorship tiers, and make the Sponsor button visible in your repositories with FUNDING.yml. The most important part is not the profile design. It is making the funding ask clear and visible.

Before you start

Check three things:

  1. You contribute to open source.
  2. You are in a supported payout region.
  3. You can complete the required payout and tax setup.

GitHub Sponsors supports sponsored developers and sponsored organizations in supported regions. Eligibility and payout requirements can change, so verify them in GitHub’s official documentation before publishing region-specific claims.

Step 1: Create your sponsor profile

Your sponsor profile should answer three questions:

  • What do you maintain?
  • Who depends on it?
  • What does sponsorship fund?

Use specific language:

Sponsorship helps fund issue triage, releases, dependency updates, documentation, and long-term maintenance for this project.

Avoid vague language:

Help me follow my passion.

People sponsor maintenance, reliability, and useful work.

Step 2: Create simple tiers

Start with three to four tiers.

TierBest forSuggested positioning
Small monthly tierIndividual usersSay thanks and fund baseline maintenance
Medium monthly tierHeavy usersFund issue triage, docs, and releases
Company tierCompanies using the projectPublic recognition and maintenance support
Custom amountFlexible supportersLet sponsors choose another amount

Do not promise support SLAs unless you want to provide paid support. Sponsorship is not the same as a support contract.

Step 3: Connect payouts

Complete the payout setup GitHub requires for your account or organization. This may include identity, tax, or payment details depending on region and account type.

Do this before promoting the sponsorship page. A broken payout path wastes early interest.

Step 4: Add FUNDING.yml

Add .github/FUNDING.yml so GitHub can display the Sponsor button on your repositories.

Example:

github: your-github-username
custom: ["https://your-project.example.com/sponsor"]

If you also use Open Collective, Ko-fi, or another platform, add only the links you actively maintain.

Step 5: Make the ask visible

Add one sentence in these places:

  • README.
  • Project website.
  • Release notes.
  • Documentation footer.
  • GitHub profile or organization profile.

Example README copy:

If this project saves you or your company time, consider sponsoring ongoing maintenance.

For companies:

Company sponsorship helps fund releases, documentation, security updates, and issue triage.

Step 6: Review after 30 days

After 30 days, check:

  • Is the Sponsor button visible?
  • Is the README ask above the fold?
  • Do sponsors understand what they fund?
  • Are tiers too complex?
  • Should company sponsorship be explained more clearly?

Small changes to wording often matter more than adding more perks.

Fees and caveats

As of the current GitHub documentation, GitHub does not charge fees for sponsorships from personal accounts. Sponsorships from organization accounts can have fees. Verify current fee details before making money claims in public copy.

FAQ

How long does it take to set up GitHub Sponsors?

The visible setup can be quick, but eligibility, payout, and tax setup may take longer. Do not promise a universal setup time.

Should I create many sponsorship tiers?

No. Start with a small number of clear tiers. Too many tiers make the decision harder.

Can organizations use GitHub Sponsors?

Yes, eligible organizations can use GitHub Sponsors. Check GitHub’s supported region and account requirements.

Is GitHub Sponsors enough for a team project?

Sometimes, but Open Collective is often better when money needs to pay shared project expenses.

Need help deciding whether GitHub Sponsors should be first? Try the Sustainability Finder.

Sources checked