> For the complete documentation index, see [llms.txt](https://mirror-networking.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mirror-networking.gitbook.io/docs/manual/transports.md).

# Transports

## Built-in Transports

These transports are included with Mirror.

* [KCP ](/docs/manual/transports/kcp-transport.md)UDP transport based on kcp.c, line-by-line translation to C#
* [Telepathy](/docs/manual/transports/telepathy-transport.md) - Simple, message based, MMO Scale TCP networking in C#. And no magic.
* [Simple Web Sockets](/docs/manual/transports/websockets-transport.md) - WebGL transport layer for Mirror that target browser clients.
* [Multiplexer](/docs/manual/transports/multiplex-transport.md) - Bridging transport to allow a server to handle clients on different transports concurrently, for example desktop clients using Telepathy together with WebGL clients using Websockets.
* [Latency Simulation](/docs/manual/transports/latency-simulaton-transport.md) - Middleman transport to test non-ideal network conditions
* [Encryption](/docs/manual/transports/encryption-transport.md) - Middleman transport to encrypt a different transport
* [Edgegap Relay Transports](/docs/manual/transports/edgegap-transports.md) - Transports to utilize [Edgegaps Destributed Relay](https://edgegap.com/en/platform/distributed-relay) Service

## Additional Transports

These transports are maintained by third parties outside of Mirror.

* [Monke](https://github.com/JesusLuvsYooh/monke) - plug and play encrypted middleman transport layer for mirror.
* [Ignorance](/docs/manual/transports/ignorance.md) - reliable and unreliable sequenced UDP transport based on ENet.
* [LiteNetLibTransport](/docs/manual/transports/litenetlib-transport.md) - UDP transport based on [LiteNetLib](https://github.com/RevenantX/LiteNetLib).

## Relay Transports

These transports are maintained by third parties and use relay infrastructure to connect clients to servers behind firewalls / NAT.

* [Steam - FizzySteamworks](/docs/manual/transports/fizzysteamworks-transport.md) - Transport utilizing Steam P2P network, building on [Steamworks.NET](https://github.com/rlabrecque/Steamworks.NET).
* [Epic - Epic Online Services](https://github.com/Ludogram/EpicOnlineTransport) - Relay transport utilizing Epic's free relay service.
* [LRM - Light Reflective Mirror](https://github.com/Speidy674/Light-Reflective-Mirror) - Relay transport for WebGL clients.

## Changing Transports

Changing transports is very easy and only requires a few steps:

* Go to the game object that has the Network Manager component
* Add another transport script via the Add Component button
* Drag the transport script to the "Transport" field in the Network Manager
* Remove the old transport script (optional)

If you have connection issues with a transport that requires port forwarding, make sure to port forward the correct protocol (TCP / UDP).


---

# 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://mirror-networking.gitbook.io/docs/manual/transports.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.