There’s a version of Batman that existed before 1988 — a hero who was wounded, yes, driven by grief, yes, but ultimately defined by a kind of grim optimism. The idea that one man, with enough discipline and enough gadgets, could hold back the darkness. And then there’s the Batman who existed after the summer of 1988, after a phone number was printed on the back of a comic book and the readers of America decided that a teenage boy should die. That Batman is the one most of us know. Haunted. Harder. Carrying something he can never fully put down.

“A Death in the Family” didn’t just kill a Robin. It fundamentally reshaped what Batman meant as a character — and the story of how it happened is every bit as strange and dramatic as the story itself.

The Robin Nobody Liked

To understand why Jason Todd’s death hit so hard, you have to first understand why so many people didn’t care if he lived.

Dick Grayson, the original Robin, had been Batman’s partner since Detective Comics #38 in April 1940. He was practically part of the furniture of the Batman mythos — acrobatic, cheerful, essential. When Marv Wolfman and George Pérez began building Dick into a major character through the New Teen Titans comics in the early 1980s, DC needed a Robin for Batman’s books. So writer Gerry Conway and artist Don Newton introduced Jason Todd in Batman #357 in March 1983. At first, Jason was practically a copy-paste of Dick — another circus acrobat, another murdered family, another kid taken under Bruce Wayne’s wing. Readers didn’t exactly embrace him with open arms even then, but they tolerated the situation.

Then the Crisis on Infinite Earths rebooted the DC Universe in 1985 and 1986, and someone decided to give Jason a makeover. Writer Max Allan Collins reimagined him in Batman #408 as a street kid — rebellious, impulsive, a little mean. Where Dick had been the kind of sidekick who made you root for him, Jason made you want to put him in timeout. He broke Batman’s cardinal no-killing rule in Batman #424 and then lied about it. Readers were not charmed. The hate mail piled up.

Jim Starlin, who took over writing duties on the Batman title, didn’t even particularly like the concept of Robin to begin with. He thought sending a child into combat with a billionaire dressed as a bat was kind of absurd, honestly. But editor Dennis O’Neil had him start using Jason in the stories, so Starlin decided to lean into his own reservations. He wrote Jason with an edge that readers found abrasive rather than compelling. By 1988, everyone involved seemed to agree: something had to give.

Fans Decide a Fate

What happened next was either a brilliant piece of fan engagement or a slightly cynical publicity stunt, depending on your perspective. Probably a little of both.

O’Neil and DC president Jenette Kahn were at an editorial retreat when O’Neil remembered a 1982 Saturday Night Live sketch — Eddie Murphy had given viewers two phone numbers to call and let them vote on whether he should boil a lobster on air. O’Neil thought: what if DC did something similar? Not with a lobster. With a Robin.

DC set up two 900 numbers and printed them on the back cover of Batman #427. Readers could call one number to let Jason Todd live, or another to let him die. The lines were open for 35 hours beginning on September 15, 1988. The storyline had already put Jason in mortal peril — the Joker had beaten him with a crowbar and locked him in a warehouse with a ticking time bomb. Batman #427 ended with the explosion. Now the readers got to decide if he survived it.

Jim Starlin and artist Jim Aparo prepared two complete versions of the next issue, Batman #428. Two alternate sets of pages. Two outcomes. O’Neil voted to let Jason live, for the practical reason that killing a major character would complicate his editorial life considerably. Starlin couldn’t vote — he was in Mexico. And then the lines closed.

The tally: 5,343 votes for death. 5,271 for survival. A margin of 72 votes.

Jason Todd died by the slimmest of democratic margins. There have been rumors ever since that a single individual programmed a computer to repeatedly dial the death number — O’Neil himself acknowledged he’d heard that story, about a lawyer and a Macintosh — but it was never confirmed. What was confirmed was the result: Batman #428, published on October 18, 1988, showed Batman arriving at the ruins of the warehouse and finding Jason’s lifeless body. The real version of that issue went to print. The alternate pages, in which Jason survived, went into storage in DC’s archives in Burbank, California, where they sat unrevealed to the public for over three decades.

The Story Itself

It would be easy to oversell “A Death in the Family” as a piece of storytelling. Even its most enthusiastic defenders admit the plot goes completely off the rails at several points. The Joker somehow becomes the Iranian ambassador to the United Nations. Batman speaks Farsi in Beirut, where Arabic is the commonly spoken language. The Joker is appointed by Ayatollah Khomeini. Retrospective reviewers have described it as “brasher than Top Gun, louder than Hulk Hogan, and more implausible than The A-Team,” which is both accurate and somehow also a little affectionate.

But the emotional throughline works. Jason, already feeling like an outsider in his own superhero partnership, leaves to find his biological mother — a genuinely sympathetic motivation. He’s betrayed by her almost immediately, handed over to the Joker to protect her own secrets. He’s beaten. He’s blown up. And he dies trying to shield her from the explosion. It’s a sad, lonely end for a kid who never quite got to be what he was supposed to be.

The Joker, for his part, doesn’t just win this one. He wins decisively, and the story never pretends otherwise. Batman arrives too late. The person he was supposed to protect is gone. Everything between him and the Joker, as Batman laments at the story’s conclusion, “ends unresolved.” That unresolved quality is actually part of what makes the story resonate — there’s no clean victory, no cathartic confrontation, just the weight of failure.

What It Did to Batman

Here’s where “A Death in the Family” earns its place in the Batman canon, whatever you think of the Joker-as-Iranian-ambassador subplot.

Before this story, the Joker was dangerous in a cartoon sort of way. He was chaos and madness and very white face paint. He was a threat to be managed, a recurring nightmare that Batman would always wake up from. After “A Death in the Family,” the Joker was something different. He had actually won. He had reached into Batman’s world, taken one of the people Bruce Wayne was responsible for, and destroyed him. That changes the calculus of every confrontation between them going forward. The Joker stopped being a dark mirror and became a genuine haunting.

But it’s what the story did to Batman himself that mattered most in the long run. Writer Gerry Conway, who had introduced Jason back in 1983, later observed that “A Death in the Family” opened the door for “the real ‘Dark Knight’ — the idea of Batman as the pitiless enforcer of Gotham.” For roughly a decade of comics that followed, Batman was harder. More driven. More dangerous in a way that made even his allies a little uneasy. Not because writers suddenly decided he should be grumpy, but because the story had given him a genuine, specific wound. He hadn’t just failed to save a stranger. He had failed to save his kid.

There’s a psychological principle at work here that makes this resonate beyond simple plot mechanics. Bruce Wayne’s entire origin is built on the idea that the right response to loss is action — channel the grief into purpose, put on the suit, go fight crime. But Jason’s death exposed the limit of that logic. You can be the world’s greatest detective, you can have a contingency plan for everything, and you can still be standing in the rubble of a warehouse too late to save someone. The story didn’t just hurt Batman. It broke something in his operating logic that couldn’t be easily repaired.

The 2011 DC New 52 initiative rebooted nearly the entire DC Universe — but editors made a deliberate decision to leave the events of “A Death in the Family” intact. In a continuity refresh that changed decades of history, this one story was considered too foundational to touch. That tells you something about what it means to the character.

The Long Shadow

For nearly two decades after Batman #428, Jason Todd stayed dead. That’s actually remarkable in comics, where death is frequently a temporary inconvenience. There was a popular saying in comic fandom: the only characters who stayed dead were Bucky Barnes, Uncle Ben, and Jason Todd. (All three of those, as comic readers eventually discovered, were lies — but the saying persisted for a long time.)

When Jeph Loeb and Jim Lee’s “Hush” storyline ran from 2002 to 2003, it briefly seemed like Jason might be returning — but it turned out to be Clayface impersonating him. The real resurrection came with Judd Winick and Doug Mahnke’s “Under the Hood” story arc, running from 2005 to 2006, which brought Jason back as the Red Hood — a violent, antiheroic vigilante with a lot of unresolved feelings toward both Batman and the Joker. The in-universe explanation for how he came back was… creative, involving a reality-altering punch from a character called Superboy-Prime, which is comics doing what comics do. But the emotional logic of the return worked: Jason came back not as a hero, but as a consequence. As proof that Batman’s failure had permanent effects, even if death itself didn’t.

The shadow of “A Death in the Family” has stretched well into other media. The 2010 animated film Batman: Under the Red Hood adapted the resurrection storyline with Bruce Greenwood as Batman and Jensen Ackles as Jason — and it’s widely considered one of the best DC animated films ever made. The 2020 interactive film Batman: Death in the Family even echoed the original reader vote gimmick, letting viewers choose whether Jason lived or died and see different outcomes unfold. The DCEU’s Batman v Superman: Dawn of Justice kept a damaged Robin suit on display in the Batcave as a wordless memorial, and Zack Snyder’s Justice League features a scene where the Joker taunts Batman over Robin’s death. The wound never really closed.

A Story Worth Defending

“A Death in the Family” is not a perfect comic. Its politics are embarrassing, its plot logic goes on vacation somewhere around the third issue, and the mechanism by which readers voted on a child’s death has been fairly described as at least a little exploitative. Frank Miller called it “the most cynical thing DC has ever done.” He wasn’t entirely wrong.

And yet. The story did something that genuinely matters in the history of the Batman character. It looked at what Batman loses when he fails — not an abstract civilian, not a nameless victim, but a child in his care — and it refused to paper over the damage. It let the Joker win. It let Batman carry that. And then it let the weight of that failure echo through decades of subsequent storytelling.

In the end, the best argument for “A Death in the Family” isn’t that it’s a masterpiece. It’s that it’s honest. Batman’s mission is ultimately defined by what he can’t save. And Jason Todd, impulsive and unpopular and dead by 72 votes, became the permanent reminder of that limitation. You don’t really know what drives the Dark Knight until you understand what he failed to prevent in that warehouse in Ethiopia — and why he’s been proving himself ever since.

---

What are your thoughts on “A Death in the Family”? Did DC make the right call letting fans decide Jason’s fate? Drop your take in the comments.