Ti
Working pre-release · Minecraft renders on Metal

A native Metal renderer
for Minecraft.

Minecraft: Java Edition draws through OpenGL 3.3 on macOS — an API Apple deprecated in 2018 and never optimised for Apple silicon.

Titanium replaces the renderer with a genuine Apple Metal backend — title screen and in-world, with no OpenGL context in the process. Not a wrapper, not a translation layer.

Why

OpenGL is a dead end on the Mac.

Apple deprecated OpenGL across its platforms in 2018. It still works, but it receives no driver investment, cannot express how Apple GPUs actually render, and leaves most of the hardware's capability unreachable.

01

Direct Metal

Titanium talks to Metal through an Objective-C++ bridge. There is no MoltenVK, no Vulkan layer, and no OpenGL shim underneath — at runtime the process speaks Metal and nothing else.

02

Built for Apple silicon

Unified memory means vertex data written by the JVM is the same memory the GPU reads. Tile-based deferred rendering means depth buffers never have to exist in main memory at all.

03

Capability-gated

Every Metal feature is checked against the live device at runtime, never inferred from the chip name or macOS version. Unsupported machines fall back cleanly instead of crashing.

How

Minecraft already has a backend seam.

Mojang's 1.21 rendering rewrite introduced an explicit, backend-agnostic graphics abstraction — and marked it @DontObfuscate, so it keeps its real names through obfuscation. Titanium implements that interface instead of patching thousands of scattered draw calls.

Minecraft render code
World, entities, particles, GUI, post-processing
→
GpuDevice · CommandEncoder · RenderPass
57 methods total — the whole backend contract
→
GlDevice
OpenGL 3.3 core
MetalDevice
Apple Metal

The OpenGL context itself is created inside GlDevice — so replacing the device removes OpenGL from the process rather than leaving a dead context behind. Verified by disassembling the 1.21.11 client, not assumed.

Status

What actually works today.

A pre-release, published in the open. This table reflects what has been built and tested — not what is planned.

ComponentDetailState
Metal backend All 57 methods of Minecraft's GpuDevice / CommandEncoder / RenderPass seam, over a native Objective-C++ core working
Shader translation All 50 vanilla pipelines translate from GLSL and compile with Metal; golden tests check translated shaders produce OpenGL's pixels working
Correctness vs OpenGL 99.8–99.96% of pixels identical in deterministic test scenes — within OpenGL's own run-to-run variation measured
Lifecycle Resize, fullscreen, resource reload, leaving and rejoining worlds — each checked by screenshot verified
Release jar Runs in a production Fabric install; falls back to OpenGL automatically on unsupported setups verified
MetalFX spatial upscaling World at reduced resolution, UI at native. Helps at high resolutions only; off by default optional
MetalFX temporal Needs motion vectors and a jittered projection Minecraft does not produce — not implemented not built
Mesh shaders The GPU supports them, but measurement found no headroom to win: at high render distance the frame is set by CPU work, so cutting GPU geometry cost changes nothing evaluated, not used
Other hardware Everything so far is measured on one machine (M3 Max, macOS 26.6) untested

Measured, with caveats

Same frozen, seeded world, same camera and settings; stock OpenGL vs Titanium, three alternating runs each, vsync off. Apple M3 Max, 1708×960.

SceneFrame timeGPU time
Open landscapeOpenGL 6.0–6.2 ms
Metal 1.4–1.5 ms
OpenGL 3.5–3.6 ms
Metal 1.9–2.0 ms
Forest canopyOpenGL 5.3–5.6 ms
Metal 1.2–1.3 ms
OpenGL 3.2–3.4 ms
Metal 1.3–1.4 ms
Open landscape, rainOpenGL 6.3–6.7 ms
Metal 1.7–1.8 ms
OpenGL 3.6–4.0 ms
Metal 2.2 ms
Open landscape,
32-chunk view
OpenGL 12.1–12.6 ms
Metal 3.6–3.8 ms
OpenGL 9.2–9.6 ms
Metal 4.0–4.7 ms

Read these carefully. One machine, four scenes. With vsync off, Titanium renders every frame but only presents the ones the display can show, while OpenGL hands every frame to the window server — part of the frame-time gap is that difference. GPU time uses Minecraft's own timer on both backends, but it rests on different instruments underneath. At the 32-chunk view distance the gap is almost entirely CPU time on the render thread — 11.0 ms per frame on OpenGL against 3.4 ms — which is also why Titanium batches its chunk draws. These numbers are not a claim about other Macs or typical gameplay.

Requirements

What you'll need.

Shader packs such as Iris and OptiFine inject GLSL and call OpenGL directly. With no GL context in the process there is nothing for them to call, so Titanium detects them at startup and stays disabled rather than failing halfway through world load.