⌘ K
GitHub Sponsors · Patreon · OpenCollective · Ko-fi

Generate .github/FUNDING.yml

Wire up the GitHub Sponsor button in seconds. Fill any platforms that apply; blank fields are skipped.

FUNDING.yml Generator
YAML
40 B
2 lines
Platforms
1
filled
Custom URLs
0
none
GitHub
single
1 usr
1 of 10 platforms set
input · platforms
output · .github/FUNDING.yml
# .github/FUNDING.yml
github: myusername
Quick Start

How to wire up the Sponsor button

Drop the generated YAML at .github/FUNDING.yml and push. GitHub picks it up automatically.

  1. 01

    List platforms

    Only fill the platforms where you actually accept sponsorships. Blanks are skipped.

    Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.

    fieldsGFMmarkedCommonMarklive
    set · markdown1 · GFM
    github: octocat
    loaded · GFMGFM · ready
  2. 02

    Multiple GitHub users?

    Use a comma-separated list — the YAML is emitted as an array.

    Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style <br> insertion.

    arraysoft-breaksoptionsconfiglive
    array · optionsno · live
    github: [a, b]
    options applied · livelive
  3. 03

    Custom URLs

    Comma-separate up to 4 custom donation URLs. Each is quoted automatically.

    The preview is scoped under a .mde class so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.

    custompreviewscoped CSSrenderstable
    custom · rendered0 · ready
    custom: ["url1", "url2"]
    rendered · liverendered
  4. 04

    Commit + push

    GitHub picks it up automatically and shows the Sponsor button on the repo page.

    Export covers both raw Markdown and rendered HTML; downloads stream as text/markdown or text/html via Blob + object URL.

    deployclipboard.md.htmlblob
    ✓ · exportedlive · done
    ✓ Copied
    shipped · ready to shipsuccess
Pro tips

Author Markdown that renders everywhere

GFM is the safe default

GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.

Soft-break behaviour varies

A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.

Escape inside code fences

Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.

Anchors are slugified

GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.

Tables need a header row

The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.

Front matter is YAML

Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.

Related toolsREADME GeneratorSECURITY.mdCONTRIBUTING.mdCoCProfile READMEBadge
Use Cases

When you need a FUNDING.yml

Open source, indie maintainers.

OSS maintainers

Surface a Sponsor button on every page of your repo. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.

GFM-compliant

Multi-platform

Funnel to your chosen platform mix — GH Sponsors, OC, Ko-fi. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.

GitHub-perfect

Team accounts

Multiple GitHub usernames in a single repo. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.

diff-friendly

Custom URLs

Direct donors to a Stripe-payment page or merch shop. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.

render-stable

Tidelift

Enterprise support contract platforms. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.

cross-platform

Charity

Route to a non-profit via custom URL. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.

SEO-friendly
FAQ

Frequently asked questions

.github/FUNDING.yml in the default branch. GitHub auto-detects it.
Yes — separate with commas. The generator emits a YAML array.
GitHub allows up to 4 custom URLs. Comma-separate them in the custom field.
Empty platforms are skipped to keep the YAML clean.
No. YAML is built locally.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!