> For the complete documentation index, see [llms.txt](https://hello.kodadot.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hello.kodadot.xyz/tutorial/teleport.md).

# Teleport

Teleport helps you to bridge assets between chains. This feature is necessary if you want to interact with other chains.

In KodaDot, we have two types of teleport:

* **🟢 Auto teleport:** You will receive this option automatically once you want to create/ buy/ interact with NFTs and you don't have enough funds on one chain. It will automatically show during the process.
* **🔵 Teleport (Bridge):** This is the same teleport as above, with the same functionality. The main difference - it's **manual**. You will find it in the menu below your profile, and you will be able to move your funds between chains as you need.

## Learn more about Teleport

{% content-ref url="/pages/w3D8NQHAt5v9P0amkglF" %}
[Auto Teleport](/tutorial/teleport/auto-teleport.md)
{% endcontent-ref %}

{% content-ref url="/pages/pqby3uHrpfCRVXVo3zvG" %}
[Teleport (Bridge)](/tutorial/teleport/teleport-bridge.md)
{% endcontent-ref %}

#### Remember

It's important to remind you that bridging funds between chains will **just move** your funds between different chains we support. Your funds **can always be returned** to the main network, and they **don't lose value** when you bridge them. The process of bridging is very quick and simple.


---

# 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://hello.kodadot.xyz/tutorial/teleport.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.