iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
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.
If your friends are on a different Minecraft Java Edition version, install the Via family on the server or its proxy. ViaVersion lets newer clients connect to an older server; ViaBackwards lets older clients connect to a newer server and requires ViaVersion; ViaRewind extends older-client support to 1.7.x and 1.8.x. For a separate gateway that bundles compatibility layers and supports online mode, use ViaProxy.
“Any version” has limits: a client cannot display features it does not understand, compatibility releases can lag behind a new Minecraft release, and very old clients need additional translation. This guide covers Java Edition only; Bedrock clients are outside its scope.
What “let players join from any version” actually means
Minecraft’s network protocol changes between releases. A server and client normally need to speak the same protocol, so a player on 1.20.x cannot automatically enter a server running an older release, and a player on an older release cannot automatically enter a newer server. Via translates packets between those protocol versions while the player is connected.
Compatibility is directional. The correct component depends on which side is newer:
#1 Best Overall
| Situation | Component | What it does |
|---|---|---|
| Newer client joining an older server | ViaVersion | Translates the newer client’s protocol for the older server. |
| Older client joining a newer server | ViaBackwards plus ViaVersion | Translates an older client to the newer server; ViaBackwards requires ViaVersion. |
| 1.7.x or 1.8.x client joining a newer server | ViaRewind plus ViaBackwards and ViaVersion | Extends ViaBackwards for those older client families. |
| Modern client reaching old, very old or classic-era servers through a separate gateway | ViaProxy | A standalone program bundling ViaBackwards, ViaRewind and ViaLegacy; it supports online mode. |
Thus, a server owner who wants the broadest practical Java range normally installs ViaVersion, adds ViaBackwards for older clients, and adds ViaRewind when 1.7.x or 1.8.x support is required. “Every version” should be read as every version supported by the particular builds you install, not every future release automatically.
Choose the right deployment for your server
Paper or another plugin-based server
On Paper, install the Via components as server plugins. The ViaVersion project lists support for Paper and also documents operation on Velocity, Fabric, Forge, BungeeCord and Sponge. Your server software and Minecraft version still have to be supported by the specific build you download.
Free tools Windows power users keep installed
One-click scans. No signup required.
Fabric or Forge
Use the corresponding Via mod loader integration rather than placing a plugin in a plugins directory. ViaVersion’s project pages list Fabric and Forge support. Match the loader, Minecraft version and Via build carefully; a plugin jar intended for Paper is not interchangeable with a Fabric or Forge mod.
Velocity or BungeeCord network
Install the compatibility layer on the proxy or on backend servers behind it. You do not necessarily need it on both. Installing on the proxy is convenient because players are translated before they reach a backend, but the ViaVersion documentation warns of trade-offs: 1.8 clients may not show sword blocking correctly, and some anti-cheat systems may perform worse when translation occurs at the proxy.
Standalone gateway with ViaProxy
ViaProxy is useful when you do not want to modify the target server, or when one gateway must handle several protocol generations. It bundles ViaBackwards, ViaRewind and ViaLegacy, can connect modern clients to old and very old servers down to classic-era versions, and supports online mode. Treat it as a separate network service: it needs its own process, configuration and listening address, and players connect to the gateway rather than directly to the backend.
ViaVersion vs ViaBackwards: the difference that matters
The names are easy to reverse. Remember the direction:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- ViaVersion: newer client → older server.
- ViaBackwards: older client → newer server, with ViaVersion installed as a dependency.
- ViaRewind: older 1.7.x and 1.8.x clients → newer server, extending the ViaBackwards path.
For example, on a server running 1.20.x, a 1.21.x player generally needs ViaVersion, while a 1.19.x player needs ViaBackwards and ViaVersion. A 1.8.x player needs all three compatibility layers. On an older server, the direction reverses: a current client can often be handled by ViaVersion, but ViaBackwards is not what makes a newer client understand an old server.
Requirements and decisions before installing
- Confirm that the scope is Java Edition. These components do not turn a Java server into a Bedrock server.
- Record the server or proxy software, its Minecraft version, and whether the network is online mode or offline mode.
- Take a backup of the server files and proxy configuration before changing plugins, mods or forwarding rules.
- Decide the oldest client you genuinely need. Supporting 1.7.x or 1.8.x requires ViaRewind and introduces more translation edge cases than supporting only recent releases.
- Choose one build channel and keep ViaVersion, ViaBackwards and ViaRewind on that same channel. Mixing release, beta or snapshot channels can produce incompatibilities.
- Allow for release lag. Since Minecraft 1.20.5, ViaVersion and ViaBackwards have generally appeared about a day after a Minecraft update when protocol changes were substantial; trivial changes can be faster. A newly released client may therefore fail to connect temporarily.
Compatibility ranges change as Minecraft changes. The official documentation says future 26.x versions should work, while other currently confirmed references cover versions through 1.21.x. Do not promise 26.x compatibility until the exact build’s documentation or download page confirms it.
Step-by-step: install compatibility on a Paper server
1. Identify the direction and target range
Write down the server version and the newest and oldest client versions your group uses. If every player is newer than the server, start with ViaVersion. If some players are older than the server, plan for ViaBackwards as well. Add ViaRewind for 1.7.x or 1.8.x clients.
2. Stop the server and make a backup
Use the host panel’s Stop control or the server console’s normal shutdown command. Copy the world folders, configuration files and the plugins directory to a separate backup location. A backup lets you remove a bad build without risking world data.
3. Install ViaVersion
- Download the ViaVersion build matching your server software and selected build channel.
- Place the plugin jar in the server’s
pluginsdirectory. Do not unzip it. - Start the server and wait for a complete startup. ViaVersion should create its configuration and report its load status in the console.
On a modded Fabric or Forge server, follow the loader-specific installation method instead; the Paper plugin directory is not used for a mod installation.
4. Add ViaBackwards for older clients
- Stop the server again after the first successful startup.
- Place the ViaBackwards jar in the same plugin or mod location, using the same release channel as ViaVersion.
- Start the server and check the startup log for dependency or version errors.
ViaBackwards cannot operate alone. If the server reports that ViaVersion is missing or incompatible, correct that dependency before testing a client.
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.
5. Add ViaRewind when 1.7.x or 1.8.x is required
- Stop the server.
- Add ViaRewind from the same build channel as the other Via components.
- Restart and check that all three components load without errors.
Some descriptions of ViaBackwards stop at versions newer than 1.8. For 1.8 and lower, use ViaRewind or another protocol solution such as ProtocolSupport rather than assuming ViaBackwards alone is sufficient.
6. Test one client at a time
Connect first with a client matching the server’s own version. Then test one newer client, one older client, and, if installed, one 1.8.x client. Test joining, moving between worlds, inventory use, chat, commands and a normal combat interaction. Record the exact client and server versions for every failure; “old version” is not precise enough to diagnose a protocol problem.
Installing Via on Velocity or BungeeCord
Choose where translation happens
For a network with a proxy, install Via on the proxy or on the backend servers behind it. Installing on both is not automatically required and can make troubleshooting harder if different builds or settings are used. A single, consistently maintained location is easier to reason about.
Proxy installation sequence
- Stop the proxy and back up its configuration and plugin directory.
- Install the proxy-compatible ViaVersion build in the proxy’s plugin directory.
- Add ViaBackwards when older clients must reach newer backends, and ViaRewind for 1.7.x or 1.8.x clients.
- Start the proxy, verify that the plugins load, and connect through the proxy address rather than a backend address.
- Test at least one client on each side of the server version, plus a legacy client if applicable.
The proxy option has known behavior differences. The ViaVersion documentation specifically notes that 1.8 clients may not display sword blocking when ViaVersion runs on the proxy, and that anti-cheat performance may be worse. If those effects matter, compare proxy placement with installation on the backend servers in a controlled test.
Using ViaProxy instead of server plugins
ViaProxy is a standalone alternative, not simply another jar to drop into a Paper directory. It bundles ViaBackwards, ViaRewind and ViaLegacy, making it suitable when a modern client must reach an older or classic-era server. It also supports online mode, which is important when the gateway must authenticate players with the normal account system.
- Run ViaProxy on a machine that can reach the target server and accept player connections.
- Configure its listening address and port separately from the backend’s address and port.
- Point players to the ViaProxy endpoint.
- Set the backend target and authentication mode according to your network’s security model.
- Test current, older and legacy clients separately; bundled support does not remove the feature and rendering limits of an old client.
Use ViaProxy when isolating compatibility from the server is more valuable than having every translation setting inside the server or proxy. Use the native Via plugins when you already operate a supported Paper, Fabric, Forge, Velocity, BungeeCord or Sponge installation and want the simplest deployment.
Recommended Free Tools
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"!
What older clients will and will not receive
Protocol translation makes a connection possible; it does not add newer game features to an older client. A client cannot render blocks, menus, particles, entities or controls that its code does not know about. The translator may substitute representations, hide unsupported content or expose a reduced interaction.
Some client-side behavior can still break even when login succeeds. The ViaVersion project documentation identifies attribute handling as an example. Expect differences in combat, item metadata, UI, rendering and server-specific mechanics when the client and server are far apart in age.
- A successful login does not prove that every plugin mechanic works.
- New server content may be invisible, simplified or unusable to an old client.
- Very old clients have more severe differences, which is why 1.7.x and 1.8.x require ViaRewind.
- Anti-cheat, combat and inventory plugins may need their own compatibility testing.
Troubleshooting: diagnose the failure by symptom
The client is rejected immediately
- Check the direction. Newer-to-older requires ViaVersion; older-to-newer requires ViaBackwards plus ViaVersion.
- Confirm that the client version is within the installed build’s supported range.
- Look at the server or proxy startup log for a missing dependency, wrong loader or incompatible build channel.
- After a brand-new Minecraft release, wait for the corresponding Via update instead of repeatedly changing unrelated settings.
1.8.x or 1.7.x cannot connect
ViaBackwards alone may not cover these versions. Install ViaRewind alongside ViaVersion and ViaBackwards, or evaluate ProtocolSupport as an alternative protocol solution. Retest through the same endpoint players actually use, because proxy placement changes the path.
The plugin loads on the server but not through the network
Players may be bypassing the proxy and connecting directly to a backend. Verify the advertised address, firewall rules and forwarding configuration, then check whether Via is installed at the layer receiving the connection. A plugin on a backend cannot translate a connection that never reaches that backend.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsLogin works but gameplay is wrong
Record the exact client/server pair and the affected feature. Attribute handling, combat presentation, inventory screens and new blocks are known categories of cross-version differences. Test with server-side gameplay plugins temporarily disabled only in a staging copy, then report a reproducible pair and symptom to the relevant project rather than treating successful login as full equivalence.
Anti-cheat flags players or combat feels different
Translation can alter packet timing and data shape. Proxy installation is specifically documented as a case where anti-cheat may perform worse. Test the backend placement option, update the anti-cheat according to its own compatibility guidance, and avoid promising identical combat behavior across versions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Maintenance after every Minecraft update
- Keep the current server version, proxy version and Via component versions in a change log.
- When Minecraft updates, test the server with its native client first.
- Check the ViaVersion and ViaBackwards project documentation for a build that names the new protocol.
- Update ViaVersion, ViaBackwards and ViaRewind together on the same channel; back up before replacing jars.
- Test one newer and one older client before announcing that the network supports the new release.
- If no compatible build exists yet, tell players which versions remain available instead of claiming universal access.
Release timing is part of the design, not an installation mistake. Since 1.20.5, the projects have generally needed about a day after an update when protocol work is required. The exact delay and supported range vary by release, so check the current project pages at update time.
Practical configurations
Friends on 1.20.x and 1.21.x, server on 1.20.x
Install ViaVersion so the newer clients can reach the older server. Add ViaBackwards only if someone must use a client older than the server. This is the smallest setup for a mostly current group.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Server on 1.21.x, friends on 1.20.x and 1.19.x
Install ViaVersion and ViaBackwards. ViaVersion handles newer clients; ViaBackwards supplies the older-client path. Test inventories and any plugins that depend on modern item or attribute data.
Server on a current release, one friend on 1.8.x
Install ViaVersion, ViaBackwards and ViaRewind, then test the 1.8.x client specifically. Expect reduced feature visibility and possible combat or attribute differences rather than a current-client experience.
Modern clients connecting to a classic-era server
Use ViaProxy when a standalone gateway is appropriate. Its ViaLegacy bundle extends the range beyond the versions normally handled by ViaBackwards and ViaRewind. Confirm the exact classic version supported by the build you select.
Security and administration considerations
Compatibility software changes the protocol boundary, so treat it as part of the trusted network surface. Download builds from the relevant project distribution, restrict administrative access to the proxy and server, and keep backups before upgrades. Online mode in ViaProxy means the gateway can participate in account authentication; configure forwarding and authentication deliberately rather than exposing an unprotected backend.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Do not use compatibility as a reason to leave every backend publicly reachable. Players should normally enter through the intended proxy or gateway, while backend ports are limited to the proxy and administrators. The exact firewall and forwarding settings depend on your host and network design, so validate them in a staging environment.
Decision checklist
- Only newer clients need access to an older server: ViaVersion.
- Older clients need access to a newer server: ViaVersion plus ViaBackwards.
- 1.7.x or 1.8.x clients must be supported: add ViaRewind.
- You need a separate gateway, online mode or classic-era reach: evaluate ViaProxy.
- You run a proxy network: choose proxy or backend placement, then test sword blocking and anti-cheat behavior.
- A new Minecraft release just shipped: verify that matching Via builds exist before changing production clients.
- You need identical features on every client: cross-version translation cannot guarantee that; standardize client versions instead.
Final perspective
The reliable way to connect Java players on different releases is to match the Via component to the direction of the mismatch, install dependencies together, and test the oldest client you intend to advertise. ViaVersion handles newer clients to older servers; ViaBackwards reverses that direction; ViaRewind reaches 1.7.x and 1.8.x; ViaProxy packages the older-version path in a standalone, online-mode-capable gateway. The result is broad access, not perfect feature parity, so publish a supported version range and update it whenever Minecraft or the Via builds change.
Quick Recap
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.
