Castles

Medieval Castles: Fortresses of Power

How kings and lords used castles to hold land, collect revenue, dispense justice and keep local people in check, making each one a seat of lordship as well as a fort.

On this page
  1. More than a place to hide
  2. A base for holding land
  3. The center of local government
  4. Controlling roads, rivers and passes
  5. Rewards, obligations and loyalty
  6. Living with a castle nearby
  7. Limits of the castle

More than a place to hide

It is tempting to see a castle as a refuge for when things went wrong. In practice, most of its working life was spent not under siege but doing something quieter: acting as the base from which a lord governed a district. The best way to understand a castle’s power is to treat it as a seat of lordship, a place where authority was stored, exercised and made visible.

This article looks at the castle as a tool of control. Its defensive features are covered elsewhere, and so are its symbolic and status roles. The question here is what a castle did for the person who held it.

A base for holding land

When a ruler took new territory, a castle was commonly among the first things built. After 1066, the Normans raised castles across England, often at towns and river crossings, to secure the lands they had been granted. The Norman settlement of England relied heavily on small garrisons in strong points, which could not be easily removed and could respond to local rebellion. The Domesday survey of 1086 even records places where houses were cleared to make room for castles, a reminder that the people living nearby bore the cost.

The same pattern appeared at other frontiers of expansion, including Wales, Ireland and parts of the Levant and Iberia. A small group of armed men, behind walls and supplied from the surrounding estates, could dominate a much larger population. Castles also made it easier to hold a district through a bad year, since a garrison could simply wait out unrest.

The center of local government

A castle was usually tied to an estate or a district, and its owner collected income from it. Rents, dues and produce came into the castle, and records of those payments were kept there. The lord’s court, where disputes over land, debts and offenses were heard, met in the hall or nearby. In many places, a castle held the prison, and the sheriff or constable who oversaw it enforced the ruler’s justice.

For a king, a network of royal castles meant that orders could be carried out far from the court. Officials called constables or castellans managed them, and the crown could appoint and remove these men, which meant control stayed with the ruler. The reach of the English crown, for example, partly depended on royal castles and the sheriffs who held them. This links to wider questions of royal administration, but the castle itself was the physical anchor.

Controlling roads, rivers and passes

Location mattered. Many castles stood where they could oversee a road, a ford, a bridge, a harbor or a river valley. A garrison there could watch traffic, collect tolls where lords had the right, and block or harass an enemy army. A strong point did not need to stop an army entirely to be useful; if an invader could not safely leave it behind, he had to stop and besiege it, and that cost time and supplies.

Control of a few key castles could therefore decide control of a whole region. Medieval campaigns were often a sequence of sieges rather than open battles, and rulers frequently preferred to take castles than to risk a pitched fight. This helps explain why the Edwardian castles in Wales were placed along the coast, where they could be supplied by sea and used to hold down a newly conquered land.

Rewards, obligations and loyalty

Castles also sat within a web of obligations. A lord might grant land to a follower on condition of service, and sometimes that service included castle guard, a period of duty in the garrison. Holding a castle on behalf of a king was both an honor and a responsibility. A trusted baron could receive one as a reward, and the king could take it back if loyalty failed.

This explains why rulers were wary of private castles. In England, kings in the 12th and 13th centuries increasingly expected permission to fortify a house, issuing what came to be called a license to crenellate. The aim was partly to control who could build strongholds. During periods of weak royal power, a surplus of unauthorized castles could encourage local lords to defy the crown, though how widespread they were is debated by historians.

Living with a castle nearby

For ordinary people, a castle could mean protection, employment and trade. Villagers might shelter within the walls in time of raiding, supply the garrison with food and work as laborers or servants. Markets often grew up near the gate. Yet the same building was also a reminder of who held power: taxes were collected there, and its soldiers might demand lodging or supplies. Reactions varied, and local views would have depended on how a particular lord behaved.

Limits of the castle

Castles were not all-powerful. They were expensive to build and maintain, they needed regular repair, and a garrison that was unpaid or underfed could become a liability. A lord who relied on his castle but lost the support of his people or his own household could find it empty of use. Castles could also be seized by rebels, and a stronghold in the wrong hands worked against its builder.

The real source of lordship was people and land, with the castle as a tool for holding both. Understood this way, a castle looks less like a lonely fortress and more like the office, courtroom and strongbox of medieval rule, all behind defensible walls.

The complete guide to castles

Medieval Castles: Architecture and Defense in the Middle Ages
Read the guide

Keep exploring

Guides from other topics

All topics →