TAP TAP GO
Identify what must remain
Before cropping, note the features that establish context: equipment connections, room boundaries, signage, safety barriers or neighbouring structures. Preserve anything essential to the claim the image supports. Avoid a crop that makes a partial view appear complete. Keep the original file and record the intended use so future designers can understand why a particular framing was selected.
Test every display size
A website may crop the same image differently on desktop and mobile. Review the actual published layout rather than only the source file. Ensure captions and status labels stay attached to the right visual. If a useful image cannot survive a narrow crop, provide a full-view option or choose another asset. The objective is an attractive page that still shows enough context for the reader to ask accurate follow-up questions.
Put the guide to work
Keep a small set of approved crops for common layouts and label their intended use. This reduces the chance that a later editor makes an automatic crop that removes important context. Review new formats separately rather than assuming the approved desktop composition will work in every narrow placement.
Hypothetical example
A mobile crop removes the label identifying a project render as proposed. The editor changes the layout so the label is live text outside the image and adds a full-view option. The visual remains striking without implying that the proposed work already exists.
Make it practical.
Use this checklist as you read. Checks are not stored.Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
