Select the original image
The browser reads supported file metadata locally. It does not run a SynthID detector or analyze pixel-level watermark signals.
This guide explains how a SynthID checker differs from an image metadata viewer, what a compatible detector may report, and how to interpret its limits before deciding what to do with an image.
This page only inspects supported metadata containers. It does not remove metadata or detect, remove, or verify SynthID watermarks embedded in image pixels. Reading EXIF or C2PA metadata does not test for a pixel-level SynthID signal.
To inspect or remove supported file metadata, use the metadata remover. It cannot tell whether SynthID is present. Open Metadata Remover
To check for SynthID, use an available compatible detector. This site does not provide pixel-watermark detection or removal.
Runs locally
or choose one from your device
JPG · PNG · WebP · HEIC/HEIF · AVIF · Up to 20 MB eachInspect supported EXIF, GPS, text, XMP, and embedded credential containers. Available fields vary by file; generator compatibility is not guaranteed.
Choose an image to inspect supported file metadata. This report does not test for SynthID.
The browser reads supported file metadata locally. It does not run a SynthID detector or analyze pixel-level watermark signals.
See supported EXIF, XMP, and credential fields that may be stored in the file. These are separate from a SynthID signal embedded in image pixels.
This report does not analyze pixels. If you need to check for SynthID, use an available compatible verification service and follow its stated media and coverage limits.
Google describes SynthID as an imperceptible watermark embedded directly into generated media. An EXIF remover or AI metadata remover works on file metadata; it cannot be presented as a SynthID watermark remover. A clean metadata report does not establish whether SynthID is present or absent.
Searches may combine OpenAI, Gemini, SynthID, and AI image watermark terms. A file may contain ordinary EXIF or Content Credentials, but this tool cannot infer its generator from a missing tag and cannot remove an invisible watermark encoded in pixels. We do not label an image as watermark-free after metadata cleanup.
Google says SynthID Detector access expanded globally in English for checking images, video, and audio made with Google AI or supported partners. Google also offers built-in verification in Gemini, Search, and Chrome for supported content. The available surface and coverage can vary, so check the provider’s current instructions and limits for the exact media you have.
A checker for SynthID has a different job from a metadata viewer. It needs to evaluate a compatible watermark signal in the media itself; reading EXIF, XMP, or Content Credentials cannot answer whether that signal is present.
A compatible service may report whether it found a signal it recognizes in supported content. Read the service’s notes about eligible media, supported generation sources, and confidence or coverage. A result applies only within that stated scope; it should not be generalized to every image, model, or watermarking system.
Metadata can describe a file’s camera, editing software, creator, or provenance records. These fields can be absent, changed, or removed during export. Their presence or absence does not establish whether SynthID is embedded in pixels. Likewise, a metadata cleanup report is not a watermark test and cannot confirm that an image is watermark-free.
If you need to inspect file details, use a metadata viewer and treat its report as a list of supported fields only. If your question is specifically about SynthID, use an available compatible verification service for that media type and follow its instructions. Keep the original file and record which copy was checked; resizing, screenshots, recompression, or platform processing can change the content presented to a detector. This site does not perform that pixel-level check or remove the watermark.
A detector’s supported input and the version of the file can affect what it evaluates. If the image has been resized, screenshotted, recompressed, or edited by a social platform, the result may apply to that processed copy rather than the original. When you need a meaningful record, keep an untouched original, submit the exact copy in question to the compatible service, and note the service and date alongside its stated limitations.
If the result matters later, note which file copy you checked, the verification service, the date, and the scope the provider describes. Preserve the untouched original and do not apply a result to a resized, recompressed, or platform-processed version. A detector’s result is limited to the input and signal it supports. It does not replace metadata inspection, and an empty metadata report is not a SynthID scan result.
A positive result means the service recognized a signal within the content and conditions it supports; it is not a general judgment about every watermark or the image’s authorship. A negative or inconclusive result also has limits: the image may be outside the detector’s supported media, source, or processing conditions. Do not treat either result as a universal guarantee. If the distinction matters for publication or review, retain the original file and consult the detector provider’s explanation of coverage before making a claim.
Keep the exact image copy and its source information, then look for a disclosure or provenance record from the person or service that supplied it. Recognized metadata may offer context about a workflow, but fields can be edited, removed, or omitted and are not a substitute for a compatible watermark check. A missing credential does not prove that an image is human-made, and a present credential does not by itself answer every authorship question. If you publish or review the image, describe what you could verify and leave unsupported conclusions open.
Use metadata cleanup for privacy and file hygiene. Follow applicable disclosure rules and keep provenance information when it matters.
Before cleanup, review the metadata report and note the supported fields that appear. After downloading the cleaned copy, inspect that copy again and compare the listed fields. A field marked removed confirms only that the supported metadata item was cleared from that output. It does not show whether a pixel-level watermark is present, absent, or still readable by a detector.
No. It cleans supported file metadata only. It does not modify image pixels to disrupt or remove SynthID, and it cannot verify whether a pixel watermark remains.
No. EXIF and many Content Credentials are file metadata. Google says SynthID is embedded into AI-generated media and is imperceptible to people. Removing metadata does not remove a watermark embedded in pixel values.
No. This page is read-only and reports supported metadata fields such as EXIF or credential containers. It does not remove file metadata, platform labels stored outside the image, or pixel-level SynthID signals. Use the metadata remover to create a cleaned copy of supported file metadata.
No. The report covers only metadata fields supported by this tool. It is not a SynthID scan, AI detector, or authenticity check.
No. A metadata checker reads supported file containers such as EXIF or XMP. A SynthID checker or detector must analyze a compatible pixel-level watermark signal. This site provides the first kind of inspection only.
Metadata cleanup does not test or remove SynthID. If you have access to a compatible detector for the relevant media type, use it separately and interpret its result within that detector’s stated limits.