The 1770 Bengal Famine: How a Company Optimised a Population Into Starvation

The Bengal famine 1770 is one of those events that history textbooks tend to file under “natural disaster,” as if the sky simply forgot to rain and millions of people happened to die. The rains did fail — that part is true. A weak monsoon in 1768 and a catastrophic drought in 1769 wrecked the rice harvest across a region that fed itself, and much of eastern India, on that harvest. But a crop failure is not the same thing as a famine. Bengal had endured droughts before and survived them. What turned scarcity into one of the deadliest famines in recorded history was not the weather. It was who was in charge of Bengal when the weather turned, and what that ruler had been built to do.

In 1770, Bengal was governed, in all but name, by a corporation. And a corporation, whatever else it is, is an engine built to extract value and return it to shareholders. When you put a machine like that in charge of a starving population, you do not get relief. You get optimisation — of the wrong thing.

How a trading company came to rule a country

To understand the famine you have to understand how a London merchant syndicate ended up holding the tax authority over thirty million people. After the Battle of Plassey in 1757 and the Battle of Buxar in 1764, the East India Company had gone from being a trading operation with warehouses and armed guards to being a territorial power. In 1765 the Mughal emperor, in no real position to refuse, granted the Company the diwani of Bengal, Bihar, and Orissa — the right to collect land revenue across the richest provinces of the subcontinent.

This is the moment worth pausing on. The Company did not conquer Bengal in order to govern it well. It acquired the taxing rights of a state while remaining, in its own bones, a profit-seeking enterprise answerable to shareholders an ocean away. It now held the two things that matter most to ordinary people’s survival — control of the land and control of the grain — and it held them not as a duty but as an asset. The revenue of Bengal existed, from London’s point of view, to pay dividends, fund armies, and finance the purchase of Indian goods for European markets. Governing was overhead. Extraction was the point.

This is a pattern I keep returning to: the capture of an existing system by an interest that answers to somebody else. The tax machinery of Bengal was old and functional. The Company did not dismantle it. It slipped into the driver’s seat and pointed it at a different destination.

When the rain failed

The 1769 monsoon was disastrously short. By the autumn, the aman rice crop — the great harvest that Bengal’s entire year was built around — had largely failed. Prices began to climb. By early 1770 the province was in the grip of full famine, and the accounts that survive from that year are almost unbearable to read: villages emptied, roads lined with the dying, people eating leaves, then bark, then the seed grain they should have planted for the following season. Reports describe the living too weak to bury the dead, and the well-documented horror of survivors driven to acts no one should ever be reduced to.

The death toll is, and must remain, an estimate. No one was counting. The figure most often repeated — roughly ten million people, on the order of a third of Bengal’s population — comes from later reckonings and Company correspondence, not a census. I state it the way it should be stated: as an estimate of a catastrophe so large that even the low guesses describe a civilisation-scale loss. Whether the true number was seven million or twelve, the meaning does not change. A significant fraction of one of the most populous, prosperous regions on Earth was wiped out in the span of about a year.

A crop failure is a misfortune. A famine of this scale is a decision — or, more precisely, the sum of a thousand decisions all pointed at the wrong objective.

How the Company made it worse

Here is the part that the phrase “natural disaster” is designed to bury. The drought created scarcity. The Company’s governance converted that scarcity into mass death, and it did so through choices that were, from a balance-sheet perspective, entirely rational.

First, and most damningly, it kept collecting the revenue. As the harvest failed and people began to starve, the land tax was not meaningfully suspended. In some assessments it was actually enforced more rigorously — pursued with vigour precisely because defaults were rising — and the following year the demand was maintained. Contemporary Company records boast, in the flat language of accountancy, that revenue collection held up remarkably well through the famine years. Sit with that. In the middle of a mass death event, the organisation in charge was pleased to report that its income had held. That single fact tells you everything about what the machine had been built to optimise. It was not optimising for the survival of Bengalis. It was optimising for the number at the bottom of the ledger.

Second, the Company and its servants had spent the preceding years distorting the grain trade in ways that made the province brittle. Company employees and their intermediaries had muscled into internal trade, using the Company’s privileges to corner markets and set prices for private gain. When scarcity hit, this hollowed-out, monopolised grain system had no slack in it. Some officials engaged in grain speculation and hoarding — buying up rice not to feed people but to sell it back to them at famine prices. When the people who control the storehouses profit more from an empty market than a full one, the storehouses stay closed.

Third, the older obligations of a ruler — to hold grain reserves, to remit taxes in a bad year, to organise relief — had no place in the Company’s operating logic. A traditional Indian state was far from gentle, but it understood, if only from self-interest, that a dead peasant pays no tax next year. It kept granaries and forgave revenue in a crisis because a ruler’s wealth was tied to the land’s long-term productivity. The Company’s wealth was tied to this quarter’s remittance to London. Relief was a cost with no line item. So there was, in any systematic sense, almost none.

Scarcity as a manufactured thing

I want to be careful and precise here, because this is where the story is usually either sanitised or exaggerated. The Company did not cause the drought. It did not, in some cartoon-villain sense, set out to kill ten million people; mass death was bad for business, and the Company’s own revenues fell hard in the years after as the depopulated land went uncultivated. What it did was worse in a quieter way. It ran Bengal through a system whose only real objective was extraction, and it kept that system running at full throttle straight through a famine, because the system had no mechanism — and no motive — to do otherwise.

That is how scarcity gets manufactured. Not usually by someone hoarding grain in a cellar and cackling, though that happened too. It gets manufactured structurally, when the institution that controls the essentials of life is optimised for something other than life. The drought decided that there would be less rice. The Company’s governance decided who would go without it, and how completely. When you strip away the euphemisms, a famine is a distribution outcome, and distribution is a choice.

When the institution that controls the essentials of life is built to answer to shareholders rather than to the people, scarcity stops being an accident and becomes a system output.

Who takes, who pays, who fights back

Run the same question I run over every episode of captured power: who takes, who pays, and who — if anyone — fights back?

Who took? The Company’s shareholders and its servants. The private fortunes made in Bengal in these years were staggering — the “nabobs” who returned to England laden with Indian wealth were a national scandal, buying up estates and parliamentary seats. The revenue held. The dividends flowed.

Who paid? The people with no cushion and no exit: cultivators, weavers, day-labourers, the landless poor. Famine, then as now, is exquisitely sorted by class. The powerful in Bengal suffered losses; the powerless suffered annihilation. The costs of a system optimised for extraction always land hardest on the people with the least ability to absorb them — that is not a bug in the arrangement, it is the arrangement.

And who fought back? At first, almost no one could — you cannot organise resistance while you are starving. But the famine did not vanish from memory. It fed a slow-burning outrage that reached back to London itself, where the sheer moral horror of a chartered company presiding over ten million deaths while congratulating itself on its revenue became impossible to ignore. It fuelled the parliamentary attacks on the Company, the impeachment drama around its officials, and the long argument over whether a private corporation should be allowed to rule an empire at all. The famine was a data point in a case that eventually, decades later, stripped the Company of its powers. Accountability came grindingly slowly, and far too late for the dead — but the pattern of profit governing human beings was, at last, named as the scandal it was.

Why 1770 still resonates

It would be comfortable to treat this as a horror sealed off in the eighteenth century, a thing that could only happen under the peculiar arrangement of a trading company holding the tax rights of a province. I don’t think it is sealed off at all. The specific machinery was of its time; the underlying pattern is not.

The pattern is what happens when a body whose fundamental purpose is profit acquires control over something people cannot live without — food, in 1770, but in other centuries it has been land, water, medicine, housing, information, the very tools we work with. The enclosure of the commons in England ran on the same logic: take a shared resource that people depended on, convert it into a private asset optimised for yield, and let the costs fall on those who lose access. And the same dynamic runs through the story of how technology gets captured — a tool built to serve many, quietly re-pointed to extract from them. Different centuries, different assets, same machine.

The lesson of the Bengal famine is not “corporations are evil.” It is something more precise and more useful. It is that an institution does what it is optimised to do, ruthlessly, even into catastrophe, and it will not spontaneously develop a conscience at the moment its objective collides with human survival. The Company kept collecting revenue through the famine not because its officials were monsters — some of them were appalled — but because the system was built to collect revenue, and no one had built into it a stronger instruction that said stop, feed them first.

So the warning is straightforward, and it is a warning about design, not villainy. Whenever we hand control over the essentials of life to a body that answers to profit before it answers to people, we are recreating, in whatever the modern idiom happens to be, the conditions of 1770. We are trusting that the machine will choose mercy over its own objective in the moment that matters. History’s answer, written in the emptied villages of Bengal, is that it will not. If we want a different outcome, we have to build the instruction to stop into the system itself — because the system, left to optimise, will do exactly what it was made to do, and count it as a success.