Terraria Field guide

Terraria crossplay: which platforms can share a server?

Check which Terraria platforms and versions can share a server, including tModLoader and TShock.

Terraria crossplay: which platforms can share a server?

PC and mobile Terraria can share a vanilla dedicated server when their releases are compatible. That existing address-based route is different from the broader console and join-code features in Re-Logic's crossplay rollout. Before arranging a group world, check the edition, the running server build and how each player will actually connect.

Status checked on 25 October 2026: the latest verified official development report, dated 24 September, still describes Crossplay Phase One as being finished for submission. It does not announce a universal console crossplay release. Plan a console group around released features documented for its exact platform, rather than a promised update.

Check the game edition and release first; then check the connection route. A reachable port cannot fix an incompatible client.

Choose the route for your group#

PlayersRoute to considerImportant boundary
Desktop vanilla clientsA compatible vanilla dedicated server, joined by addressVerify each installed client and the running server release.
Android and iOSCompatible mobile multiplayer or a compatible dedicated serverStore updates and regional editions can differ.
Desktop vanilla and mobileA compatible vanilla dedicated server with an address-based joinThis does not depend on a Steam friend invitation appearing on the phone.
PlayStation, Xbox or Switch mixed with other platformsCheck current released crossplay notes for that specific consoleDo not assume the planned Phase One interface has shipped everywhere.
tModLoader playersA matching tModLoader server and compatible mod setupVanilla clients cannot join tModLoader sessions.
TShock usersA TShock release supporting the intended Terraria client versionServer administration plugins are not a universal crossplay bridge.

Keep legacy console and handheld editions outside a current-platform compatibility assumption. Their familiar game name does not establish the same protocol or update path. A regional mobile edition also needs its own release check.

Understand what the roadmap actually changes#

DR Studios' February 2026 explanation distinguishes the existing PC/mobile/server connection by address from two rollout stages. Phase One brings that foundation to consoles, including local discovery and remote addresses. Phase Two aims to simplify connections across networks through a session ID or join code. The September report still places Phase One ahead.

A statement that “crossplay is coming” therefore does not mean PC and mobile have no usable route today. Conversely, a successful PC/mobile session does not prove every console has the same remote joining interface.

Crossplay also does not establish cross-save or shared progression between storefronts. Joining a friend's world and automatically transferring your character to a different device are separate requirements. Decide which one your group needs before moving any files.

Record versions before changing the network#

Ask each player for the exact version displayed by the game, the platform/store and whether they launched vanilla Terraria or tModLoader. Record the dedicated server's startup version too. A server downloaded months ago does not become current when the owner's Steam client updates.

Use release notes to establish compatibility. Different platform-only hotfix suffixes do not automatically prove incompatible network versions; equally, a shared “1.4.5” label does not prove a match. Keep the complete numbers and verify the actual join on the intended releases.

Do not downgrade the only copy of a developed world to chase a compatibility window. Preserve world and character backups first, then use a separate test world for a different release. A newer save may not open correctly in an older executable.

TShock and tModLoader require separate decisions. TShock adds server-side administration features. tModLoader requires participating players to use tModLoader; its own documentation explicitly excludes vanilla clients. A plugin called “crossplay” is not evidence that unsupported consoles, missing mod content or arbitrary game versions will work together.

Try the PC/mobile dedicated-server route#

For a mixed vanilla desktop/mobile group, start with the dedicated server setup and a small test world. Keep the developed world untouched while checking compatibility.

  1. Start the intended server build and wait for it to finish loading the selected world.
  2. Join from the desktop through its address-based multiplayer option.
  3. On mobile, use the remote server/address option and supply the same reachable host and configured port. Menu wording can vary by build.
  4. Have one player test from a genuinely external network, such as mobile data. A local Wi-Fi success only verifies the local route.
  5. Confirm both players see and can interact in the same world before committing the group to it.

A typical Terraria server uses TCP port 7777, but use the port actually configured. For a host behind a router, its forwarding and the host firewall both matter. With carrier-grade NAT, a forwarding rule on your home router alone cannot establish an incoming public route. A VPS instead has its own host and provider firewall boundaries.

For infrastructure you own, Nexardo offers a common administration interface. The selected game build, player editions and reachable connection path still determine whether this particular group can join.

Interpret the failure you actually see#

A version rejection calls for a client/server build comparison. A timeout calls for address, port, listener and firewall checks; it does not prove that PC/mobile crossplay is unavailable. A missing Steam invitation on a phone calls for the address-based route. Mod-loading errors belong to the tModLoader version and mod list investigation.

Keep the complete error text and the server log from the attempted connection. Record whether the same device succeeds locally and fails externally. That distinction prevents hours spent changing game versions to solve a network path problem.

Recheck official release notes when planning console participation: this is an active rollout. Confirm the released platform feature and perform a real join before announcing that the whole group can use one server.

Sources#