Ideogram check: metadata beats reading the lettering

Ideogram is known for rendering legible text inside images, which makes it a useful case for explaining why visual reasoning has stopped working. The old tell — garbled lettering — is exactly what this generation of models fixed, so an image with clean typography tells you nothing about its origin. What can still be checked is the file: XMP and EXIF tool fields, and the download file name. AICheck365 reads those in your browser and reports which field each hit came from.

Short answer: read the fields, not the typography

Check the original download for tool strings in XMP and EXIF — Software, CreatorTool, Credit — and note the file-name pattern. These are unsigned, so they can be edited or stripped, and a re-encode usually removes them. Legible or well-kerned text in the image itself is not evidence either way, in either direction.

Sample status and evidence profile

Bundled Ideogram sampleNot bundled yet. This page does not claim a reproduced Ideogram test until a licensed original can be published alongside the other samples.
What the parser matchesThe tool-pattern matcher recognises Ideogram strings in metadata field values and in file names, and reports which field produced the match.
Evidence levelUnsigned descriptive metadata: useful and readable, but weaker than a verifiable C2PA manifest.

Signals to Check

XMP / EXIF fieldsCreatorTool, Software and Credit can name the generating tool when the original export is intact.
File nameDownload names sometimes carry a platform pattern or identifier. Useful context, trivially renamed.
Text renderingNot a signal this tool uses. Clean typography is what current models produce, so it cannot separate generated images from photographed or designed ones.
C2PA Content CredentialsNot something to count on here. A signed manifest, if present, was most likely added by a later editing step.

Why "the text looks right" cuts both ways

Garbled lettering was once a dependable tell, and its disappearance is often described as models getting better at text. The more useful framing is that the heuristic was never measuring what people thought: it flagged a rendering limitation, not synthetic origin. Now that the limitation is largely gone, clean text carries no signal — and its converse never worked either, since photographs of real signage get mangled by compression and low resolution all the time. This is precisely the gap that file-level evidence is meant to fill.

What to do when the fields are empty

Because these fields are unsigned and easily stripped, an empty result is the normal outcome for anything that has been shared. A few follow-ups help more than re-running the check:

  • Ask for the file as downloaded from the platform, before it was posted or forwarded.
  • Look for the highest-resolution published copy — social platforms re-encode downward and drop metadata on the way.
  • Check whether the file is a screenshot: those carry the capture tool's own metadata and none of the original.
  • Compare against platforms that sign their exports, where a valid manifest can settle the question outright.

Limits

Use the EXIF/XMP reader for the descriptive fields; run the full detector when you also want C2PA and PNG parameters checked.

FAQ

How do I check whether an image came from Ideogram?

Read the original download's XMP and EXIF fields for a tool name, and note the file-name pattern. The check is free, runs in your browser, and the file is never uploaded.

Can I tell from the text in the image?

No. Rendering legible text is something current models do well, so clean typography is not evidence of anything — and garbled text in a real photograph is common once compression gets involved.

Does Ideogram add C2PA Content Credentials?

Do not count on it. The dependable signals here are descriptive metadata fields, which are readable but unsigned.

Are files uploaded for checking?

No. Parsing runs locally in your browser through Rust compiled to WebAssembly.

Sources and verification records

Important: not finding this platform’s origin signals does not rule out that the file was generated by it. The provenance may never have been written, or it may have been removed during export, compression, transcoding, or screenshotting.