> 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).
# Devnet Faucet
[Devnet Faucet](https://j.tools/en/tools/devnet-faucet) hands you free Solana devnet SOL for testing. 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, no signing on your end. Just an address and a click.
{% hint style="info" %}
**Coming soon.** Devnet Faucet is not live yet. The page currently shows a coming-soon screen, so the claim form is not exposed. While you wait, the [Solana CLI airdrop](#what-to-use-in-the-meantime) covers the same need.
{% endhint %}
## What it will do
* Send free **devnet** SOL to any valid devnet wallet address you enter.
* Let you pick a preset amount or type a custom one, within the allowed range.
* Return a Solana Explorer link (cluster set to devnet) so you can confirm the transfer landed.
* Run the whole thing server-side. You supply an address only, so there is nothing to sign and no keys to expose.
It is built for the testing loop, not for value. Devnet SOL is worthless outside of devnet and exists only so you can exercise real flows without spending anything.
## When to use this
* 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.
* You want a one-click claim instead of running the `solana airdrop` command yourself.
## What you will need
* A valid Solana devnet wallet address. The faucet checks it as a base58 [pubkey](/getting-started/glossary.md), so a mainnet address or a typo will be rejected.
* Nothing else. No wallet connection and no signature are required from you. The platform faucet covers the transfer.
{% 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 %}
## How a claim will work
When the tool goes live, the flow looks like this:
{% 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 type a custom value. The allowed range is shown in the tool, and the exact bounds are set by the platform and can change at launch.
{% endstep %}
{% step %}
### Claim
Click **Claim Free SOL**. The request goes to the faucet, which picks a funded platform faucet wallet (or falls back to a direct devnet airdrop), 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
| Field | What it does |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Recipient address | The devnet wallet that receives the SOL. Validated as a base58 Solana pubkey. Mainnet transfers are not supported. |
| Amount | How much devnet SOL to claim. The tool shows the allowed range, with presets plus a custom input. First-time claims may be fixed to a small set amount (see below). |
## Limits and fair use
The faucet is shared, so it has guardrails to keep it usable for everyone.
* **Free.** There is no platform fee. Devnet SOL has no monetary value, so there is nothing to charge for.
* **First-claim policy.** A wallet's first successful claim is capped to one fixed, small amount (the exact figure is the current default, shown in the tool and subject to change). This is on by default.
* **Rate limits, cooldown, and quotas.** Each IP and wallet gets a limited number of requests per window, a cooldown between claims, and a daily cap. The defaults are modest on purpose. If you hit one, wait and try again later.
## If something goes wrong
Because the faucet is shared and devnet itself can get congested, a claim can be rejected or temporarily queued.
* **Invalid address or amount.** `INVALID_ADDRESS` means the address is not a valid devnet pubkey; `INVALID_AMOUNT` means the amount is outside the allowed range.
* **Slow down.** `RATE_LIMITED`, `COOLDOWN_ACTIVE`, and `DAILY_QUOTA_EXCEEDED` all mean you have hit a fair-use guardrail. Wait out the window.
* **First-claim rules.** `FIRST_CLAIM_ALREADY_USED` means that wallet already took its one free first claim; `FIRST_CLAIM_FIXED_AMOUNT` means the first claim must use the fixed amount.
* **Faucet busy.** `FAUCET_TEMPORARILY_UNAVAILABLE`, `FAUCET_OUT_OF_STOCK`, and `CLAIM_TIMEOUT` are retriable. Devnet was congested or the faucet is refilling. Try again shortly.
* **Not set up.** `FAUCET_NOT_CONFIGURED` means the server faucet is not funded or enabled yet.
For the full list, see the [Error codes reference](/reference/error-codes.md).
## FAQ
Is devnet SOL worth anything?
No. It only works on Solana devnet and has no value on mainnet or any exchange. It exists purely so you can test without spending real money.
Do I need to connect a wallet or sign anything?
No. You enter a devnet address and that is it. The platform faucet does the signing and sending server-side, so there is no signature and no key handling on your side.
Why was my claim limited or rejected?
The faucet is shared, so it enforces rate limits, a per-wallet and per-IP cooldown, and daily quotas. A new wallet also gets a fixed small first claim. If you hit a limit, wait for the window to reset and try again.
When does it go live?
It is in coming-soon status. The backend exists, but the public page currently shows a placeholder. Until then, use the Solana CLI airdrop below.
## What to use in the meantime
Until Devnet Faucet ships, the Solana CLI gives you the same test SOL:
```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" %}
[Wallet Generator](/tools/wallets/wallet-generator.md)
{% endcontent-ref %}
{% content-ref url="/pages/FBclvwoESckP7xeMzCIh" %}
[WSOL Wrapper](/tools/utilities/wsol-wrapper.md)
{% endcontent-ref %}
{% content-ref url="/pages/tcfZtvMT2fZ8MMKcMlpF" %}
[Close Account](/tools/utilities/close-account.md)
{% endcontent-ref %}
{% hint style="success" %}
**J Tools is non-custodial.** We never hold your private keys and never ask for them. Every transaction is built in your browser and signed by your own wallet. If any page ever asks you to paste a private key, stop, close it, and let us know.
{% 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.