> For the complete documentation index, see [llms.txt](https://docs.megaeth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.megaeth.com/user-guide/faucet.md).

# Get ETH on Testnet

MegaETH testnet faucet — request limits, eligibility, and how to get testnet ETH.

The MegaETH faucet gives you free testnet ETH so you can try out the network without spending real money. Testnet ETH has no monetary value — it is only for testing.

{% hint style="warning" %}
The faucet is for **testnet only**. If you need ETH on MegaETH Mainnet, see [Get Funds on Mainnet](/user-guide/bridge.md) for bridging and other options.
{% endhint %}

## How to Get Testnet ETH

Visit the faucet at [**testnet.megaeth.com**](https://testnet.megaeth.com).

Enter your wallet address and complete the verification step. The faucet will send testnet ETH directly to your wallet.

{% hint style="info" %}
If you are on the Fluffle whitelist, registered via Discord, active in Telegram, or have interacted with MegaETH on Twitter, you may already be prefunded and can start using the chain right away.
{% endhint %}

## Limits

* The faucet provides **1 testnet ETH**, **100 testnet USDM**, and **1,000 testnet MEGA** per user every 24 hours.
* Requests are tracked by IP address. Switching wallets will not bypass the limit.
* If you need more testnet ETH to deploy and test a protocol, reach out to the team directly.

## Rules

* Do not set up your own faucet in your dApp. Direct users to the official MegaETH faucet instead.
* The limits exist to prevent abuse and maintain network stability — not to create artificial scarcity.

## After Mainnet

The faucet will remain open after mainnet launch, but will continue to distribute tokens only for the testnet. It will not be possible to bridge testnet ETH onto mainnet.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.megaeth.com/user-guide/faucet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.