How to make a share image for every new page
Short answer: A share image (also called an Open Graph image, or OG image) is the picture that appears when someone pastes your page link into Facebook, LinkedIn (a business social network), Slack (a team chat app) or a messaging app. It comes from one line in the page's code, the og:image tag, and the usual size is 1200 x 630 pixels. For a few pages, copy one Canva template (a design website with free and paid plans) and swap the headline by hand. For dozens of pages, generate the image from the page title with a template, then test each link in the platform's preview tool before you share it.
You publish a new page, paste the link into a post, and the preview is a grey box or the wrong picture. Fixing that for every page by hand costs time you do not have. The fix is one template, one tag and one check, done the same way every time.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
The short version: every page needs an og:image tag that points to a picture of about 1200 x 630 pixels, at a web address that starts with https. Make the picture from a template so only the headline changes. Then check the preview in Facebook's Sharing Debugger (you must log in to Facebook to use it) before you post. If you have fewer than about 15 pages, a Canva template and ten minutes per page is the cheapest route. Past that, it pays to generate the images automatically.
Where code is needed, you will see what to ask a developer for.
This page may contain affiliate links from which Blur Studio earns commissions.
What a share image is and where it shows up
When you paste a link into a social network or chat app, that app visits your page, reads a few tags in the page's hidden header, and builds a preview card. The card usually has a title, a short description and one picture. The tags come from the Open Graph protocol, a small standard that Facebook started and many apps now follow (the standard's own page is at ogp.me).
The protocol lists four required tags: og:title, og:type, og:image and og:url. It also lists optional picture details: the picture's address over https, its type, its width, its height and a text description called og:image:alt. The protocol says that if you set the image you should set the alt text too. A page with no Open Graph tags is treated as a plain website page, and apps then guess a picture or show none.
Here is what the tags look like. You do not type these yourself on most website builders, but it helps to know what to ask for.
<meta property="og:title" content="Your page title" />
<meta property="og:type" content="website" />
<meta property="og:url" content="https://example.com/your-page" />
<meta property="og:image" content="https://example.com/share/your-page-v1.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:image:alt" content="Short plain description of the picture" />
Two details matter later. First, the image address must be https. Second, Facebook's sharing documentation says images are cached based on the URL and will not update unless the URL changes. That one line explains most "my preview is stuck" complaints, and I come back to it below.
The size, shape and file type to use
Use 1200 x 630 pixels. That is a 1.91 to 1 rectangle. Vercel (a company that hosts websites) recommends 1200 x 630 in its image generation documentation, and Facebook's best practices page says to use images at least 1080 pixels wide for the best display. Facebook's sharing documentation accepts JPEG, GIF and PNG files and asks you to set the width and height tags.
Other numbers you may see are for other jobs. LinkedIn's single image ad uses 1200 x 628 for the same 1.91 to 1 shape, but that is an ad format, not a rule for link previews. Facebook link image ads have their own minimum of 600 pixels wide and recommend a 1 to 1 square in the ad context. Do not mix the ad sizes with the page preview size.
For X (the platform formerly called Twitter) card sizes and file limits, and for LinkedIn's image rules and cache behaviour on link previews, check each platform's current developer page before you rely on a number. Using 1200 x 630 and keeping the file small is a safe default that works for the platforms whose rules are published.
- Size: 1200 x 630 pixels.
- Type: PNG or JPEG. Use JPEG for photos, PNG for flat colour and text.
- Address: https only, on your own domain.
- Text: a short headline, large letters, high contrast. Previews are often shown small, so a long sentence is hard to read. Keep the headline under about eight words and keep it away from the edges, because some apps crop.
Your options, from least to most effort
| Option | Best for | Cost to check | Weak spot |
|---|---|---|---|
| One default image for the whole site | A new site where nothing else is ready | Free (your time) | Every link looks the same |
| Canva template, swap the text by hand | Up to about 15 pages | Free plan; Pro and Business are paid (the US view of Canva's page showed US$18 and US$25 a month, excluding tax, as of November 2026; prices show in local currency, so check yours) | Manual; you must upload and link each file |
| Freelance designer | A flagship campaign or a brand refresh | Quote or hourly rate | Slow and costly for every new post |
| Generate from a template with code | Dozens or hundreds of pages, or pages made from a database | Developer time once, then close to nothing per page | Needs a developer or a tool that does it |
| An AI site builder with an image step (Ploy is one) | You already build your site there | Credits (see below) | You must check every image |
The right row depends on how many pages you add each month. A rough rule of mine: under five new pages a month, a Canva template wins. Over twenty, or pages from a spreadsheet, automatic generation wins.
The Canva route: one template, swap the text
Canva is a website for making designs from templates. Its pricing page shows a Free plan and paid Pro and Business plans, with a yearly option that saves from 16 percent. The US view showed Pro at US$18 a month for one person and Business at US$25 a month per person, excluding tax, as of November 2026. Other countries see local currency and time limited offers, so check the price for your own country and ignore intro offers. Brand Kits, which store your colours, fonts and logos, are limited to 1 on Free (with 3 colours), 5 on Pro and 100 on Business.
- Create a custom size design of 1200 x 630 pixels.
- Put your logo in one corner, a background colour from your brand, and one large text box for the headline.
- Save it as "Share image template". For each new page, make a copy, change the headline and download it as PNG or JPEG.
- Name the file after the page and the version, for example
pricing-guide-v1.png. The version part matters for the cache trap below. - Upload it to your site and point the page's
og:imagetag at it.
Time it. At ten minutes an image, forty pages cost about 6 hours 40 minutes.
The automatic route: an image made from the page title
If your site is built with code, the share image can be created the moment someone asks for it. Vercel's open source tool, @vercel/og, does this. According to Vercel's documentation (last updated 16 June 2026), it uses two libraries, Satori and Resvg, to turn a small piece of layout code into a PNG. It is included in the Next.js App Router (a popular website framework) through next/og, and the result is cached on Vercel's network.
Limits that the same page states, and that you should know before you promise anything:
- Only flexbox and a subset of CSS work. CSS grid (
display: grid) is not supported. - Fonts must be ttf, otf or woff files, with ttf or otf preferred.
- The maximum bundle size is 500KB, including fonts and images. A big photo background can break this, so use plain colour or a small file.
- The page recommends allowing the image route in your robots.txt file (a file that tells crawlers what they may fetch) so that social crawlers can reach it. If you block it, previews can fail.
If your site does not use Next.js, other tools do the same job, and any developer can build a small version. What you give the developer is a brief, not code. A good brief is short.
A brief you can hand to a developer
- Create one 1200 x 630 share image per page, built from the page title and our logo.
- Use our brand colours and one font file we supply.
- Write the matching
og:image,og:image:width,og:image:heightandog:image:alttags on every page. - Add a version number to each image address so a changed image gets a new address.
- Fall back to our default image if a title is empty or too long.
- Do not block the image route in robots.txt.
Where Ploy fits, as one option among several
Ploy is an AI website builder: you describe a site to its chat Agent and it builds and hosts it. Its homepage lists automated ad creative, and its Ploybooks library (saved workflows you can run on a schedule) lists one called Social Ad Asset Generation. Ploy's credits page says AI credits are spent on images and documents, among other things. Ploy does not publish a credit cost for a single image, so you cannot price one share image in advance.
Ploy's public documents do not say whether it sets a different share image for each page by itself, so do not assume it. If your site is on Ploy, ask its Agent for exactly the tags in the brief above, then check the finished page in the debugger as described in the test section. Ploy's integrations list also shows a Canva connection on Starter and above, so a Canva template can sit beside your Ploy site.
Ploy's plans as of November 2026 (from its pricing page): Free at $0 with 500 AI credits a day up to 2,000; Starter at $50 a month or $480 a year with 4,000 credits a month; Pro at $300 a month or $2,880 a year with 24,000 credits a month; Enterprise by quote. Unused credits do not carry over. Check the pricing page for your own numbers before you decide. Also note that PloyAds, its ad product, is a waitlist page, not a tool you can use today, so do not plan around it.
Ploy-written pages and images need a human check before they go live. An AI image can put the wrong word, an odd logo or a made-up detail on your card, and a wrong card is seen by everyone who shares the link.
The cache trap: why your new picture does not show
Facebook stores the first picture it sees for a link, keyed on the picture's web address. If you replace the file but keep the same address, the old preview stays. The fix has two parts:
- Change the address. Rename the file (
pricing-guide-v2.png) or add a version to the address, and update the tag. - Open Facebook's Sharing Debugger (developers.facebook.com/tools/debug/), paste the page address and scrape it again. The tool shows the tags it found, any errors, and a fresh preview.
Do not assume platforms refresh pictures on their own. How long LinkedIn or X keep theirs is something to check on their pages. The safe habit is the same everywhere: a new picture gets a new address.
A worked example with made-up numbers
Say you run a plumbing firm with a 12 page site and plan to add one how-to guide a week. The numbers below are invented to show the arithmetic.
| Item | By hand each time | Template plus a checklist |
|---|---|---|
| Minutes per new page | 25 (new design each time) | 8 (swap headline, export, upload, test) |
| Pages in a year | 52 | 52 |
| Hours in a year | about 21.7 | about 6.9 |
| Wrong or missing previews | Common, no check | Caught in the test step |
The saving is about 14.7 hours a year, and the real gain is that every link looks the same and gets checked. If instead you were adding 200 product pages from a spreadsheet, 8 minutes each is over 26 hours, and automatic generation clearly wins.
A test plan with pass and fail rules
Run this on every new page before you share the link, and again on the first page you publish after any site change.
| Check | Pass | Fail, fix by |
|---|---|---|
| Open the image address in a browser | It loads over https | Fix the address or the file upload |
| Image size | 1200 x 630 and small enough to load fast | Re-export at the right size |
| Tags in the page source | og:title, og:type, og:url, og:image, width, height and alt all present | Add the missing tags |
| Facebook Sharing Debugger | Shows your image and no errors | Read the error, fix, scrape again |
| Paste into a private chat in LinkedIn or Slack | Card shows the right picture and title | Change the image address and test again; check LinkedIn's own help pages for its preview tool |
| Text on the card | Headline readable at thumbnail size, no spelling errors | Shorten the headline, enlarge the type |
| Robots | Image address is not blocked in robots.txt | Allow it |
Common mistakes
- Using the logo as the share image. It is small and says nothing about the page.
- No alt text. It helps people who use screen readers and the protocol asks for it.
- Pictures behind a login or a staging address. The crawler cannot fetch them.
- A huge photo. It loads slowly, and if you generate images with code it can break the 500KB bundle limit.
When to skip an AI tool for this
- You have fewer than about 15 pages. One Canva template is cheaper and simpler than a subscription for this alone.
- Your site is not hosted on the tool. Do not move a whole website just to get share images.
- The page is a high stakes one, such as a launch or a legal notice. Have a person design and review that image.
- You cannot check each image. Unreviewed AI images are the risk, not the saving.
Related reading on this site
If the new pages should also look like your current site, read how to make new pages match your current website style. If you make many pages for different services and suburbs, see landing pages for every service and suburb. For Ploy's own plans see Ploy AI pricing explained.
How I'd approach this
Start by counting. How many pages will you add in the next six months? If it is under 15, use one Canva template and a one-page checklist, and keep the files named with a version number. If it is more than that, or if pages come from a spreadsheet, write the developer brief above and have the images generated from the page title.
If your website is already on Ploy, ask its Agent to add the full set of tags and a default image first, and run the test table on one page before you trust it for all of them. If you are not on it, do not move for this one job. A freelancer or any website builder can add the same tags.
Your first week: Day 1, pick the size (1200 x 630), the font and the colours. Day 2, make the template and a default image. Day 3, add the tags to your page template, or send the brief. Day 4, test five pages in the Sharing Debugger and a chat app. Day 5, write the checklist and put it where whoever publishes pages will see it. If you want a custom image pipeline or ongoing care for your site, Blur Studio builds that; you can see what that includes. This is general information; check each platform's current rules.
Questions people ask
What size should an Open Graph image be?
Use 1200 x 630 pixels, a 1.91 to 1 shape. Vercel's documentation recommends that size, and Facebook's best practices page says to use images at least 1080 pixels wide. Keep the file at https and small enough to load fast. Check X and LinkedIn's own pages for their current limits.
Why does my share image not update after I change it?
Facebook caches images by their web address, so a changed file at the same address keeps the old preview. Give the new file a new address (for example add v2 to the name), update the tag, and scrape the page again in Facebook's Sharing Debugger.
Do I need a different image for every page?
No, but unique images tend to look better when links are shared. A sensible plan is one default image for the whole site and a template-made image for every post, guide or product page that people are likely to share.
Can I make share images for free?
Yes. Canva has a Free plan, and a template saves most of the work. Check Canva's pricing page for what is limited on Free. You can also make a simple one in any design tool you already own.
Does Ploy make a share image for each page automatically?
Ploy's public documents do not describe a per-page share image setting, so do not assume it. Ploy lists automated ad creative on its homepage and spends AI credits on images. Ask its Agent for the tags, then test the result. You can look at Ploy's plans and check what your credits cover.
Do I need alt text on a share image?
The Open Graph protocol says that if you set og:image you should set og:image:alt too. It is a short plain description of the picture, and it helps people who use screen readers.
How do I test a preview before I post?
Log in to Facebook and open the page address in its Sharing Debugger, which shows the tags it found, any errors and the preview. Then paste the link into a private chat on the app where you will share it. Fix errors and test again before you post publicly.
Is an AI-made share image safe to publish without checking?
No. AI images can contain spelling mistakes, odd logos or invented details. Review each one, as you would review any page you publish. For the same reason, check the headline text on the card against the page title.
More in this topic: Websites: ad ideas, share images and brand decks (4 guides) →
Sources
- The Open Graph protocol (ogp.me)
- Sharing for webmasters (Facebook for Developers)
- Sharing best practices (Facebook for Developers)
- Sharing Debugger (Facebook for Developers)
- Open Graph image generation (Vercel documentation)
- Canva pricing (Canva)
- Ploy pricing (Ploy)
- Credits (Ploy documentation)
- Integrations (Ploy documentation)