Order-Independent Transparency (OIT) is a rendering technique used to improve how overlapping transparent surfaces are drawn. Minecraft Java 26.3 introduced a new order-independent transparency algorithm as part of its rendering changes. That means the feature discussed here is now part of the vanilla Java client; you do not need to install Canvas or Sodium plus Indium just to get the new 26.3 transparency algorithm.
Why transparent blocks can look wrong
Glass, stained glass and other translucent surfaces are difficult to render when several layers overlap. The renderer must combine the colour and transparency of surfaces that may be in front of or behind one another from the current camera position. If the rendering method handles those layers in an unsuitable order, parts of the scene can look incorrectly blended or appear in the wrong visual order.
This can be noticeable in glass domes, aquariums, layered windows, glass tunnels and builds with several translucent materials crossing the same view. The effect depends on the geometry, camera angle, graphics settings and the specific transparent blocks in the scene. It is not accurate to say that every glass build always flickers or that every transparency artifact has the same cause.
What changed in Minecraft Java 26.3
Mojang's Java 26.3 release notes say that the previous “Improved Transparency” approach was replaced with a new order-independent transparency algorithm, which is expected to be much better at solving translucency issues. The wording matters: Mojang describes an improvement, not a promise that every possible transparent rendering problem is eliminated.
The release notes also add a rebindable debug key combination, F3 + X, to toggle “Improved Transparency.” If you are comparing the new behavior, use the same world, camera position and graphics settings for each test. Check the Controls menu if the key combination has been changed in your installation.
Do you need a graphics mod?
No additional graphics mod is required to use the OIT algorithm introduced in Java 26.3. The change is part of the vanilla Java client. Canvas, Sodium, Indium and shader packs are separate projects with their own rendering paths and compatibility requirements. They may offer other visual features, but they should not be presented as mandatory installation steps for the vanilla 26.3 transparency change.
If you already use a shader or rendering mod, check its current compatibility notes for Java 26.3. A mod may replace or alter parts of the rendering pipeline, so its behavior can differ from the unmodified client. Test with a clean vanilla profile if you need to determine whether an artifact comes from Minecraft itself or from an installed mod.
How to compare the transparency result
- Launch Minecraft Java 26.3 or a later version that includes the same feature.
- Open a world with a glass structure that previously showed an obvious transparency issue.
- Stand at a fixed position and note the camera angle, render distance and graphics settings.
- Use the documented
F3 + Xdebug key combination to toggle Improved Transparency. - Compare the same view again, looking for changes in overlapping glass and other translucent surfaces.
- Repeat from another camera angle and with different translucent blocks before deciding whether the issue is resolved.
For a fair comparison, do not change shader packs, resource packs, render distance and graphics settings at the same time. If you change several things at once, you will not know which setting caused the difference. Screenshots from the same position are useful for documenting the result, but remember that image compression and display settings can affect how subtle transparency differences appear.
What about performance?
OIT is a graphics-rendering feature, so its cost is primarily on the player's computer. It does not make the dedicated server render the glass, and it does not directly increase or decrease server TPS. A player with low FPS should check their GPU load, resolution, render distance, drivers and other graphics mods separately from server performance.
Mojang's 26.3 release notes do not publish a universal percentage for the frame-rate cost of the new algorithm. Do not rely on claims such as a fixed 5–15% performance hit unless they come from a reproducible benchmark on the same hardware, game version and scene. The cost can vary with the number of translucent surfaces, resolution and graphics setup.
If you notice a performance regression, compare the same scene with the setting enabled and disabled. Record frame times as well as average FPS, because short stutters can be hidden by an average. Test in a clean profile before blaming a server or removing unrelated plugins.
Does OIT change how glass blocks work?
No. The 26.3 transparency update changes how the client renders translucent surfaces. It does not change the crafting recipe, collision, blast resistance or gameplay behavior of glass blocks. Players can still build with ordinary and stained glass as before; the intended improvement is visual.
What if the glass still looks wrong?
First, confirm that you are actually running Java 26.3 or a later version with the feature. Then test without shaders or other rendering modifications, check the Improved Transparency toggle and update your graphics drivers if appropriate. If the problem remains, capture a screenshot and note the exact game version, graphics settings and steps needed to reproduce it. That information is more useful for a bug report than a general statement that “glass is broken.”
Official feature reference
Mojang's Java 26.3 release notes describe the replacement transparency algorithm and the rebindable F3 + X toggle. Use the official release page linked in the source panel for the exact wording and related technical changes.
Minecraft.How is an independent community site and is not affiliated with Mojang or Microsoft.
