Someone Using Your Photos? How to Find Fake Accounts and Report Them

Save the account URL and the specific use of your picture, then choose the platform report that fits what you observed. If there are threats, intimate images or financial harm, use official support first. You do not need to identify an account operator or complete a search before seeking help.

A friend sends a screenshot of a profile with your face and an unfamiliar name. It is reasonable to feel unsettled. Start with that concrete page; there is no need to accept a follow request, open a payment link or confront whoever is behind it.

For Australian readers, eSafety's catfishing guidance explains saving the profile, reporting it to the service and blocking unwanted contact. For intimate-image threats, go straight to eSafety's sexual-extortion support steps. The support section below separates that situation from ordinary photo reuse.

When	Useful next step	Avoid
Right now	Pause harmful requests and record the known URL	Replying to prove who you are
When safe	Save relevant lawful context and submit a platform report	Posting a public accusation
After reporting	Keep the receipt and review account security	Assuming receipt means removal
Later	Follow the service's response or official support guidance	Searching indefinitely for every possible copy

This guide focuses on your own photos and a bounded reporting task. If you already have an Instagram account to assess, the known-account Instagram guide separates public profile claims from risky messages.

For stolen soldier pictures, the military romance-scam guide explains how to separate the person pictured from the account making a claim.

A copied photo, an account pretending to be you and a similar-looking face are different findings. Read the page's claims and context before choosing a report category. Describe what the account shows or says, while leaving its operator, motive and legal status unresolved unless an appropriate authority establishes them.

Use a small claim log. In one column, write the observation: your photograph appears as the avatar, the bio uses your name, or a message asks for payment. In another, write what remains unknown, such as who controls the account or where a repost began.

• Possible impersonation: the account presents itself as you, rather than merely showing your image.
• Other reuse: a page displays your picture but may be a repost, credited article, advertisement or another use requiring a different complaint.
• Uncertain resemblance: the image looks similar, but you cannot establish that it depicts you.

These are working categories for a private report, not legal conclusions. A credit does not settle permission, and a missing credit does not identify the uploader. If a rights dispute matters, ask the relevant platform or a qualified adviser which process applies.

For example, imagine a public page using your photograph beside a different name. Record both facts without writing that the named person stole it. The name could be invented, copied or unrelated; this hypothetical example illustrates why image evidence and account-control evidence must remain separate.

eSafety describes accounts pretending to be someone else and directs people to platform reporting. Keep that task distinct from finding a person's address, employer or private contacts. None of those details is needed to report the page you observed.

Begin with an image search of one ordinary public photograph you are permitted to use. Consider public-web face search only if a narrow source question remains. Open the candidate page, record its context and stop at enough information for the report; neither search offers a complete inventory of your images.

1. Define the question. Write “Does this public page reuse my profile picture?” rather than “Who is this person?” If you already have the relevant account URL, proceed to documentation instead of searching again.
2. Choose an allowed image. Use your own non-intimate photo without children or unrelated faces. Do not upload private messages, identity documents or a screenshot containing another person's personal details.
3. Try image search. Google explains uploading a file or searching with an image URL. Its results can include similar images and websites with the same or a similar image; the source page still needs inspection.
4. Inspect the page. Compare the image with your original file and note the caption, handle and relevant claim. A thumbnail alone may omit the surrounding explanation.
5. Add face search only if needed. 221B's published methodology describes candidate public pages across different photos, with incomplete coverage and manual review. It excludes private accounts, messages and platform-internal data.
6. Close the task. Save relevant findings or record “not established.” Do not keep changing photos until the tool gives the conclusion you wanted.

The public-photo source guide gives a wider explanation of source context. For misuse reporting, keep the scope smaller: the particular account, photograph and claim at issue. Do not bypass a login, privacy setting or access restriction to fill a gap.

When a public source points to Instagram, the Instagram photo source guide explains how to check the link without trying to reach private content.

Image search looks for the same or visually similar pictures, while face search may return public pages containing a similar-looking face across different photos. Choose the method for the source question, not for a verdict. Neither establishes account control, permission, wrongdoing or that every relevant page has been found.

Your question	Useful first approach	What remains unresolved
Is this particular photograph reused?	Image search, then inspect the page	Permission and who uploaded it
Could a different photograph be relevant?	Optional permitted public-web face search	Whether the candidate actually depicts you
Is this account claiming to be me?	Read the profile and preserve the claim	Who operates it and why
There are no results	Record the limit and use the known account URL	Whether other copies exist

Google's image-search help describes websites containing an image or a similar image. It does not promise an original publisher or a complete history. An early page date, a search rank or a matching crop should not be treated as proof that one person copied another.

221B's source-review method likewise treats a score as a way to prioritise pages, rather than a probability of identity. A high score can still lead to an irrelevant page; several reposts can point back to one source chain. Read the actual image role instead of counting thumbnails as independent evidence.

The practical test is whether the page adds a relevant, checkable fact. If it does not, leave it out of your report. You can report an observed misuse concern without buying a search, and you can stop when the information remains uncertain.

Keep a small private record of the account, the relevant content and when you saw it. Include enough context for a platform reviewer to locate the issue, without collecting unrelated personal information. Follow official evidence guidance for harmful material; do not download or redistribute sexual images of anyone under eighteen.

Australia's eSafety evidence guide recommends recording web addresses, usernames, dates and context. It specifically warns against saving sexual images of people under eighteen. For that material, record its location and use official reporting rather than making another copy.

• Location: the exact profile URL, handle and relevant post URL; preserve unusual spelling rather than correcting it.
• Observation: a short factual description of the picture and claim, with the date, time and time zone of your review.
• Lawful context: screenshots of the relevant profile or message when safe and appropriate, without unrelated conversations.
• Your reference: the ordinary original photo or posting record if the service asks for it; dates alone do not settle ownership.
• Submission: the reporting reason you chose, confirmation number and any response from the platform.

A useful note could read: “On this date, this account displayed my profile photograph and described itself using my name.” That is more precise than “I found the scammer.” Leave the operator's identity blank unless you have direct, relevant evidence that the reviewing service requests.

Keep report material away from public comments and group chats. If a service requests identity evidence, reach its official help route independently and follow its instructions there. Do not send documents to an account claiming it can remove the page for you.

Use the official reporting process for the platform where the account appears, and select the reason supported by the page. An impersonation report concerns the account's claim to represent someone; other photo reuse may need another route. Keep the confirmation, and do not assume a report guarantees removal or a response time.

Instagram and Facebook

eSafety's Instagram guide links the platform's impersonation help, including in-app and online reporting. Its Facebook guide links content-reporting and account controls. Open the relevant help route immediately before submitting, because menus, eligibility and the evidence requested can differ.

Report the account and any relevant post or message using the available categories. Explain the observed claim in plain words, rather than adding uncertain names or facial-similarity scores. If someone sent you a screenshot, ask for the profile link through your existing trusted conversation, without asking them to confront the account.

TikTok, Tinder, LinkedIn and X

• TikTok: use eSafety’s TikTok reporting guide and follow the current instructions for your situation.
• Tinder: its impersonation guidance directs the affected person to a form with “Someone is impersonating me.” It explains how an authorised representative or someone who knows the affected person can proceed.
• LinkedIn: its fake-profile help describes the More → Report / Block flow and an impersonation reason. It also cautions that an incomplete profile is not automatically fake.
• X: read the authenticity policy and use the relevant reporting route for the observed conduct; a parody or fan label needs context rather than an automatic accusation.

Save the outcome separately from your original observations. “Report received,” “action taken” and “account unavailable” are different states. If a report is rejected, use the service's available review process and supply clearer relevant evidence; do not organise mass reports or chase unrelated look-alikes.

When photo misuse involves money, threats or account access, prioritise the affected service and official support for your country. Preserve relevant lawful evidence and stop unsafe requests. A face search cannot recover funds, resolve blackmail or identify an offender, so further searching should not delay the appropriate reporting or recovery route.

Australian support routes

Cyber.gov.au's identity-theft recovery guidance covers securing affected accounts, financial protection and reporting. Use it when there is actual identity misuse or account compromise, rather than assuming that a copied photo alone proves either. If funds or card details are involved, contact the financial provider through a known official channel.

For sexual extortion, eSafety's current Australian guidance says not to pay or send more intimate content. It directs people under eighteen to the Australian Centre to Counter Child Exploitation, and adults to the relevant platform and eSafety when an intimate image is shared.

Follow that page's age-appropriate help route rather than uploading an intimate image to a search tool. If there is an immediate threat to life or risk of harm in Australia, Cyber.gov.au directs people to call 000. Outside Australia, use your local emergency and official reporting services.

Keep support separate from investigation

Tell a trusted person what is happening if that helps you get support. You do not have to solve the account's identity or read every message alone. The purpose of a report is to provide relevant evidence to the people equipped to assess it.

Avoid contacting people shown in search results or asking strangers to investigate. They may be unrelated or also affected. Preserve the particular threat or payment request and use the official route; an unverified identity claim can distract from the conduct that needs attention.

Review your audience and contact settings, keep useful records and return to a self-check only when a concrete concern calls for it. Privacy controls can reduce exposure but cannot retract every public copy. Treat a quiet search as a limited observation, and choose a clear stopping point rather than continuous monitoring.

The Instagram and Facebook eSafety guides linked above describe visibility, tagging and contact controls. Review the settings that matter for your own use, and check your account-security options if you suspect access you did not authorise. A new privacy setting does not prove an existing public copy has disappeared.

• Reduce unnecessary exposure: check who can see ordinary posts and who can contact or tag you.
• Keep a focused record: store the report receipt and relevant URLs together, so you can respond to a platform question.
• Set a stopping rule: finish when the known page is documented and reported, or when the remaining question cannot be established.
• Use a specific follow-up: review a service response or a newly reported account, rather than searching on an open-ended schedule.

On 30 October 2026, the source review for this guide checked different tasks against different documents: Google's help for image-search output, platform help for reporting, eSafety for evidence and support, and 221B's published method for search limits. This was a review of documentation, not a search-accuracy test or a submitted impersonation report.

See how candidate source pages are presented

The walkthrough below shows the product's public-source review format. It can help you understand what a candidate page means before deciding whether a search serves your own narrow question. It does not demonstrate complete coverage, account ownership or a safety verdict.