A logo can look excellent at presentation size and disappear in a browser tab. A long name can become unreadable in a social avatar. The solution is not to shrink the same artwork until it fits; it is to test the identity as a set of recognisable versions in the placements the business will actually use.
This is a shape and recognition review. Color contrast is a separate check, covered in our brand palette accessibility test. The small-format test asks whether someone can identify the business when detail, width, and nearby text change.
Put the design into real containers
Create a contact sheet with at least these mockups: a browser tab, a mobile header, a circular or square social avatar, a square ad logo, and a wide ad logo. Include the full wordmark, any symbol or monogram, and a stacked version if proposed. Show each at its intended rendered size, not enlarged on a slide.
There is a practical reason to test variants. Google Search's favicon guidance calls for a square favicon visually representative of the site brand and says its appearance in search is not guaranteed. Google Ads guidance accepts square and landscape logo ratios in responsive display ads, recommends careful centering and cropping, and cautions against small text. These are different containers with different constraints; neither source declares one logo composition universally best.
| Placement | The question to answer | Failure to catch |
|---|---|---|
| Tiny tab or search favicon | Is one distinctive cue still visible? | Fine detail turns into a dot |
| Social avatar | Does the mark survive the actual crop or mask? | First or last letters disappear |
| Mobile header | Is the name legible without consuming the whole header? | Navigation is squeezed out |
| Square and wide ad logo | Can both versions be recognized as the same brand? | Two exports look like unrelated businesses |
If an app icon is in scope, check that separately. Apple's icon guidance notes that fine details become hard to discern at smaller sizes and that system masking changes the visible edge. An ordinary business site does not need to commission an app icon just because it needs a favicon.
Run a five-second recognition check
Show the contact sheet to a few people who were not in the design presentation. Ask what they read or recognize in each placement, which versions they think belong to the same company, and what they confuse with a competitor. Record the exact failure, not just a preference vote. If the wordmark is too small, a dedicated symbol or compact lockup may solve the constraint while the full wordmark remains primary elsewhere.
Test against real neighboring content: a social feed, browser tabs, and an ad preview. A mark that works in isolation may disappear beside dense imagery or another circular avatar. Check exported files, not only editable artboards, because cropping and scaling happen after design approval.
Write an explicit rule for which version goes where, including a minimum viable size for each version based on the team's tests. The sizes are project decisions, not a global standard. ARCHV's visual identity work can include this application test before a client invests in launch assets. The identity handoff guide addresses the separate question of files and permissions after the design is approved.