Gera Tools

FUNDING.yml Builder

Generate a GitHub FUNDING.yml to add a Sponsor button to your repo

Create a valid .github/FUNDING.yml that adds a Sponsor button to your GitHub repository, with GitHub Sponsors, Patreon, Open Collective, Ko-fi, Tidelift, Buy Me a Coffee, Liberapay, and custom donation URLs. It runs free in your browser on Gera Tools, with nothing uploaded.

Last updated Source: Gera Tools

Where does FUNDING.yml have to live?

GitHub reads the file from .github/FUNDING.yml in the default branch of a repository. You can also place a repo-wide default in a special .github repository for your account or organisation.

Add a Sponsor button with a valid FUNDING.yml

GitHub shows a Sponsor button on a repository when it finds a .github/FUNDING.yml listing your funding platforms. The format is small but strict about keys and quoting — one malformed line hides the button entirely. This builder produces a guaranteed-valid file from your handles.

Why this file matters for open-source maintainers

A Sponsor button on your repository’s header turns passive users into financial supporters without requiring them to hunt down a donation link. It appears prominently on the repository page, in search results, and (for GitHub Sponsors specifically) on your profile. Many developers do not realise that the button can link to multiple platforms simultaneously, or that GitHub’s own Sponsors programme is just one option.

The supported platforms vary considerably in their fee structures and community focus:

  • GitHub Sponsors — zero platform fee; funds sent directly. Best for GitHub-native audiences.
  • Patreon — percentage fee; strong for ongoing subscription relationships and tiered rewards.
  • Open Collective — transparent, fiscally sponsored model; ideal for projects that want collective governance rather than individual income.
  • Ko-fi — low-fee one-off tips and subscriptions; popular for individual creators.
  • Liberapay — no fees (they take donations themselves); popular in the European open-source community.
  • Tidelift — subscription model that funds maintainers of packages used by enterprise subscribers.
  • Buy Me a Coffee — simple tip model, small percentage fee.
  • Custom URLs — link to PayPal, your own donate page, or any other platform.

How the file works

GitHub reads .github/FUNDING.yml from the default branch. Each key maps to a platform:

github: yourusername
patreon: your-patreon-slug
open_collective: your-collective
ko_fi: your-ko-fi-handle
tidelift: "npm/your-package-name"
buy_me_a_coffee: your-handle
liberapay: your-handle
custom:
  - https://paypal.me/yourname

The github field accepts up to four usernames (written as a YAML list if more than one). The tidelift field uses a platform/package-name format, not a username. The custom field accepts up to four full URLs.

The builder writes exactly the right key names, quoting values that need it (URLs, anything with special characters) and omitting platforms you leave blank.

Common mistakes

  • Wrong file location — the file must be .github/FUNDING.yml exactly (note the capital FUNDING). The button does not appear if the file is at FUNDING.yml or funding.yml in the root.
  • Invalid YAML — a missing space after a colon, an unquoted URL, or a tab instead of spaces hides the button without any error message.
  • Tidelift format — enter npm/package-name, not just package-name. The platform prefix is required.
  • Multiple GitHub Sponsors usernames — enter them as a YAML list; a comma-separated string does not work.

After committing the file to your default branch, the Sponsor button appears on the repository header within a few minutes.