Set Shopify’s default Open Graph image at Online Store > Preferences. In Social sharing image and SEO, choose Add image or Change image, select the file, and save. Shopify uses this image as a fallback when a page does not provide another image.
On Shopify’s free themes, products, collections, and blog posts normally use their own featured images. Pages without a featured image, such as the homepage or an About page, use the store-level social sharing image unless the theme’s settings or code supplies something else.
Set the store-wide social sharing image
Shopify labels the setting “Social sharing image,” while the metadata most themes output is the Open Graph og:image tag. The setting is useful for pages that do not have a more specific image.
- Sign in to Shopify admin.
- Open Online Store > Preferences.
- Scroll to Social sharing image and SEO.
- Select Add image if no image is configured, or Change image to replace the current one.
- Upload an image from your device or choose one already available in the file picker.
- Save the preference, then verify the rendered page metadata before relying on a social-network preview.
This changes the store-level fallback. It does not necessarily replace a product’s featured image or a custom theme’s hard-coded share image.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
Which image Shopify actually chooses
There are two separate decisions: what image a page provides, and what Shopify uses when that page provides none. Shopify’s documented behavior for its free themes is:
- Product page: the product’s featured image.
- Collection page: the collection’s featured image.
- Blog post: the post’s featured image.
- Pages without a featured image: the store social sharing image, including common cases such as the homepage and About page.
A theme can change this behavior. Shopify describes the precedence for image selection as follows:
- Images hard-coded in theme files have the highest priority.
- Images uploaded in theme settings, such as social-media, social-sharing, or checkout settings, are next.
- The image in Online Store > Preferences is the default fallback.
Consequently, a preference image can be configured correctly yet never appear if the active theme emits another URL first. A blank-looking preference field can also be misleading: some themes display only an image uploaded through their own settings. Check Theme settings > Checkout > Logo and Theme settings > Social media or Social sharing when the preference image is missing or ignored.
Choose the right implementation path
| Path | Best for | Control | Risk |
|---|---|---|---|
| Online Store preferences | A store-wide fallback without code | Lowest; applies where no other image exists | A theme or page template may override it |
| Theme settings | Themes that expose a social or checkout image field | More control than the global fallback | Setting names and behavior vary by theme |
| Liquid metadata | Developers who need deterministic or conditional output | Highest; can preserve page-specific logic | Incorrect edits can create duplicate or invalid metadata |
| PreviewBuilder: Link Image | Merchants wanting an app-managed or automated approach | App-dependent customization | Features and current terms should be checked in the Shopify App Store |
Set an image in a custom theme
Use the no-code preference first. If the generated page still contains the wrong image, inspect the theme rather than repeatedly replacing the admin upload.
Recommended Free Tools
Find the existing Open Graph tag
- In Shopify admin, open Online Store > Themes.
- For the theme you are using, open the code editor. Work on a duplicate theme when possible so the live storefront remains unchanged while you test.
- Search all theme files for
og:image. Shopify says social meta tags are commonly kept in a snippet, but the exact file name differs by theme. - Record any conditional logic around products, collections, articles, and pages before editing it. Those branches may intentionally emit page-specific images.
Use Shopify’s global page_image object when appropriate
Shopify’s Liquid documentation demonstrates using the global page_image object as the value for the Open Graph tag. It points to the image configured in admin and can replace a theme-specific share-image setting when that is the behavior you want.
<meta property="og:image" content="http:{{ page_image | img_url: '1200x1200' }}">The snippet above is an illustrative pattern from Shopify’s article, not a universal drop-in replacement. Check the filters and syntax used by your active theme. Current theme requirements also call for Open Graph and Twitter card tags, so avoid deleting existing tags simply because one image value is wrong.
Preserve page-specific branches
If a theme already selects a product, collection, or article image, keep that logic and use page_image only as the fallback branch. A common safe pattern is to leave the existing page-specific assignment intact, then provide the admin-configured image when no page image is available. The exact Liquid conditions depend on the theme version; inspect the rendered output after every change.
Verify the generated metadata
Do not judge the result only from Shopify’s editor. Open the public page in a browser, view the page source or inspect the document head, and find property="og:image". Confirm that:
- There is an
og:imagetag. - The URL points to the intended image rather than an old asset.
- There is not a later duplicate tag with a different URL.
- The image URL is publicly reachable without a staff login.
Shopify recommends checking social previews with Twitter’s Card Validator, Facebook’s Crawler/Sharing Debugger, and LinkedIn’s Post Inspector. These services fetch the public URL as their crawlers do and can expose warnings that are invisible in the theme editor. A debugger preview is a test of the fetched page, not proof that every platform has already discarded an older cached card.
Troubleshooting common failures
| Symptom | Likely cause | What to do |
|---|---|---|
| The preference image saves but a product still shows another image | The product has a featured image, or the theme emits product-specific metadata | Inspect the product page source and the theme’s og:image logic. This is expected in free themes when a featured image exists. |
| The homepage shows an old image | A theme setting or hard-coded image has higher precedence | Check Theme settings > Social media/Social sharing and search the code for og:image and fixed asset URLs. |
| The preference field is blank or the chosen image is not listed | The theme may expose only its own settings, or the image was configured elsewhere | Check Theme settings > Checkout > Logo and the social-media settings before editing Liquid. |
The page source has no og:image |
The theme’s metadata snippet was removed, conditionally skipped, or malformed | Restore the theme’s supported Open Graph structure and validate the output on a duplicate theme. |
| Facebook, LinkedIn, or X still displays the previous image | The platform cached the earlier metadata | Run the URL through the relevant debugger or inspector to request a fresh scrape. Shopify notes that Facebook can retain images for a number of days. |
| Search results still show an old image | Search indexing is separate from social-card caching | Refresh the social preview independently, then resubmit the sitemap if the search result remains outdated. |
| The image works in source but not in a preview tool | The crawler cannot fetch the asset, or the platform has a stale cache | Open the image URL without being logged in, check for access restrictions, and use the platform’s inspection tool again. |
Or skip the browser setup
If you want a rendered screenshot of the public storefront after changing its metadata, ScreenshotNeo returns a PNG, JPEG, WebP, or PDF from one GET request. It is a screenshot service, not a replacement for Shopify’s Open Graph setting, so use it to check what visitors see rather than to write the og:image tag.
Before the capture, ScreenshotNeo accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be turned off. Only clean shots are billed. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response identifies the page verdict and billing status in X-Page-Verdict and X-Billed headers. An MCP server also exposes take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients.
See the ScreenshotNeo API documentation for the complete option list. These examples capture a public Shopify storefront; replace the access key and store URL with your own values.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://your-store.myshopify.com -o shopify-store.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://your-store.myshopify.com"}, timeout=90)
r.raise_for_status()
open("shopify-store.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://your-store.myshopify.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
require('fs').writeFileSync('shopify-store.webp', Buffer.from(await res.arrayBuffer()));ScreenshotNeo includes full-page capture with lazy images loaded, CSS-selector element capture, custom CSS and JavaScript, waits for a selector, delay, or network idle, custom headers and cookies, device presets, retina scale, resizing, caching with a chosen TTL, signed links, asynchronous jobs with signed webhooks, bulk capture for up to 100 URLs per call, and a usage API. Every feature is available on every plan. The Free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account to try it.
Best Value
Operational and cost considerations
Changing an Open Graph image is a metadata change, so the main delays come from theme deployment and third-party crawler caches rather than from Shopify’s upload screen. Test a duplicate theme before publishing Liquid edits, keep a record of the previous snippet, and verify both a page with a featured image and a page that relies on the fallback.
For repeated visual checks, a screenshot API can avoid installing browser automation locally. ScreenshotNeo’s cache can be configured with a TTL you choose, and cache hits are not billed. Its paid plans are $5 for 3,000 shots (Starter), $15 for 15,000 (Growth), $39 for 60,000 (Pro), $99 for 250,000 (Scale), and $249 for 1,000,000 (Business); yearly billing provides two months free.
The Bottom Line
Use Online Store > Preferences > Social sharing image and SEO for Shopify’s fallback image, then inspect og:image and your theme’s precedence rules if a page still shows a different preview.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
