Key takeaways
- Bags (bags.fm) launches every token on Meteora's Dynamic Bonding Curve and, by default, charges a 2% fee per trade with 1% going to a creator pool before migration, according to Bags' documentation.
- After a Bags token migrates to a Meteora DAMM v2 pool, the default fee stays at 2%, split 0.75% to the protocol, 0.75% to the creator pool and 0.5% compounded into liquidity.
- On new SOL fee-share configs, Bags gives the token's deployer 25% of the gross creator pool, and the configured fee recipients split the other 75%.
- Bags creator fees wait in each token's fee-share account until a recipient claims them, and Bags' API returns ready-to-sign claim transactions for a wallet and token mint.
- As of November 2026, SOLTidy's Claim Creator Fees tool scans Bags fee shares alongside pump.fun, LaunchLab and Meteora and charges 5% of the SOL claimed.
The short answer
Bags creator fees are a share of every trade of a Bags token, held in that token's fee-share account until each listed recipient claims. By default Bags charges 2% per trade and sends 1% to the creator pool before migration and 0.75% after, with 25% of the pool reserved for the deployer on new SOL configs. You claim in the Bags app, through Bags' API or CLI, or with a multi-launchpad tool such as SOLTidy's Claim Creator Fees.
How do Bags creator fees work?
Bags creator fees work through a fee-share program that sits between the trading pool and the creators. Every Bags token launches on Meteora's Dynamic Bonding Curve with a config of its own. The partner share of that curve's fees is routed into Bags' fee-share program, which keeps a platform share and splits the rest, the creator pool, among the wallets the token's configuration lists.
That design is what sets Bags apart. A pump.fun coin has one creator wallet; a Bags token can share fees with a team, a collaborator or a community wallet from day one, each with a share in basis points. Bags' API reference describes support for up to 100 fee claimers.
What does Bags charge, and how much goes to creators?
Bags offers several fee modes, chosen at launch. These come from Bags' fee customization guide, checked November 5, 2026. The creator column is the gross creator pool:
| Fee mode | Before migration (protocol / creator) | After migration (protocol / creator / compounding) | Graduates at |
|---|---|---|---|
| Default | 2% (1% / 1%) | 2% (0.75% / 0.75% / 0.5%) | 85 SOL |
| Low pre / high post | 0.25% (0.125% / 0.125%) | 1% (0.25% / 0.25% / 0.5%) | 85 SOL |
| High pre / low post | 1% (0.5% / 0.5%) | 0.25% (0.0625% / 0.0625% / 0.125%) | 85 SOL |
| High flat | 10% (5% / 5%) | 10% (2.5% / 2.5% / 5%) | 85 SOL |
| 2% flat, 85% supply locked | 2% (1% / 1%) | 2% (0.75% / 0.75% / 0.5%) | ≈ 100 SOL |
| Default, 1K supply | 2% (1% / 1%) | 2% (0.75% / 0.75% / 0.5%) | 85 SOL |
| 2% base, 96% supply locked | 2% (1% / 1%) | Starts at 2%, falls by market cap to a 0.5% floor | 80 SOL |
The compounding part after migration goes back into the pool's liquidity rather than to anyone's wallet.
The deployer share
On newly created SOL fee-share v2 configs, Bags gives the token's deployer 25% of the gross creator pool, and the normal fee recipients divide the remaining 75%. Bags' own example: with a 2% fee and no compounding, 1% goes to the platform, 0.25% to the deployer and 0.75% to the configured recipients.
Worked example
A token on the default mode does 200 SOL of volume on the curve, graduates, then does 1,000 SOL of volume on its DAMM v2 pool.
| Phase | Volume | Creator pool rate | Creator pool | Deployer (25%) | Recipients (75%) |
|---|---|---|---|---|---|
| Bonding curve | 200 SOL | 1% | 2 SOL | 0.5 SOL | 1.5 SOL |
| DAMM v2 pool | 1,000 SOL | 0.75% | 7.5 SOL | 1.875 SOL | 5.625 SOL |
| Total | 1,200 SOL | 9.5 SOL | 2.375 SOL | 7.125 SOL |
If the recipients are two wallets at 50% each, each claims about 3.56 SOL. Your actual claimable balance is the real number; this is for planning.
How do you claim Bags fees?
You claim by signing transactions that move your share out of the token's fee-share account into your wallet. There are three routes.
In the Bags app. Connect the wallet that is listed as a recipient and claim from your earnings view. App menus change, so look for fees or earnings. You pay only network fees.
With Bags' API or CLI. Bags' claim guide says the flow needs only "a token mint address and your wallet". The API returns "an array of versioned transactions ready to sign and send", choosing the claim path by position type (virtual pool, DAMM v2 or custom fee vault). The CLI offers bags fees list, bags fees claim and bags fees claim-all. The docs add one important detail: the deployer share uses a separate Deployer Fees flow, and the creator claim endpoints "do not include or withdraw it", even when the deployer is also a recipient.
With SOLTidy's Claim Creator Fees. If you launch on several launchpads, one scan is easier than checking each:
- Open Claim Creator Fees and connect your creator wallet, or switch to many wallets and paste several keys. Keys stay in your browser.
- The scan reads Bags' fee-share program for every Bags token where your wallet is in the first three claimer slots, on both the current program and the original two-claimer version, plus pump.fun, PumpSwap, Raydium LaunchLab and CPMM, and Meteora DBC and DAMM v2.
- Review each row's SOL, SOLTidy's 5% and what you keep. If fees are still in a token's pool, the row says the amount includes them; the claim collects them into the fee share first.
- Claim all or row by row. Claims are packed into as few transactions as fit and pay out to the wallet that earned them.
Example: 1.2 SOL as your share of a Bags token and 0.8 SOL from a LaunchLab vault claim together for 1.9 SOL to you and 0.1 SOL to SOLTidy. SOLTidy's scan covers recipient shares in the fee-share program; for the separate deployer share, use Bags' Deployer Fees flow. If you only launch on Bags, the Bags app costs less.
Why can't I see my Bags fees?
The usual reasons, from most to least common:
- Your wallet isn't a recipient. Only wallets listed in the token's fee-share configuration can claim. A wallet that only deployed the token has the deployer share, which is claimed separately.
- Fees haven't been collected from the pool yet. Bags moves fees from the pool into the fee share periodically. SOLTidy's scan includes those by simulating the collection; some views show only what has been collected.
- The fee mode pays little before migration. On the low-pre mode, the creator pool gets 0.125% on the curve.
- The token has had little volume. Fees are a percentage of volume, and most launches see little. Jupiter's index counted 2,708 Bags launches and only 8 graduations in the 30 days to November 5, 2026, shown on SOLTidy's Launchpad Stats.
Selling Bags tokens from several wallets
Creators who hold tokens across several wallets can sell them with Bags Mass Sell, which sells on the bonding curve or, after graduation, on the token's Meteora pool through Jupiter, from up to 200 wallets for 0.5% of the SOL received, capped at 0.1 SOL per run. Bags Mass Buy does the reverse. SOLTidy cannot create Bags tokens: every Bags launch is signed by Bags' own token-creation authority through its API.
Selling a large share of a token you earn fees on is visible to every holder. Say what you are doing.
Bottom line
Bags pays creators from a fee-share account per token: by default 1% of curve volume and 0.75% of pool volume, with 25% of that pool going to the deployer on new SOL configs and the rest split among up to 100 recipients. Claim recipient shares in the Bags app, through Bags' API and CLI, or across every launchpad at once with SOLTidy's Claim Creator Fees for 5%; claim the deployer share through Bags' Deployer Fees flow. For comparison, pump.fun creator fees explained works through the same math for pump.fun.
Questions & answers
How much does a Bags creator earn?
On the default fee mode, the creator pool receives 1% of every trade before migration and 0.75% after. On new SOL fee-share configs the deployer gets 25% of that pool and the configured recipients share 75%, so a coin with 100 SOL of pre-migration volume puts 1 SOL into the pool: 0.25 SOL to the deployer and 0.75 SOL to the recipients. Other fee modes range from 0.125% to 5% for the creator pool.
How do I claim my Bags fees?
Connect the wallet that is listed as a fee recipient and claim in the Bags app, or use Bags' API or CLI, which return ready-to-sign claim transactions for your wallet and a token mint. Tools that read Bags' fee-share program, such as SOLTidy's Claim Creator Fees, can also find and claim your share. Only listed recipients can claim, and fees always pay out to their own wallets.
What is the Bags deployer fee?
On newly created SOL fee-share v2 configs, Bags reserves 25% of the gross creator pool for the token's deployer, separate from the fee recipients. Bags' docs say the deployer share has its own Deployer Fees flow, and the normal creator claim endpoints do not include or withdraw it, even when the deployer is also a recipient.
Can Bags fees be split with other people?
Yes. Bags is built around fee sharing: a token's fee-share configuration lists recipient wallets and their shares in basis points. Bags' API reference describes support for multiple fee claimers, up to 100. Each recipient claims its own share.
When does a Bags token graduate?
On most fee modes when 85 SOL has been raised on the bonding curve, according to Bags' docs; the 85%-supply-locked mode graduates at about 100 SOL and the 96%-locked mode at 80 SOL. The token then migrates to a Meteora DAMM v2 pool. Graduations are rare: Jupiter's index counted 8 Bags graduations from 2,708 launches in the 30 days to November 5, 2026.
Why does my Bags claim show fees still in the pool?
Bags collects trading fees from a token's pool into its fee share periodically. Fees earned since the last collection are still in the pool. SOLTidy's scan simulates that collection step to show your full share, and the claim moves them in first, so the amount can differ slightly if trades happen in between.
