Skip to main content
QikTools™
Content Credentials checker

Was this made with QikTools?

Check any picture, video, audio file, PDF, Word, PowerPoint or Excel document or ZIP pack — or paste a text. If QikTools made it, you’ll see when, with which tool, and how it was marked as AI-generated. We never show who made it.

Files are checked in memory and never stored. We never show who made a file.

What we check

The exact file

A file's SHA-256 fingerprint is compared with every file our servers have delivered. A match means it's byte for byte what we made.

Content Credentials

The signed C2PA manifest: who signed it, whether it still matches the file, whether the signer is on the C2PA Trust List, when it was signed (trusted timestamp), and whether it says the file was made with AI.

Embedded metadata

The IPTC “made by a trained algorithm” tag and the unique generation ID we write into every picture, video, audio file and PDF we sign.

Invisible watermark

Most pictures our servers make carry an invisible watermark (Adobe TrustMark). It's designed to survive screenshots, re-compression and resizing, so a copy with its metadata stripped can often still be traced to its generation. Transparent, very small, very large, very wide or animated pictures don't get one.

Visual match

When nothing else is left, a visual fingerprint can still show a picture looks like one we made. That's a hint, never proof.

Text fingerprint

Pasted text is compared, word for word or passage by passage, with one-way fingerprints of the text our tools generate — never the text itself. It finds exact copies, excerpts, lightly edited copies and generated passages inside a longer text.

Signed text marks

A text file exported from QikTools (.md, .html, .txt, .vtt, .json) carries a machine-readable AI mark, signed by QikTools when we recognise its words. The check confirms the signature and whether the text changed since.

Signed document and pack marks

PDFs, Word, PowerPoint and Excel files, and ZIP packs from QikTools carry an AI mark signed by us. Drop one here to see when it was signed, with which tool, and whether the file — or every file in the pack — is still exactly what we signed. Your device reads the file; only its mark and fingerprints are sent.

What a result tells you

Made with QikTools
The file came out of QikTools: exactly as delivered, signed by us and unchanged, or traced by its generation ID or watermark.
Label
A visible “AI-generated” mark on realistic pictures and videos. Audio in a cloned voice, and AI speech delivered as audio (for example from AI Voice Studio), starts with a short spoken disclosure (“This audio was generated with AI.”); videos with AI speech carry the visible label.
Content Credentials
A tamper-evident record, signed with our certificate, of how the file was made. If the file changes, the signature stops matching.
Model
The AI model that made it, when we recorded one. Files from our editors also list the earlier generations they were made from.

Trusted or valid? Credentials are “trusted” when the signer’s certificate is on the C2PA Trust List. QikTools isn’t on that list yet (we haven’t completed the C2PA Conformance Program), so other checkers may show our credentials as from an unknown source. They are still valid: a valid signature means the file hasn’t changed since we signed it, and this page confirms it was signed by QikTools.

How QikTools marks what it makes

Realistic pictures and videos carry a visible “AI-generated” label in the bottom-right corner. Audio in a cloned voice, and AI speech delivered as audio (for example from AI Voice Studio), starts with a short spoken disclosure (“This audio was generated with AI.”); videos with AI speech carry the visible label. Every file our servers make also carries embedded metadata and a unique generation ID; most pictures an invisible watermark; and, where the format allows, signed Content Credentials, timestamped when our timestamp service is available. Files you export from our editors are signed the same way when signing succeeds. Pictures of realistic people are also tagged “contains-synthetic-performer” for marketplaces. Removing any of these marks is against our terms.

Read about our AI labels and Content Credentials

How QikTools marks AI-written text

Text our tools write is AI-generated, and the EU AI Act asks us to make it recognisable by machines and checkable by anyone. Here’s how.

  • Downloads carry a machine-readable AI mark where each format keeps its details: Markdown front matter, HTML meta tags and schema.org data, JSON entries, Word, PDF and PowerPoint document properties, a note in WebVTT captions, or a short labelled line at the end of a .txt file. When we recognise the words of a downloaded text file, its mark is digitally signed by QikTools, so anyone can confirm it and see whether the text has changed since.
  • Copies carry the same mark in their formatted (HTML) version. The plain text stays exactly the text.
  • Plain text loses its details once it’s copied, so our servers keep a one-way fingerprint of each finished piece of about 30 words or more — never the text, and nothing about who made it: just the tool, the model and the day. This checker compares against those fingerprints, which we keep for 3 years.
  • No hidden characters. We don’t slip invisible characters or look-alike letters into your text: they confuse screen readers, search and character limits, and they disappear with a single clean-up.
  • Not marked: small edits to your own writing (spelling, grammar, a word or two — under 15% of it), code and formulas, transcripts, and translations of your own text.

A check can’t recognise text that has been heavily rewritten or translated, and “no match” never proves a person wrote something. Removing these marks to pass AI text off as human-written is against our terms.

For developers: signed marks are JWS (RFC 7515) over the SHA-256 of the text’s canonical form, verifiable with the certificate chain at /api/provenance/text/certs. The one-line form reads qiktools-ai-text: v=1; ai=true; dst=trainedAlgorithmicMedia; tool=…; date=…; verify=…; sig=….

How QikTools marks documents and ZIP packs

PDFs, Word, PowerPoint and Excel files and ZIP packs can’t carry Content Credentials the way a picture or a video can, so we sign a short statement instead, with the same certificate.

  • Where the mark lives. A PDF carries it in its metadata, a Word, PowerPoint or Excel file in its document properties (AI-generated, generator, date and a link to this page), and a ZIP pack as a file called QIKTOOLS-AI-PROVENANCE.json that lists every other file with its SHA-256 fingerprint and whether AI made it.
  • What it says. That the file came out of one of our tools, on what date, how AI was involved (the IPTC “digital source type”) and a fingerprint of what we signed. It never names a person, an account or your file’s own name, and a signature doesn’t say the content is true or checked.
  • Your file stays with you. To sign it, your browser sends only the fingerprint (for a pack: the names, sizes and fingerprints of its files). To check it here, the file is read on your device and only its mark and fingerprints are sent. Nothing is stored.
  • Changed since? Edit the document or the pack and this page says so: “made with QikTools, then changed”, and for a pack which files changed, went missing or were added. If a download was made while signing wasn’t available, the AI mark is still in the file and this page says “Marked as AI-generated by QikTools, not signed”.

For developers: the signature is a JWS (RFC 7515) of type qiktools-ai-mark+jwt, verifiable with the certificate chain at /api/provenance/text/certs. A PDF’s is the qiktools:Mark attribute of its XMP and covers the PDF as it was built (the mark is appended after it, and nothing else may follow); an Office file’s is the ProvenanceSignature custom property and covers the SHA-256 listing of every part except the document properties.

Free detection API

Platforms, newsrooms and researchers can run the same check from their own systems, free, with no account or key. Send the file itself (up to 25 MB) or a link to it; you get back JSON with the verdict, the match, and what we recorded — never who made the file. Nothing you send is stored.

curl -X POST https://www.qiktools.com/api/verify \
  -H 'Content-Type: application/octet-stream' \
  --data-binary @picture.jpg
curl -X POST https://www.qiktools.com/api/verify \
  -H 'Content-Type: application/json' \
  -d '{"url": "https://example.com/picture.jpg"}'
curl -X POST https://www.qiktools.com/api/verify/text \
  -H 'Content-Type: application/json' \
  -d '{"text": "Paste the text to check here…"}'

Limits per network address: 12 checks a minute and 300 a day; 6 links a minute. Pictures, video, audio and PDFs. The answer’s verdict is one of verified, altered, similar, unrecognised, browser_export, other_ai or none.

Texts (up to 200,000 characters, same limits): the answer’s verdict is exact, match, partial, none or too_short, with a confidence, the share that matches, and the day and tool. Add "receipt": true for a signed copy of the result. The text is fingerprinted in memory and forgotten.

Seen a QikTools file used to deceive or harm someone?

Tell us, with the link or the file’s generation ID. Intimate or morphed images of real people are handled first, within hours.

Report misuse