Free tools Windows power users keep installed
One-click scans. No signup required.
If your friends are on a different Minecraft version, install the Via family of protocol-translation tools. ViaVersion lets newer Java clients connect to an older server; ViaBackwards lets older clients connect to a newer server and requires ViaVersion; and ViaRewind extends the older-client side to 1.7.x and 1.8.x. For a separate gateway that also reaches classic-era clients, use ViaProxy, which bundles ViaBackwards, ViaRewind and ViaLegacy.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Minecraft Java servers with free DDoS protection and up to three free backups a day.
This guide covers Minecraft Java Edition. Bedrock clients are outside its scope, and no translator makes every release identical: a client cannot display or use features that its own version does not contain.
As an Amazon Associate I earn from qualifying purchases.
What “any version” can and cannot mean
Minecraft clients and servers normally have to speak the same network protocol. A Via component translates packets between protocol versions so a Java player can connect even when the server and client were released at different times. The server still runs one actual Minecraft version; Via changes what each connected client receives.
“Any version” therefore means “any version covered by the installed Via builds,” not literally every release ever made. A newly released client can be temporarily unsupported, and very old clients need additional components. The tools also do not add modern blocks, menus or mechanics to an old client. An older player may connect successfully while seeing substituted items, missing visuals or different behavior.
#1 Best Overall
Edition and release boundaries
- This procedure is for Java Edition servers and Java Edition clients.
- ViaVersion project pages list support on Paper, Velocity, Fabric, Forge, BungeeCord and Sponge. The exact versions supported by a particular build change over time.
- Official documentation describes future 26.x releases as intended to work, while other compatibility statements currently confirm support only through 1.21.x. Treat 26.x support as unverified until the current ViaVersion documentation or Hangar listing confirms it.
ViaVersion vs ViaBackwards: choose the direction first
The direction of the mismatch determines which component you need. Installing the wrong one is the most common reason a player still receives an incompatible-client error.
| Player and server versions | Component | What it does | Additional requirement |
|---|---|---|---|
| Newer client joining an older server | ViaVersion | Translates the newer client protocol for the older server. | None of the other Via components is required for this direction. |
| Older client joining a newer server | ViaBackwards | Translates an older client protocol for a newer server. | ViaVersion must be installed alongside it. |
| 1.7.x or 1.8.x client joining a newer server | ViaRewind | Adds the older 1.7.x and 1.8.x protocols to the ViaBackwards path. | Install ViaVersion and ViaBackwards as well. |
| Modern or old client reaching older and classic-era servers through a gateway | ViaProxy | Standalone proxy that bundles ViaBackwards, ViaRewind and ViaLegacy. | Run the proxy as a separate connection point; it supports online mode. |
Quick decision guide
- Your server is older than some players: start with ViaVersion.
- Your server is newer than some players: install ViaVersion and ViaBackwards.
- You need 1.7.x or 1.8.x players on a newer server: add ViaRewind to that pair.
- You want one gateway for several backends, including very old or classic versions: evaluate ViaProxy.
- You need clients from both sides of the server version: use ViaVersion plus ViaBackwards; add ViaRewind only for 1.8 and older.
How to let players join from different versions on Paper or Spigot
For a conventional plugin server, the simplest deployment is to place the Via plugins in the server’s plugin directory. Make a backup before changing protocol components, especially on a live network.
- Identify the server’s actual Minecraft version and software. Confirm that it is Paper, Spigot-compatible software or another platform listed by the ViaVersion project. Record the exact release so you can choose matching plugin builds.
- Download ViaVersion from its current official distribution listing. Select a build compatible with your server software and Java runtime. Do not mix an arbitrary development build with stable builds of the other Via components.
- Install ViaVersion. Stop the server, copy the ViaVersion JAR into the server’s
pluginsdirectory, and start the server once. A configuration directory should be created during startup. - Add the reverse-direction components when needed. To allow older clients on a newer server, place ViaBackwards in the same directory. For 1.7.x or 1.8.x clients, add ViaRewind too. ViaBackwards cannot operate without ViaVersion.
- Keep the build channel consistent. Use the same release channel across ViaVersion, ViaBackwards and ViaRewind. Mixing release channels can produce missing protocol mappings or startup errors.
- Restart and read the startup log. Confirm that each plugin enables without dependency or protocol errors before inviting players. A clean startup does not guarantee every release pair is supported, so test the client versions you intend to allow.
- Test both directions. Join once with a client newer than the server and once with an older client. Check movement, inventory, chat, combat and the blocks or entities central to your game mode.
What to install for common Paper layouts
| Server situation | Install | Expected result |
|---|---|---|
| 1.20 server, players on 1.21.x | ViaVersion | Newer clients can be translated down to the 1.20 protocol when that pair is supported. |
| 1.21.x server, players on 1.20.x | ViaVersion + ViaBackwards | Older clients can be translated up to the 1.21.x server protocol. |
| Modern server, players on 1.8 | ViaVersion + ViaBackwards + ViaRewind | The 1.8 client is added through ViaRewind’s extended protocol support. |
| Server and clients already use the same release | No translator required | Native protocol support is simpler and avoids translation edge cases. |
The version examples illustrate direction, not a promise that every listed release pair is currently mapped. Check the current compatibility listing before choosing a production combination.
Allow older clients to join a newer server
This is the setup people usually mean when they ask to let old clients join a current server. ViaVersion alone is not enough: it primarily handles newer clients talking to older servers. Install ViaBackwards with it, then add ViaRewind for the 1.7.x and 1.8.x range.
Why the three-plugin stack matters
- ViaVersion supplies the protocol framework and newer-client compatibility.
- ViaBackwards supplies mappings for older clients on newer servers and depends on ViaVersion.
- ViaRewind covers 1.7.x and 1.8.x clients that are outside the normal ViaBackwards range described by some project documentation.
If a 1.8 player still receives an unsupported-version message after ViaBackwards is installed, the missing piece is usually ViaRewind or an incompatible build combination. Some older-client features will remain imperfect even after the connection succeeds.
Using ViaVersion behind Velocity or BungeeCord
A proxy network introduces two possible installation points: the proxy itself and the backend servers. Via components can be installed on the proxy or on the backend servers behind it; they do not have to be installed in both places. Choose one deliberate point for the translation path and keep the versions consistent across the network.
Rank #3
- The classic UNO card game builds fun on game night with a Minecraft theme.
- UNO Minecraft features a deck and storage tin decorated with graphics from the popular video game.
- Players match colors and numbers to the card on top of the discard pile as in the classic game.
- The Creeper card unique to this deck forces other players to draw 3 cards.
- Makes a great gift for kid, teen, adult and family game nights with 2 to 10 players ages 7 years and older, especially Minecraft and video game fans.
- Stop the proxy and the affected backend servers.
- Install the compatible Via components on the proxy or on the backend layer you selected.
- Start the proxy, confirm its plugins or mods load, then start the backends.
- Connect with representative client versions and test transfers between backends, not just the initial login.
The ViaVersion documentation warns that installing ViaVersion on the proxy can prevent 1.8 clients from seeing sword blocking correctly, and anti-cheat systems may perform worse. If accurate 1.8 combat visuals or strict anti-cheat behavior matter, test proxy placement against backend placement before standardizing the network.
Fabric and Forge servers
ViaVersion is also listed as running on Fabric and Forge. On a modded server, use the loader-specific Via distribution rather than copying a plugin JAR into a directory where the loader cannot load it. The project ecosystem includes ViaFabric and ViaLoader; select the current artifact that matches your loader and Minecraft release.
- Verify the server’s loader, Minecraft release and Java version.
- Install the loader-compatible ViaVersion component in the server’s mods location.
- If older clients must join a newer modded server, install the matching ViaBackwards component and ViaRewind where 1.7.x or 1.8.x support is required.
- Launch once, inspect the mod list and log for dependency errors, then test with a client that has the same required gameplay mods.
Protocol translation does not make incompatible gameplay mods compatible. Every player still needs whatever client-side mods the server requires, and a translated protocol cannot supply a missing mod feature.
Rank #4
- Now Minecraft lovers can play a special version of UNO!
- Same as Basic UNO but features Minecraft characters and includes special Creeper rule card. Draw this card and the other players have to draw three more cards from the pile!
- The goal is to get rid of all the cards in your hand.
- First player or team to 500 wins.
- When you're down to one card, don't forget to yell "UNO"!
When a standalone ViaProxy is the better fit
ViaProxy is a separate program rather than a plugin loaded directly by the game server. It bundles ViaBackwards, ViaRewind and ViaLegacy, allowing a modern client to reach older and very old servers, down to classic-era versions covered by its current mappings. It also supports online mode.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Basic ViaProxy deployment
- Choose a machine that can reach the Minecraft server and accept player connections. Keep the proxy’s listening port separate from the backend’s port.
- Download the ViaProxy release that matches the Java runtime and platform requirements stated by its current documentation.
- Start ViaProxy once so it creates its configuration, then set the backend address, listening address and authentication mode.
- Point players at the proxy address instead of the backend address.
- Test a modern client, an older supported client and, if needed, a classic-era client. Verify that online-mode authentication and skin or profile behavior meet your network’s requirements.
ViaProxy is useful when you cannot install plugins on the target server, when several server versions must be exposed through one gateway, or when you need the bundled ViaLegacy path. It adds another process to monitor, so plan restarts, logs and firewall rules as you would for any proxy.
Connect Java clients to a different server version: practical examples
| Goal | Server-side arrangement | What the player does | Important check |
|---|---|---|---|
| Friends on a newer release join your older survival server | ViaVersion on the server or selected proxy | Launch the newer Java release and connect normally. | Wait for a Via build that maps that release; a brand-new release may not work immediately. |
| Friends on an older release join your current server | ViaVersion + ViaBackwards | Launch the older Java release and use the same server address. | Expect missing modern features on the old client. |
| 1.8 PvP players join a modern server | ViaVersion + ViaBackwards + ViaRewind | Launch Java 1.8 and connect. | Test combat, attributes and anti-cheat; behavior can differ from native 1.8. |
| One gateway serves modern, old and classic-era backends | ViaProxy with its bundled components | Connect to the proxy’s address and select the intended backend. | Confirm the proxy’s current mapping range and online-mode behavior. |
Maintenance after a Minecraft update
Protocol tools trail a Minecraft release because mappings must be updated. From Minecraft 1.20.5 onward, ViaVersion and ViaBackwards have generally appeared about a day after an update when protocol changes are substantial; trivial protocol changes can be faster. That is a general release pattern, not a guaranteed service-level promise. Do not advertise immediate support for a just-released client until the current build says it is supported.
- Before updating the server, record the working Via component versions and make a backup.
- Check the current ViaVersion documentation and Hangar listing for the new server and client protocols.
- Update ViaVersion, ViaBackwards and ViaRewind together on the same release channel.
- Restart in a staging environment and test the oldest and newest client versions your community uses.
- Only then update the production server or proxy, retaining the previous plugin files for rollback.
Compatibility claims for future 26.x versions are not verified here; treat them as a documentation check rather than a guarantee. The current compatibility range for a specific build is the authority at the time you deploy.
Limitations you should explain to players
Old clients do not gain new features
ViaBackwards translates packets; it cannot add a new game’s user interface, block model or mechanic to an old executable. The player may see a substitute item, an empty space or a simplified interaction. Build instructions, quests and menus that assume a modern client may need an older-client fallback.
Client-side behavior can still break
Some behavior remains client-owned after translation. Attribute handling is one documented example. Combat timing, animations, rendering and inventory edge cases should be tested rather than promised. A connection that succeeds is not proof that every plugin or game mode behaves identically.
Very old protocols need a dedicated path
Some descriptions of ViaBackwards stop at 1.8 and lower. Use ViaRewind for 1.7.x and 1.8.x, or investigate ProtocolSupport when its current compatibility and maintenance status fit your server. Do not assume that installing ViaBackwards alone covers every historical release.
Quick Recap
Troubleshooting version-join failures
“Incompatible client” still appears
- Confirm the client is Java Edition, not Bedrock.
- Check the direction: newer-to-older needs ViaVersion; older-to-newer needs ViaVersion plus ViaBackwards.
- For 1.7.x or 1.8.x, verify ViaRewind is installed and enabled.
- Check the current build’s compatibility list; a newly released client may simply be waiting for a mapping.
- Read the startup log for a failed dependency or a mismatched release channel.
The plugin or mod fails at startup
- Make sure ViaBackwards is not installed without ViaVersion.
- Use artifacts built for the server’s platform: plugin for a plugin server, loader-compatible mod for Fabric or Forge, and the standalone ViaProxy distribution for a proxy process.
- Remove duplicate copies from both proxy and backend while testing, then add the second location only if your chosen architecture requires it.
- Roll back to the last known-good set of matching builds if the failure began immediately after an update.
The player joins but gameplay looks wrong
- Test the same feature with a native-version client to separate a Via translation issue from a server plugin issue.
- Expect missing modern features on old clients rather than treating every visual difference as a connection failure.
- Check proxy placement when 1.8 sword blocking or anti-cheat behavior is important; proxy installation has documented trade-offs.
- Record the exact server version, client version, Via component versions and reproduction steps before reporting a bug.
Operational checklist
- Write down the server’s actual Minecraft release and platform.
- List the oldest and newest client releases you intend to allow.
- Select ViaVersion for newer clients, ViaBackwards for older clients, and ViaRewind for 1.7.x or 1.8.x.
- Use ViaProxy when a separate gateway and classic-era support are required.
- Keep all Via components on one release channel.
- Choose proxy or backend deployment deliberately and test transfers through the whole network.
- Back up before updates and verify support after every Minecraft release.
- Tell players that protocol translation cannot add features or guarantee identical client-side behavior.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
