The Synthless mark

The badge is a link, not a claim. It points at a page that says what was checked, when, and by whom — so a reader never has to take the badge’s word for anything.

What the badge is

The badge is the verdict stamp, served as an SVG from synthless.com/badge/{id}.svg. It carries the verdict, the verification ID and the date it was issued.

It is generated on our side, from the record, every time it is requested. That is deliberate: the badge cannot say something the verification page does not. If an ID is revoked, every badge already embedded on every site changes to the struck-through form by itself. Nobody has to remember to take it down.

The two below are live — each one is the badge endpoint’s real output for that ID, exactly as it would appear on your own page.

Using the badge

Embed it with the snippet below, replacing {id} with your verification ID. The badge must stay a link to its own verification page.

Do not alter the badge image, its colours, or its proportions.
Do not host your own copy. A cached badge can outlive a revocation.
Do not place it next to a file it was not issued for. One badge, one file, one ID.
Do not use the mark, the wordmark or the stamp to describe Synthless itself as endorsing you.

What you may write

The badge says what was checked. Wording next to it must not say more than that.

Allowed

Declared human-made on Synthless
Checked with Synthless
Synthless ID SL-0000-0000

Not allowed

Verified not AI
AI-free
100% human
SynthID-verified
Synthless certified authentic

No file check can establish that a person made something; a declaration and an accountable name is what Synthless adds, and the wording has to say so.

When no detector can look

Most generative tools leave nothing behind that anyone can read. Midjourney and Stable Diffusion embed no watermark we can detect, and an image that has been screenshotted, re-encoded or passed through a messaging app has usually lost whatever content credentials it once carried. There is no check we can run, now or later, that reliably answers “was this made by a model?” for a file like that.

So a clean result here proves nothing. It means the specific things we know how to look for were not found — no AI watermark we can read, no content credential declaring generative AI. It does not mean none was used. Any service that tells you otherwise is selling you a confidence it does not have, and the cost of that false confidence falls on whoever is wrongly accused, or wrongly believed.

This is precisely why the declaration exists, and why it can be revoked. Where detection runs out, Synthless stops guessing and asks a named person to state plainly that they made the thing — knowing that if it turns out to be false, the ID is revoked in public, on the page the badge already points at. That is a weaker claim than detection pretends to offer, and a much more honest one: it is backed by someone who can be held to it.

Revocation policy

Every verification ID can be revoked. A revoked ID is not deleted: its page stays public, turns red, and shows the date and the reason. A badge that quietly disappears tells a reader nothing, and leaves the original claim standing everywhere it was copied.

An ID is revoked when any of the following is established:

The declaration was false — the work was generated or altered by AI.
The signer did not have the right to sign for the work.
The badge is used on a file the ID was not issued for.
The signer asks us to revoke it.

Anyone can report an ID from its verification page. A report is reviewed by a person; the signer is contacted at the email address they signed with and given the chance to answer, unless the file plainly contradicts the declaration. Revocation is recorded in the public revocations log.

Synthless does not revoke an ID because someone dislikes the work, or because a detector merely estimates that a file might be synthetic. An estimate is not evidence.