itch.io doesn't split revenue between collaborators, so most teams that sell there end up working from the purchases export: a CSV with one row per purchase. It has a lot of columns, and only a few of them decide what your team actually earned.
Getting the file
Open your itch.io dashboard, find the purchases for your projects and export them as CSV. Exporting one month at a time keeps the files small and makes it easy to see which months you've already handled. Don't open and re-save the file in a spreadsheet before importing it; that can quietly change dates and amounts.
What a row looks like
Here's a trimmed row with the money columns kept and the buyer details left out:
id,object_name,amount,created_at,tip,marketplace_fee,source_fee,amount_delivered,currency
88123,Salt & Ember,12.00,2026-10-03 14:20:11 UTC,0.00,1.20,0.65,10.15,USD
88124,Salt & Ember: Map Pack,5.00,2026-10-04 09:02:44 UTC,1.00,0.50,0.45,4.05,USDThe real export has more columns, including the buyer's name, email and billing address. Those aren't needed to work out shares.
The columns that matter
| Column | What it is |
|---|---|
amount | What the buyer paid, including any tip |
marketplace_fee | itch.io's share of the sale |
source_fee | The payment processor's fee |
amount_delivered | What's left for you after both fees |
currency | The currency of the amounts on that row |
created_at | When the purchase happened |
object_name | The game, book or asset that was bought |
amount_delivered is the number to split if your team splits on net. It's the amount minus both fees: on the first row, 12.00 − 1.20 − 0.65 = 10.15.
Note
itch.io lets each seller choose the share it keeps, so marketplace_fee isn't the same percentage for everyone. Read it from the file rather than assuming it.
Two columns are easy to misread:
product_priceis in cents, while every other money column is in dollars (or the row's currency). Don't add it to the others. Splitfold doesn't read it.payoutsays whether itch.io has paid the money out yet. It's about your payout schedule, not about who earned what, so it doesn't change anyone's share.
From one row to everyone's share
Take a $10.00 purchase where amount_delivered is 8.41, on a project split on net: Ana 45%, Ben 35%, the house 20%.
| Collaborator | Exact share | Amount (USD) |
|---|---|---|
| Ana | 3.7845 | 3.79 |
| Ben | 2.9435 | 2.94 |
| House | 1.6820 | 1.68 |
Rounded down, the shares come to 8.40, one cent short. That cent goes to Ana, whose remainder is the largest, so the three amounts add up to 8.41 exactly. If the project had a recoupable cost outstanding, it would come off the 8.41 first and the split would apply to what's left.
Mixed currencies
Buyers can pay in different currencies, so one export can hold USD, EUR and GBP rows side by side. Add each currency up separately, or convert each sale on its own date. Splitfold converts every sale to your workspace currency at the European Central Bank rate for the sale date, and keeps the original amount and rate on the sale.
Refunds and repeat exports
A refund can show up as a flag on the original purchase rather than as a row of its own, and a later export may mark a purchase as refunded that an earlier one didn't. Either way, a refunded sale should take its share back from the same people it paid. Splitfold books the refund as a negative sale that reverses the split. Re-exporting an overlapping date range is also common, so whatever you use to add things up needs to recognise rows it has already counted. In Splitfold every row gets a fingerprint, so importing the same month twice never counts a sale twice.
Mapping products to projects
object_name is the product, not necessarily the project. A game and its soundtrack might be two products in one project with one split; an anthology might be one product that pays a dozen contributors. Decide the mapping once and keep it. Splitfold asks you to map each new product the first time it appears and remembers the choice for later files.
For the import steps, see Importing sales and Which file to export from each store.