Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Set LinkedIn’s preview image in the shared page’s HTML <head>. Add an absolute, publicly reachable image URL to og:image, then provide the page title, description, URL, and image dimensions. LinkedIn documents a minimum 1200 × 627-pixel image, an approximately 1.91:1 ratio, JPG/PNG/GIF formats, and a 5 MB maximum.
Use these Open Graph tags in the page head
Place the metadata in the source HTML of the URL people will share—not in the image file and not in a LinkedIn post editor. A minimal, complete example is:
<head>
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/page">
<meta property="og:title" content="A clear page title">
<meta property="og:description" content="A concise description of the page">
<meta property="og:image" content="https://example.com/images/linkedin-preview.jpg">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="627">
<meta property="og:image:alt" content="Description of the preview image">
</head>Change every example value to match the live page. The og:image URL must be absolute (for example, beginning with https://), publicly reachable, and served as an actual image response. If that URL returns an error document, login page, or other HTML instead of an image, LinkedIn cannot use the intended artwork.
Meet LinkedIn’s image requirements
| Requirement | What to use |
|---|---|
| Minimum dimensions | 1200 × 627 pixels |
| Recommended proportion | Approximately 1.91:1 |
| Maximum file size | 5 MB |
| Supported formats | JPG, PNG, or GIF |
A 1200 × 627 canvas exactly meets LinkedIn’s documented minimum. A 1200 × 630 canvas is close to the recommended proportion, but it is not a separate LinkedIn requirement. Keep important text and logos away from the edges so modest cropping or responsive display does not remove them.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsUnderstand what each property does
og:type
Use website for a normal article, landing page, documentation page, or company page. The Open Graph protocol supports other object types, but the correct value depends on the content represented by the URL.
og:url
Set this to the canonical URL you want associated with the share. Use the final public URL, including the correct protocol and path. Do not use a local development address or a relative path.
og:title and og:description
These supply the title and summary shown with the image. Keep them specific to the destination page and ensure they are present in the initial document source when your site uses server-side rendering or a static build.
og:image
This is the image URL LinkedIn should fetch. Use a stable HTTPS address on a host that permits public requests. Avoid expiring signed URLs unless you know they remain valid when a crawler fetches the page.
Recommended Free Tools
Image dimensions and alternative text
og:image:width and og:image:height describe the file’s pixel dimensions. They are optional Open Graph structured properties, but including them makes the metadata explicit. og:image:alt is a description of the image, not a caption; describe the visual content rather than repeating promotional copy.
Other structured properties
The protocol also defines og:image:url (identical to og:image), og:image:secure_url, and og:image:type. Add them only when your implementation needs to state those values. They do not replace the required image URL in the basic example.
Prepare the image before publishing
- Design at the target canvas. Start at 1200 × 627 pixels or another canvas with approximately a 1.91:1 ratio.
- Export a supported format. Choose JPG for photographic artwork, PNG for sharp interface graphics or transparency, or GIF when a GIF is appropriate. Keep the resulting file at or below 5 MB.
- Give it a permanent public URL. Upload it to your site or asset host and confirm that an unauthenticated request receives the image itself.
- Check the response. The URL should return an image content type and a successful response, not a redirect to a sign-in page, a 404 template, or an HTML error.
- Reference that exact URL. Copy the complete HTTPS address into
og:image; a relative value such as/images/card.jpgis not sufficient.
Add the tags in common site architectures
Static HTML
Edit the template that renders the page and place the tags between <head> and </head>. If many pages use one template, make the title, description, canonical URL, and image variables rather than hard-coding one page’s values everywhere.
CMS-managed pages
Use the SEO or social-sharing fields provided by your CMS, then inspect the generated source. A preview inside the editor is not proof that the published URL emits the tags. Confirm that the final HTML contains one intended set of values in the document head.
React, Vue, or another client-rendered application
LinkedIn may request the initial HTML without running your application’s browser JavaScript. Prefer server-side rendering, static generation, or a framework metadata API that writes the tags into the response sent for the URL. After deployment, view the rendered page source—not only the live DOM in developer tools—and verify that the properties are already present.
Multiple locales or page variants
Generate page-specific values for each canonical URL. The image URL, title, description, and og:url should describe the same page and language rather than relying on a single global image for unrelated content.
Verify the live LinkedIn card
- Publish the template and image, then open the public page in a private browser window.
- View the page source and search for
og:image,og:title,og:description, andog:url. Confirm they are inside the document head and contain the production values. - Open the image URL directly. Check the pixel dimensions, file format, file size, and that the response is the image rather than an HTML page.
- Paste the live page URL into an Open Graph preview or validator. Use its rendered card to inspect the image, title, description, and any reported fetch errors.
- After changing the image or metadata, validate the live URL again. A tool may display a previously fetched result until it retrieves the updated page.
Troubleshoot a missing or incorrect image
| Symptom | Likely cause | Fix |
|---|---|---|
| No image appears | The tag is absent from the initial source, uses a relative URL, or points to a private asset. | Place the tag in the server-rendered <head>, use a complete HTTPS URL, and make the asset publicly fetchable. |
| A broken-image card appears | The image URL returns an HTTP error, redirects to authentication, or returns HTML. | Open the URL without logging in, inspect the response, and correct the host, path, permissions, or file deployment. |
| The old image remains | A preview service or intermediary is showing a cached fetch. | Confirm the new tags are live, then run the URL through a preview or validator again. Keep the same stable URL only when the new file is correctly served. |
| The image is cropped unexpectedly | The canvas does not follow the approximately 1.91:1 proportion or important content touches the edges. | Re-export at 1200 × 627 or a similarly proportioned canvas and move essential text inward. |
| The card is rejected or inconsistent | The file is over 5 MB, below 1200 × 627 pixels, or in an unsupported format. | Resize or recompress the file and export it as JPG, PNG, or GIF within the documented limit. |
| Metadata differs from the page | A CMS plugin, framework default, or duplicate tag is emitting another value. | Inspect the complete source, remove conflicting output, and ensure one intentional set of page-specific properties is generated. |
| The validator cannot fetch the page | Authentication, a blocked crawler, robots restrictions, DNS/TLS problems, or a temporary server failure may prevent retrieval. | Test the URL from an unauthenticated network, check access controls and robots settings, verify HTTPS and DNS, and retry after the server responds normally. |
Keep production metadata reliable
- Use stable asset paths. Changing the filename for every deploy can make old shares and cached previews point at missing files. If you replace an image at the same URL, verify that the new response is valid before sharing.
- Generate values from page data. Build the Open Graph title, description, URL, and image from the same record that renders the page so they cannot drift apart.
- Test unauthenticated access. A browser session with cookies can hide a permission problem that a social crawler encounters.
- Validate after infrastructure changes. CDN rules, security middleware, image optimization, and redirects can alter the response even when the HTML template did not change.
- Keep the image within limits. Oversized files slow retrieval and violate the documented 5 MB maximum; recompress rather than lowering dimensions below the 1200 × 627 minimum.
Or skip the browser setup
If you need a rendered capture of the page for review, documentation, or an automated workflow, ScreenshotNeo can return a screenshot from one request. It is separate from LinkedIn’s metadata parser: you still add and verify the Open Graph tags above, while ScreenshotNeo captures what the live page renders.
For example, capture the page after publishing your tags with cURL:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallBest Value
- 1. Custom Nail art Tray: Show off your nails with our personalized nail art tray Photo Prop! This 4-inch disk is made of strong acrylic. It's great for anyone who loves nail art, works as a nail tech, or wants to promote their nail design. We laser engrave names and social media handles, then fill them with resin for a smooth look. Perfect for showing off your nails or promoting your nail business online.
- 2. Material: Crafted from 5mm thick, high-quality acrylic,it provides a comfortable and secure grip, making it easy to hold while displaying your nail art. The glossy, smooth acrylic surface offers a perfect backdrop for your designs.
- 3. Design: Sleek round acrylic disc with a cut-out notch for easy handling during photos.NOTE: Black will be prone to showing finger prints and dust/scratches easily.
- 4. Ideal for Social Media and Business Promotion: Consistent use of the nailfie disk builds a cohesive, professional brand image, setting you apart from the competition. Whether you're attracting new clients or showcasing your talent, the nail art display plate is essential for promoting your business online.
- 5. Perfect Gift for Nail Technicians: Personalized nail art tray disk is an ideal gift for any nail technician or artist.Whether for a friend, colleague, or even yourself, the nail art display plate is a gift that every nail professional will value and use frequently.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/page -o shot.webpThe same request in Python:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/page"}, timeout=90)
open("shot.webp", "wb").write(r.content)And in Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/page' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the ScreenshotNeo documentation for request options and response handling. Before capture, it can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be disabled. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing result. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
Every plan includes the features. The Free plan provides 1,000 screenshots per month without a card; paid plans start at $5 for 3,000 shots (Starter), followed by $15 for 15,000, $39 for 60,000, $99 for 250,000, and $249 for 1,000,000. Yearly billing gives two months free. Create a free ScreenshotNeo account to start with the no-card allowance.
FAQ
Can I use an image hosted on a development machine?
No. The shared page and its image must be reachable from the public internet at the time LinkedIn fetches them. A localhost address, VPN-only host, or authenticated asset will not provide a usable preview.
Is 1200 × 630 an official minimum?
No. LinkedIn’s documented minimum is 1200 × 627 pixels. A 1200 × 630 canvas is merely close to the stated 1.91:1 proportion, so label it as a practical alternative rather than a platform requirement.
Free tools Windows power users keep installed
One-click scans. No signup required.
Frequently Asked Questions
Can I use an image hosted on a development machine?
No. The shared page and its image must be reachable from the public internet when LinkedIn fetches them; localhost, VPN-only, or authenticated assets cannot provide a usable preview.
Is 1200 × 630 an official minimum?
No. LinkedIn documents 1200 × 627 pixels as the minimum. A 1200 × 630 canvas is only a close practical match to the approximately 1.91:1 ratio.
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.
