If you have an RTX 3060 or better, you can push Minecraft to photorealistic levels with path-traced lighting, voxel-based global illumination, ray-traced reflections, and physically-based rendering. The shaders below combine "high" and "ultra" impact packs that demand serious GPU power but deliver results that rival dedicated ray-tracing titles. These are the packs you reach for when you want wallpaper-quality screenshots or cinematic video footage.
Path tracing, voxel GI, SSPT, and ray-traced reflections are the headline features at this tier. Packs without at least one of these advanced techniques are better suited to the mid-range list.
High-end shaders should support PBR resource packs with normal maps, specular maps, and emissive textures. This is where the photorealistic detail comes from.
At this tier, we care about maximum fidelity. Cinematic depth of field, accurate caustics, and detailed volumetric clouds separate the best packs from the rest.
| # | Shader | Tier | Loader | Min GPU | VRAM |
|---|---|---|---|---|---|
| 1 | Complementary Unbound | High | Iris, OptiFine | GTX 1070 / RX 5600 XT | 4 GB |
| 2 | SEUS Renewed | High | OptiFine | GTX 1060 / RX 580 | 3 GB |
| 3 | SEUS PTGI HRR | Ultra | OptiFine | RTX 3060 / RX 6700 XT | 6 GB |
| 4 | Kappa Shader | High | Iris, OptiFine | GTX 1070 / RX 5600 XT | 4 GB |
| 5 | Photon Shader | Ultra | Iris | RTX 3060 / RX 6700 XT | 6 GB |
| 6 | iterationT | High | Iris, OptiFine | GTX 1070 / RX 5700 | 4 GB |
| 7 | Rethinking Voxels | Ultra | Iris | RTX 3060 / RX 6700 XT | 6 GB |
| 8 | Continuum Shaders | Ultra | OptiFine | RTX 3070 / RX 6800 | 8 GB |
| 9 | Voyager Shaders | High | Iris, OptiFine | GTX 1070 / RX 5600 XT | 4 GB |
| 10 | Exposa Shaders | High | Iris, OptiFine | GTX 1070 / RX 5700 | 4 GB |
| 11 | Hysteria Shaders | Ultra | Iris | RTX 3070 / RX 6800 | 8 GB |
The high-fidelity sibling of Complementary Reimagined. Unbound pushes visual quality further with path-traced global illumination and more demanding effects for those who want cinematic results.
The legendary shader pack that helped popularize Minecraft shaders. SEUS Renewed continues the legacy with modern rendering techniques and a signature warm, cinematic look.
The path-traced version of SEUS. PTGI HRR delivers near ray-tracing quality through advanced path tracing techniques, producing some of the most realistic lighting in Minecraft.
The reason this bracket exists. Path tracing with ray-traced reflections and shadows, plus caustics that move across a riverbed. The catch is the version ceiling at 1.20.4 and OptiFine only, so decide the version question first.
A high-quality cinematic shader from RRe36 featuring advanced lighting with path-traced global illumination and volumetric clouds.
A cutting-edge path-traced shader for Iris with advanced global illumination, volumetric effects, and PBR material support.
The pick for a current world: path-traced global illumination with a neutral grade, on Iris, from 1.19 to 26.1.2. It leaves the colour alone and lets the light do the work.
A cinematic shader featuring screen-space path tracing for highly accurate lighting. Known for its natural color palette and film-like quality.
A voxel-based global illumination shader that uses voxelized scene data for accurate light bouncing. Produces colored lighting and realistic indirect illumination.
Lights from a voxel model of your surroundings rather than by tracing through geometry, so coloured light stays correct behind you. It is often the one that stays playable where the others do not.
A premium, studio-quality shader pack that pushes Minecraft visuals to photorealistic levels. Continuum features advanced path tracing and industry-standard PBR rendering.
One of the two entries that asks 8 GB, and the older implementation of the pair. If it hitches rather than slowing evenly, it is running out of memory rather than out of speed.
A cinematic shader designed for content creators with emphasis on atmospheric effects, volumetric clouds, and film-quality depth of field.
A cinematic shader with emphasis on exposure and color grading. Designed for photography-style Minecraft visuals with detailed atmospheric rendering.
A high-end voxel-based path-tracing shader that combines multiple cutting-edge rendering techniques for near-photorealistic results.
Voxel global illumination and path tracing in the same pack, with caustics and coloured lighting on top. The most demanding thing on this site, and it needs Minecraft 1.20 or newer.
High-end shaders use three main approaches to advanced lighting. Path tracing (used by SEUS PTGI HRR and Continuum) traces rays from the camera through the scene, bouncing them off surfaces to calculate realistic indirect lighting and reflections. This produces the most accurate results but is extremely GPU-intensive.
Voxel-based global illumination (Rethinking Voxels, Hysteria Shaders) converts the nearby Minecraft world into a 3D voxel grid and traces light through that simplified representation. This is faster than full path tracing while still delivering colored indirect lighting and accurate light bouncing through rooms and corridors.
Screen-space path tracing (iterationT, Complementary Unbound) limits ray tracing to what is visible on screen. It is less accurate than full path tracing since it cannot account for off-screen geometry, but it runs significantly faster and still produces natural-looking lighting with soft contact shadows and indirect color bleeding.
For raw visual quality, path tracing wins. For playable frame rates with advanced lighting, voxel GI is the best compromise. SSPT sits in between and is often the most practical choice for players who want to actually play the game rather than just take screenshots.
Regardless of which technique you choose, pair your shader with a PBR resource pack like Patrix or Realistico for the full effect. Without PBR textures, many of these advanced lighting features cannot show their full potential since they need normal maps and specular data to calculate realistic surface reflections.
The hardest part of running the heaviest packs is not the hardware. It is that the most celebrated pack in this class stopped moving forward. SEUS PTGI HRR runs up to Minecraft 1.20.4 and Continuum Shaders does the same, and if your world is on 1.21 then two of the five most powerful shaders available are simply not options, whatever your card can do.
That leaves a smaller field than the reputation suggests, and it is worth knowing which way the field has moved. The packs that do support current versions here run on Iris rather than OptiFine, because that is where the development has gone. If you have been on OptiFine for years, this is the point at which the switch stops being optional.
There is a second, quieter version problem: a pack can support a Minecraft version while the loader for it lags behind by a few weeks after a release. The pack page will say 1.21 and the game will refuse to load it, and the missing piece is the loader rather than the shader. Checking which loader build you have before concluding a pack is broken saves an evening.
None of this is an argument against the tier. It is an argument for deciding the version question first and the visual question second, which is the opposite of how most people arrive here.
People arrive at this page and conclude they need a new graphics card. Sometimes that is true. Before spending anything, two checks are worth an evening, because both are free and both fix a surprising number of cases.
First, run the world with shaders off and fly across unexplored terrain. If that stutters, the problem is not the shader and a new card will not fix it. Generating and loading new chunks is work for the processor and the disk, and a machine that struggles there will struggle with any pack layered on top.
Second, check how much memory Minecraft itself has been given, and whether you are on Iris with Sodium or on OptiFine. The packs on this page ask for 8 GB of system memory behind the card, and a default launcher profile often allocates far less. Sodium alone can change the baseline frame rate enough to move a pack from unplayable to workable.
If both checks come back clean and the pack still hitches rather than slowing evenly, then it really is video memory, and that is the one thing you cannot configure your way out of. At that point the honest options are the tier below or a card with more of it.
If your machine can hold anything on this page, the interesting question stops being whether a pack will run and becomes what you want to do with the room you have. Three answers are worth considering, and they pull in different directions.
You can spend it on fidelity, which is what most people do: the heaviest pack your card can hold, at its default settings, all the time. That is a reasonable choice and it is also the one most likely to end with the pack quietly turned off, because the cost is paid on every ordinary session and the benefit is mostly visible when you stop to look.
You can spend it on distance instead. A lighter pack with a much larger render distance gives you a world that feels bigger, and on a build that is meant to be seen from far away that reads as more impressive than better lighting on the nearest twenty blocks.
Or you can spend it on smoothness: a mid-weight pack at a frame rate high enough that the game feels immediate. On a high refresh rate monitor that difference is more noticeable in play than any lighting improvement.
None of those is wrong, and the right answer changes with what you are doing that evening. Keeping two packs installed and switching between them is not indecision, it is using the machine properly.
Running something this demanding for hours is a different proposition from running a benchmark for two minutes, and the difference is physical rather than graphical.
A card under sustained full load gets hot, and a hot card slows itself down to stay safe. That is why a session can start smooth and end noticeably less so with nothing having changed on screen. If your frame rate degrades over the first twenty minutes and then settles lower, you are looking at thermals rather than at the pack.
Noise is the part nobody mentions until they live with it. Minecraft is a game people play while talking to other people, and a machine that spins up to a roar is a real cost, particularly on a laptop. Capping the frame rate slightly below what the machine can hold is the single most effective way to keep a room quiet.
Power matters on a portable machine for a second reason: many laptops run their graphics considerably slower on battery than on mains, sometimes by half. If a pack behaved differently yesterday, check what it was plugged into before you check anything else.
There is a category of machine that does unusually well here and gets written off by most advice: an older card with a generous amount of memory. Because the thing that decides whether these packs load is capacity rather than speed, a card that is two generations behind but well provisioned can run things that a newer, leaner card simply refuses.
What you get is not the frame rate a review would quote. It is the option of running the pack at all, at a lower render distance and a modest frame rate, which for building and screenshots is often exactly enough.
The practical approach is to start conservative and work up rather than starting at the defaults and being disappointed. Set a shorter render distance than feels right, let it be stable, and then push one thing at a time until it is not.
And if it stalls rather than slows, you have found the ceiling that cannot be tuned around. That is worth knowing precisely, because it is the one case where the answer really is different hardware rather than different settings.
Not every session is worth a high-end pack, and not every machine in the house is this one:
Last updated . This page is rebuilt when its own figures change, not on every deploy.
