"According to new research from Kapwing, more than one in five videos recommended to brand-new YouTube accounts are low-quality, AI-generated clips appropriately known as "AI slop." These videos, which are also taking over social media, are mainly made to capture people's attention and generate advertising revenue, but they're not as harmless as that makes them sound. Kapwing's research shows this slop is completely reshaping YouTube's ecosystem as we know it."
"Its researchers found that of the first 500 videos served to a new account, 104 were AI slop. That's over 20%. The findings suggest that YouTube's recommendation system isn't doing this by accident; instead, it's habitually and intentionally exposing new users to it. AI slop isn't the only issue, either: Kapwing also found that a third of the first 500 videos are compulsive, low-quality "brainrot" videos, whether AI-generated or not."
"By reviewing the top 100 trending YouTube channels in every country, it found that hundreds of high-ranking channels are dedicated almost entirely to AI-generated videos. Collectively, these channels have racked up tens of billions of views and hundreds of millions of subscribers worldwide. That breaks down to an estimated $117 million in annual revenue. And who knows how much revenue is coming from those fake celebrity-fronted AI scam ads on YouTube, as well."
More than one in five videos recommended to brand-new YouTube accounts are low-quality, AI-generated clips called 'AI slop.' Of the first 500 videos served to a new account, 104 were AI slop, and a third of those first 500 videos qualify as compulsive, low-quality 'brainrot' content. Hundreds of high-ranking channels focus almost entirely on AI-generated videos, collectively amassing tens of billions of views and hundreds of millions of subscribers. Those channels generate an estimated $117 million annually and often feature surreal animated shorts or bright looping animations targeted at children, with large audiences in Spain, South Korea, Egypt, Brazil, and India.
Read at SlashGear
Unable to calculate read time
Collection
[
|
...
]