How to Install Minecraft Texture Packs
Texture packs are resource packs. On Java, they are ZIP files you drop into resourcepacks. On Bedrock, they are .mcpack files that import when you double-click them. This guide covers both editions, load order, and what to do when a pack does not appear.
Java Edition
- Download the pack. It should be a
.zipfile. Do not extract it unless the creator explicitly says to. - Open the resourcepacks folder. Press
Win + R, type%appdata%\.minecraft\resourcepacks, and press Enter. On macOS:~/Library/Application Support/minecraft/resourcepacks. On Linux:~/.minecraft/resourcepacks. - Place the ZIP directly inside
resourcepacks. Not in a subfolder. - Launch Minecraft. Go to Options → Resource Packs. The pack appears in the left column.
- Move it to the right column. Hover over the pack and click the arrow. Click Done.
Bedrock Edition
- Download the pack. Bedrock packs are usually
.mcpackfiles. - Double-click the file. Minecraft should launch and import the pack. Wait for the "Import Successful" message.
- Activate it. Go to Settings → Global Resources → My Packs. Click the pack and select Activate.
If double-click does not work, place the file manually in the resource_packs folder:
- Windows:
%localappdata%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\resource_packs - Android:
/games/com.mojang/resource_packs/
Load order matters
Resource packs load from bottom to top in the selected column. If two packs change the same texture, the one higher in the list wins.
This matters most when using add-ons. Fresh Animations Add-ons, for example, must be loaded above the base Fresh Animations pack. Otherwise the base pack overrides the add-on and you see no change.
If the pack does not appear
- You extracted the ZIP. Java packs load as ZIPs. If you extracted it, re-zip the folder or re-download.
- Version mismatch. A pack built for 1.20 may still work on 1.21, but some do not. Check the pack's page for supported versions.
- Wrong folder. Texture packs go in
resourcepacks, notshaderpacksormods. - Empty or corrupt ZIP. If the download failed partway through, the ZIP may be unreadable. Re-download and check file size.
Resolution and performance
Resolution is not the same as performance cost. A 32x pack can be heavier than another 32x pack if it uses more textures. This is why Patrix 32x is significantly heavier than Faithful 32x, despite the same resolution — Patrix uses hundreds of extra textures for tiling and randomization.
| Resolution | Typical use | Performance impact |
|---|---|---|
| 8x | PvP, low-end hardware | Below vanilla |
| 16x | Vanilla-plus, animations | Same as vanilla |
| 32x | Vanilla-plus at higher detail | Small increase |
| 64x | Vanilla-plus on high-res displays | Moderate increase |
| 128x+ | Realistic PBR, screenshots | Significant increase |
OptiFine vs Fabric for connected textures
Some packs use OptiFine-specific features: connected textures, custom entity models, custom colors. On Fabric, those features come from separate mods.
| Feature | OptiFine | Fabric equivalent |
|---|---|---|
| Connected textures | Built in | Continuity |
| Custom entity models | Built in | Entity Model Features (EMF) |
| Custom entity textures | Built in | Entity Texture Features (ETF) |
| Custom colors | Built in | Colormatic (older versions) |
Frequently asked questions
Does a 32x pack look better than 16x?
Will texture packs affect my frame rate?
Can I combine two texture packs?
Do texture packs work on Bedrock and Java at the same time?
What is a PBR texture pack?
Related guides
How to Install Shaders — for Iris and OptiFine.
How to Install Maps — for world downloads.
Iris vs OptiFine — which loader to use for connected textures and shaders.