Summary
A Polygon faucet is a service that sends small amounts of testnet POL to a wallet address so you can pay gas while building on Polygon test networks. Test POL has no real value and only works on testnets such as Polygon Amoy (chain ID 80002).
The most common source is the official Polygon faucet, which dispenses test POL for Amoy and test ETH for Ethereum Sepolia. Several third-party faucets also serve Amoy, often with different drip sizes, cooldowns, and wallet or social-login requirements. Whichever you use, the tokens land on the testnet only — they will not appear on Polygon mainnet.
This page covers how to claim test POL, add Amoy to your wallet, verify the drip with an RPC call, and fix the usual reasons a faucet request appears to fail. It also explains where a reliable Amoy RPC endpoint fits into the workflow, including when a managed or dedicated node from OnFinality makes sense.
Key Takeaways
- A Polygon faucet dispenses testnet POL only; it cannot send real POL to Polygon mainnet.
- Most faucet requests target Polygon Amoy (chain ID 80002), the current PoS testnet.
- Faucets usually require a wallet address, a captcha, and sometimes a social or account login.
- If a drip does not show up, check the network selected in your wallet before assuming the faucet failed.
- Verify a drip with a balance or transaction lookup over an Amoy RPC endpoint rather than relying on the wallet UI alone.
- Test POL is for gas and contract testing; never send real funds to a testnet address expecting them back.
Quick answer: what a Polygon faucet actually gives you
A Polygon faucet sends a small amount of testnet POL to an address you specify. That POL is used to pay gas on a Polygon testnet, most commonly Polygon Amoy. It has no market value and does not exist on Polygon mainnet.
The official Polygon faucet is the first place to try. It supports Amoy for test POL and Ethereum Sepolia for test ETH, which is useful when a Polygon test flow also touches Ethereum tooling. Third-party faucets such as Chainlink, Alchemy, QuickNode, GetBlock, and Stakely also serve Amoy, each with its own drip size, cooldown, and login requirements.
The important distinction: a faucet request is a testnet transaction. If your wallet is pointed at Polygon mainnet, the drip will not appear there, and any POL you see on mainnet is real and unrelated to the faucet.
- Faucet tokens are testnet-only and cannot be bridged to mainnet as real value.
- Amoy is the current PoS testnet; older Mumbai references are outdated.
- Drip sizes are small by design — enough for gas, not for load testing at scale.
Decision guide: which faucet path fits your situation
Faucet choice depends less on the brand and more on what your test flow needs: a one-off drip, a repeatable CI claim, or tokens for a specific integration such as an oracle or wallet connector.
Use the table below to pick a starting point, then verify the result over RPC before debugging anything else.
| Criterion | What to check | Why it matters |
|---|---|---|
| Official Polygon faucet | Supports Amoy (POL) and Ethereum Sepolia (ETH); requires wallet address and captcha | Best default for a first drip and for matching official docs |
| Chainlink faucet | Amoy POL plus LINK; wallet connect flow | Useful when your contract also needs test LINK for oracle work |
| Alchemy / QuickNode / GetBlock faucets | Account or social login, drip size, cooldown | Good fallback when the official faucet is rate-limited or dry |
| Stakely multicoin faucet | Small POL drip, captcha, optional social step | Quick top-up for gas when you only need a little POL |
| Community / Discord drips | Community rules, bot registration, trust | Last resort; verify the sender and never share a seed phrase |
Amoy chain settings to add before you claim
Most faucet confusion comes from a wallet pointed at the wrong network. Add Polygon Amoy to your wallet first, then request the drip to an address on that network.
The settings below match the Polygon Amoy network configuration. Keep the chain ID and currency symbol consistent so the wallet does not create a duplicate network entry.
| Criterion | What to check | Why it matters |
|---|---|---|
| Network name | Polygon Amoy | Clear label avoids mixing it up with Polygon mainnet |
| Chain ID | 80002 | Wrong chain ID sends the wallet to a different network |
| Currency symbol | POL | Amoy gas is denominated in POL, not MATIC |
| RPC URL | https://polygon-amoy.api.onfinality.io/public | A working endpoint lets you confirm balances and receipts |
| Block explorer | https://amoy.polygonscan.com | Use it to look up the faucet transaction hash |
Claiming test POL and confirming it over RPC
Open the faucet, select Amoy, paste your wallet address, complete the captcha or login step, and submit. The faucet returns a transaction hash. Copy it — that hash is the fastest way to confirm whether the drip was sent.
Do not trust the wallet balance alone. Wallets cache balances and sometimes show stale values. Query the Amoy endpoint directly to confirm the balance and the transaction receipt.
- Use an address you control and have backed up; faucets cannot reverse a drip.
- Wait for the transaction to be mined before retrying — duplicate requests can hit cooldowns.
- If the faucet shows a hash, check it on Amoy Polygonscan before assuming failure.
Debug path: when the faucet drip does not appear
Work through these checks in order. Most 'faucet not working' reports resolve at the first or second step, usually because the wallet was on mainnet or the transaction was still pending.
If the transaction hash exists and is confirmed but your balance is still zero, confirm you are reading the balance for the same address on chain ID 80002.
| Criterion | What to check | Why it matters |
|---|---|---|
| Balance shows zero | Wallet network set to Amoy, chain ID 80002 | Mainnet wallets never show testnet POL |
| Faucet says request sent, no hash | Captcha or login step completed; cooldown expired | Incomplete requests are often silently dropped |
| Hash pending for a long time | Amoy network status and gas price | Congestion delays confirmation, not the drip itself |
| Faucet refuses the address | Address format, faucet per-address limits | Some faucets cap claims per address or per day |
| Contract call still fails | Gas limit, contract address, RPC endpoint health | The drip may be fine while the endpoint or call is the problem |
Where the RPC endpoint fits after the faucet
A faucet gets you gas; an RPC endpoint gets you a working chain connection. Public endpoints are fine for a quick balance check, but they can be slow or rate-limited during repeated test runs. For CI pipelines, staging deployments, or teams running many contract tests, a managed RPC API or a dedicated node gives you a more predictable connection.
OnFinality provides RPC API access and dedicated node infrastructure for Polygon networks. You can point your test tooling at an endpoint you control, then move the same workflow to mainnet when you are ready. Check the Polygon network page for current endpoint details and the pricing page to match capacity to your workload.
- Use a managed endpoint for repeatable test runs and CI jobs.
- Use a dedicated node when test or staging traffic needs isolated resources.
- Keep testnet and mainnet endpoints in separate config so they never mix.
Safety and operational notes
Faucets are a common target for scams. No legitimate faucet needs your seed phrase or private key. If a site asks for either, close it. If someone offers to 'top up' your wallet in exchange for a payment, treat it as a scam.
Test POL is not an investment and cannot be sold. Keep test wallets separate from wallets that hold real assets, and label them clearly in your config so a test script never points at mainnet by accident.
- Never share a seed phrase or private key with a faucet or a person offering tokens.
- Keep test and production wallets separate.
- Store Amoy and mainnet RPC URLs in separate environment variables.
Frequently Asked Questions
Can I get real POL from a Polygon faucet?
No. Faucets dispense testnet tokens only, usually on Polygon Amoy. Real POL exists on Polygon mainnet and must be acquired through an exchange or other legitimate source.
Which network does the Polygon faucet send to?
The official Polygon faucet supports Polygon Amoy for test POL and Ethereum Sepolia for test ETH. Third-party faucets may support Amoy and other testnets, so check the network selector before submitting.
Why did my faucet request not arrive?
The most common causes are a wallet pointed at mainnet instead of Amoy, an incomplete captcha or login step, or a faucet cooldown. If you have a transaction hash, check it on Amoy Polygonscan before retrying.
How much test POL does a faucet send?
Drip sizes vary by faucet and can change over time. They are intended to cover gas for testing, not to fund large-scale load tests. For heavier testing, plan to top up from multiple sources or use a funded test wallet.
Do I need an RPC endpoint to use a faucet?
Not to claim the drip, but you need one to confirm the balance and run transactions afterward. A reliable Amoy RPC endpoint makes it easier to verify drips and debug failed contract calls.
Ethereum
Solana
Polygon
Base
Arbitrum
BNB Chain
Polkadot
Optimism
