The Solana devnet faucet at faucet.solana.com, operated by the Solana Foundation, airdrops free devnet SOL to a wallet address for testing programs and transactions. As of October 2026 the faucet allows a maximum of 2 requests every 8 hours, and signing in with GitHub unlocks a higher limit, per the Solana Foundation faucet. The same airdrop is available from the command line with solana airdrop 2, per Solana's devnet SOL guide.
​

Devnet is the Solana cluster that application developers should target, and its tokens are not real, per Solana's cluster documentation. This page covers every route to devnet SOL that Solana's own guide lists, the faucets that publish their own limits, and the settings needed to connect a wallet or CLI to devnet. All pages were fetched on October 13, 2026.
​

There are five routes to devnet SOL: the Solana Foundation web faucet, a CLI or SDK airdrop, third-party web faucets, a proof-of-work faucet and a local validator. Web faucets are fastest for a one-off wallet. The CLI suits scripts. A local validator removes rate limits entirely for tests that do not need a public network.
​

The Solana Foundation faucet is a web form: pick devnet or testnet, enter an address and an amount, and confirm the airdrop. Anonymous use is capped per time window. Signing in with GitHub raises the cap, and the faucet validates GitHub accounts, so some accounts may not pass.
​

The Solana Foundation faucet page shows a maximum of 2 requests every 8 hours and says it does not distribute mainnet SOL. It also tells AI agents not to use the web form and lists three programmatic alternatives instead: the CLI airdrop, the proof-of-work faucet and a local validator. The devnet SOL guide lists the same faucet as the Solana Foundation's public web faucet for both devnet and testnet.
​

The CLI airdrop asks the devnet RPC node to send SOL to an address. Point the Solana CLI at devnet once, then request an amount. It is the quickest route inside scripts and CI, though airdrops share rate limits with everyone else using the public endpoint.
​

The commands come from Solana's cluster docs, the devnet SOL guide and the Solana Foundation faucet page. In JavaScript, the guide shows connection.requestAirdrop() against https://api.devnet.solana.com. To use an RPC provider's faucet instead, set the CLI URL to that provider's endpoint and run the same airdrop command; the guide lists Helius, QuickNode and Triton as providers that distribute devnet SOL.
​

Solana's own guide lists six web faucets for devnet, two Discord bot faucets and a proof-of-work faucet. They exist because the public faucet is rate limited. Each has its own limit, so cycling through two or three usually gets a developer enough SOL for a day of testing.

Devnet has one public RPC endpoint, https://api.devnet.solana.com, a single node with published rate limits. The Solana CLI only needs that URL or a provider URL. Teams that hit the limits should switch to a keyed endpoint from an RPC provider rather than retry.
​

Solana's cluster docs list these devnet rate limits per IP as of October 2026:
​

The same page says devnet typically runs the same software release branch as mainnet and may be subject to ledger resets, while testnet is for stress-testing upgrades and validator performance. That is why application developers should build on devnet, not testnet. Explorer options for devnet transactions are covered in Best Solana block explorers.
​

Ordinary transactions cost a few thousand lamports, and a lamport is a billionth of a SOL. Program deployments need far more, because a deploy first copies the program's data into a funded buffer account, so deploys use the most devnet SOL.
​

The base fee is 5,000 lamports per signature, per Solana's fee docs, and one lamport equals 0.000000001 SOL, per Solana's terminology reference. Fee mechanics are covered in Solana Transaction Fees. When a deploy fails midway, SOL can sit in a buffer account; the devnet SOL guide shows solana program show --buffers to list them and solana program close to reclaim the SOL.
​

Devnet faucets are rate limited by design, shared by every developer on the network, and sometimes empty when demand spikes. Devnet itself can be reset. Neither problem blocks development, but both argue for keeping heavy tests on a local validator.

No. Devnet tokens are not real, per Solana's cluster docs.
​

https://api.devnet.solana.com, per Solana's cluster docs.
​

Devnet for applications. Testnet is for stress-testing releases and validator performance, per Solana's cluster docs.
​

Run solana-test-validator and airdrop to localhost, which faucet.solana.com describes as having no rate limits, per the Solana Foundation faucet.
​

Yes, from Circle's faucet or the CDP Faucet; see USDC testnet faucets.
​

Faucet limits, commands and endpoints were read from Solana Foundation, QuickNode and Coinbase Developer Platform pages on October 13, 2026. No airdrops were requested. Limits change; check the live pages.