Every month, thousands of developers open their GitHub Sponsors dashboard, see a few hundred dollars sitting there from strangers who rely on their library, and quietly wonder: do I actually have to do anything with this?
The honest answer is yes — and the rules are stranger than most maintainers expect. Sponsorship income doesn't behave like a paycheck or even like typical freelance income. It moves through unusual intermediaries (Stripe, fiscal hosts, platform processors), it can be legally a "hobby" or a "business" depending on facts you may not have thought about, and the tax forms involved have changed enough in the last two years that a lot of the advice circulating online is already out of date.
If you maintain a project that pulls in sponsorship money — whether it's $20 a month from five people or a five-figure annual budget funding a team — here's what's actually true for GitHub Sponsors, Open Collective, and Patreon in 2026, and how to keep your books straight so tax season isn't a scramble.
The three platforms work completely differently
It's tempting to treat "sponsorship income" as one category. It isn't. Each platform routes money through a different legal and financial structure, and that structure determines what paperwork shows up in your mailbox come January.
GitHub Sponsors: Stripe, and a 1099-NEC if you clear $600
GitHub Sponsors pays maintainers directly through Stripe. If you're a U.S. taxpayer and your sponsorship income for the year exceeds $600, GitHub issues a Form 1099-NEC before January 31 of the following year — not a 1099-K, which is what most people assume. Before you can even publish a sponsors profile, GitHub requires you to submit a W-9 (U.S. individuals) or a W-8 BEN / W-8 BEN-E (international individuals and companies), which Stripe collects and holds on file.
GitHub does not withhold any tax from your payouts, and it explicitly does not issue tax forms to international maintainers — the responsibility for figuring out and reporting the income sits entirely with you, wherever you're based. If your country requires a tax identification number, you provide it; if not, GitHub lets you write "not legally required" on the form.
Open Collective: the fiscal host absorbs the paperwork
Open Collective works differently again. Instead of paying you directly, money sits with a fiscal host — a legal entity (often a nonprofit) that holds funds on behalf of your project, approves expenses, and pays them out. This is why many open-source projects on Open Collective don't need their own bank account or legal entity at all: the host mutualizes that overhead, typically for a fee of 5–15% of incoming funds.
The tax wrinkle: if you submit $600 or more in invoiced expenses to a US-based fiscal host in a year, US law requires the host to collect your tax information — even if you live outside the US. That $600 threshold applies specifically to invoice expenses (i.e., you billing the collective for your work), not to reimbursements, grants, or payroll, which are treated differently.
Patreon: a 1099-K, tied to gross pledges
Patreon reports differently still, issuing a 1099-K that reflects your gross pledge revenue for the year — before Patreon's own platform fees are subtracted. That distinction matters: the number on the form is not your take-home amount, and you'll need your own records to back out fees as a deductible business expense.
The 1099-K threshold confusion — and what's actually true for 2026
If you searched around before reading this, you may have seen conflicting numbers: $600, $2,500, $5,000, $20,000. Here's what's actually in force.
The American Rescue Plan Act (2021) originally set a $600 reporting threshold for third-party payment platforms, phased in gradually — $5,000 for 2024, $2,500 for 2025, with $600 expected to fully take effect in 2026. That plan was reversed. The One Big Beautiful Bill Act, signed in July 2025, repealed the lower thresholds and reinstated the original federal rule: platforms only have to issue a 1099-K once you cross $20,000 in payments and more than 200 transactions in a calendar year.
Two things to keep in mind despite that reversal:
- Whether or not you receive a 1099-K, the income is still taxable. The form is a reporting mechanism, not the source of your legal obligation to report income. If Patreon doesn't send you a form because you stayed under $20,000, you still owe tax on every dollar of sponsorship income.
- State thresholds can be lower than the federal one. Some states run their own reporting rules independent of the IRS combined federal/state filing program, so a platform might still send you a form based on state law even when federal law wouldn't require it.
Is your sponsorship income a hobby or a business?
This is the question that actually determines how you're taxed, and it's the one most maintainers never think to ask.
The IRS draws a hard line between a hobby (something you do for enjoyment, without a genuine profit motive) and a business (an activity you engage in to make money). The distinction isn't about how much you earn — it's about intent and behavior, assessed against nine IRS factors that include things like whether you keep accurate records, whether you've made changes to improve profitability, and whether the activity has produced net profit in at least three of the last five years.
The tax consequences are significant either way:
- If it's a business (reported on Schedule C): your net sponsorship income is subject to both ordinary income tax and the 15.3% self-employment tax once net earnings hit $400 — but you can deduct legitimate business expenses (the laptop you develop on, a portion of your home office, paid CI minutes, conference travel to talk about your project) against that income.
- If it's a hobby (reported as "other income" on Schedule 1): you don't pay self-employment tax, but you also can't deduct hobby-related expenses against it. You're taxed on the gross amount with no offsetting write-offs.
Most maintainers who treat their project seriously — publishing a roadmap, actively soliciting sponsors, tracking expenses, reinvesting in the project — are going to land on the business side of that line, especially once income becomes recurring and substantial. If you're in that position, quarterly estimated tax payments are worth planning for, since nobody is withholding anything from a Stripe payout the way an employer would from a paycheck.
A worked example: three platforms, one maintainer
Say you maintain a moderately popular CLI tool. Over the course of a year: GitHub Sponsors brings in $2,400 from 40 individual sponsors, an Open Collective campaign funded by a corporate user nets $8,000 routed through a fiscal host (after the host's 10% fee), and a Patreon tier pulls in $1,800 in gross pledges before Patreon's processing fees.
Here's what actually lands in your mailbox — and what doesn't:
- GitHub Sponsors: since $2,400 clears the $600 threshold, you get a 1099-NEC in January reporting that full amount.
- Open Collective: you never see a 1099 from Open Collective itself, because the fiscal host handled the legal and tax relationship with the corporate sponsor. What you need to track yourself is the $8,000 gross expense you invoiced, and the 10% ($800) the host retained as its fee — that fee is a real cost of doing business, not something the IRS assumes you'll remember on your own.
- Patreon: because $1,800 is well under $20,000, you likely receive no 1099-K at all under the post-OBBBA rules. That doesn't mean the $1,800 (minus Patreon's cut) isn't taxable — it is, in full, regardless of whether a form ever arrives.
Add it up and you've got roughly $11,600 in gross sponsorship activity across three platforms, only one of which sends you a form, and none of which withhold a cent for taxes. If this is a business for you (and at this volume, with active solicitation and reinvestment, it likely is), that's income subject to self-employment tax on top of ordinary income tax — which is exactly why quarterly estimates matter more than the forms themselves.
International maintainers face a different set of gaps
If you maintain a widely-used project from outside the U.S., the reporting picture gets even thinner. GitHub explicitly does not issue tax forms to non-U.S. taxpayers, which means there's no paper trail arriving from the platform side — the entire burden of recognizing and reporting the income falls on you and your local tax authority. You'll still need to supply a W-8 BEN (as an individual) or W-8 BEN-E (as a company) before GitHub Sponsors will even activate your profile, and you'll need either your country's tax identification number or a written statement that your country doesn't require one.
Cross-border sponsorship also raises the separate question of sales tax or VAT on any perks you offer sponsors (early access, private repos, swag) — that liability generally follows the sponsor's location, not yours, which is a different rulebook than income tax and worth flagging to a local advisor if perk-based tiers make up a meaningful share of your funding.
A practical checklist for maintainers
- Track gross income by platform, not just the total. GitHub, Open Collective, and Patreon each report (or don't report) differently, and you'll want your own reconciliation if a platform's form doesn't match what actually hit your bank account.
- Keep the fee schedule separate from the deposit. Patreon's 1099-K shows gross pledges; Open Collective's host fee comes off the top. Recording the fee as its own line item, rather than just netting it out, makes your records defensible if you're ever asked to substantiate a deduction.
- Decide — and document — your profit motive early. If you're aiming to run this as a business, start acting like one on day one: separate the money, keep receipts, and be able to point to the steps you took to grow sponsorship (that's exactly what the IRS's nine factors are checking for).
- Set aside money for quarterly estimates if you expect meaningful self-employment tax liability. A rough rule of thumb many freelancers use is 25–30% of net sponsorship income, adjusted once you've seen a full year of numbers.
- Don't assume no form means no obligation. The 1099-K threshold reversal means fewer maintainers will get a form at all in 2026 — that doesn't reduce anyone's actual tax bill.
Keep Sponsorship Income as Clean as Your Codebase
If you're already comfortable with plain text and version control, treating your sponsorship income the same way is a natural next step. Beancount.io gives you plain-text accounting — every GitHub Sponsors payout, Open Collective expense, and Patreon deposit as a diffable, auditable ledger entry instead of a spreadsheet you have to reconstruct every April. Check out the documentation to see how quickly you can set up categories for sponsorship income, platform fees, and deductible expenses, and get a real answer to "hobby or business?" before the IRS asks it for you.