SenseDefend

Synthetic-media instruments, by article and effective date

Two entries that answer one column differently

Each page takes one column and two entries whose published answers to it pull in opposite directions. Pairs that agree are not filed, because a page saying both vendors do the same thing helps nobody. As of 2026-09-12.

What makes two entries worth setting side by sideTwo published answers to one column are filed as a pair when they would lead a reader to different decisions. Two answers that match are not filed, however neat the symmetry looks, because the page would report only the symmetry.Do the two published answers pull in different directions?Opposite answersFiled as a pairA flag defaulting to off against a switchthat ships on; a price against a policySame answer, different wordsNot filedTwo API references both documenting anoptional flag that defaults to falseWhy some obvious pairings are missing
Fig. 1 The selection rule is strict on purpose: a comparison with nothing to compare is the easiest kind of filler to write.

A register makes sixteen entries look like sixteen comparable positions. Most of the time they are not: one entry is a policy, several are technical descriptions, and the rest are prices. Setting two of them against each other on one named column is the shortest way to show that the difference is real and where it lies.

The selection rule is deliberately strict. Two API references that both document an optional flag defaulting to off are not a pair, however convenient the symmetry would be, because the page would have nothing to report beyond the symmetry itself. A flag that defaults to off against a switch that ships on is a pair.

Neither side is scored. What each page does is name the column, quote both vendors, and say which of the two duties in the article each answer bears on. Where the two answers turn out to bear on different duties, that is the finding and the page says so.

1The pairs

  • SynthID and SceneMixer — One entry describes a signal inside the content with no removal documented.
  • Sora and Pika — A system card naming a standard applied to every asset, against a pricing page that never mentions the container at all.
  • Firefly and ElevenLabs — A manifest attached beside the pixels, against a pattern mixed into the sound itself.
  • Nova Reel and Designer — Two entries adopting the same provenance standard and bounding it differently: one by a version, the other by a named part of the product.
  • AudioSeal and SynthID — One entry claims detection down to the sample; the other claims survival through cropping, filters, frame-rate changes and compression.
  • Wan and Firefly — Open weights whose terms ask nothing about marking, against a hosted product that writes credentials into everything it makes.
  • SceneMixer and Pika — A switch anybody logged in can flick, against a boundary that only a purchase crosses.
  • Kling and Hailuo — A brand mark applied unless a paid membership removes it, against a label that appears only when an individual request asks for one.
  • Sora and Runway — A described moving watermark tied to two named download surfaces, against a mark inferred from a phrase missing on a free plan's column.
  • Synthesia and HeyGen — Two avatar platforms on the same layer: one names conditions including an API test flag and leaves the list open, the other names two prices.
  • Wan and SceneMixer — One entry quotes the words the mark renders and names the corner.
  • Firefly and Kling — One page was read for a mark in the frame and records that none is described.
  • LTX Studio and Pika — Two pricing pages gating the same layer at different heights, and two free-tier cells filled by exactly the same inference from a missing phrase.
  • Runway and Synthesia — One entry's position is read from a phrase missing on a plan table.
  • SceneMixer and HeyGen — A switch inside the product against a purchase at a named price.
  • Hailuo and Kling — A parameter carried by every individual request, against a benefit attached to a membership.
  • Synthesia and Wan — Upgrading and generating the video again, against setting a boolean on the next request.
  • SynthID and Pika — One entry documents no way at all to take its mark off.
  • Nova Reel and Runway — An entry that applies marking to all output with no removal documented, beside one that lists removal on its paid plans.
  • ElevenLabs and Synthesia — No removal documented for an embedded audio signal, against a stated case where a mark cannot be taken off a finished video.
  • Sora and Designer — Detection tools one vendor calls internal, against a named public site that anybody holding the file can open in a browser.
  • ElevenLabs and Nova Reel — A detector limited to one vendor's own marks, against credentials that any public verification tool can inspect.
  • Firefly and Sora — A coalition given as over 3,300 members, against detection tools a vendor describes as internal.
  • AudioSeal and ElevenLabs — A published method anybody may implement, against a working detector scoped to one vendor's own marks.
  • Sora and Nova Reel — Both write manifests under the same specification.
  • SynthID and Synthesia — A signal built to survive somebody else's handling, against a mark a customer cannot take off a finished file of their own.
  • AudioSeal and Firefly — A signal inside the content, against a manifest beside it.
  • Designer and SynthID — One claim is bounded by a named set of features; the other spans a whole family of products with no product and no version named anywhere on the page.
  • ElevenLabs and Sora — One entry says models from elsewhere in its own product are generally not marked.

A pair is filed when the two published answers would lead a reader to different decisions.

Elsewhere in the record: EU, Duties, Generators, Statements, Fields, Questions, Terms, Learn, Data. How an instrument is read is set out on the sourcing page.