Tom Felton extends Broadway run as Draco Malfoy for the final time
Tom Felton extends his Broadway run as Draco Malfoy in Harry Potter and the Cursed Child through January 2027

Tom Felton will continue playing Draco Malfoy in Broadway’s Harry Potter and the Cursed Child for an additional two months, marking the final extension of his current run.
Producers announced Tuesday that Felton will remain with the production at the Lyric Theatre through Jan. 3, 2027. He was previously scheduled to leave the Broadway production on Nov. 1.
Felton began his engagement as the adult Draco Malfoy on Nov. 11, 2025. The actor originally portrayed Draco as a child in the Harry Potter film franchise. His Broadway casting marked the first time an original Harry Potter film cast member joined the stage production.
Since Felton joined Harry Potter and the Cursed Child, the production has regularly ranked among Broadway’s top-grossing shows. His appearance has also brought renewed attention to the stage adaptation, which opened on Broadway in 2018.
The play is set 19 years after the events of the original Harry Potter story. It follows an adult Harry Potter, Ron Weasley, Hermione Granger and Draco Malfoy as they navigate parenthood while their children begin their own lives at Hogwarts.
Felton will not perform during several previously announced periods, including Aug. 17-23, Sept. 14-20, Oct. 12-18 and Nov. 2.
The current Broadway cast includes John Skelley as Harry Potter, Trish Lindstrom as Ginny Potter and Emmet Smith as their son, Albus Potter. Rachel Christopher plays Hermione Granger, while Daniel Fredrick portrays Ron Weasley. Janae Hammond plays Rose Granger-Weasley, with Aidan Close as Scorpius Malfoy and Kristen Martin as Delphi Diggory.
Felton’s extended Broadway engagement gives audiences additional opportunities to see the actor return to the Harry Potter universe in a role he first played on screen.



















COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ