“Fake app” check: how to verify a claim, image, or screenshot
About this check
If you are asking whether an app, image, or screenshot is fake, start with the exact thing you need to establish: what does this item claim, and what evidence supports it? A finished answer should not be just “looks real” or “looks fake.” It should identify the claim, show the sources checked, and make clear whether the evidence supports it, contradicts it, or does not settle it.
The manual check
First, separate the claim from the presentation. A screenshot may show a headline, a quote, a date, a number, or a post attributed to someone. Write down the specific statement you are checking rather than treating the whole image as one conclusion.
Next, inspect the original context if you can find it. Look for the account, page, publication, or document where the item supposedly appeared. Check the wording, date, surrounding text, and whether the source actually says what the screenshot claims. Do not treat a cropped image, forwarded message, or unattributed post as its own proof.
Then search for the key claim in exact or distinctive wording. Compare the results rather than relying on the first page you find. Look for sources that directly address the statement and note whether they agree, disagree, or merely repeat the same unsourced material.
For an image, examine what is actually being asserted. The question may be whether the image is authentic, whether it shows the claimed event, or whether the image has been paired with an unrelated caption. Those are different checks. A screenshot also needs a text check: read the words shown in the image and verify the claim they make, not just the appearance of the interface.
Finally, record the result with its limits. If the evidence supports the claim, say what supports it. If reliable evidence contradicts it, say what conflicts with it. If the available material cannot decide the question, leave it unresolved. A manual search should not turn missing evidence into confidence.
Where the manual method stops
Manual checking depends on finding relevant material, interpreting it correctly, and keeping the original claim separate from later commentary. It can become difficult when a screenshot has no source, an image is separated from its context, search results repeat one another, or available sources do not answer the precise question. In those cases, the honest result is not a forced yes or no. The claim may remain unverified.
That is the distinction a useful verification answer needs: a clear verdict, the evidence behind it, and enough uncertainty to show where the evidence ends.
A way to check it with VOM
VOM’s verification app is available at vom-app.com/app. It installs on a phone or desktop as an app and requires an internet connection.
VOM verifies claims using real-time web search and cites the sources behind each verdict. Its response includes a verdict, a confidence score, and the sources it used. A verdict can be true, false, or inconclusive. When the evidence cannot settle a claim, VOM reports it as inconclusive rather than forcing the answer into yes or no.
You can also upload an image for assessment. VOM reports whether the image is likely authentic, likely AI-generated, or unverifiable. If the image is a screenshot, VOM reads the text inside it, so the forwarded image can be checked without retyping the words.
The point is not to replace judgment with a label. It is to make the question specific, connect the answer to sources, and preserve uncertainty when the evidence does not support a stronger conclusion. VOM also supports natural back-and-forth conversations for everyday questions, learning, brainstorming, writing, and planning; it can turn a written idea into a generated image; and it offers local, world, and trending feeds of circulating claims. It answers in the language being used across its eight supported languages.