> For the complete documentation index, see [llms.txt](https://docs.j.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.j.tools/tools/utilities/devnet-faucet.md). # Solana Devnet Faucet: Free Test SOL Daily [Devnet Faucet](https://j.tools/en/tools/devnet-faucet) hands you free Solana devnet SOL so you can test flows on a network that costs nothing. You paste a devnet wallet address, pick an amount, and the platform faucet signs and sends the test SOL with a transaction you can track on the explorer. No wallet connection and no signing on your side. Just an address and a click. {% hint style="success" %} **Claim limits.** Up to 25 SOL per claim, 25 SOL per 24 hours counted per wallet and per IP, and 30 seconds between claims. No login, no wallet connection, no signature. {% endhint %} ## What it is Devnet Faucet is a one-click source of free devnet SOL. Devnet is Solana's public test network, a separate cluster from mainnet that runs the same programs but carries no real value. The SOL it dispenses exists only so you can pay test transaction fees, fund test wallets, and exercise the same flows you would run on mainnet without spending a cent. You give the faucet a devnet address and an amount. The platform faucet wallet covers the transfer and hands you back an explorer link so you can confirm the SOL arrived. No token to pick, no signature to give, and no GitHub login of the kind other faucets ask for. ## How it works (under the hood) A faucet is the inverse of every other tool here. Instead of you signing and the platform charging a fee, the platform signs and pays, and you only supply a destination. When you submit a claim, the request goes to the faucet server. It validates the address as a base58 Solana public key and checks the amount against the allowed range. If both pass, the faucet picks a funded platform faucet wallet on devnet, builds a transfer, signs it with the faucet wallet's key, and sends it to the devnet cluster. When no faucet wallet is configured at all, the server can fall back to a direct devnet airdrop request; when that fallback is off as well, the claim returns `FAUCET_NOT_CONFIGURED`. A configured pool that has run dry does not fall back: the claim returns `FAUCET_OUT_OF_STOCK` and you retry once it refills. On a claim that goes through, the SOL lands in your address and you get the explorer link. Because the faucet wallet signs everything, you never connect a wallet and never produce a signature. You hand over a public address, and that is all the faucet ever sees of you. The faucet is shared across everyone, so it runs guardrails: a 30-second cooldown between claims, a rolling 25 SOL per 24 hours quota, both counted per wallet and per IP, and a 1000 SOL per 24 hours cap across the whole faucet. These keep the pool usable rather than draining it for one caller. ## When to use it * You are a Solana developer or tester who needs throwaway SOL on devnet. * You are smoke-testing a token mint, an [LP](/concepts/dexes-and-liquidity.md), or a swap on devnet and need gas to cover fees. * You just generated fresh test wallets and want to fund them before running a flow. * You want a one-click claim instead of running the `solana airdrop` command yourself. ## Before you start * Have a valid Solana **devnet** wallet address ready. The faucet validates it as a base58 [pubkey](/getting-started/glossary.md), so a typo or a mainnet-only address will be rejected. * Nothing else is required. {% hint style="warning" %} This is **devnet only**. Never send a mainnet address or any real asset through this tool. Devnet SOL has no monetary value and cannot move to mainnet. {% endhint %} ## Step by step {% stepper %} {% step %} ### Enter your devnet address Paste the Solana devnet wallet address that should receive the SOL. {% endstep %} {% step %} ### Pick an amount Choose one of the preset amounts or drag the slider. You can claim anything from 0.1 up to 25 SOL, with a daily cap of 25 SOL per wallet and per IP. {% endstep %} {% step %} ### Claim Click **Claim Free SOL**. The request goes to the faucet, which picks a funded platform faucet wallet (or a direct devnet airdrop when no faucet wallet is configured), signs, and sends. {% endstep %} {% step %} ### Confirm on the explorer On success you get a Solana Explorer link with the cluster set to devnet. Open it to see the transfer. {% endstep %} {% endstepper %} [**See Devnet Faucet in the app →**](https://j.tools/en/tools/devnet-faucet) ## The options, explained * **Recipient address:** The devnet wallet that receives the SOL. Validated as a base58 Solana pubkey. Mainnet transfers are not supported, so a mainnet-only address or a typo is rejected. * **Amount:** How much devnet SOL to claim, from 0.1 up to 25 SOL. Preset buttons plus a slider let you pick any amount in range. The 25 SOL cap applies per wallet and per IP over a rolling 24 hours. ## Fees and costs {% hint style="warning" %} **About fees.** Every action has two costs: the Solana **network fee** paid to validators, and the **J Tools platform fee**. The platform fee always shows in the app before you confirm, and nothing is charged until you sign. Fees can change over time, so trust the in-app summary rather than a number you saw once. {% endhint %} **This tool is free.** There is no platform fee. Devnet SOL has no real value; it is for testing only. | Cost | Amount | | -------------------- | ----------------------------------------------------------------------------------------------- | | J Tools platform fee | Free (0 SOL) | | On-chain cost | None for you. The platform faucet wallet pays the devnet transaction fee (valueless devnet SOL) | There is no network fee for you either. The platform faucet wallet pays the devnet transaction fee, and devnet fees are paid in devnet SOL that carries no value. You spend nothing on either side. ## Common mistakes and troubleshooting The faucet is shared and devnet itself can get congested, so a claim can be rejected or temporarily queued. The error tells you which guardrail you hit. * **Invalid address or amount.** `INVALID_ADDRESS` means the address is not a valid devnet pubkey, often a mainnet address pasted by mistake. `INVALID_AMOUNT` means the amount is outside the allowed range. * **Slow down.** `COOLDOWN_ACTIVE` means the 30-second wait between claims has not passed for your wallet or your IP. `DAILY_QUOTA_EXCEEDED` means the 25 SOL per 24 hours quota on that wallet or that IP is used up, and the message tells you how much is left. Both clear on their own. * **Faucet busy.** `FAUCET_TEMPORARILY_UNAVAILABLE`, `FAUCET_OUT_OF_STOCK`, `FAUCET_DAILY_CAP_REACHED` and `CLAIM_TIMEOUT` are retriable. The pool is empty, refilling, or past its 1000 SOL daily backstop, or devnet was congested. Try again shortly. * **Not set up.** `FAUCET_NOT_CONFIGURED` means no faucet wallet key is configured on the server yet. The codes above are specific to the faucet. For general platform errors, see the [Error codes reference](/reference/error-codes.md). ## Advanced tips * Splitting a claim across several devnet wallets does not raise your total. The 25 SOL per 24 hours quota and the 30-second cooldown are counted per IP as well as per wallet, so the same connection hits the same ceiling however many addresses you use. Plan a test session against one 25 SOL budget. * Always open the returned explorer link with the cluster set to devnet. A mainnet explorer view will show the address as empty even when the devnet transfer succeeded. * Devnet resets and congestion are normal. If a claim times out, the SOL usually did not move, so a retry is safe rather than a double-spend. ## Alternative: the Solana CLI If you prefer the terminal, the Solana CLI airdrop covers the same need. The public devnet airdrop is often rate-limited or busy, so this faucet is usually the more reliable route: ```bash solana airdrop 2 --url devnet ``` If you need fresh test wallets to fund, [Wallet Generator](/tools/wallets/wallet-generator.md) creates them. To prepare wrapped SOL or clean up rent-bearing accounts during testing, [WSOL Wrapper](/tools/utilities/wsol-wrapper.md) and [Close Account](/tools/utilities/close-account.md) help round out a devnet workflow. ## Related tools {% content-ref url="/pages/a7TACAPAW24OFOSbtgNw" %} [Solana Wallet Generator](/tools/wallets/wallet-generator.md) {% endcontent-ref %} {% content-ref url="/pages/FBclvwoESckP7xeMzCIh" %} [Wrap and Unwrap SOL](/tools/utilities/wsol-wrapper.md) {% endcontent-ref %} {% content-ref url="/pages/tcfZtvMT2fZ8MMKcMlpF" %} [Close Token Accounts](/tools/utilities/close-account.md) {% endcontent-ref %} {% hint style="success" %} **J Tools is non-custodial.** We never store or transmit your private keys and never ask for your seed phrase. Every transaction is signed in your own browser, and nothing about a key ever reaches our servers. A few multi-wallet tools do let you paste private keys for throwaway hot wallets, which stay in your browser tab and are used only to sign locally. Never paste a key tied to long-term holdings, and if a page ever asks for your seed phrase, stop and close it. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.j.tools/tools/utilities/devnet-faucet.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.