Chunks & world size · Java · Intermediate

How to Convert Block Coordinates to Chunk and Region (.mca) File Names

When managing or repairing a Minecraft Java Edition world, you often need to pinpoint which exact region file on your disk contains a specific build or corrupted area. This guide explains the exact bit-shift math used by the game to convert in-game block coordinates into chunk coordinates and r.X.Z.mca region file names. You will also learn how to visually locate and manage these 512x512 block regions directly in your browser using our Chunk Trimmer without ever uploading your world files.

Open the Chunk TrimmerPaint chunks on the map and delete them, or remove every chunk nobody really visited.

What you need

  • A Minecraft Java Edition world folder or .zip backup
  • The in-game X and Z block coordinates of your target location (found by pressing F3 in-game)
  • A modern web browser to run our local Chunk Trimmer tool
  • A complete backup copy of your world folder stored in a safe location before modifying any files

Step by step

  1. 1Record Your In-Game Block Coordinates

    Enter your world in Minecraft Java Edition, walk to the location you want to locate on disk, and press F3 to open the debug screen. Look at the 'Block' or 'XYZ' line and write down the X (East/West) and Z (North/South) integer values. You can ignore the Y (vertical height) coordinate because Minecraft Java Edition stores the entire vertical column of a world inside the same horizontal chunk and region.

    Tip: If you scan down the F3 screen to the 'Chunk' line, Minecraft actually displays the calculated chunk and region values for you, which is great for double-checking your manual math.

  2. 2Calculate Chunk Coordinates from Block Coordinates

    To convert your block X and Z coordinates into chunk coordinates, divide each number by 16 and round down to the nearest whole integer (a mathematical floor division, or a bitwise right-shift by 4: Block >> 4). We divide by 16 because every chunk is exactly 16 blocks wide by 16 blocks long. For example, block coordinate X = 350 divided by 16 is 21.875, which floors down to Chunk X = 21. Pay close attention to negative numbers: block coordinate Z = -350 divided by 16 is -21.875, which must round down (further away from zero) to Chunk Z = -22.

    Tip: In bitwise math, right-shifting a negative number by 4 (such as -350 >> 4) automatically applies floor rounding, giving you -22 without needing extra steps.

  3. 3Calculate the Region (.mca) File Name from Chunk Coordinates

    Next, take your chunk X and Z coordinates, divide each by 32, and again round down to the nearest integer (a bitwise right-shift by 5: Chunk >> 5). We divide by 32 because every region file groups together a 32x32 grid of chunks, which equals a 512x512 block area (16 times 32 equals 512). Continuing our example, Chunk X = 21 divided by 32 is 0.656, which floors to Region X = 0, while Chunk Z = -22 divided by 32 is -0.6875, which floors to Region Z = -1. Your target blocks are therefore saved inside the file named r.0.-1.mca.

    Tip: You can skip the chunk step entirely by dividing your original block coordinates by 512 and flooring the result (or bit-shifting right by 9: Block >> 9).

  4. 4Locate the Dimension Folder on Disk

    Before modifying or inspecting any files, make a complete duplicate backup of your world folder so you never risk permanent data loss. Open your world save directory and navigate to the appropriate subfolder based on which dimension your coordinates came from. Overworld regions are stored directly in the 'region' folder, Nether regions are inside 'DIM-1/region', and The End regions are inside 'DIM1/region'. Inside, you will find your calculated r.X.Z.mca file alongside matching data files inside the sibling 'entities' and 'poi' folders.

  5. 5Verify and Manage Regions Visually with the Chunk Trimmer

    Instead of doing the math manually for dozens of areas, open our Chunk Trimmer tool in your browser. Click 'Open world folder or .zip', select your world, and choose your target dimension to load the 2D map right on your device (your files are processed locally in your browser and never upload to any server). Hover your cursor over the rendered map grid to see the exact block coordinates, chunk coordinates, and r.X.Z.mca file name simultaneously. From here, you can safely select specific chunks or entire 512x512 regions to keep or prune, then download your updated world.

How it works

Minecraft Java Edition uses the Anvil storage format (.mca) to prevent worlds from generating millions of tiny individual chunk files on your hard drive, which would severely slow down operating system file lookups. By grouping 16x16 block chunks into 32x32 chunk region files, a single .mca file cleanly encapsulates 1,024 chunks, or an area of 512x512 blocks from the bottom of the world to the build height limit.

The game engine relies on power-of-two sizes (16 is 2 to the 4th power, 32 is 2 to the 5th power, and 512 is 2 to the 9th power) so the CPU can use ultra-fast bitwise shift operations instead of slow division. When calculating where a block resides in memory, shifting a binary integer right by 4 bits (>> 4) instantly yields the chunk coordinate, and shifting right by 9 bits (>> 9) yields the region coordinate. Because two's complement binary shifts naturally round toward negative infinity (flooring), region r.0.0.mca spans from block 0 to 511, while r.-1.-1.mca spans from block -512 to -1.

Internally, each r.X.Z.mca file begins with an 8-kilobyte header split into two 4KB tables: chunk offsets and timestamps. To find where a specific chunk is stored inside that file, Minecraft calculates the chunk's local coordinate within the region using a bitwise AND operation (Chunk_X & 31 and Chunk_Z & 31, which always results in a number from 0 to 31). The engine then finds the header index using the formula ((Chunk_X & 31) + (Chunk_Z & 31) * 32) * 4, telling it the exact byte offset where that chunk's compressed NBT data begins.

Common mistakes

  • Rounding negative numbers toward zero instead of flooring them: Standard division of -10 by 512 is -0.019, and many people round that to 0. However, r.0.0.mca only holds positive coordinates (0 to 511); block -10 actually lives in r.-1.X.mca because you must always round down toward negative infinity.
  • Using the Y coordinate in your file calculation: In standard Java Edition, chunks span the entire vertical height of the world (for example, Y -64 to 319 in modern versions), meaning the Y coordinate has zero effect on which .mca file is used.
  • Forgetting to translate Nether coordinates: Although the Nether has an 8:1 travel ratio with the Overworld, its region files still use the exact coordinates shown on your F3 screen while standing in the Nether—do not multiply or divide by 8 when looking up files inside the DIM-1/region folder.
  • Deleting a file in the 'region' folder while leaving its counterparts in 'entities' and 'poi': Since Minecraft 1.17, mob entities and villager Points of Interest are stored in separate folders using the exact same r.X.Z.mca naming scheme. If you manually delete a terrain region file to reset an area, you should also remove the matching file in 'entities' and 'poi' (or use our Chunk Trimmer, which handles them together) to prevent orphaned mobs or ghost villager job sites.

FAQ

Why does region r.-1.-1.mca start at block -1 instead of -512?

Because region r.0.0.mca claims block 0 through block 511 (which is exactly 512 blocks). Consequently, the very first negative block (-1) must belong to the adjacent negative region, meaning r.-1.-1.mca covers blocks -1 through -512.

How can I find a chunk's local position inside an .mca file?

Take the global chunk coordinate and find the positive remainder when divided by 32 (in code, Chunk & 31). For example, global Chunk X = -22 gives a local region coordinate of 10 (since -22 + 32 = 10), meaning it sits in column 10 of that region's 32x32 internal grid.

What are the .mcc files I sometimes see next to .mca files?

If a single chunk becomes extraordinarily large (exceeding roughly 1 megabyte of compressed data due to massive amounts of NBT data like written books or chests), Minecraft saves that oversized chunk into an external file named c.ChunkX.ChunkZ.mcc to prevent breaking the .mca internal sector limit.

Is it safe to open my world in the browser Chunk Trimmer?

Yes, completely safe and private. Our tools run 100% locally inside your web browser using JavaScript, meaning your world files are read directly from your disk and are never uploaded over the internet. Still, always keep a backup copy of your world before saving changes.

By dividing your in-game X and Z block coordinates by 16 (and flooring) to get chunk coordinates, and by 512 (and flooring) to get region coordinates, you can accurately locate any r.X.Z.mca file on disk or manage them visually in your browser using our Chunk Trimmer.

More chunks & world size guides

Chunks & world sizeWhy You Must Clean entities and poi Folders When Deleting Region ChunksWhen resetting terrain in a Minecraft Java Edition world, simply deleting terrain files from the `region` folder is no longer safe in modern versions (1.17+). Minecraft now separates block data, entity data, and villager points of interest across three distinct folders that must be modified together. This guide explains why these files must stay synchronized and how to use our Chunk Trimmer to prune them safely without causing ghost villagers or orphaned mobs.JavaIntermediate4 steps
Chunks & world sizeHow to Delete Specific Chunks so New Game Updates Generate Fresh TerrainWhen a major Minecraft update releases, new biomes, ores, and structures will only appear in areas of your world that you have never visited before. Instead of traveling thousands of blocks away from your home, you can delete the surrounding explored chunks that you haven't built in. When you walk back into those deleted areas in the latest version, the game will seamlessly generate brand-new update terrain right outside your base.Java & BedrockBeginner5 steps
Chunks & world sizeHow to Fix Harsh Chunk Borders and Wrong Biomes After Version UpgradesUpgrading a Minecraft world to a major new version often leaves ugly, sheer cliffs or sudden biome shifts where old terrain meets newly generated chunks. While modern versions of the game include automatic terrain blending, it only works where old chunks directly meet completely ungenerated space. By using our browser-based Chunk Trimmer to prune unbuilt outer chunks, you can force the game to regenerate those borders smoothly without ever uploading your private world files to a server.Java & BedrockIntermediate5 steps
Chunks & world sizeHow to Regenerate a Single Ruined or Griefed Chunk Back to Natural TerrainDealing with a huge crater, lag machine, or griefed landscape right next to your base can feel frustrating, especially if you don't want to restore an old backup and lose recent build progress. Fortunately, Minecraft builds and saves worlds in individual 16x16 vertical columns called chunks. By deleting the data for just the ruined chunk using our browser-based tool, you can force the game to cleanly rebuild that specific square of natural terrain from your world seed.Java & BedrockBeginner4 steps
Chunks & world sizeHow to Reduce World File Size by Trimming Low-InhabitedTime ChunksOver time, Minecraft Java Edition worlds can balloon into gigabytes of data just from players flying across the terrain in search of structures or biomes. By using the browser-based Chunk Trimmer tool, you can safely delete chunks players merely passed through while preserving every single block where someone stopped to build. Because this tool processes everything locally in your browser, your large world files never have to be uploaded to a server.JavaIntermediate5 steps