SenseDefend

Synthetic-media instruments, by article and effective date

Sora and Veo, read for what each documents about marking

Sora's system card lists C2PA metadata on all assets, a moving visible watermark on videos downloaded from sora.com, and internal detection tools. Google's marking layer is described as an invisible watermark embedded across its generative models. The article asks providers for the machine-readable kind and deployers for the disclosure kind. From 3 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.

Which layer of a file carries the claimA signed metadata layer is read by a platform, an embedded signal is found by a detector, and a visible notice is seen by a viewer. The two schemes read on this page cover different layers, and the article asks different parties for each.Which layer is the provenance claim on?A signed metadata layerRead by a platformC2PA metadata on all assets,per one system cardAn embedded signalFound by a detectorAn invisible watermark builtto survive cropping andfiltersA visible noticeSeen by a viewerA moving watermark ondownloads; a corner badge atdeliveryThree layers, two paragraphs, two parties
Fig. 1 The layers are kept as separate rows because one is not a substitute for another.

1What this record already holds

The rows this record already holds for both schemes, and the article's own rows on what marking is asked for, who it is asked of, and where the technical detail is expected to arrive.

  • OpenAI Sora (openai.com)
    C2PA metadata on all assets, listed as providing verifiable origin through an industry standardfirst item under provenance safety toolingSora 2 System Card, OpenAI / recorded 2026-09-22
  • OpenAI Sora
    A visible moving watermark on videos downloaded from sora.com or the Sora appthe layer tied to the download routeSora 2 System Card, OpenAI / recorded 2026-09-22
  • OpenAI Sora
    Internal detection tools to help assess whether a video or audio was created by the vendor's productsthird item on the same listSora 2 System Card, OpenAI / recorded 2026-09-22
  • SynthID
    An invisible watermark is embedded across Google's generative AI consumer products, added at the moment content is createdthe marking layer behind Google's video modelsGoogle DeepMind, SynthID / recorded 2026-09-12
  • SynthID
    Designed to stand up to cropping, filters, frame-rate changes and lossy compressionstated robustnessGoogle DeepMind, SynthID / recorded 2026-09-12
  • Article 50(2)
    Providers must mark synthetic audio, image, video and text in a machine-readable formatincluding general-purpose AI systemsAI Act Explorer, Article 50 / recorded 2026-09-12
  • Article 50(4)
    Deployers must disclose image, audio or video content that is a deep fakefirst subparagraphAI Act Explorer, Article 50 / recorded 2026-09-12
  • Article 50(4)
    For evidently artistic, creative, satirical or fictional work the duty narrows to disclosing that such content exists, in a way that does not hamper enjoyment of the workfirst subparagraphAI Act Explorer, Article 50 / recorded 2026-09-12
  • Article 50(7)
    The Commission is to encourage codes of practice on detection, marking and labelling, and may adopt an implementing act if a code is inadequateprocedure in Article 98(2)AI Act Explorer, Article 50 / recorded 2026-09-12

2What each vendor publishes

One system card lists three things in a row: C2PA metadata on all assets, described as providing verifiable origin; a visible moving watermark on videos downloaded from sora.com; and internal detection tools to help assess whether a video or audio was made by the model. Read as a set, the card covers a signed layer, a layer a viewer sees and a layer the vendor keeps for itself.

The other entry, on a DeepMind page, is a marking layer rather than a product page: an invisible watermark embedded across a family of generative models, described as designed to stand up to cropping, filters and frame-rate changes. It is a signal written at generation, made to survive what happens to a file afterwards, and it says nothing about a notice a viewer would see.

3What each of them leaves out

The gaps are as informative as the statements. The system card states no route to remove the visible mark, which is recorded as not stated rather than as impossible; the marking page describes no visible layer at all, and no removal route either. Neither silence is filled in from a pricing page of the same vendor, and neither is read as a denial.

That is the discipline this record applies to every entry, and it matters most exactly here. A provenance scheme is documented in the place a vendor chooses, and a scheme described in one document may be documented differently in another; a reader comparing two of them is comparing two documents rather than two products.

4Which duty each kind of mark speaks to

The article splits the two audiences. Providers must mark synthetic audio, image, video and text in a machine-readable format, which is the audience a signed layer or an embedded signal answers. Deployers must disclose content that is a deep fake, narrowed for evidently artistic, creative, satirical or fictional work, which is the audience a visible notice answers. It applies from 2 August 2026, and the article also looks to codes of practice to carry the technical detail of detection, marking and labelling.

Keeping the two columns apart is not pedantry. A product providing one kind of mark has not thereby provided the other, and a buyer reading a supplier's documentation as if it settled both is holding a claim where a duty needs a sentence. Whether any arrangement satisfies a paragraph is not decided here; both rows are quoted, both are dated, and the conclusion belongs to whoever knows the deployment.

5What the threads counted

The collection behind this column counted both names across one window: 11,729 posts naming Sora, carrying 4,662 comment mentions, and 4,456 for Veo with 705. Seventy-eight posts put the two against each other, as a question of look and cost rather than of provenance.

The posts quoted below belong to that argument, and the record carries them without treating either name's popularity as evidence about its marking. A count says how often a name comes up; the rows above say what its vendor wrote down, and the two are kept apart on purpose.

6What each maker's own pages state

What each maker's own pages state, read 2026-10-13.
MakerWhat its own pages stateRead on
Google FlowGoogle's models: Veo 3.1 (native audio), Nano Banana, Gemini Omni; an agent and Scenebuilder2026-10-13
SceneMixer“Responsibility for what you generate and what you fed in sits with you, and our liability is capped in the terms.”2026-10-13
SoraApp discontinued April 26, 2026; API discontinued September 24, 20262026-10-13

Inclusion rule. Rows are the makers this page reads, each on its own public pages, plus one pipeline this record follows. A cell carries that maker's own wording for the point; a page that does not address the point is written as unstated rather than read as a denial. Order. Alphabetical by maker name.

Which columns the source fillsFilled where the page behind the row names something in that column, hollow where that page is silent. Silence is recorded rather than filled in.Which columns the source fillsSora, per its system cardSora, per itssystem cardGoogle SynthID, per DeepMindGoogle SynthID, perDeepMindArticle 50, as the Explorer prints itArticle 50, as theExplorer prints itThe machine-readable layerThe machine-readable layer — Sora, per its system card: C2PA metadata on all assets, listed as providing verifiable originThe machine-readable layer — Google SynthID, per DeepMind: An invisible watermark embedded across Google's generative modelsThe machine-readable layer — Article 50, as the Explorer prints it: Providers must mark synthetic audio, image, video and text in a machine-readable formatThe visible layerThe visible layer — Sora, per its system card: A moving watermark on videos downloaded from sora.comThe visible layer — Google SynthID, per DeepMind: Not stated on the page readThe visible layer — Article 50, as the Explorer prints it: Deployers must disclose a deep fake, narrowed for evidently fictional workWhat can check itWhat can check it — Sora, per its system card: Internal detection tools, kept in-houseWhat can check it — Google SynthID, per DeepMind: Designed to stand up to cropping, filters and frame-rate changesWhat can check it — Article 50, as the Explorer prints it: Codes of practice on detection, marking and labelling are to be encouragedThe date carried by the readingThe date carried by the reading — Sora, per its system card: 2026-09-22, the system cardThe date carried by the reading — Google SynthID, per DeepMind: 2026-09-12, the marking pageThe date carried by the reading — Article 50, as the Explorer prints it: Applies from 2 August 2026, per Article 113
Fig. 2 Filled where the page behind the row names something in that column, hollow where that page is silent. Silence is recorded rather than filled in.
Two vendors' marking schemes beside the article's own rows on marking.
Read for each of the threeSora, per its system cardGoogle SynthID, per DeepMindArticle 50, as the Explorer prints it
The machine-readable layerC2PA metadata on all assets, listed as providing verifiable originAn invisible watermark embedded across Google's generative modelsProviders must mark synthetic audio, image, video and text in a machine-readable format
The visible layerA moving watermark on videos downloaded from sora.comNot stated on the page readDeployers must disclose a deep fake, narrowed for evidently fictional work
What can check itInternal detection tools, kept in-houseDesigned to stand up to cropping, filters and frame-rate changesCodes of practice on detection, marking and labelling are to be encouraged
The date carried by the reading2026-09-22, the system card2026-09-12, the marking pageApplies from 2 August 2026, per Article 113

Inclusion rule. Cells are what each source states, taken from the source named in the header. A row a source does not address is written as unstated rather than completed from the other vendor's documentation. Order. As the rows are listed above.

7What the threads counted

Two names, counted over one window, and the arguments that put them against each other. The posts quoted after the tables are about how the tools look and what they cost, which is what the comparison mostly carries.

Posts and comment mentions for the name on this page, collected 2026-10-14.
NamePostsComment mentionsPositiveNegative
Sora1172946621112452
Veo445670521178

Inclusion rule. Names the collection counted and that this page is about. The tallies come from the same posts, and a post arguing with itself can land in both. Order. Descending by posts.

How often two names came up against each other in the material read.
NameAgainstTimesWhat the argument is about
SoraVeo78Counted without a line

Inclusion rule. Pairs that name a maker on this page and carry a count in the collection. Order. Descending by the count.

Is anyone still using Veo 3.1?

r/VEO3, collected 2026-10-14

Would cheaper Veo 3.1 with free tries win you back?

r/VEO3, collected 2026-10-14

8Where the other one fits a schedule better

  • The provenance has to travel as signed metadata — C2PA metadata on all assets is a standard a receiving platform can read without asking the vendor, which suits a pipeline that hands files to someone else.
  • The signal has to survive an edit — A layer designed to stand up to cropping, filters and frame-rate changes answers the failure mode a metadata layer runs into the moment a file is re-encoded.
  • The question is whether anyone outside can check it — Tools kept in-house and robustness claims written for third parties are different answers to the same question, and this record keeps them in separate rows so the difference stays visible.

Written for the search "sora vs veo". Beside it: Google Flow's terms and genre bans.