Texture Pack vs Resource Pack vs Shader

A resource pack is the official, modern term for the add-on file that replaces a game's built-in assets. It is a .zip (or .mcpack on Bedrock) that Minecraft loads on top of the default game files. Despite the name "texture pack" sticking around in conversation, Mojang renamed the system to resource pack back in Java Edition 1.6 (2013) for a reason: a single pack can change far more than textures.

A resource pack can override any of these:

• Block and item textures — the images painted onto every block, tool, and mob.
• Sounds — footsteps, ambience, music discs, mob noises.
• Models — the 3D shape of blocks and items (via JSON models).
• Fonts and language files — the in-game typeface and text.
• GUI and UI elements — menus, the HUD, container backgrounds.
• PBR maps — extra texture data (normal, specular/height) that shaders and RTX read for realistic surfaces.

So every texture pack is a resource pack, but not every resource pack is only about textures. When people say "I installed a texture pack," they almost always mean a resource pack that focuses on visuals. To put one in, see the full install guide.

"Texture pack" is the legacy term and the part most players actually care about: the images wrapped around every block and item. Before 1.6, the entire system was called a texture pack because that was essentially all it could change. The word stuck, which is why you still see packs advertised as "texture packs" on CurseForge and Modrinth even though they are technically resource packs.

The most visible thing a texture pack does is resolution and art style. Vanilla Minecraft ships at 16×16 pixels per block. A realistic pack repaints those same blocks at higher resolution — 32×, 64×, 128×, 256×, or beyond — with photographic detail instead of pixel art. Higher resolution means sharper surfaces but a bigger download and more GPU memory. For a full breakdown, see the resolution guide.

Where Optimum Realism fits

Optimum Realism is a realistic resource pack in this sense: it replaces the block and item textures with high-detail, photoreal surfaces, and it ships the PBR maps that make those surfaces react to light. The base 64× edition is free; higher resolutions are available through Patreon. Because it is "just" a resource pack, it loads on top of vanilla and works whether or not you add a shader — though you get far more out of it when you do.

A shader pack is a different thing entirely. It does not touch your block textures — instead it rewrites how the game renders light. Shaders add things vanilla Minecraft does not do, such as:

• Realistic shadows that move with the sun.
• Reflective water with waves and ripples.
• Reflections on wet, metallic, or polished surfaces.
• Volumetric fog, god rays, bloom, and atmospheric color.
• Depth and bumpiness on surfaces (by reading PBR normal maps).

On Java Edition, shaders are loaded through a mod — Iris or OptiFine — and the shader file goes into a shaderpacks folder, not the resource packs folder. See the shaders page and the shader install guide for the exact steps. Popular shader packs include Complementary, BSL, and SEUS.

On Bedrock Edition, there are no Java-style shader packs. Realistic lighting there comes from RTX (ray tracing) on supported GPUs, which is built into the game rather than added as a separate file. RTX reads PBR maps that ship inside the resource pack. More on that in Bedrock RTX explained.

One honest trade-off: shaders are the single biggest hit to your frame rate. Heavier shaders can roughly halve FPS on a mid-range machine, so if performance matters, choose a lighter preset. There are tips in boosting FPS.

The cleanest way to think about it is a stack, applied in order on top of vanilla Minecraft:

1. The resource (texture) pack repaints the blocks and supplies the PBR maps — the raw material.
2. The shader (or Bedrock RTX) reads those textures and PBR maps, then lights the scene — shadows, reflections, depth, atmosphere.

They live in different folders and rarely conflict. The resource pack goes in resourcepacks; on Java, the shader goes in shaderpacks. They are activated in different menus too: resource packs under Options → Resource Packs, shaders under Video Settings → Shaders (Iris/OptiFine).

This is exactly why a PBR pack needs a shader to shine. The pack's normal and specular maps are invisible under vanilla lighting — nothing in the base game knows how to interpret them. Add a shader (or turn on RTX) and the same blocks suddenly gain depth, glossy wet stone, and reflective metal. The realism is the combination. If your textures look flat even with a pack installed, the usual cause is "no shader / RTX yet" — see why textures look flat or shiny.

You do not need three separate things — you need two, because "texture pack" and "resource pack" are the same file. The real question is whether you add a shader. Here is how to decide:

• Resource pack only: good for low-end PCs, servers that block mods, or anyone who just wants nicer-looking blocks without the FPS cost. You get higher-resolution art but vanilla flat lighting.
• Resource pack + shader (or RTX): the full realistic look — shadows, reflections, and depth. This is what most "realistic Minecraft" screenshots are using. It costs frames, so you want a capable GPU or a lighter shader preset.
• Shader only, no pack: still a big visual upgrade thanks to the lighting, but blocks stay at vanilla 16× detail. Fine, but you are leaving the biggest realism gains on the table.

For most people chasing realism, the answer is a PBR resource pack plus a shader (Java) or RTX (Bedrock). Optimum Realism is built for exactly that pairing — it works on its own, but its PBR maps come alive once a shader or RTX is reading them. Browse the full guide library if you want to go deeper on any piece.