{"id":779217,"date":"2026-07-23T04:32:20","date_gmt":"2026-07-23T04:32:20","guid":{"rendered":"https:\/\/www.newsbeep.com\/us\/779217\/"},"modified":"2026-07-23T04:32:20","modified_gmt":"2026-07-23T04:32:20","slug":"meta-made-its-own-ai-detection-system-it-should-have-just-used-googles","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/us\/779217\/","title":{"rendered":"Meta made its own AI detection system. It should have just used Google\u2019s"},"content":{"rendered":"

IIn March, Meta\u2019s Oversight Board called on the company<\/a> to \u201cmeet its public commitments and employ its own tools\u201d to help quell the spread of deceptive generative AI content across platforms. Meta responded in July by introducing Content Seal<\/a> \u2014 an invisible watermarking technology that flags images generated by the company\u2019s new AI model. But it was basically a footnote buried in the company\u2019s announcement for its Muse image and video generation tools.<\/p>\n

As someone who spends a lot of time scrutinizing AI labeling systems, Content Seal doesn\u2019t fill me with confidence. There are already more established solutions, like C2PA Content Credentials and Google\u2019s SynthID<\/a>, that Meta could have used instead of launching its own system significantly later. After digging around to figure out why Meta has launched its own system, I\u2019m not convinced that Meta has thought this through.<\/p>\n

By Meta\u2019s description, Content Seal works similarly to SynthID<\/a>. The watermark, invisible to human eyes, provides a \u201chidden provenance signal\u201d embedded into AI-generated images that can then be scanned and flagged by a detection tool, helping online users to differentiate deepfakes from authentic content. Like SynthID, Meta also says that Content Seal watermarks remain intact and can still be detected if the image is \u201ccropped, compressed, resized, or screenshotted.\u201d<\/p>\n

So, if Content Seal functionally does the same thing\u2026 why not just adopt SynthID? Meta already operates as a steering committee member<\/a> of the Coalition for Content Provenance and Authenticity (C2PA) that promotes the separate Content Credentials standard alongside Google, so it\u2019s shown willingness to work with others on solving the growing issue of AI detection. SynthID has also already been adopted by OpenAI, so clearly Google is also willing to open its technology up to rival AI providers in the name of improving transparency.<\/p>\n

Content Seal has several limitations in its current state despite those similarities to Google\u2019s system. For now, users can only detect Content Seal watermarks through a dedicated web tool<\/a> that Meta is testing, meaning Meta hasn\u2019t built those detection capabilities into its Meta AI chatbot like Google has with Gemini<\/a>. It sounds like that may be in the works, however. Meta spokesperson Faith Eischen told The Verge that the company is \u201cexploring ways to bring detection closer to where people encounter AI-generated content.\u201d Given that\u2019s where AI detection is needed most, and has been for some time, why isn\u2019t it available at launch?<\/p>\n

The watermark itself is also only being applied to images generated by Muse in the Meta AI app and Meta.ai website, which means online users can\u2019t use it to detect content created by Meta\u2019s older AI models. Support for generated video isn\u2019t available either, though Meta says this is coming \u201csoon.\u201d<\/p>\n

\"<em>Here\u2019s<\/a>\"<em>And<\/a>PreviousNext<\/p>\n

1\/2Here\u2019s the information that\u2019s displayed when Meta\u2019s detection tool successfully flags an image that\u2019s been made or edited using its own Muse model. Image: Jess Weatherbed \/ The Verge<\/p>\n

Meta has imposed a daily limit on how many times you can check images for Content Seal through its detection tool. Eischen said this rate limit is designed to support \u201cnormal usage\u201d while protecting the detection system from being misused. Meta didn\u2019t clarify what such misuse would look like \u2014 presumably, attempts to crack the system<\/a> to avoid watermarked content from being detected \u2014 but Google<\/a> and OpenAI\u2019s detection tools<\/a> have similar rate limitations. C2PA stands out as the only system that doesn\u2019t cap how many times users can check content. Any limitation on detection feels counterintuitive to improving AI transparency at scale, so this feels like a missed opportunity for Meta\u2019s system to do something better than SynthID.<\/p>\n

On Meta\u2019s own platforms like Facebook and Instagram that apply AI labels, Eischen said unspecified metadata \u201calongside Content Seal watermarking\u201d is being used to help users identify AI-generated content. When I asked Meta if it was instructing other online platforms like TikTok and LinkedIn that scan and label AI content on how to detect Content Seal, Eischen said the company is \u201cdetermined to work with our industry peers to make sure users have the best experience possible.\u201d<\/p>\n

That sounds like broader support for the standard is still a work in progress, which could prevent Muse-generated images from being effectively labeled outside of Meta\u2019s own platforms. When I fed a test image I made using Meta\u2019s Muse model into Gemini and the official C2PA detection portal, neither tool could confirm that it was AI-generated. There\u2019s also the question of whether Content Seal can be applied to image and video files alongside SynthID and Content Credentials without interfering with those other standards. Meta didn\u2019t provide any clarification for this on record.<\/p>\n

\"A<\/a><\/p>\n

I tried asking Gemini if my test image was AI, but if Meta embeds any other provenance markers into its AI content, then it\u2019s not something that Google can detect. Image: Jess Weatherbed \/ The Verge<\/p>\n

\u201cLike others, we built Content Seal natively towards our own technical specifications and products. It takes multiple approaches working together to address this across the ecosystem, and we\u2019re glad to be contributing to that effort,\u201d Eischen said. \u201cWe\u2019ll have more to share about Content Seal soon.\u201d<\/p>\n

Given Content Seal can only detect images generated using Meta\u2019s very latest AI model, I have to wonder what the company has been doing all this time. Meta has provided AI image generation tools since 2023<\/a>, so it\u2019s already churned out a lot of fakery that can\u2019t be detected by its own proprietary system. It also introduced AI tags to Instagram and Facebook in 2023, which angered many photographers at the time by mistakenly labeling real photographs as \u201cMade by AI<\/a>.\u201d<\/p>\n

Three years on, Meta still isn\u2019t sure about how to pitch itself as both a factory for AI content and the solution for identifying it, especially across its own platforms. Even senior leadership at Meta seems to be at a loss for what it should do next.<\/p>\n

In an interview on Lenny Rachitsky\u2019s podcast, Instagram head Adam Mosseri<\/a> initially embraced the idea that people who dislike AI-generated content should be allowed to keep it out of their social feeds \u2014 which sounds awfully like a filtering feature<\/a> that would require a reliable AI labeling system. He even suggests that authenticity itself will become more desirable as something that AI can\u2019t provide.<\/p>\n

\u201dIn a world where there\u2019s an abundance of synthetic content, I actually think people are going to seek out creativity and authenticity and people more, not less,\u201d Mosseri said.<\/p>\n

\u201cI don\u2019t think we should filter out AI content\u201d<\/p>\n

During the same interview, however, Mosseri said \u201cI don\u2019t think we should filter out AI content,\u201d while affirming that \u201cwe should let you know if content is AI content or not.\u201d Mosseri also reiterated an opinion<\/a> he\u2019d previously expressed that it might be \u201cmore practical to fingerprint real media<\/a> than fake media.\u201d That doesn\u2019t make Meta sound confident in its own ability to develop a viable AI labeling system. It\u2019s had plenty of time to do so between building its social platforms into slop factories for shrimp Jesus<\/a> and other generative brainrot<\/a>, yet the Content Seal launch still feels like it was rushed out the door.<\/p>\n

It offers no unique benefits for consumers over the similar, established SynthID system, and instead just creates yet another hoop that people have to jump through to verify AI content. Maybe Meta should have just adopted Google\u2019s watermarking standard instead, like OpenAI has. Facebook and Instagram users may be better off if it had. Eischen tells me that Meta has been contributing open-source watermarking research<\/a> for years now, so it didn\u2019t cook this tech up overnight, but I would expect a better consumer-facing experience to show for it.<\/p>\n

If Meta wants to stand on its own solutions instead, it\u2019ll need more than a half-baked SynthID clone to prove it\u2019s actually serious about AI transparency \u2014 certainly a more reliable one at least. Reuters<\/a> has already found that Content Seal failed to detect more than half of the Muse-generated images it tested after they had been cropped.<\/p>\n

Follow topics and authors from this story to see more like this in your personalized homepage feed and to receive email updates.Jess WeatherbedClose\"Jess<\/p>\n

Jess Weatherbed<\/p>\n

Posts from this author will be added to your daily email digest and your homepage feed.<\/p>\n

FollowFollow<\/p>\n

See All by Jess Weatherbed<\/a><\/p>\n

AIClose<\/p>\n

AI<\/p>\n

Posts from this topic will be added to your daily email digest and your homepage feed.<\/p>\n

FollowFollow<\/p>\n

See All AI<\/a><\/p>\n

AnalysisClose<\/p>\n

Analysis<\/p>\n

Posts from this topic will be added to your daily email digest and your homepage feed.<\/p>\n

FollowFollow<\/p>\n

See All Analysis<\/a><\/p>\n

MetaClose<\/p>\n

Meta<\/p>\n

Posts from this topic will be added to your daily email digest and your homepage feed.<\/p>\n

FollowFollow<\/p>\n

See All Meta<\/a><\/p>\n

ReportClose<\/p>\n

Report<\/p>\n

Posts from this topic will be added to your daily email digest and your homepage feed.<\/p>\n

FollowFollow<\/p>\n

See All Report<\/a><\/p>\n

TechClose<\/p>\n

Tech<\/p>\n

Posts from this topic will be added to your daily email digest and your homepage feed.<\/p>\n

FollowFollow<\/p>\n

See All Tech<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"IIn March, Meta\u2019s Oversight Board called on the company to \u201cmeet its public commitments and employ its own…\n","protected":false},"author":2,"featured_media":779218,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[182,4687,181,507,1282,2853,172,74],"class_list":["post-779217","post","type-post","status-publish","format-standard","has-post-thumbnail","category-artificial-intelligence","tag-ai","tag-analysis","tag-artificial-intelligence","tag-artificialintelligence","tag-meta","tag-report","tag-tech","tag-technology"],"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/posts\/779217","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/comments?post=779217"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/posts\/779217\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/media\/779218"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/media?parent=779217"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/categories?post=779217"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/us\/wp-json\/wp\/v2\/tags?post=779217"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}