Minecraft Bedrock 26.33 Hotfix: Custom-Block Texture Bleeding Explained

Minecraft Bedrock 26.33 has one job. Mojang’s July 9, 2026 changelog documents a fix for texture bleeding on custom blocks that use automatic block-face UV assignment with undersized textures.

That is useful for pack creators, but only if the symptom matches. A tiny changelog should stay a tiny, precise article—not become a list of visual problems the release never claimed to solve.

What “texture bleeding” means in this case

A custom block face is expected to sample a defined part of a texture. When an automatically assigned face uses an undersized texture, pixels from outside the intended boundary can appear along an edge or across the face. The 26.33 note says that specific automatic-assignment case was corrected.

This explanation helps identify the symptom; it is not a new Mojang compatibility claim. The changelog does not provide a supported texture-size table, affected-device list or promise that malformed content will be repaired by the client. Pack authors still own valid files, paths, geometry and version declarations.

What the fix covers

A clean creator retest

1. Keep the exact same resource and behavior pack versions.
2. Open a copy of the test world at the same coordinates.
3. View the same block face from the same distance and lighting.
4. Capture the result, fully close Minecraft, reopen, and check again.
5. Record the device, build, pack version and whether the artifact survived.

Capture a baseline before changing the pack. Record the block identifier, resource-pack version, behavior-pack version if one is present, texture dimensions and the model face that shows the artifact. Use a simple test world with no unrelated visual packs. A clean baseline lets you tell a client correction from a pack edit that happened at the same time.

After updating, do the first run without modifying the texture. If the edge is clean, save and reopen the world, then repeat from another normal viewing distance. If the artifact returns only after another resource pack is added, preserve both single-pack results and treat the combination as a separate conflict.

How to classify a failure that remains

Protect the rollback route

Keep the last working pack files and the untouched world copy until the updated client has passed a save and reopen. Do not overwrite the only resource source just to produce a comparison. If you change the image dimensions or UV definitions after updating, save that as a new pack revision so the original failure remains reproducible.

A useful report states what was expected, which face bled, the exact Bedrock and pack versions, whether automatic face assignment was used, the texture dimensions, and whether the result survives with other packs removed. That evidence is more actionable than “custom blocks are broken.”

What 26.33 does not cover

The official page does not claim to repair missing textures, incorrect file paths, malformed geometry, manual UV mistakes, every transparent edge or all graphics drivers. It also does not list specific platforms or a bug ID. If your case does not match the three-part trigger, use the Bedrock add-on troubleshooting checklist and preserve the content log.

MineBrush has not run a pack or device matrix for this article. The factual boundary comes from the official Minecraft Bedrock 26.33 changelog, rechecked on August 25, 2026.