Combine Images: before exporting one PNG, align orientation, canvas width policy, background strategy, and mixed-DPR screenshots
The tool stitches multiple images vertically or horizontally in the browser with spacing and background color, then exports a single local PNG—no server-side storage of your assets. Rework usually comes from pixels and clients, not “merge failed”: mixing 1x and 2x captures makes type sizes jump; alternating transparent PNGs with opaque phone shots often shows gray or black bands in Slack/Teams/WeChat previews. Ultra-wide horizontal canvases get aggressively downscaled and look mushy; vertical chains carry status-bar timestamps, clipboard leaks, or internal URLs. If reading order only lives in chat history, nobody can reconstruct the story next week. Document start point, width normalization, background choice, and redaction rules, then sanity-check inside the real IM or ticket viewer—not only in design tools.
How to use Combine Images: pick axis and order, normalize width or top alignment, then verify readability after client compression
- Rename or number sources in true read order; if Retina shots are included, decide whether to normalize to logical CSS width or physical pixels and pre-scale upstream. Pick one background policy—white, light gray, or all-transparent—and avoid sandwiching transparent panels between opaque ones unless intentional.
- Add gutters so step boundaries read instantly; confirm button feet and currency decimals are not clipped. For side-by-side reviews lock identical zoom and align to a horizon, table row, or grid so reviewers do not chase fake deltas.
- After export check long-edge pixels and file weight; split into “part 1/2” when IM limits bite. Redact tokens, phones, employee mail, and internal hostnames before sharing; log merge direction, gap, and a file hash on the ticket or expense note for audit.