> For the complete documentation index, see [llms.txt](https://docs.sphera.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sphera.world/nft-bridge/how-to-bridge.md).

# How to Bridge

This guide walks you through bridging your Sphera NFTs between Hedera and Avalanche.

## Prerequisites

Before you start, make sure you have:

* [ ] **HashPack Wallet** - For Hedera transactions ([download](https://hashpack.app))
* [ ] **MetaMask or EVM Wallet** - For Avalanche transactions
* [ ] **HBAR** - Small amount for Hedera gas fees (\~2-5 HBAR)
* [ ] **AVAX** - Small amount for Avalanche gas fees (\~0.01 AVAX)
* [ ] **A Sphera NFT** - In one of the supported collections

## Bridge: Hedera → Avalanche

### Step 1: Connect Your Wallets

1. Go to [nftbridge.sphera.world](https://nftbridge.sphera.world)
2. Click **Connect HashPack** and approve the connection
3. Click **Connect MetaMask** and approve the connection

### Step 2: Select Your NFT

1. Your Hedera NFTs will appear in the grid
2. Click on the NFT you want to bridge
3. The NFT card will highlight when selected

### Step 3: Choose Destination

1. Click **Bridge**
2. Enter your Avalanche destination address (or leave blank to use connected wallet)
3. Review the transaction details

### Step 4: Approve & Lock

1. Click **Confirm Bridge**
2. **First transaction**: Approve the bridge contract to transfer your NFT
3. **Second transaction**: Lock your NFT in the bridge contract
4. Wait for confirmation (\~10-30 seconds)

### Step 5: Receive on Avalanche

1. The bridge will automatically mint your wrapped NFT on Avalanche
2. You'll see a success message with transaction links
3. Your NFT now appears on Avalanche!

## Bridge: Avalanche → Hedera

### Step 1: Connect Your Wallets

Same as above - connect both HashPack and MetaMask.

### Step 2: Select Your Wrapped NFT

1. Your Avalanche NFTs will appear in the grid
2. Click on the wrapped NFT you want to bridge back
3. Make sure your MetaMask is on Avalanche network

### Step 3: Burn & Unlock

1. Click **Bridge**
2. Enter your Hedera destination address (or leave blank to use connected wallet)
3. Click **Confirm Bridge**
4. Approve the burn transaction in MetaMask
5. Wait for the bridge to unlock your original NFT

### Step 4: Receive on Hedera

1. The bridge will unlock your original NFT on Hedera
2. You'll see a success message with transaction links
3. Your original NFT is back in your Hedera wallet!

## Transaction Times

| Direction          | Typical Time  |
| ------------------ | ------------- |
| Hedera → Avalanche | 10-30 seconds |
| Avalanche → Hedera | 10-30 seconds |

## Fees

| Network               | Approximate Fee   |
| --------------------- | ----------------- |
| Hedera (lock/unlock)  | \~1-2 HBAR        |
| Avalanche (mint/burn) | \~0.005-0.01 AVAX |

## Troubleshooting

### Transaction stuck?

* Check [HashScan](https://hashscan.io) for Hedera transactions
* Check [Snowtrace](https://snowtrace.io) for Avalanche transactions
* If stuck for more than 5 minutes, contact support

### NFT not appearing?

* Refresh the page
* Disconnect and reconnect your wallet
* Wait a few minutes for blockchain indexing

### Need help?

Join our [Discord](https://discord.gg/ny4uKYPYfx) for support.


---

# 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.sphera.world/nft-bridge/how-to-bridge.md?ask=<question>&goal=<endgoal>
```

`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.