How to Install Resource Packs on Minecraft Bedrock

Bedrock resource packs are distributed as .mcpack files. A .mcpack is simply a ZIP archive with a different extension that Windows, Android, iOS, and consoles all hand straight to Minecraft. The import is a single action:

1. Download the pack’s .mcpack file to your device. On Optimum Realism you grab it from the downloads section; most creators offer a Bedrock .mcpack alongside the Java .zip.
2. Open the file. On Windows or mobile, double-tap (or double-click) it. Minecraft launches by itself and shows an “Importing” message, then a green confirmation.
3. That’s the install done. The pack now sits in your Available list, ready to apply — but it is not switched on yet. That happens in the next step.

If double-tapping does nothing, the file association may be wrong, or your browser saved it as a plain .zip. Renaming the extension from .zip to .mcpack almost always restores the one-tap behaviour. The troubleshooting section below covers the rest.

Where the files actually land

Behind the scenes, the import unpacks into Bedrock’s resource_packs folder inside com.mojang. You rarely need to touch it, but knowing it exists helps when a manual install is your only option — for example copying a pack across devices, or recovering one a launcher refused to import.

Importing a pack and using it are two different things. Bedrock gives you two places to activate a pack, and the difference matters:

Global Resources — every world at once

From the main menu, go to Settings → Global Resources. You’ll see two columns: My Packs (everything you’ve imported) and Active. Tap your pack, then choose Activate to move it into the Active column. A globally active pack applies to every world you load — handy if you want one realism pack everywhere without setting it per world.

Per-world — just one save

To use a pack in a single world only, open that world’s Edit screen (the pencil) — or the Create New World screen — and pick the Resource Packs tab. Activate the pack here and it applies to that world alone, leaving your other saves untouched.

A per-world pack always wins over a global one for that world, so you can keep a default look globally and override it on specific maps. When several packs are active, Bedrock stacks them top to bottom and packs higher in the list override those below — so drag your main realism pack to the top of the Active column.

New to all of this? The full installation guide walks through both Java and Bedrock with screenshots, and our cross-platform install guide shows how the Java side compares.

On Bedrock, “realism” usually means more than crisp textures — it means physically based rendering (PBR) and, on the right hardware, hardware ray tracing (RTX). These rely on extra texture maps a normal pack doesn’t ship, so a pack has to be built for it. Optimum Realism includes those PBR maps, which is what lets it light up under RTX.

To turn ray tracing on:

1. Make sure an RTX/PBR-enabled pack is active (global or per-world) — without one, there is nothing for ray tracing to render.
2. Go to Settings → Video and look for the Ray Tracing toggle. Turn it on.
3. Load the world. Surfaces now show real reflections, emissive blocks cast light, and metals look metallic.

If the Ray Tracing toggle is missing or greyed out, it is almost always one of two things: your PC doesn’t have an RTX-capable GPU (ray tracing here is a Windows-PC feature, not available on mobile or console), or the active pack doesn’t include PBR maps. Activating a true PBR pack first is what makes the option appear. For the full picture of how Bedrock’s ray tracing works, see Bedrock RTX explained.

You don’t need an RTX card to benefit, though. Optimum Realism’s free 64x pack sharpens textures on any Bedrock device; higher resolutions and the full PBR set for RTX are available through Patreon. To understand the maps involved, our PBR explainer breaks it down without the jargon.

Most failed Bedrock installs come down to a handful of causes. Work through these before assuming the pack is broken:

• The file is a .zip, not a .mcpack. Some browsers and chat apps re-save downloads as .zip. Rename the extension to .mcpack and open it again, or extract it manually into the resource_packs folder.
• The pack imported but won’t appear. If you extracted it by hand, the manifest.json may sit one folder too deep. The folder you drop into resource_packs must contain manifest.json at its top level — not inside a nested subfolder. Re-importing the original .mcpack avoids this entirely.
• “Import failed” or nothing happens. A corrupted or partial download is the usual culprit. Delete the file and download it again over a stable connection.
• Wrong app opened the file. On Windows, an archive tool may have claimed the .mcpack association. Right-click → Open with → Minecraft to force the import.
• Version mismatch. A pack built for a newer Bedrock release can show warnings or missing textures on an older client. Update Minecraft to the latest version, then re-apply the pack.
• It imported but looks flat. That’s a rendering setting, not a failed install — see why textures look flat or shiny for the fixes.

Still stuck? Our FAQ covers device-specific quirks, or browse all guides for deeper dives on shaders, PBR, and performance.