Skip to main content
AI Watermark Removal

Provider tracker

DeepSeek Watermark: What China's Labeling Law Actually Requires

DeepSeek's chat interface tells you in plain visible text that you're reading AI output, and that much is settled by DeepSeek's own Terms of Service and disclosure pages. The trigger is a named Chinese rule: the Measures for Labeling of AI-Generated Content, paired with mandatory standard GB 45438-2025, finalized March 14, 2025 and effective September 1, 2025. What is not settled, despite how often it gets repeated, is the separate claim that DeepSeek embeds an invisible statistical watermark inside its text. Nothing DeepSeek has published describes that, and the confusion almost certainly traces to the Chinese standard's own vocabulary rather than to anything DeepSeek engineered.

Published 2026-08-11Updated 2026-08-11Confirmed

Key takeaways

  • Confirmed: chat.deepseek.com displays visible reminder labels stating content is AI-generated, and DeepSeek's Open Platform Terms of Service require API developers to label AI-generated content under Chinese law.
  • GB 45438-2025 is unusually specific. "Explicit" labeling means visible on-screen text, audio, or graphics (the tag "AI生成" is the standard example), while "implicit" labeling means machine-readable metadata: provider name or code, a content reference number, and a watermark where feasible.
  • Not confirmed: an invisible or statistically embedded text watermark in DeepSeek's output. Its model and algorithm disclosure page describes only the visible label, with nothing hidden underneath.
  • DeepSeek's Janus-Pro image generator has no confirmed watermark either, visible or invisible, a real gap next to Google, OpenAI, Meta, and Amazon, all of which document invisible watermarks in their image output.
  • DeepSeek's compliance activity is entirely China-oriented. No DeepSeek source addresses the EU AI Act's Article 50 marking requirement at all, despite the API being reachable internationally.

Provider map

Text watermark status by provider

Detector guide
How to read this map

Confirmed means an official or primary source documents text watermarking. Contested means official sources disagree with each other. Watchlist means regulation, research, or provider behavior makes the topic worth tracking closely.

What DeepSeek actually documents

Confirmed

Here's every marking mechanism DeepSeek describes in its own words, and there are fewer than the coverage suggests.

DeepSeek's Open Platform Terms of Service, Section 3.7, put a labeling duty on developers who build on its API. Chinese law treats those developers as "network information service providers," and that status requires them to label AI-generated or synthesized content.

The same clause bans maliciously removing, altering, forging, or concealing a label once it's applied. That's an obligation on the people integrating the API, not proof that DeepSeek's own chat product carries anything embedded.

DeepSeek's consumer product does its own labeling, and its model and algorithm disclosure page names exactly three places it shows up:

  • A reminder on the welcome page when a session starts
  • A label appended to the end of generated text
  • A notice at the bottom of the interface

All three state that the content is AI-generated and may be inaccurate. The disclosure page walks through that mechanism and stops: no invisible watermark, no statistical signal, no metadata scheme appears anywhere in it.

DeepSeek also issued a company announcement around September 1, 2025 confirming it had added content labeling under the same regulation.

The law behind the label: GB 45438-2025

Confirmed

You'll see exactly what China's standard demands, because its wording is where nearly all the confusion about DeepSeek starts.

China's Cyberspace Administration finalized the Measures for Labeling of AI-Generated Content, along with the mandatory national standard GB 45438-2025, on March 14, 2025. Both took effect September 1, 2025.

Among labeling regimes tracked across major jurisdictions, this is the most technically prescriptive one found anywhere. Instead of saying "disclose AI content," it defines two label types with named required fields:

  • Explicit labeling: on-screen text, audio, or graphics a person can actually see or hear, with the Chinese-language tag "AI生成" as the standard example.
  • Implicit labeling: machine-readable metadata embedded in the file itself, specifically the provider's name or code, a content reference number, and a watermark where technically feasible.

The measures cover five content types at once:

  • Text
  • Images
  • Audio
  • Video
  • Virtual scenes

The obligation also doesn't stop at whoever generated the content. Platforms distributing it have to verify and enforce labeling on material their users upload.

That's a meaningfully wider net than most comparable rules, including the EU's Article 50, which mostly targets the entity building the AI system rather than every platform passing its output along.

Why "DeepSeek hides a watermark" keeps getting repeated

Community discussion

Here's where the invisible-watermark claim comes from and why DeepSeek's own pages don't back it.

The Phandroid report from around September 3, 2025 describes DeepSeek's labeling as pairing the visible label with an "implicit" hidden digital fingerprint that survives redistribution. It's more specific and more interesting than anything DeepSeek has published, which is exactly why it spread.

Neither DeepSeek's Open Platform Terms of Service nor its model and algorithm disclosure page says anything of the kind. Both describe the visible reminder and nothing else.

So the claim describes a general compliance category every covered platform in China has to satisfy. It isn't evidence of a DeepSeek-specific algorithm biasing token choices the way Google's SynthID does for Gemini.

Until DeepSeek publishes its own account of an embedding mechanism, or an independent test finds one, treat "DeepSeek has an invisible watermark" as community discussion rather than confirmed fact.

Two gaps DeepSeek has never addressed

Research/proposal

These are the two questions DeepSeek's documentation leaves wide open, and both matter if you're shipping something on its API.

The first is images. DeepSeek has never published anything confirming a watermark, visible or invisible, in output from Janus-Pro, its MIT-licensed image generator.

That leaves DeepSeek's image line behind Google, OpenAI, Meta, and Amazon, each of which documents an invisible watermark in its own generated images.

The second is Europe. Every DeepSeek compliance document found addresses Chinese law only, and nothing from the company discusses the EU AI Act's Article 50 machine-readable marking requirement either way.

DeepSeek's API gets used well outside China, so for anyone serving EU users there's a live question here. Does labeling built for Chinese regulators do anything for a European one, or is this simply a gap nobody has closed?

FAQ

Does DeepSeek watermark its text output?

DeepSeek confirms a visible AI-content label, driven by Chinese regulation. No DeepSeek source, not its Terms of Service and not its model and algorithm disclosure page, confirms an invisible or statistically embedded text watermark. The popular claim to that effect traces to one secondary report and isn't backed by anything DeepSeek has published.

Is DeepSeek's labeling the same as the EU AI Act's marking rules?

No. DeepSeek's confirmed labeling responds to China's Measures for Labeling of AI-Generated Content and standard GB 45438-2025, effective September 1, 2025, a different legal regime with different required fields than Article 50. Whether or how DeepSeek meets Article 50 hasn't been found in any DeepSeek source.

What does China's "implicit labeling" requirement actually require?

Under GB 45438-2025, implicit labeling means machine-readable metadata embedded in the generated file: the provider's name or code, a content reference number, and a watermark where technically feasible. It's a defined legal category with specific fields, not a synonym for a hidden statistical signal buried in word choice, which is the more dramatic and unconfirmed version of the claim circulating about DeepSeek.

Does DeepSeek's image generator carry a watermark?

Not confirmed either way. DeepSeek hasn't published anything describing a watermark, visible or invisible, in output from Janus-Pro, its open-source image model. Google, OpenAI, Meta, and Amazon all document invisible watermarks in their own image generators, so this is a genuine gap rather than an industry norm.

Next steps

  • See what the question looks like when a provider actually confirms an invisible text watermark. Anthropic says supported Claude models weave one into generated text, with detection tooling still unpublished. Claude watermark tracker
  • Work out what Europe asks for, since DeepSeek's Chinese compliance documents say nothing about it. EU AI Act and AI watermarking
  • Paste a DeepSeek reply into the free in-browser checker to see whether any invisible Unicode characters came along. Nothing DeepSeek documents would put them there, which is a reason to check rather than assume. Invisible character checker

Sources and citation status