Favicon and OG Image: Small Details with a Big Impact on Clicks and Trust
Two tiny image files often help decide whether someone clicks your link or just keeps scrolling: the favicon (the small icon in the browser tab) and the OG image (the preview image that shows up when your link is shared in WhatsApp, LinkedIn, Slack or Facebook). Both are technically trivial to set up - and yet they're surprisingly often forgotten or done half-heartedly. This article explains why they matter, when they really make a difference and how to get them right.
Why these details matter at all
People make click decisions in a fraction of a second. A generic globe symbol in the browser tab or a broken, empty link preview sends an unconscious signal: nobody bothered here. The opposite is also true - a clean icon and a tidy preview convey care and reliability, exactly the qualities a potential customer expects from you.
In practical terms, the two work like this:
- Favicon: Makes your tab recognisable among many open tabs, appears in bookmarks and browser history, and sometimes shows up next to your URL in Google's search results.
- OG image: Determines how professional your link looks the moment someone shares it. An attractive preview is clicked measurably more often than a bare link with no image.
To be honest: these elements won't turn a bad page into a good one. But on a good page, they needlessly give away clicks and trust when they're missing. They're part of the basic hygiene of any professional website.
Setting up the favicon properly
A favicon today is more than the old favicon.ico. Different devices and contexts expect different sizes. A small set makes sense:
- An SVG version as a scalable master icon for modern browsers.
- PNG files in 32x32 and 16x16 pixels for the tab.
- An Apple touch icon at 180x180 pixels for the home screen on iPhones.
- Optionally a
site.webmanifestfor Android devices.
What matters is that the design is still recognisable at 16 pixels. A full logo with a wordmark never works at that size - use a clear symbol, a single letter or a simplified mark with good contrast instead. Test it against both light and dark tab backgrounds.
The OG image that gets shared
The OG image sits in your page's source code as a meta tag (og:image) and is read by social networks. The proven approach is:
- Format 1200x630 pixels (an aspect ratio of roughly 1.91:1) - the common denominator across almost all platforms.
- An absolute URL to the image file, not just a relative path, otherwise some services show nothing at all.
- Legible text and a logo with enough margin, because some platforms crop the edges.
- The
og:titleandog:descriptiontags as well, so the preview's headline and text are correct.
One common pitfall: platforms cache the preview. When you change the image, you often still see the old version. Tools like the Facebook Sharing Debugger or the LinkedIn Post Inspector let you refresh the cache on demand and check at the same time that all tags are being read correctly.
A quick practical check
Here's how to tell in a few minutes whether your site is set up cleanly:
- Open your site in a browser tab - does your own icon appear, or a grey default symbol?
- Share your home page to yourself as a test in a messenger - do you get a complete preview with image, title and text?
- Look at your subpages - ideally, important pages have their own fitting OG image rather than the same one everywhere.
- Check the preview on your phone, not just on the desktop.
When the effort is worth it - and when it isn't
For any public website meant to win customers, the effort almost always pays off, because it's small and one-off. It's a different story for a purely internal application or a tool behind a login that will never be shared - there, an elaborate OG image is simply unnecessary. A simple favicon never hurts, though.
For us, both elements are part of the standard delivery on every project. We run seven of our own brands in production - from an accessibility scanner to a product portal with over 177,000 entries to a marine SaaS. From running these day to day, we know how differently platforms render previews and where the typical cache and format traps lie. It's exactly these small details that ultimately make the difference between a site that looks professional and one that looks almost professional.