A logo can look clear on a presentation slide and become hard to read as a favicon. Test the mark where people will actually encounter it. A small-size failure often comes from letters, counters, or thin strokes that collapse together on the target display.
Build a sheet with real-size samples
Place the mark at 16, 24, 32, and 64 pixels on light and dark backgrounds. Add the exact colors used in your product header or social templates. View the sheet at 100% and look at each size for a second or two. If you have the vector artwork, export small versions from it and check them separately. An SVG retains the shape when resized. Actual small pixels still limit the detail a viewer can see.
For an example, imagine a wordmark with a ring of small lettering around a symbol. At 64 pixels it may retain a clear boundary. At 16 pixels the letters may look like visual noise. Make an icon-only draft that keeps the recognizable central silhouette, then compare both versions beside neighboring favicons.
Separate branding and interface checks
A logo exception in the WCAG minimum contrast criterion applies to text that is part of a logo or brand name. Labels and controls near it still need their own checks. Put the mark beside its actual menu label, confirm the logo remains recognizable, and verify the functional text separately. Document which sizes get the full mark and where the compact version is used.
Continue with Oakgen Agent
Open in Oakgen Agent
Review the prefilled prompt before sending.


