Open the stack, look past the top-pick thumbnail, and select the specific photos you actually want. The thumbnail is one image, not the whole group. Then write down each chosen file and where it came from, count the real chosen files, and build the batch from that list. Do not treat the cover photo as a stand-in for the stack, and do not treat it as a duplicate or a face-identity result.
Find public social profile clues with our TraceSeek app.
Why the thumbnail is not the input set
A stack in Google Photos gathers similar backed-up photos and shows one of them as the top pick, which the user can change. The top pick is not a favorite, and it is not a summary of everything in the stack. That matters for search: if you build a batch from what you see on the cover, you may be searching one image while believing you searched several, or missing a version you meant to include. Google's help says that in the Photos view, when sharing or adding stacks, the Selected items only option applies to the top pick, while the Includes photo stacks option applies to all stack items. Two selections in the same stack can therefore contain different pictures. [Google Photos: top picks and stack selection]
- Open the stack and count the images inside it before deciding anything.
- Note which image is currently the top pick.
- Check the options shown in your Google Photos App version to see whether your selection takes the cover only or the whole stack.
Inspect each image, then choose deliberately
Work through the stack and look at each image on its own. Decide which ones are permitted for your batch and which are not. A useful habit is to ask three separate questions: what does this image show, where did it come from, and what am I allowed to do with it. Keep those answers apart. The fact that two photos sit in one stack tells you the library grouped them as similar; it tells you nothing about the people, events or source behind them. A cropped or edited copy is still a separate input file, not a duplicate you can quietly drop.
- For each image, record the filename or a short description and its source context.
- Mark images you are excluding and say why in one short note.
- Choose the exact files you will use rather than accepting the default selection.
Count the actual chosen files
After choosing, count what you selected. If selecting the cover pulled in only one image, your batch is one file. If selecting all stack items included several, your count should match. Write the number down next to the list and keep them together. Counting is not a formality: it shows whether the batch reflects your decision or the stack's grouping. Grouping similar photos into a stack does not change available storage, so decisions about storage and decisions about batch content are separate matters.
| observation | limit | next step |
|---|---|---|
| The stack shows one thumbnail as its top pick | A cover image does not represent the other stack items | List and select each image you intend to use |
| Two images look almost the same | Visual similarity is grouping, not proof of identical files or of who appears | Keep both entries if both are permitted, and label each with its source |
| The selection options differ between sharing and adding | Which items a selection includes can vary | Check the options shown in your App version and confirm the count after selecting |
Keep the source context with every file
A bare image is a weak input. Beside each chosen file, note where it came from, how it was obtained and what it is meant to test. That note is what lets you interpret a result later. Public username and image searches can surface public social-profile clues, but a match does not guarantee coverage, and it does not verify identity, ownership or current activity. Treat a surfaced profile as a lead to examine, not a conclusion. This is a limit of the method, not a flaw in your notes.
- Record the source beside each file, even when the source is obvious.
- Do not merge two files into one row just because they look alike.
- Keep excluded copies in the same list, marked as excluded.
What this step does and does not settle
Input inspection settles a narrow question: which files are going into the batch, and how many. It does not settle whether any of them appears elsewhere online. Image-matching search can look for versions of a public image, and AI-assisted public-profile analysis can help read public pages, but neither one proves who is in a photo or what someone intended. Do not use a match, a badge, a privacy setting or a similar photo as evidence of identity, motive or safety. Separate what you observed from what you are still deciding. Suppose, hypothetically, a stack holds four pictures of one street scene; after inspection you might keep two and exclude two, and your batch should then contain two files with two source notes, nothing more.
- Note any mismatch you find between an image and its stated source.
- Stop the batch for that image until you can record its real provenance.
Record the limit and stop
If a source is missing, private, mismatched or ambiguous, write that limit down and stop drawing conclusions from that image. If you cannot establish that an image came from a permitted public source, drop it from the batch instead of guessing. Review the list where the facts are missing and keep those entries small and visible. Do not attempt to obtain private material or to work around a missing source; a stopped item is a finished decision, not a task you left undone. When the list is complete, build your TraceSeek batch from the chosen files and their notes, and keep the count beside them.
- Close each ambiguous item with one sentence describing what is missing.
- Rebuild the batch only from files whose source context is complete.
A couple more questions
Does choosing the top-pick thumbnail search the whole stack?
No. The top pick is one photo inside the stack, and Google's documentation distinguishes selections that apply only to it from selections that include all stack items. Check the options shown in your App version and confirm which images are selected before counting.
Is a stack a set of identical files?
Not necessarily. Stacks group similar backed-up photos, and similar can mean cropped, resized or otherwise edited versions. Inspect each image and treat it as its own input with its own source note.
What should I do if one image in the stack has an unclear source?
Record the exact limit, such as a missing origin or an intermediate copy, and leave that image out of the batch until the source context is clear.
Does a public image match confirm who is in the photo?
No. A surfaced public profile is a lead to examine, not proof of identity, ownership or current activity. Keep observations, their limits and your next decision separate.
Sources & editorial notes
Official references checked on October 24, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.