Ninja warns AI deepfakes could destroy live streaming within a year

Ninja warns AI-generated deepfake videos may soon make streaming impossible without urgent regulations and watermarks.


Pop Culture & Art June 18, 2025
Photo: Reuters

Tyler “Ninja” Blevins, one of the most recognizable names in gaming and live streaming, has issued a strong warning about the future of the industry in light of rapid advances in artificial intelligence.

The Twitch veteran believes AI-generated deepfake videos will soon pose an existential threat to streamers.

Speaking during a recent broadcast, Ninja said AI technology, like Google’s Veo3, is progressing so quickly that it could make streaming “impossible” within a year if proper safeguards aren’t implemented. His main concern centers around the rise of convincing AI-generated videos showing streamers engaging in fake gameplay or making offensive statements.

“If there’s no watermark that’s unremovable, streaming is going to be over,” Ninja said. “There will be AI videos of me saying unhinged things, and people will believe them.”

Ninja also highlighted the potential for AI to be used maliciously by those trying to fabricate scandals or spread fake drama. The ability to prompt AI to create such content could lead to reputational damage for many creators.

His comments follow a viral video where Veo3 generated a fake Fortnite streamer celebrating a win. While not yet flawless, the video demonstrated just how close AI is to replicating real-time content.

The broader implications are already unfolding. Earlier in 2025, an Australian radio station used an AI-generated host for months without public awareness, highlighting how easy it is to deceive audiences.

As AI continues to blur the lines between real and fake, Ninja’s warning emphasizes the urgent need for mandatory content labeling and watermarking tools to protect the integrity of live streaming platforms.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ