Skip to content
THE AGE OF ROMEHistory, brought closer
52 BC · Gaul · The Roman siege lines

The Siege of Alesia: Caesar’s army between two enemies

Julius Caesar defeated Vercingetorix at Alesia in Gaul in 52 BC by maintaining a blockade while repelling a Gallic relief army. Roman siege works faced inward toward the trapped defenders and outward toward the approaching reinforcements. After coordinated attacks failed, Vercingetorix surrendered. The victory broke a major Gallic coalition, but further resistance followed, and the cost included starvation, captivity and enslavement.

Watch & listen Read the history

A narrated episode with an illustrated historical guide and sources.

Dramatized view across Caesar’s siege works at Alesia.
Dramatized illustration · Caesar: The Siege of Alesia
A moment in the Roman world

Watch. Listen. Look closer.

A short introduction, then the history and its sources below.

2:30 · Episode film

AI-generated historical dramatization. Open the film page

The narrated history

Hear the story.

0:41 · Narration

Read the transcript

Gaul, 52 BC. Vercingetorix holds Alesia while Julius Caesar surrounds the hilltop stronghold. Roman soldiers build one line of defences facing the trapped Gauls and another facing the relief army gathering outside. Food runs short within the town. Then attacks strike from both directions, testing the Roman lines at once. Caesar's forces hold, and the relief army withdraws. Vercingetorix surrenders. Captivity and enslavement follow for many of the defeated. Alesia breaks a major coalition against Rome and strengthens Caesar's position, while further resistance continues across Gaul.

Sources and context

The historical guide below follows the people, events and surviving accounts behind this episode. Explore the sources.

The event at a glance

The essentials.

Date
52 BC, during Caesar’s campaigns in Gaul
Location
Mont Auxois at Alise-Sainte-Reine, Burgundy, modern France
Commanders
Julius Caesar and his lieutenants against Vercingetorix and a Gallic relief coalition
Tactical problem
A blockade defended simultaneously against attacks from inside and outside
Result
Roman victory and Vercingetorix’s surrender; later fighting continued in Gaul
01

Why Vercingetorix resisted Rome

Caesar had campaigned in Gaul since 58 BC, intervening in local rivalries and extending Roman control through warfare, alliances and coercion. Vercingetorix, an Arvernian leader, helped bring several Gallic peoples into a coalition in 52 BC. These were distinct communities with their own leaders and interests, not a single modern nation with a uniform command structure.

The campaign was not an uninterrupted procession of Roman victories. Caesar captured Avaricum after a siege, but failed at Gergovia. Vercingetorix tried to use cavalry, attacks on supplies and the destruction of resources to weaken the Roman army. After a later cavalry reverse, he withdrew to the defensible hilltop settlement of Alesia, occupied by the Mandubii.

Evidence: Caesar · Gallic War 7.15–33 · Caesar · Gallic War 7.34–52 · Caesar · Gallic War 7.63–74

02

Where was Alesia? What archaeology establishes

Alesia is identified with Mont Auxois at Alise-Sainte-Reine in Burgundy. Excavations have found Roman siege works, weapons, coins and military equipment. The site’s museum describes nineteenth-century excavations and later investigations that support the identification. Alternative locations have been proposed, but Alise-Sainte-Reine is the accepted archaeological location.

The hilltop, nearby streams, open plain and surrounding heights explain the siege’s shape. Caesar judged a direct storming difficult and chose to cut the defenders off. Archaeology supports the presence of a large Roman siege here; it does not independently verify every number, speech or dramatic moment in Caesar’s narrative.

Evidence: MuséoParc Alésia · Archaeology of the site · MuséoParc Alésia · History of the site · Caesar · Gallic War 7.63–74

03

How Caesar’s two lines of fortifications worked

The first line faced Alesia to prevent escape and block supplies. Caesar then created an outer system facing the expected relief army. Between them his troops occupied a defended zone of camps, forts and connecting works. In practical terms the sequence was: town and besieged army; inward-facing Roman defences; Roman positions; outward-facing defences; relief forces beyond.

These were not two smooth stone walls. Caesar describes ditches, an earthen rampart with a palisade, towers and fields of concealed or exposed obstacles. He gives circuit lengths of eleven and fourteen Roman miles, roughly sixteen and twenty-one kilometres. Those figures come from his account; the works followed the landscape rather than making perfect concentric circles.

Evidence: Caesar · Gallic War 7.63–74

04

The siege was a contest over food and time

Vercingetorix sent his cavalry out before the enclosure was completed, instructing them to obtain relief from their communities. He centralized and rationed food inside Alesia. Caesar also had a supply problem: soldiers building and guarding an extensive perimeter had to collect timber and provisions while defending against sorties. Obstacles helped compensate for the difficulty of manning every part of the works.

When supplies dwindled, the Mandubian population was expelled from the stronghold. Caesar records that people approached the Roman works begging for food and offering themselves as slaves, but he refused to admit them. His text does not provide a complete individual account of their fate. It does show civilians trapped between the military decisions of both sides.

Evidence: Caesar · Gallic War 7.63–74 · Caesar · Gallic War 7.75–90

05

The relief army and the first attempts to break through

The relief coalition included commanders such as Commius, Vercassivellaunus, Eporedorix and Viridomarus. Caesar assigns enormous numbers to it, figures that cannot be verified and should not become precise modern force counts. Its arrival changed the blockade into a battle on two fronts, with defenders inside Alesia trying to coordinate with forces outside.

An initial cavalry battle ended in a Roman success, with Caesar highlighting his German horsemen. A subsequent night attack used prepared hurdles and ladders against the outer works, while Vercingetorix attempted a sortie. Darkness, obstacles and delays limited coordination. Roman lieutenants shifted troops from quieter positions to threatened sectors, showing why the connected defensive system mattered.

Evidence: Caesar · Gallic War 7.75–90

06

How Caesar won the final battle

The relief commanders identified a vulnerable northern sector where the ground made the Roman position difficult. Vercassivellaunus led a selected force against it while attacks elsewhere prevented the Romans from concentrating freely. Vercingetorix advanced from inside at the same time. Caesar’s narrative describes defenders worn down as attackers filled obstacles and pressed the rampart.

Caesar moved reinforcements and sent Labienus to the threatened sector, then joined the action with further troops. Cavalry sent around the outside struck the attackers from behind. The attack collapsed and the relief army withdrew. The result depended on works, reserves, local command and cavalry together; describing it simply as a wall defeating a larger army misses the active fighting.

Evidence: Caesar · Gallic War 7.75–90

07

Vercingetorix’s surrender and the captives

The next day, according to Caesar, Vercingetorix placed his fate before the Gallic council, after which leaders were handed over and weapons surrendered. Caesar’s own description is brief. Plutarch’s much later account adds the famous theatrical scene of Vercingetorix arriving in splendid armour and placing himself at Caesar’s feet. That image should be attributed to its source rather than presented as securely witnessed detail.

Caesar held Vercingetorix captive and distributed many other prisoners as spoil, while treating selected groups differently for political reasons. Vercingetorix later appeared in Caesar’s triumph and was executed. Victory therefore meant more than the ending of a battlefield engagement: it placed human beings at the conqueror’s disposal.

Evidence: Caesar · Gallic War 7.75–90 · Plutarch · Life of Caesar 27 · Cassius Dio · Roman History 43.19

08

Did Alesia end the Gallic Wars?

Alesia shattered the coalition around Vercingetorix, but resistance did not disappear immediately. The continuation of the Gallic War, written by Aulus Hirtius, describes further campaigns in 51 BC, including Uxellodunum. Treating Alesia as the last violence of the conquest erases both later fighting and the ongoing effects of Roman rule.

The victory strengthened Caesar’s military reputation and political resources. It did not give him the title of emperor or make civil war automatic. Disputes over his command and future office continued until he crossed into Italy in 49 BC. The next political stage was Caesar’s return to Rome, followed by the conflict that produced Pharsalus and eventually dictatorship for life.

Evidence: Aulus Hirtius · Gallic War 8.1–48 · Caesar · Gallic War 7.75–90 · Caesar · Civil War 1.1–11

09

How reliable is Caesar’s account?

Caesar is indispensable because he commanded the Roman army and provides the fullest surviving sequence. He is also explaining and justifying his own success. His praise of Roman endurance, enormous enemy totals and presentation of personal leadership need to be read alongside his political interests.

The most responsible reconstruction distinguishes levels of confidence. A major siege at Alise-Sainte-Reine, extensive Roman works and the defeat of Vercingetorix are well supported. Exact force strengths, private motives and the literal wording of speeches are much less secure. The human consequences can be acknowledged without inventing eyewitness scenes for people whose accounts have not survived.

Evidence: Caesar · Gallic War 7.63–74 · Caesar · Gallic War 7.75–90 · MuséoParc Alésia · Archaeology of the site

Follow the sequence

Timeline

  1. Early 52 BC

    Vercingetorix helps organize a broad revolt against Roman power in Gaul.

  2. Earlier in 52 BC

    Caesar captures Avaricum but suffers a reverse at Gergovia.

  3. Before the siege

    A Gallic cavalry defeat is followed by Vercingetorix’s withdrawal to Alesia.

  4. Siege preparations

    Roman troops surround the hilltop position; Vercingetorix sends cavalry to seek reinforcements.

  5. The double blockade

    Caesar adds outward-facing defences and gathers supplies as a relief army assembles.

  6. Relief attempts

    A cavalry action and a night assault fail; a final coordinated attack threatens the northern sector.

  7. Surrender, 52 BC

    The relief army disperses and Vercingetorix is handed over.

  8. 51 BC and afterward

    Roman campaigns continue; Caesar’s growing power later contributes to the political crisis at Rome.

Understand the event

Questions people ask

Who won the Siege of Alesia?

Julius Caesar’s Roman army won in 52 BC. It held its siege works against a relief army and attacks from the besieged force, after which Vercingetorix surrendered.

Where is Alesia today?

The accepted site is Mont Auxois at Alise-Sainte-Reine in Burgundy, France. Excavated fortifications and military finds support the identification.

Why did Caesar build two walls?

He needed an inner defensive line to contain Alesia and an outer one to resist reinforcements. Both consisted of varied earthworks, palisades, ditches and obstacles rather than simple stone walls.

How many soldiers fought at Alesia?

Exact strengths are uncertain. Caesar’s very large totals for the Gallic armies cannot be independently verified, so they should be labelled as his claims rather than accepted counts.

What happened to Vercingetorix?

He surrendered and was held captive. Years later he was displayed in Caesar’s Roman triumph and executed.

Did Alesia make Caesar emperor?

No. It was a victory in Gaul in 52 BC. Caesar’s civil war began in 49 BC, and he became dictator for life in 44 BC. Augustus is conventionally regarded as Rome’s first emperor.

Did all resistance in Gaul end at Alesia?

No. Further campaigns followed, including Uxellodunum in 51 BC. Alesia was a major turning point rather than an immediate end to all fighting.

Read the evidence

Sources and perspective

Sources are identified beside the sections they support. Ancient and medieval authors wrote from particular positions; a detailed story can still be partisan, late or uncertain. Archaeology can test an account without confirming every detail.

  1. Caesar · Gallic War 7.15–33

    The campaign around Avaricum; Caesar’s account presents his military decisions defensively.

  2. Caesar · Gallic War 7.34–52

    The campaign at Gergovia and Roman reverse, described by the commander responsible.

  3. Caesar · Gallic War 7.63–74

    The retreat to Alesia, food arrangements and defensive works. Measurements and troop strengths are Caesar’s reports.

  4. Caesar · Gallic War 7.75–90

    The relief coalition, expelled civilians, attacks, surrender and treatment of captives, narrated by the victorious commander.

  5. MuséoParc Alésia · Archaeology of the site

    Museum overview of excavated siege works and finds. Archaeology supports the site identification but not every detail of the literary narrative.

  6. MuséoParc Alésia · History of the site

    The site museum’s account of the identification at Alise-Sainte-Reine and the history of excavation.

  7. Plutarch · Life of Caesar 27

    A later, more theatrical surrender narrative; the scene is not a contemporary eyewitness record.

  8. Cassius Dio · Roman History 43.19

    A later account of Vercingetorix’s execution following Caesar’s triumph, several years after Alesia.

  9. Aulus Hirtius · Gallic War 8.1–48

    The continuation demonstrates that campaigns followed Alesia; it was written by Caesar’s associate, not by Caesar himself.

  10. Caesar · Civil War 1.1–11

    Caesar’s partisan account of the later dispute over command and his advance into Italy.

Published . Updated . Research, authorship and corrections.

Report a historical correction
One more story, a little more perspective

Keep your place in history.

Reading progress stays in this browser, on this device.

Choose your next episode