Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Marvel finally admits to – and fixes – glaring Spider-Man: Homecoming error

Marvel Studios president Kevin Feige has addressed timeline discrepancy

Jacob Stolworthy
Friday 27 October 2023 10:27 BST
Comments
Spider-Man: Homecoming - Trailer

Your support helps us to tell the story

From reproductive rights to climate change to Big Tech, The Independent is on the ground when the story is developing. Whether it's investigating the financials of Elon Musk's pro-Trump PAC or producing our latest documentary, 'The A Word', which shines a light on the American women fighting for reproductive rights, we know how important it is to parse out the facts from the messaging.

At such a critical moment in US history, we need reporters on the ground. Your donation allows us to keep sending journalists to speak to both sides of the story.

The Independent is trusted by Americans across the entire political spectrum. And unlike many other quality news outlets, we choose not to lock Americans out of our reporting and analysis with paywalls. We believe quality journalism should be available to everyone, paid for by those who can afford it.

Your support makes all the difference.

Marvel has finally fixed one of the most glaring errors that featured in Spider-Man: Homecoming.

In 2017, when Tom Holland’s debut standalone film as the character was released, many die-hard Marvel Cinematic Universe (MCU) viewers noticed that the timecard featured in an early scene was actually incorrect.

After a scene setting up the film’s villain, Michael Keaton’s Adrian Toomes aka the Vulture, the intertitle “8 Years Later” appears on the screen – however, the film takes place before the year this would position it as within the MCU timeline.

The Direct noticed a clarification in a new book, which is titled Marvel Studios’ The Marvel Cinematic Universe – An Official Timeline.

On page 173, a text box explains that Toomes incorrectly says the Battle of New York, as featured in Avengers Assenble, occurred eight years before the events of Homecoming.

In actual fact, it happened four years before, meaning the film is set in 2016 and not, as the incorrect timecard would suggest, 2020.

As explained by character Miss Minutes, the animated Time Variane Authority mouthpiece in Disney+ series Loki, “Adrien Toomes says the Battle of New York was eight years ago, but that event was only four years prior. This one’s a real head scratcher for us – I reckon an analyst misplaced the case file.”

Of course, thanks to Loki, time is no longer a straight line in the MCU, with the latest Doctor Strange and Ant-Man films exploring the Multiverse, which is a series of alternate timelines featuring Marvel characters, dead and alive.

Adrian Toomes (Michael Keaton) is to blame for the glaring Marvel error in ‘Spider-Man: Homecoming’
Adrian Toomes (Michael Keaton) is to blame for the glaring Marvel error in ‘Spider-Man: Homecoming’ (Sony Pictures Releasing)

In the book’s foreword, Marvel Studios president Kevin Feige acknowleged that there might be timeline discrepancies featured in the MCU as several projects “were created by different storytellers during different periods of Marvel’s history.”

He added: “The timeline presented in this book is specific to the MCU’s Sacred Timeline through Phase 4. But, as we move forward and dive deeper into the Multiverse Saga, you never know when timelines may just crash or converge (hint, hint/spoiler alert).”

Apple TV+ logo

Watch Apple TV+ free for 7 days

New subscribers only. £8.99/mo. after free trial. Plan auto-renews until cancelled

Try for free
Apple TV+ logo

Watch Apple TV+ free for 7 days

New subscribers only. £8.99/mo. after free trial. Plan auto-renews until cancelled

Try for free

Loki is currently airing on Disney+, with new Captain Marvel film, The Marvels, set to be released on 10 November.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in