Minecraft Bedrock 26.34/35 is a platform-specific hotfix page, and the build number matters. The original July 23, 2026 rollout covers PlayStation and Nintendo Switch. The July 28 update labels 26.35 as Switch-only.
Mojang says 26.35 includes additional gameplay fixes, but the page does not name them. The only explicit fix bullet on the combined page addresses texture bleeding on certain custom blocks. That gives players and creators one solid fact—and a clear limit.
Platform and build matrix
| Build | Documented platform scope | What is documented |
|---|---|---|
| 26.34 | PlayStation and Nintendo Switch | Hotfix rollout; the combined page includes the custom-block texture correction. |
| 26.35 | Nintendo Switch only | Additional gameplay fixes were rolling out, but individual bullets are not supplied. |
The custom-block graphics fix
The listed fix targets texture bleeding on custom blocks that use automatic block-face UV assignment with undersized textures. This is a creator-facing edge case, not a blanket repair for every broken texture or model.
To check it, keep the same pack build, custom block, lighting and camera angle. Compare the affected face before and after the client update. If the block is still wrong, inspect the content log and the pack’s geometry and texture definitions. If the problem extends beyond this documented UV case, use MineBrush’s Bedrock add-on troubleshooting route.
Build a useful before-and-after check
A screenshot taken after updating is not enough by itself. Preserve the original pack and a copy of the world, then record the console family, displayed Bedrock build, pack version, affected block identifier, face direction and viewing distance. Use the same scene after the update. A clean edge in that matched comparison supports the documented fix; a different block, texture or camera setup does not.
If the artifact remains, separate client behavior from content behavior. First load the custom block with only the required pack layers active. Then check whether the texture dimensions and automatic face assignment match the original reproduction. Finally, save, close Minecraft completely and reopen the world. A one-frame improvement that disappears after a reload is not a stable result.
When the console has not received the expected build
Platform rollouts are not always simultaneous. Do not uninstall the game, delete a world or remove a working pack just because another player reports a newer number. Check the platform’s normal update screen, finish pending downloads, restart the console and read the version shown by Minecraft again. If PlayStation remains on 26.34, that can still match the documented scope; the official page labels 26.35 as Switch-only.
On Switch, seeing 26.35 proves the client number, not the contents of the unnamed “additional fixes.” Test the issue you actually experienced and describe the result in concrete terms. Avoid posting a guessed list that other players may mistake for official patch notes.
Player checklist
- Record whether you are on PlayStation or Switch.
- Read the build number shown by the game; do not call both console builds 26.35.
- Preserve a backup of an important world.
- Finish the platform update and restart the game.
- Retest the exact crash, gameplay action or custom-block scene that mattered.
- Save and reopen the test world before promoting the update to your main play session.
Rollback and report path
If an add-on world becomes less stable after the client update, stop changing variables. Keep the original world copy and the last working pack release. Reproduce the problem in a disposable copy with only the required resource and behavior packs, then report the console, Bedrock build, pack version and smallest repeatable action. A game client cannot normally be rolled back through an unsupported route, but the world and pack stack can still be protected while the creator investigates.
What remains unknown
The official page does not enumerate the additional Switch fixes in 26.35 and does not map the custom-block bullet exclusively to either build. This article therefore keeps the page-level fix and the platform rollout separate. MineBrush has not tested either console build.
Read the official Minecraft Bedrock 26.34/35 changelog for the source record, rechecked August 25, 2026.

PLAYER QUESTIONS
Discussion
Include the exact edition, version and step when asking for help.