Polygon Multisender: Pay Many Wallets in POL, USDC or a Token

This Polygon multisender pays your list of Polygon PoS wallets in POL or one ERC-20 token, such as USDC or your own token. You pay a 2 POL Tokenry fee per recipient plus gas, both in POL, even on a USDC list. Up to 400 wallets go in each transaction, and longer lists are split. Your wallet signs every send.

Polygon ERC-202 POL per recipient, plus network gas

Token

From your wallet

Amount

Tokenry fee: 2 POL per recipient

Recipients

Header rows, extra columns and tab, comma or semicolon separators are handled for you

One recipient per line. Format: address,amount

Paste your recipient list above, upload a CSV, or add manually

Why Tokenry

  • No Code Required

    Create, send and manage tokens without writing any code. Your wallet signs every step.

  • Fully Transparent

    All token data is publicly visible and verifiable on block explorers.

  • Multi-Chain

    Works on Solana and 13 EVM chains, including Ethereum, Base, Arbitrum, Polygon and BNB Chain.

  • Full Ownership

    You have full control. We never hold your keys, tokens, or authority.

How it works

Send tokens to multiple addresses on Polygon

  1. 1

    Connect your wallet and confirm Polygon PoS

    Connect MetaMask, Rabby, Phantom, Coinbase Wallet, another browser wallet or WalletConnect. If your wallet is on another network, press "Switch to Polygon".

  2. 2

    Select POL or one ERC-20 token

    POL is preselected; for a token, choose it in the menu or paste its contract address. The menu shows each token's short address, so you can tell native USDC from USDC.e.

  3. 3

    Paste, upload or type the recipient list

    Use "Paste List", "Upload CSV" or "Manual Entry", with one address,amount pair per line.

  4. 4

    See what the list costs and what would fail

    Press "Review airdrop" to see the Tokenry fee and the number of transactions. Payouts that would fail are flagged, with a button to remove them.

  5. 5

    Confirm, then sign each Polygon transaction

    Press "Confirm and send", then confirm any signature or approval and each transaction, in order. Each confirmed transaction links to PolygonScan and cannot be undone.

FAQ

Frequently asked questions

Something not covered here? Contact support.

Why do I need POL to airdrop USDC on Polygon?

You need POL because Polygon PoS takes gas in POL, and the Tokenry fee is paid in POL too, whatever token the list sends. The Tokenry fee is 2 POL per recipient, so 400 recipients cost 800 POL in Tokenry fees, plus gas. The POL must be in your wallet on Polygon PoS; POL held on Ethereum does not count. POL (formerly MATIC) became Polygon's gas token on September 4, 2024 (Polygon).

Should I send native USDC or USDC.e on Polygon?

Send native USDC on Polygon unless your recipients ask for USDC.e. Circle issues native USDC, and its contract list for Polygon PoS gives 0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359. USDC.e, at 0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174, is a bridged form, and Circle says bridged forms of USDC such as USDC.e are not issued by Circle. Both report the symbol "USDC". Before you bulk send USDC on Polygon, compare the contract address in the menu and in the review's "Contract" row with the one your recipients expect. USDC.e sent to someone who wanted native USDC is a different token in their wallet.

What does my wallet approve when I send tokens on Polygon?

Sending POL on Polygon needs no approval; a token needs a signature or an approval so the multisender can send it from your wallet. From an ordinary wallet, native USDC needs only an ERC-2612 permit, a signed message that costs no gas. USDC.e and USDT (shown as USDT0) need an approval transaction, and smart-contract wallets, such as a Safe, always approve. The approval covers only what is left to send, never an unlimited amount. The prompt names the multisender contract, 0xC1CEbE1dE66Efdd0b415e5fbb5462469BB1b86ba, whose source code is verified on PolygonScan; the review's "Multisender contract" row shows the same address. Nobody owns that contract, it has no function to withdraw funds, and each token payout moves directly from your wallet to the recipient.

Does a Polygon token's tax or max wallet apply to multisender payouts?

A Polygon token's own rules apply to each multisender payout as if you sent it yourself, so you do not need to exempt the multisender. For a token made with Tokenry's current Polygon token creator, buy and sell taxes do not apply to payouts to wallets. A transfer tax, if set, is charged only when you and the recipient both use ordinary wallets, and never while your wallet owns the token. A payout that would push a recipient above the max wallet is skipped, and the others still arrive. The token's owner can raise or remove the limits in the Polygon token manager; "Remove limits" cannot be undone.

Is a multisender worth 2 POL per wallet when Polygon gas is low?

On Polygon, a multisender is worth it for fewer wallet confirmations, not to save POL. Paying each wallet with a separate transfer costs only gas, with no Tokenry fee. The gas a multisender saves per token payout is small next to the Tokenry fee, so one-by-one sends cost less POL in total. The multisender gives you one wallet confirmation per transaction instead of one per recipient, plus a review of the whole list before you sign.

01

How a long Polygon list splits under the 33,554,432 gas cap

The Polygon multisender runs on Polygon PoS (chain ID 137) only; Polygon zkEVM has shut down. Polygon PoS caps every transaction at 33,554,432 gas, set by the Madhugiri hardfork on December 9, 2025 (Bor v2.5.0).

Normally the split comes from Tokenry's setting of up to 400 wallets per transaction, not from Polygon's cap. A 400-wallet POL send to new wallets is estimated at about 14.6 million gas, under half the cap.

One review accepts as many as 10,000 recipients, and a repeated address is paid only once. The batch transfer on Polygon then goes out as several transactions in a row: a list of 900 wallets goes as 400, 400 and 100. The next wallet prompt opens after the previous transaction confirms. When a list stops after at least one transaction has gone through, "Send the remaining N" builds a new review with only the wallets whose transaction failed or was never sent.

02

What a refused payout or a contract recipient costs on Polygon

When the token refuses a payout, or a wallet refuses POL, the Polygon multisender skips that payout. The other payouts in that transaction still arrive. The skipped payout's Tokenry fee comes back in the same transaction, and so does its POL on a POL list. A refused token payout never leaves your wallet. Circle can block addresses on native USDC, so a USDC payout to a blocked address is skipped this way.

A payout that would stop the whole transaction must be removed before you can confirm. A transaction that still reverts pays no one and takes no Tokenry fee, but its gas is spent.

The review warns about recipients that are contracts, such as a DEX pool. Tokens sent to a contract often cannot be moved out. A multisig address on your list may exist on Ethereum but have no contract on Polygon PoS, and a Safe cannot always be recreated there. The review then treats it as a normal wallet, so check each multisig before you send.