Social preview cards and image sizes for posts
When you paste a link into a post or a chat, many apps show a card with a title, a short description and an image. That card comes from tags in the page’s HTML. Getting it right makes a shared link look intentional instead of broken.
Where a card comes from
When an app sees a link, its crawler fetches the page and reads tags in the <head>. The most widely read set is the Open Graph protocol. A minimal set looks like this:
<meta property="og:title" content="Spring studio sale">
<meta property="og:description" content="Twelve new canvases, sizes and prices inside.">
<meta property="og:image" content="/images/spring-card.jpg">
<meta property="og:url" content="/spring.html">
In a real page, og:image and og:url must be full absolute addresses including your domain; the short paths above only keep the example brief. X (formerly Twitter) also reads its own twitter:card tag, where the value summary_large_image asks for a wide image instead of a small square thumbnail.
Aspect ratios in general terms
Aspect ratio is width divided by height. Getting the ratio right matters more than the exact pixel count, because apps scale images but crop the ones with the wrong shape.
| Use | Common shape | Example size | Ratio |
|---|---|---|---|
| Link preview card | Wide landscape | 1200 × 630 | about 1.91 : 1 |
| Square feed post | Square | 1080 × 1080 | 1 : 1 |
| Portrait feed post | Slightly tall | 1080 × 1350 | 4 : 5 (0.8) |
| Full-screen story or short video | Tall | 1080 × 1920 | 9 : 16 (0.5625) |
Platforms revise their recommended sizes, maximum file sizes and crop rules. Before a big campaign, open each platform’s own help or developer page and search for “image size” or “sharing best practices” to confirm the current figures.
Designing one image that survives cropping
- Start with the wide link-card shape, since that is what most link previews use.
- Keep the title text and any face or logo inside the central area, away from all four edges.
- Use large type: the card is often shown at a fraction of its real size on a phone.
- Make sure the text has strong colour contrast against the background.
- Export as JPEG for photos or PNG for flat graphics and text, and keep the file small.
Testing a card
Several platforms offer an official debugging or preview tool that fetches your page and shows the card it would build. These tools also refresh the platform’s cached copy, which matters because a card that was wrong once can stay wrong until it is re-fetched. You can also read the tags yourself: view the page source in your browser and search for og:.
Common mistakes
- Relative image paths in
og:image. Crawlers need the full address. - Images blocked by robots rules or login walls, so the crawler gets nothing.
- The same card for every page. Each page deserves its own title and description.
- Tiny text that becomes unreadable once the card shrinks in a feed.
Questions
I changed the image but the old card still shows. Why?
Platforms cache cards. Run the URL through that platform’s preview or debugging tool to force a fresh fetch, or wait for the cache to expire.
Do I need separate tags for every network?
Usually not. Most apps fall back to Open Graph tags. Add platform-specific tags only when you want different behaviour on that platform.