Historical interpretive map of the Battle of Plataea in 479 BC

Plataea 479 BC: The Battle That Ended the Persian Invasion

Iron Standard — Update 2 · 7 September 2026. Plataea is often described as the inevitable land victory that completed what Salamis began. Herodotus gives us a much messier battle: cavalry pressure, a damaged water supply, disputed coalition command, a night withdrawal that went wrong and separated contingents, then a Persian pursuit that converted apparent Greek retreat into close combat. This revision treats that disorder as the centre of the investigation rather than smoothing it into a perfect Spartan plan.

The Regimental Record · Ancient World · Persian Wars · Battlefield Investigation · 479 BC

Part of the Persian Wars 480–479 BC campaign series →

Plataea broke the principal Persian field army remaining in mainland Greece. It was not simply “heavy hoplites beat lightly armed Persians.” Before the decisive fighting, Persian cavalry had created exactly the sort of operational pressure Mardonius wanted: Greek supply routes and water access were compromised, and the coalition was forced to move.

The Iron Standard question

Was Plataea a planned Greek tactical victory—or did the coalition survive a failed withdrawal long enough for Mardonius to mistake disorder for collapse and pursue onto less favourable terms?

Our current judgement is that the decisive battle was recovered rather than perfectly planned. Persian pressure forced a Greek movement that fragmented. Mardonius then made a rational but costly inference: that the fragmentation meant the enemy was fleeing and could be finished. Once substantial Persian forces pressed forward and Greek heavy infantry held together locally, the character of the battle changed.

Historical map of the Battle of Plataea in 479 BC
A later reconstruction, not a contemporary staff map. Jean-Denis Barbié du Bocage, eighteenth century; useful for orientation but incapable of proving exact ancient deployments. Public domain.

Source genealogy

Herodotus, Book IX, is the essential narrative for diplomacy, contingent lists, manoeuvres, the water crisis, the failed night movement and the final fighting. He wrote decades later, preserved civic traditions and composed speeches and moral scenes.

Plutarch gives later biographical traditions, especially around Aristides and Pausanias. He wrote centuries after the battle and frequently shaped history around character and moral judgement.

Battlefield topography can test whether the broad operational problem—river, foothills, routes through Cithaeron and access to water—is plausible. It cannot independently verify the exact position of every contingent or every speech.

As at Salamis, there is no surviving Persian operational account equal to Herodotus’ detail. Claims about Mardonius’ private motive therefore require particular caution.

Plataea at a glance

Date 479 BC; precise modern-calendar dating remains uncertain
Location Boeotia between the Asopus, Plataea and the approaches to Mount Cithaeron
Greek command Pausanias, Spartan regent, with contingents retaining their own political and military leadership
Persian command Mardonius, with imperial contingents and allied Greek forces
Greek numbers Herodotus’ contingent list is valuable, but the exact total including light troops is disputed
Persian numbers The literary totals are not secure modern strength returns; the army was large, multinational and cavalry-rich
Result Decisive coalition victory; Mardonius killed and the principal Persian field position destroyed

After Salamis: Persia still had a strategy

Xerxes’ withdrawal after Salamis did not end the invasion. Mardonius retained a selected land force and spent the winter farther north. In 479 he tried to split the coalition politically, including offers intended to detach Athens from the Peloponnesian alliance.

Athens refused, but unity was not automatic. The Athenians needed a major coalition army to move north while Sparta had powerful reasons to think first about the Isthmus. The final mobilisation therefore represents a political achievement as well as a military one.

The battlefield problem: cavalry, water and supply

The Greeks preferred broken and higher ground near Cithaeron, where Persian cavalry had less freedom. Mardonius had no reason to attack a strong coalition position simply because later histories wanted a decisive battle.

Instead, cavalry pressure attacked the operational system around the army. Convoys crossing mountain routes were vulnerable. The Gargaphian spring became increasingly difficult to use. An army with water and supply problems eventually has to move even if its infantry line remains intact.

Iron Regiment confidence call: Persian cavalry pressure was a principal reason the Greek position became untenable — high confidence. The exact sequence and location of every watercourse described by Herodotus — lower confidence, because ancient hydrology and place identification are difficult to reconstruct precisely.

The night withdrawal: where the clean victory narrative breaks

The coalition planned to move towards more sustainable ground. The operation did not unfold cleanly. Central contingents moved farther than intended. Spartans and Tegeans remained behind amid a dispute associated by Herodotus with the Spartan officer Amompharetus. Athenians took another route.

By dawn the coalition line was fragmented. That is not what a commander would normally design before a decisive battle.

The important point is not to mock Pausanias. Night movement by a large coalition without modern communications was inherently difficult. The failure shows the limits of command and control even in the victorious army.

Why Mardonius attacked

From the Persian side, the evidence could look highly favourable. Days of cavalry pressure had finally forced the Greeks to move. Their line was visibly broken and contingents appeared to be retreating. A rapid attack could destroy them before they re-formed.

Calling that decision simple “rashness” relies heavily on hindsight. The deeper mistake was assuming that disordered movement meant lost fighting cohesion. The Spartans, Tegeans and Athenians were separated, but they were not all running helplessly.

The decisive fighting

1. Persian forces cross towards the apparent retreat

Mardonius advanced with the Persian core while other contingents followed with varying order. The pursuit reduced some of the advantages of the earlier defensive and cavalry-based position.

2. Missile pressure continues

Herodotus describes Persian archery from behind shield barriers while Spartans and Tegeans waited. His account also gives Pausanias a dramatic religious appeal before the advance. The religious scene reflects Greek understanding of legitimate action as well as the strain of enduring missiles.

3. Greek heavy infantry closes

Once close combat developed, large shields, long thrusting spears and armour gave Greek hoplites important advantages. This should not be turned into a racial or civilizational law. Persian infantry had been effective across an enormous empire and fought hard at Plataea. The tactical mismatch became acute in this particular close engagement after cavalry and manoeuvre had ceased to dominate.

4. Mardonius is killed

The commander’s death was a major shock at the point of crisis. Herodotus attributes the killing to a Spartan named Aeimnestus. The exact individual story is difficult to verify independently; the broader collapse following Mardonius’ death is central to the narrative.

5. Athenians fight Greek allies of Persia

On another sector Athenians fought Theban and other Greek forces aligned with Persia. Plataea therefore exposes the civil dimension of the war: this was never every Greek community united against an external invader.

6. The Persian camp falls

Survivors withdrew to fortified positions. Coalition forces eventually broke into the camp, transforming field defeat into strategic disaster for the remaining principal army.

Evidence audit

Claim Assessment Confidence
Persian cavalry and supply pressure forced the Greeks to reconsider their position Central to Herodotus’ sequence and operationally coherent High
The Greek night movement proceeded according to plan Contradicted by Herodotus’ account of separation and confusion Very low
Mardonius attacked because he saw apparent Greek retreat Strong narrative support; exact private reasoning cannot be independently audited Medium-high
Greek heavy infantry had an advantage once close combat was established Consistent with equipment, formation and battle narrative High
Persian troops were simply inferior fighters Unsupported civilizational caricature Very low
Herodotus’ largest manpower totals are precise audited figures Ancient literary numbers with major logistical and evidential problems Low
Mardonius’ death accelerated Persian collapse Strong ancient narrative support High
Plataea ended the Persian Empire’s role in Greek affairs False; Persian political and military influence continued for generations Very low

Competing explanations

The hoplite explanation emphasizes armour, large shields and spear fighting. It explains the decisive close-combat phase but not why the Persians allowed the battle to reach that form.

The pursuit explanation gives Mardonius’ interpretation of the withdrawal greater weight: apparent Greek collapse drew Persian forces forward and reduced the value of cavalry, missile depth and a prepared position.

The coalition-resilience explanation stresses that separated contingents retained enough local cohesion to fight despite a failed movement.

The cavalry-logistics explanation reminds us that Persia was strategically successful before the final engagement: its horsemen had forced the Greeks to abandon an increasingly unsustainable position.

The command-shock explanation gives Mardonius’ death a major role in turning tactical reverse into wider collapse.

Iron Regiment’s current judgement: Plataea was not a flawless Greek plan. Persian cavalry created the crisis; the coalition’s withdrawal then failed; Mardonius tried to exploit what looked like flight. The Greeks won because disorder did not become dissolution and because the ensuing close fight favoured their heavy infantry. Victory was recovery under pressure, not inevitability.

What would change our mind?

  • Battlefield archaeology securely fixing large parts of the clash in locations that materially alter the accepted movement sequence.
  • Palaeohydrological work changing reconstruction of the Gargaphian spring, the “Island” or other water features enough to alter the logistics argument.
  • Persian administrative or military evidence describing Mardonius’ orders, strength or perception of the Greek movement.
  • New inscriptions materially revising coalition contingents or command relationships.

What Plataea did—and did not—mean

The battle ended the immediate large-scale Persian attempt to conquer mainland Greece. It did not destroy the Achaemenid Empire. Persia remained a great power and later shaped Greek politics through diplomacy, subsidies and intervention.

Nor did victory create permanent Greek unity. The coalition’s political contradictions survived the battle and soon reappeared in conflicts among the victors.

Continue the campaign

Sources and further reading

  • Herodotus, Histories, Book IX — Perseus Digital Library.
  • Plutarch, Life of Aristides. Later biographical tradition, used with caution.
  • J. F. Lazenby, The Defence of Greece 490–479 BC.
  • Peter Green, The Greco-Persian Wars.
  • George Cawkwell, The Greek Wars.
  • William Shepherd, Plataea 479 BC.

Revision record

Iron Standard Update 2 — 7 September 2026. Rebuilt the article around the failed Greek night movement and Mardonius’ decision to pursue; separated operational success before the battle from the close-combat outcome; challenged “inevitable hoplite superiority” and literal ancient numbers; added source genealogy, confidence grading, competing explanations and falsifiability; preserved the existing map and URL.


Shop the history

There is no forced Plataea product link. Explore the Ancient World collection or Historic Battles.

History first. Clothing second.

Back to blog