What the Minecraft launcher actually downloads

18 August 2026 · 6 min read

GameMapa editorial · how we check facts
Checked: Claude (AI) — fact-checked against the Ukrainian original; not proofread by a native speaker

The Minecraft launcher pulls down at least three separate pieces, not one file — the client, resources through a separate index, and dozens of libraries — which is why the game folder ends up far heavier than the client alone.

It looks like clicking “Play” downloads a single thing. In reality, the launcher checks the official version file that Mojang publishes and splits the download into several independent pieces based on it.

Three parts to one version

The official version 26.2 file shows that a single Minecraft version isn’t one file at all. It separately lists the client itself, the libraries needed to run it, and a link to a separate resource index. Each of these parts has its own address and downloads on its own, rather than sitting inside one shared archive.

This isn’t unique to this version — it’s how the version file format is organised in general, and the official launcher reads it the same way on every launch.

The client weighs less than you’d expect

The client file itself — the one that directly launches Minecraft — weighs just 37.4 MB. That’s small for a modern game, and the reason is simple: this file contains no libraries, no textures, no sounds. The launcher fetches all of that separately, following a list that the version file only describes through links.

That’s why comparing “the size of the game” to the size of this one file is misleading: the client is only a small slice of what ends up on disk.

Libraries: 131 separate files

The biggest reason the game folder outweighs the client is the libraries. The version 26.2 file lists 131 libraries that the launcher downloads separately from the client. This is ready-made code for handling audio, networking, graphics and other system-level tasks that the game itself doesn’t need to rewrite — Mojang plugs in existing solutions instead.

Each library on that list is its own file with its own address and its own version. If a required library is already on disk from another version of the game, the launcher can skip re-downloading it — which is why reinstalling a version you’ve already had tends to be faster than the first install.

Resources come from a separate index

Textures, sounds and everything else you see and hear in the game also aren’t part of the client file. The launcher pulls resources through a separate index numbered 32 — it isn’t part of the client file, only pointed to from it.

It’s a separate bookkeeping system: the index lists every resource individually, and the launcher checks which files are already on disk before fetching only what’s missing. That’s why a version update doesn’t always mean re-downloading every texture and sound at once — if part of the resource set hasn’t changed between versions, the launcher can leave the files you already have in place.

Compliance level: what complianceLevel means

The same official file has another field — complianceLevel. For version 26.2, it’s set to 1. It’s a technical field the official launcher reads on startup, and the version file itself doesn’t explain in detail what each possible value means. That isn’t stated on the page, so rather than guessing at an explanation nobody published, we’ll leave it there.

Why the game folder outweighs the client

Put it all together and it’s clear why the .minecraft folder ends up weighing far more than the client’s 37.4 MB over time.

Libraries and resources simply aren’t shown in the client file, so the game’s real footprint on disk is always bigger than the client’s own size — and that’s normal, not a sign of clutter.

Why you shouldn’t clean out .minecraft by hand

It’s tempting to save space by deleting things from the .minecraft folder yourself — old libraries or resources can look like dead weight. We’re deliberately not recommending specific files to remove: everyone’s build, mods and installed versions differ, and what looks unnecessary in one setup can be exactly what another setup needs.

The safer approach is to let the launcher organise those files itself — it already checks what’s downloaded and what isn’t. If you’re genuinely short on disk space, check first whether you have several full game versions installed at once — several full versions, not individual libraries, are usually what eats up the most space.

How to verify this yourself

Mojang publishes all of these fields openly, and the official launcher reads the very same file at startup. That means you can check everything above yourself, without a third-party source:

1. Find the official Minecraft version manifest — an open file that Mojang updates with every release.
2. In the manifest, find the version you want and the link to its separate file.
3. Open that file — you’ll see the library list, the resource index and the complianceLevel field exactly as the launcher sees them.

It’s the same route the official launcher takes, so the data there is always current as of the version’s release.

What isn’t stated here

The official version file doesn’t say how large the resources under index 32 are, and it doesn’t explain the compliance-level scale — there’s only the value 1 for version 26.2, with no description of what other values mean. It’s more honest to say plainly that this isn’t stated on the page than to invent a figure that isn’t there.

If you’re curious how Minecraft’s official editions differ from each other, there’s a separate guide on the difference between Java and Bedrock. And if it’s not the launcher you’re after but what to do inside the game, take a look at how much Minecraft Realms costs and what height to mine diamonds at.

Short version

A single Minecraft version isn’t one file — it’s a 37.4 MB client plus 131 libraries and a separate resource index numbered 32, all fetched by the launcher on its own. That’s exactly why the game folder outweighs the client, and it’s normal — not a reason to clean out .minecraft at random.