Minecraft Bedrock 26.33 Hotfix: Custom Block Textures Fixed
What Changed
Minecraft: Bedrock Edition 26.33 is a focused hotfix that shipped on 9 July 2026. It carries a single, surgical repair:
- Texture bleeding on custom blocks is fixed. Specifically, blocks that use automatic face UV assignment with undersized textures were showing unwanted colour or pixel "bleed" across their edges, a visual glitch that made custom blocks look smeared or incorrectly coloured at their seams. That's now resolved.
Because it's a hotfix, the rollout is staggered, each platform (Android, iOS, Windows, consoles) receives it as soon as it clears that store's approval process, so don't be alarmed if it hasn't appeared on your device just yet.
Why It Matters
One fix might sound trivial, but texture bleeding can genuinely ruin the look of a carefully crafted custom block. For creators, marketplace builders, and server operators who ship their own resource packs, a bleed artifact is the kind of thing that looks embarrassingly unprofessional, even when the underlying model and texture are perfectly made. Getting this corrected in a fast hotfix, rather than waiting for the next major update cycle, shows responsiveness to the content-creator community.
For everyday players who don't use custom blocks, the visual impact is zero, but the update is still worth installing because keeping your client current avoids compatibility headaches down the road.
Java and Bedrock
This release is Bedrock Edition only. Java Edition is unaffected and receives no changes in this hotfix. The two editions follow independent release tracks, and a UV-mapping fix on Bedrock's custom-block pipeline has no equivalent issue on the Java side, which handles block models differently.
If your household runs a mix of Java and Bedrock players (very common in families!), only the Bedrock devices need this update, Java players are already good to go.
For Server Owners
If you self-host a Bedrock or mixed-edition server and you distribute a custom resource pack to players, check your custom blocks after your players update to 26.33. The fix changes how undersized textures are rendered with automatic UV assignment, so blocks that previously looked fine on older clients may now appear slightly different, almost certainly for the better, but worth a quick visual review.
If you're running Geyser to bridge Java and Bedrock players, keep an eye on Geyser's release notes for any mapping updates that accompany this Bedrock client change. No server-side Geyser update is required for this hotfix, but staying current on both sides is always good practice.
For Parents
Nothing alarming here! This is a small, automatic maintenance update. If your child plays Minecraft on a phone, tablet, or console, the update will appear in their respective app store and install like any other. No new features, no changed settings, no new purchases, just a visual bug quietly swept up.
The only thing to be aware of is the staggered rollout: if your child asks why their friend already has the update and they don't, that's perfectly normal. It'll arrive on every platform within a short window.
For Players
Did you ever notice weird colour smearing along the edges of custom blocks on servers or in marketplace worlds? That's exactly what this fix targets. After updating to 26.33, those blocks should look crisp and clean, the way their creators intended.
Here's the short checklist for players:
- Open your app store and update Minecraft if the prompt hasn't appeared automatically.
- Jump into any world that uses custom blocks and enjoy the cleaner look.
- No settings to change, no worlds to rebuild, it just works.
Do SNT Kingdoms Need an Update?
Short answer: no server-side action is needed, and SNT kingdoms are not yet compatible with Bedrock 26.x clients.
Here's the full picture. SNT Gaming kingdoms use Geyser + Floodgate to let Bedrock players join alongside Java players, a great setup that has worked reliably for a long time. However, the underlying server stack (Velocity proxy, Paper 1.21.11 backends, and the Fabric 1.21.4 SharedLife backend) relies on ViaVersion, ViaBackwards, and ViaRewind for broad client compatibility. Those projects, along with PaperMC and Velocity themselves, have not yet migrated to Mojang's year-based versioning scheme that introduced the 26.x series.
What that means in practice:
- Bedrock clients on version 26.33 cannot currently connect to SNT kingdoms.
- Bedrock players should keep a compatible older Bedrock version installed if they want to join their kingdom, or connect via a Java Edition client (1.13–1.21.11 are all supported).
- The single texture-bleed fix in this hotfix has no impact on server-side logic, so nothing changes on our end today.
As soon as the Paper, Velocity, and Via ecosystem catches up to Mojang's new versioning, SNT kingdoms will be updated and Bedrock 26.x support will be enabled. We'll post an article the moment that happens, so watch this space!