Which biomes generate villages
Villages are tied to a short, specific list of biomes, and the exact list depends on your edition. The reference lists 6 biomes that generate a village in Java Edition: plains, savanna, taiga, meadow, snowy plains and desert. Bedrock Edition adds two more — snowy taiga and sunflower plains — bringing its total to 8. The familiar figure of "seven biomes" is a widely repeated shorthand rather than an exact count: the source's own list gives 6 for Java and 8 for Bedrock, and the usual "seven" simply leaves snowy taiga out. Forests, jungles, swamps, mountains and oceans never generate a village of their own.
The biome also decides the village's style — the wood, the paths and the shapes of the buildings. A meadow and a sunflower plain both build in the plains style, and snowy taiga builds in the taiga style. The style is set by the biome at the village's centre, so if that point falls outside a village biome the whole settlement falls back to the plains style.
Village styles by biome
The style a village builds in, and the biomes that produce it. The "Bedrock only" rows do not generate a village in Java Edition at all.
| Village style | Biomes it generates in | Edition |
|---|---|---|
| Plains | plains, meadow | Java + Bedrock |
| Plains | sunflower plains | Bedrock only |
| Desert | desert | Java + Bedrock |
| Savanna | savanna | Java + Bedrock |
| Taiga | taiga | Java + Bedrock |
| Taiga | snowy taiga, taiga hills, snowy taiga hills | Bedrock only |
| Snowy | snowy plains | Java + Bedrock |
A village is defined by beds, not by buildings
Here is the rule that explains almost every village bug. A village has no fixed centre, size or radius — it exists only while villagers are linked to "points of interest". A subchunk (a 16×16×16 section of the world) counts as a village centre if it contains at least one claimed bed, bell or job-site block, and the 26 subchunks around it — a 3×3×3 cube, 27 in total — are pulled in as part of the same village.
Two consequences follow. First, the maximum population of a village is simply its number of valid beds: remove beds and the ceiling drops with them. Second, a village is created the moment the first villager links to the first bed, and it ceases to exist when the last bed link is broken — by the bed being destroyed, by a player sleeping in it, or by a villager failing to pathfind to it. When that happens, every villager loses its job-site and bell links and the settlement stops behaving like a village at all.
When the first villager links to a bed, the game creates a working boundary of 65×25×65 blocks centred on that bed's pillow, and it is that boundary — not the buildings — that decides where cats and iron golems can spawn. As more villagers link and unlink, the boundary and its centre shift, which is why a village's "centre" can drift over time and why the well or bell you remember is not always where the game thinks the middle is.
The fastest way to find one: /locate
If commands are available, stop walking. In Java Edition, /locate structure #village prints the coordinates of the nearest village of any style; Bedrock Edition uses /locate structure village instead. Both need permission level 2, and Bedrock additionally requires cheats to be on. Java players can also run /locate poi #village to jump to the nearest villager point of interest — that search is a sphere with a 256-block radius, and a stray bed, bell or workstation is often closer to you than the village structure itself.
No commands? The cartographer's explorer map is the in-game equivalent — the reference describes villages as locatable with the explorer maps cartographers sell, and the style shown depends on the biome the villagers came from. Beyond that, finding a village by hand is really a matter of covering new ground efficiently, which is the part most players get wrong.
Exploration that actually finds villages
Villages only generate alongside new chunks. The reference is explicit that they do not generate in existing chunks, so re-walking your home area will never produce one — you have to push into terrain the game has not generated yet. That single fact turns "explore randomly" into a strategy:
- Walk straight lines. Pick one axis and travel it. You cover new chunks at a steady rate and can retrace your route exactly; wandering in circles keeps reloading ground you have already searched.
- Follow the water. A boat is the fastest way to scan a long coastline, and villages often sit on the gentle ground near river mouths and ocean shores.
- Scan from height at dawn. Climb the highest hill and look for boxy silhouettes and the regular rectangles of farm plots. Villages prefer flatter terrain, so open lowlands between hills are the highest-probability band.
- Read the paths. Villages lay paths between their buildings — grass and dirt paths in plains, savanna, taiga and snowy villages, smooth sandstone paths in the desert. A straight strip of path you did not build is a strong signal.
- Watch for surface oddities. A building generated over the ocean sits on a flat platform of grass or sand; a savanna village on a mountain can be split across the slope with houses both on top and at the bottom. Both are visible from a distance, before you see a single villager.
Three worked examples
Example 1 — beds decide population and cats. A village with 12 valid beds has a maximum population of 12 villagers, and cats spawn at one per 4 beds: 12 ÷ 4 = 3 cats. Raise it to 24 beds and the population ceiling becomes 24, while the cat count hits the cap — 24 ÷ 4 = 6, so the game serves only 5. The cap is reached at 20 beds; any more beds past that add villagers but no cats.
Example 2 — how big the boundary really is. The 65×25×65 boundary has a horizontal footprint of 65 × 65 = 4,225 blocks. At 16×16 = 256 blocks per chunk that is about 16.5 chunk-equivalents of surface. Because a 65-block span rarely lines up with chunk borders, it can touch up to 25 chunks (5×5) — which is why two "different villages" a short walk apart often turn out to be the same settlement.
Example 3 — the odds of a zombie siege. A siege has a 10% chance at midnight every night when a village holds at least 20 valid beds. Over 30 nights that is 0.1 × 30 = 3 sieges on average; over a full in-game year of 365 nights it is 0.1 × 365 = 36.5 sieges. At 20 beds you are always a candidate, so a wall and a few iron golems are not paranoia — they are arithmetic.
First-night value, and the etiquette that protects it
A found village is first-night gold: beds to sleep through the night, farms to harvest, hay bales to break into wheat, and villagers to trade with using emeralds. Iron golems patrol the streets, and cats spawn inside the village — one per 4 beds, up to five.
There is etiquette, and it is also mechanics. Replant every crop you harvest, because farms are the village's food source and its breeding depends on it. Do not sleep in a villager's bed — using a bed unlinks it, and if that was the last linked bed the village stops existing and the villagers lose their job-site links. And trade early: professions and prices lock in after a villager's first trade, so a Librarian you find on day one is worth more than the same villager on day thirty.
One warning about style. Some villages generate abandoned: every villager is a zombie villager, the doors and torches are missing, cobblestone turns to mossy cobblestone with cobwebs, and the glass is stained brown. Abandoned villages spawn stray cats and livestock but no iron golems, and baby zombie villagers there have a 5% chance to appear as chicken jockeys. Clear the zombies before you call it home.
Common mistakes when village hunting
- Re-walking explored ground. Villages do not generate in existing chunks. If you have already loaded an area, it will never contain a village — travel outward.
- Wandering instead of running an axis. A straight line covers new chunks predictably; circling mostly re-loads the same ones and hides the direction you have yet to search.
- Sleeping in a villager's bed. It unlinks the bed. Break enough links and the village ceases to exist, taking every job-site link with it.
- Counting buildings instead of beds. The population ceiling is the number of valid beds, not the number of houses. A big-looking settlement with three beds supports three villagers.
- Harvesting farms without replanting. You starve the food supply that drives breeding, and the village stops growing just when you wanted more villagers.
- Assuming "seven biomes" is a Java number. Java is 6, not seven; the extra biomes — snowy taiga and sunflower plains — are Bedrock-only. Searching a Java world for a snowy taiga or sunflower plains village means hunting a biome that cannot hold one.
Sources and standards
Where these figures come from
Every rule on this page is taken from the published reference material below rather than from memory. The village biome list, the bed-and-subchunk definition of a village centre, the 65×25×65 boundary, the cat and siege rules and the location commands were checked against the source, and each worked example is reproduced by the script that built this page.
- Minecraft Help Center — official Mojang/Microsoft support documentation for game mechanics.
- Minecraft (official site) — the game of record for mechanics, versions and release notes.
Figures, formulas and reference tables last verified: 7 October 2026.