
One visible Google Photos thumbnail can represent a stack containing several photos. In the documented Android sharing workflow, “Selected items only” applies to the top pick, while “Includes photo stacks” includes every item in that stack. Inspect the stack and the sharing choice before sending a reference collection to an editor.
Key Takeaways
- A stack cover and the full set of photos are different selections.
- Use the stack grid when you need a particular subset.
- Confirm the recipient received the intended images, not merely the expected number of thumbnails.
Inspect what the thumbnail represents
Open the stack and review the filmstrip or its grid. Google's Android Photos-view guidance explains that similar photos can be grouped behind a suggested top pick. Grouping changes the view; it does not reduce the collection's storage use.
Write down whether the recipient needs the cover photo, several chosen references or the whole group. That decision should come before invoking Share. A thumbnail count in the main Photos view is not a dependable inventory of the files behind those stacks.
Choose the scope for this action
When sharing a stack from Photos view, inspect the prompt. Google's current documentation describes two choices:
| Choice | Documented scope |
|---|---|
| Selected items only | The stack's top pick |
| Includes photo stacks | Every item in that stack |
This comparison applies to the documented sharing flow. Do not infer that every other action uses the same prompt or default. A choice appropriate for an archival handoff may be inappropriate for a small approved reference set.
Select a subset inside the stack
For selected members, open the stack, use the thumbnail menu and choose Multi-select. Select the photos you intend to share there, then invoke Share. Check the actual selected pictures instead of assuming changing the top pick selects all useful variations.
The portrait-burst guide helps judge expression and clarity. That editorial decision does not establish which members the app's next sharing action will include. Keep the quality decision and the sharing scope connected in your own record.
Try a small, explicit handoff
Consider a proposed stack containing a frontal portrait, an alternate angle and an unwanted rehearsal expression. The editor needs the first two only. Sending the entire stack adds an unapproved reference; sending only the top pick omits the angle.
Open the group, select those two specific members and check the receiving set. Ask the editor to identify the actual images, not simply confirm that a link opened. This is an acceptance example, not an account operation performed for this guide.
Use an approved-version record to connect the chosen references with the intended task. Keep unnecessary personal variations out of that handoff rather than relying on the receiver to guess which thumbnail is approved.
Accept the receiving collection
Compare the delivered images with your short reference list. Confirm both that required views are present and that unrelated members were not added. If the set is wrong, correct the sharing scope and identify the replacement clearly. The shared-copy guide explains why changing later access does not recall files already downloaded.
Accept when sender and recipient can identify the same intended reference set. The stack's suggested cover is useful navigation, but it does not approve every member or establish that a particular editing app received the correct inputs.
Related tasks
- Which Burst Photo Should I Choose as My Portrait Reference?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Does Revoking a Review Link Remove the Images Someone Already Downloaded?
Sources and scope
- Google Photos: Organize Your Photos View on Android: A Photos-view stack has a top pick. For the documented sharing action, Selected items only uses the top pick and Includes photo stacks uses all members; the stack grid permits a selected subset.
Based on the complete official Android documentation captured October 29, 2026. The example and acceptance checks are proposed, not a tested share or observed account incident.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.