How to Increase FPS with Complementary Shaders

Every shader pack costs frame rate; the craft is spending that cost on the effects you actually see. If Complementary Shaders runs slower than you would like, work through the fixes in this order, they are ranked by typical impact, and the first two solve most cases on their own. No invented benchmarks here: your numbers will differ from anyone else's, so each step tells you how to verify the gain on your own machine.

1. Drop the quality profile one step

The profile (Potato to Ultra) bundles dozens of values. One step down, High to Medium, Medium to Low, is the single broadest FPS lever inside the pack, and the developers ordered each bundle so the least visible effects are trimmed first. Change it in the pack's settings screen, then test in your busiest scene. Profile logic: presets explained.

2. Reduce render distance

Render distance multiplies everything: more chunks means more terrain to light, shadow and reflect. It is a game setting, not a pack setting, and it is frequently the real culprit when a "shader problem" appears. Drop it by two chunks and re-test. The full interaction between distance, shadows and fog is in render distance and performance, including how slightly denser fog can hide a shorter distance beautifully.

3. Trim shadow distance, then shadow resolution

Shadows require the world to be rendered again from the sun's position. Cutting shadow distance shrinks that second render; cutting shadow resolution cheapens it. Distance first, in villages, forests and interiors you will barely notice, and the saving is real. Iris users also have a loader-level shadow distance cap that does the same job. Details: lighting and shadow settings.

4. Lower cloud quality

The shader sky is rendered with depth across your whole view, every frame, whenever you are outdoors. Detailed clouds are a constant tax. One step down on cloud quality is a standard, low-regret FPS recovery, judge it at sunset, where cloud quality shows most, before deciding it is invisible. See clouds and atmosphere settings.

5. Ease the water reflections

Reflections re-render the scene mirrored. If your world is lakes, rivers and coast, reflection quality is a major cost centre; one step down recovers meaningful frames while the water still looks alive. In a desert world, skip this, there is nothing to save. Water and reflection settings explains the balance with wave detail.

6. Consider resolution and window mode

Rendering at a lower resolution (or using your platform's upscaling where available) cuts every per-pixel cost at once, shadows, water, sky, all of it. It softens the image, which is why it sits late in this list, but on a high-DPI laptop screen the trade is often surprisingly painless. Fullscreen exclusive mode also tends to behave better than borderless windowed on some systems; test both.

7. System hygiene

• Drivers: current graphics drivers matter for shader-heavy workloads, see GPU and driver compatibility.
• Background load: browsers, recorders and launchers competing for the GPU will show up as shader stutter. Close what you do not need.
• Allocated memory: modded setups that starve the game of RAM stutter regardless of graphics settings. If you run many mods, check your allocation.
• The loader stack: Iris + Sodium exists precisely to give the game more headroom, the compatibility guide explains the pairing.

Verify gains honestly

After each change: same world, same spot, same view direction, same time of day. Watch the frame rate for thirty seconds, not three, shader cost varies with what is on screen. Change one thing at a time or you will never know what helped. The full method is the performance optimisation guide. If your problem is not low average FPS but hitching and spikes, your article is reducing lag and stuttering, a different diagnosis entirely.

Why the same settings feel fast in one place and slow in another

The seven steps above are ranked for an average scene, but no scene is average. Understanding where the cost concentrates helps you apply the right fix first instead of working the whole list blindly. Indoors and underground, shadows and sky largely drop out of the frame, if performance is still poor in a cave or a storage room, look away from the pack and towards render distance, entities, and base-game load. Outdoors at ground level, clouds and atmosphere run constantly, which is why step 4 punches above its weight for surface exploration. Over water, reflections dominate: a coastal base can be your slowest scene even on a strong machine, while an identical build inland runs easily. In dense forest and jungle, shadow work multiplies because so much geometry sits inside the shadow render. When a single scene type is your problem, trim the system that scene taxes rather than dropping the whole profile, you keep the look everywhere else.

Two quick checks laptop and high-resolution players skip

Before assuming the pack is at fault, laptop players should confirm two things that mimic a shader problem exactly. First, which GPU is the game actually using? Laptops may default to integrated graphics, and no in-pack setting compensates for rendering on the wrong chip. The game's F3 debug screen shows the GPU in use, if it names the integrated graphics instead of your dedicated card, fix that in your system graphics settings before touching any shader option. Second, what resolution are you really rendering at? A high-resolution laptop or desktop display multiplies every per-pixel effect in the pack. Step 6 covers lowering it, but even checking whether the game is running at native resolution, a scaled resolution, or a window smaller than you think often explains a sudden drop after a display or docking change. Both checks take a minute and can save an hour of pointless tuning.

Knowing when to stop

Quick fixes have a natural end point: the frame rate holds steady in your busiest scene, turning and travelling feel even, and further trims cost more in looks than they return in smoothness. Chasing the counter higher past that point usually means sacrificing shadows, water, or sky that you installed the pack to see. If you reach the end of this list and performance is still not where you want it, the honest options are the structured route, work through the performance optimisation guide scene by scene, or accepting a lower profile as your daily setting and reserving higher profiles for screenshots and slow exploration. Neither is a failure; both are the pack being used as it was designed, with profiles from Potato to Ultra precisely so different machines can find their own point on the ladder.

Frequently asked questions