Meta made its own AI detection system. It should have just used Google’s

IIn March, Meta’s Oversight Board called on the company to “meet its public commitments and employ its own tools” to help quell the spread of deceptive generative AI content across platforms. Meta responded in July by introducing Content Seal — an invisible watermarking technology that flags images generated by the company’s new AI model. But it was basically a footnote buried in the company’s announcement for its Muse image and video generation tools.

As someone who spends a lot of time scrutinizing AI labeling systems, Content Seal doesn’t fill me with confidence. There are already more established solutions, like C2PA Content Credentials and Google’s SynthID, 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’m not convinced that Meta has thought this through.

By Meta’s description, Content Seal works similarly to SynthID. The watermark, invisible to human eyes, provides a “hidden provenance signal” 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 “cropped, compressed, resized, or screenshotted.”

So, if Content Seal functionally does the same thing… why not just adopt SynthID? Meta already operates as a steering committee member of the Coalition for Content Provenance and Authenticity (C2PA) that promotes the separate Content Credentials standard alongside Google, so it’s 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.

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

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’t use it to detect content created by Meta’s older AI models. Support for generated video isn’t available either, though Meta says this is coming “soon.”

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 “normal usage” while protecting the detection system from being misused. Meta didn’t clarify what such misuse would look like — presumably, attempts to crack the system to avoid watermarked content from being detected — but Google and OpenAI’s detection tools have similar rate limitations. C2PA stands out as the only system that doesn’t 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’s system to do something better than SynthID.

On Meta’s own platforms like Facebook and Instagram that apply AI labels, Eischen said unspecified metadata “alongside Content Seal watermarking” 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 “determined to work with our industry peers to make sure users have the best experience possible.”

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’s own platforms. When I fed a test image I made using Meta’s Muse model into Gemini and the official C2PA detection portal, neither tool could confirm that it was AI-generated. There’s 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’t provide any clarification for this on record.

“Like 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’re glad to be contributing to that effort,” Eischen said. “We’ll have more to share about Content Seal soon.”

Given Content Seal can only detect images generated using Meta’s 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, so it’s already churned out a lot of fakery that can’t 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 “Made by AI.”

Three years on, Meta still isn’t 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.

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

”In a world where there’s an abundance of synthetic content, I actually think people are going to seek out creativity and authenticity and people more, not less,” Mosseri said.

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

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’s 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 for years now, so it didn’t cook this tech up overnight, but I would expect a better consumer-facing experience to show for it.

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