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

In March, Meta’s Oversight Board told the company to meet its public commitments and use its own tools against deceptive generative AI content on its platforms. In July, Meta answered with Content Seal, an invisible watermarking system that marks images produced by the company’s new AI model so they can be flagged as machine-generated.

Content Seal works as an invisible watermark embedded in images from Meta’s own generative model. The mark is meant to travel with the image and support later detection, rather than relying only on post-hoc classifiers that try to guess whether content is synthetic after it is already circulating.

For engineers and builders shipping generative features, the decision is concrete: Meta is treating provenance as a product responsibility for outputs from its own model, not as a third-party moderation problem alone. Anyone integrating Meta image generation into apps or workflows should expect watermarked outputs and plan for how that signal shows up in moderation, labeling, and trust pipelines.

The Verge’s framing is that Meta built its own AI detection stack when it could have used Google’s. That puts Content Seal in a competitive lane where large platforms are choosing between shared standards and in-house provenance tools, even when the Oversight Board’s pressure was about Meta using tools it already owned and had promised to deploy.

What to watch next is whether Content Seal is limited to images from Meta’s new model or expands across more Meta-generated formats, and whether Meta actually deploys the system in the way the Oversight Board demanded—using its own tools to slow deceptive generative content on its platforms, not only announcing a watermark for one model’s outputs.