About the Astroworld shader database

Astroworld runs a Minecraft network and publishes reference databases next to it, on shaders, texture packs, items, mobs, biomes, crafting and villager trading. Each of them exists for the same reason: the information is out there, but it is scattered across forum posts, video descriptions and download pages, and none of those will tell you whether the pack you are looking at will run on the machine you own.

Every shader page here answers that question first. What the pack needs in video memory and system memory, which Minecraft versions it covers, whether it loads under Iris or OptiFine or both, what it actually changes about the picture, and what it gives up in return. The pack itself is downloaded from the page its own author publishes, which is linked from each entry. We do not host or repackage anyone's work.

The hardware requirements, version ranges and loader support are compiled per pack and checked against what the pack does when it is loaded, rather than copied from a summary somewhere else. Where a pack ships several presets, the figures describe the preset the author treats as the default, because that is the one you get when you install it and change nothing.

The screenshots on each page come from the pack's own author. The comparison images between effects are ours, taken in the same world and from the same position so the only difference between two shots is the setting being described. Nothing on this site is an upscaled thumbnail: when the original is only available small, we say so rather than stretching it.

A tier such as low impact or ultra impact is a memory budget rather than a promised frame rate. Your frame rate depends on your render distance, your world and what else the machine is doing. The memory ceiling does not, which is why it is the number we publish.

Every page on this site carries a last updated date at the bottom, and that date is worked out from the text of that page rather than from the last time the site was rebuilt. If a page says August and it is October, that means the figures on it have not changed since August, not that nobody looked. A fresh date printed over stale facts would be worse than no date at all.

Version support is the thing that goes out of date fastest, because a pack that stops at 1.20.4 does not announce it. Where a pack no longer covers the current release, the page says so in the text rather than only in a table, since that is the detail that decides whether it is worth reading any further.

Corrections are welcome and they get acted on. If a version range is wrong, a requirement has moved, or a pack has been taken over by a new maintainer, the support channels linked in the footer of every page reach us, and it helps to say which page and which line.

If you are the author of a pack listed here and you would rather a screenshot or a description were changed or removed, the same route applies and it is dealt with first.