Vertical stacks: great for step 1→N thumb scrolling—fatal when frame order drifts from the real click path
`vertical-photo-stack` serves support repros, release timelines, and mobile vertical reading. Risks include step numbers that do not match actual navigation, uneven window heights that make gutters look crooked, and IM clients that crush long captures. Normalize logical width, keep consistent segment spacing, and write environment (browser, role, branch) outside the pixels—faster than arguing in thread.
`vertical-photo-stack`: write a one-line environment summary, normalize width and gutters, then split if IM compression kills legibility
- Above the first panel, text-lock browser/version, role, branch, and repro date; import shots in true click order and scale to one logical width. When mixing dark apps and white admin pages, insert a labeled divider instead of hard-stitching into one continuous background.
- Use vertical spacing and large step numbers; verify each panel still shows the button you tap next—not half a button at the bottom edge. Dry-run inside the target IM; if the whole strip mushes, export “part A/B” with continued labels.
- Name files with ticket id and version; redact before merging so emails in the seam are not missed. Add a plaintext bullet recap under the image for search and accessibility teammates.
Vertical merge FAQ: IM compression, step order, dark/light seams, external redaction
Looks sharp in Feishu, turns mosaic in WeChat—resolution or forced downscale?
Long-edge pixels or MB weight usually trigger recompression. Measure both against your internal cap, then split segments, modestly shrink the canvas, or provide a cloud link to the lossless original. Test on the receiver’s client.
Engineering cannot follow the chain but QA insists order is right—missing step or drifting labels?
Screen-share walkthrough against numbers; add prose like Settings → Billing → Export for implicit steps such as cached logins. Capture missing actions instead of debating the merge tool.
Dark app stitched to white console—dirty halo at the seam even on white background. Source fix?
Luminance jump: add a neutral band explaining themes, or rim-light dark captures slightly before merging. Stay in sRGB throughout to avoid surprise casts.
iPhone and Android widths differ—vertical stack looks like stairs. Avoid hand cropping?
Batch center each capture on a shared canvas width with symmetric side gutters rather than stretching one side. Label segments when mixing landscape and portrait flows.
Client-bound long capture includes internal codenames—how to redact without unreadable gray blobs?
Use gray bars plus text like PROJECT-A instead of solid blocks over entire lines; mask only URL queries while keeping domain tiers. Ship internal vs customer variants rather than one ambiguous file.