Resource Packs Explained: Textures, Models & Sounds

A resource pack is Java Edition's way of restyling the game without touching gameplay. Every texture, 3D model, sound, font and bit of UI you see can be replaced by files in a pack. Like datapacks, they're plain .zip folders of assets and JSON, they need no mods, and they're applied through the in-game options menu. (On Bedrock the equivalent is the 'resource pack' half of an add-on.)

The folder layout

A resource pack starts with pack.mcmeta (description + pack_format, just like a datapack) and an 'assets' folder. Inside assets/minecraft you'll find 'textures' (PNG images for blocks, items, entities and the GUI), 'models' (JSON that says how an item or block is shaped and which textures it uses), 'sounds' plus a sounds.json index, 'blockstates' (which model to show for each block variant), and optionally 'font' and 'lang'.

• ▸textures/ — the PNG images themselves.
• ▸models/ — JSON describing shape and which textures to apply.
• ▸blockstates/ — picks a model per block state (e.g. stair facing).
• ▸sounds/ + sounds.json — custom audio and where it plays.

How textures and models connect

Minecraft blocks aren't a single image — a grass block uses a green top, a dirt side and a dirt bottom, wired up by its model and blockstate files. That per-face mapping is why a good Minecraft look needs more than one texture per block. Item models can even change with custom model data, which is how packs add 'new' items by re-skinning existing ones.

Packs vs. datapacks, together

Resource packs and datapacks are two halves of a whole: the datapack adds a custom mob's behaviour and the resource pack gives it a model and texture; the datapack runs a minigame and the resource pack themes its UI. Knowing which half owns which job saves a lot of confusion when something looks right but behaves wrong, or vice versa.