Minecraft Java Snapshot 26.3-snapshot-1: What You Need to Know
What Changed
On 23 June 2026, Mojang pushed snapshot 26.3-snapshot-1 to the Java Edition launcher, the first publicly versioned build under Mojang's newer year-based naming scheme (26.x represents 2026 development builds). Because this is a fresh version manifest entry, a detailed changelog article has not yet appeared alongside it. What we do know is that it sits firmly in the experimental snapshot track, meaning it carries work-in-progress features that are still being tested and are subject to change before any full release.
In short: something new is brewing inside the Java codebase, but the full ingredient list is still being revealed. We'll follow up the moment an official changelog drops.
Why It Matters
Snapshots are Mojang's way of letting the community peek behind the curtain during development. They are not intended for everyday play, worlds opened in a snapshot can break when you try to load them in a stable release. That said, snapshots matter a great deal to the wider Minecraft ecosystem because:
- They signal the direction of upcoming features and gameplay changes.
- Mod developers, plugin authors, and server software teams use them to begin compatibility work early.
- They give the community a chance to give Mojang feedback before things are locked in.
The 26.x naming convention is also notable in itself, it marks Mojang's move away from the traditional 1.x versioning that players have known for over a decade. That's a bigger shift than it might first appear.
Java and Bedrock
This snapshot is Java Edition only. Bedrock Edition follows its own separate release cadence through Previews and Beta builds on the Microsoft Store, Xbox, and mobile platforms. No matching Bedrock Preview has been announced alongside this snapshot. Bedrock players on SNT kingdoms can continue playing as normal, nothing on that side of the fence has changed today.
For Server Owners
If you run your own Minecraft infrastructure, here is the practical picture:
- Do not deploy this snapshot on a live server. Snapshot builds are unsupported by PaperMC, Velocity, and the Via suite, and can corrupt player data or world files.
- The shift to year-based versioning (26.x) means the entire server-software ecosystem, Paper, Purpur, Velocity, ViaVersion, Geyser, needs dedicated migration work before any 26.x build can be safely used in production.
- Keep an eye on the PaperMC and ViaVersion GitHub repositories for compatibility announcements; that's where migration timelines will surface first.
- Your current stable stack is not at risk, this is purely a snapshot on the experimental track.
For Parents
Your child may come home excited about this snapshot and ask to try it out. A few friendly reassurances:
- Snapshots are optional. The regular Minecraft launcher keeps stable and snapshot installations completely separate, so their main world is safe.
- If they do experiment with the snapshot in a separate instance, remind them never to open a world they care about in a snapshot version, worlds can become unloadable on the stable release afterwards.
- Because no detailed changelog is available yet, it's worth waiting a day or two for the community to document exactly what's new before diving in.
- On any SNT kingdom, nothing changes today, their favourite worlds and friends are right where they left them.
For Players
Snapshots are genuinely exciting to explore, and 26.3-snapshot-1 is no exception, especially because the 26.x series represents a whole new chapter for Java Edition. Here's how to enjoy it safely:
- In the Java launcher, create a new installation set to snapshot 26.3-snapshot-1 and point it at a brand-new world.
- Never load your main survival world in a snapshot, always make a backup first if you're curious.
- Share what you find! The Minecraft community loves snapshot reports, bug spotting, and feedback posts on the official feedback site.
- Your SNT kingdom is still running perfectly, hop on and tell your friends what you discovered in the snapshot.
Do SNT Kingdoms Need an Update?
No, and here's exactly why. SNT Gaming kingdoms run Paper 1.21.11 backends behind a Velocity proxy, with ViaVersion, ViaBackwards, and ViaRewind handling client compatibility for versions 1.13 through 1.21.11. Geyser and Floodgate extend that to Bedrock players as well.
The critical point is that MC 26.x clients are not yet supported by PaperMC, Velocity, or the Via suite. Mojang's move to year-based versioning requires significant migration work across all of those projects before any 26.x connection can be safely accepted. Until that ecosystem work is complete, SNT kingdoms will remain on the current stable stack, which is exactly where a well-run, family-friendly server should be.
All six worlds in your kingdom, Survival, SharedLife, RandomLoot, Chaos, Spleef, and Rivals, are fully operational and completely unaffected by today's snapshot release. When the broader server ecosystem is ready for 26.x, SNT Gaming will update and let every kingdom owner know in advance.