How to Test Open Graph Images: Complete Guide to OG Tag Validation
Master Open Graph image testing. Learn validation techniques, common mistakes, debugging tools, and best practices to ensure your social media previews look perfect every time.
Why Testing Open Graph Images Matters
When you share a link on social media—whether it's Twitter, Facebook, LinkedIn, or Slack—the platform pulls specific metadata to create a preview. This preview is called a rich snippet, and it's powered by Open Graph (OG) tags in your HTML. Among the most critical OG tags is the og:image tag, which determines what image appears when your content is shared.
I've seen hundreds of links go viral with the wrong image, or worse—no image at all. A compelling preview can increase click-through rates by up to 40%. A broken or missing OG image can tank your engagement. That's why testing and validating your OG images before launch isn't optional—it's essential.
From my experience building and testing content across multiple platforms, I've learned that the difference between a post that performs and one that doesn't often comes down to proper OG tag validation. In this guide, I'll share everything I've learned about testing OG images correctly.
What Are Open Graph Tags?
Open Graph is a protocol developed by Facebook that allows any web page to become a "rich object" in social networks. It consists of meta tags in the HTML head section that define how your page should appear when shared.
The core OG tags include:
og:title— The headline shown in the previewog:description— The description text below the titleog:image— The image URL displayed in the previewog:url— The canonical URL of your pageog:type— The type of content (article, video, etc.)
While all these tags matter, the og:image is often the make-or-break element. Social platforms prioritize eye-catching visuals, and a well-designed OG image can dramatically increase shares and clicks.
The OG Image Specifications You Need to Know
Before testing, you need to understand the technical requirements. Different platforms have different ideal dimensions, but there's a sweet spot that works across all of them.
| Platform | Recommended Size | Min/Max | Aspect Ratio |
|---|---|---|---|
| 1200x630px | 600x314 to 1200x630 | 1.91:1 | |
| 1200x630px | Minimum 144x144px | 1.91:1 | |
| 1200x627px | Minimum 200x200px | 1.91:1 | |
| Slack | 1200x675px | Minimum 200x200px | 16:9 |
My recommendation: Use 1200x630px as your standard OG image size. This works beautifully across Facebook, Twitter, and LinkedIn, and it's the most widely recommended dimension in the industry.
og:image:width and og:image:height tags. They help social platforms optimize rendering and can improve load times.
Method 1: Using Official Platform Debuggers
Facebook Sharing Debugger
The most reliable way to test OG images is through Facebook's Sharing Debugger. It's the industry standard because Facebook is the most strict about OG validation.
Here's how to use it:
- Go to Facebook Developers Sharing Debugger
- Paste your URL in the search box
- Click "Debug"
- Review the "Open Graph" section
- Check for warnings and errors
The debugger will show you:
- What image Facebook will display
- The image dimensions Facebook detected
- All parsed OG tags
- Specific warnings or errors
- How your preview will appear on different devices
From my experience, if your OG tags pass Facebook's debugger, they'll work well on virtually any platform. Facebook has the most comprehensive validation system.
LinkedIn Post Inspector
LinkedIn has its own OG validation tool. If you're sharing content for B2B or professional audiences, this is essential.
- Go to LinkedIn Post Inspector
- Enter your URL
- Review the preview
- Check for image rendering issues
Twitter Card Validator
Twitter uses slightly different OG tags (Twitter Card tags). To validate:
- Go to Twitter Card Validator
- Paste your URL
- Confirm the image appears correctly
- Check for any protocol errors
Method 2: Manual Source Code Inspection
Sometimes the simplest validation is checking the HTML directly. This is especially useful when debugging why a platform isn't picking up your OG image.
Browser Developer Tools
Right-click on any page → "View Page Source" (or Ctrl+U / Cmd+U) and search for "og:image":
Verify:
- The URL is absolute (not relative)
- The URL is HTTPS (required by most platforms)
- The image file exists and is accessible
- Width and height dimensions are included
- The image format is web-optimized (JPEG, PNG, or GIF)
I've debugged dozens of broken OG images, and most issues come down to relative URLs or HTTP instead of HTTPS. Always use absolute HTTPS URLs.
Method 3: Using Third-Party OG Testing Tools
Beyond official platform tools, several third-party services offer comprehensive OG testing:
Share Preview
A visual OG preview tool that shows exactly how your link will appear on different platforms simultaneously. Test your OG tags instantly.
Metatags.io
Displays real-time previews of OG tags across multiple platforms. Shows how titles, descriptions, and images render on each social network.
Opengraph.xyz
Simple, fast OG tag checker. Returns raw JSON data of all detected OG tags, useful for technical debugging.
SEO.com Meta Tag Analyzer
Comprehensive meta tag analysis including OG tags, Twitter Cards, and structured data validation.
Common OG Image Testing Mistakes (and How to Avoid Them)
Mistake #1: Using Relative URLs
Social platforms can't access your domain context. They need the full absolute URL.
❌ Wrong: /images/preview.jpg
✅ Correct: https://example.com/images/preview.jpg
Mistake #2: Using HTTP Instead of HTTPS
Most modern platforms reject non-HTTPS image URLs for security reasons.
❌ Wrong: http://example.com/image.jpg
✅ Correct: https://example.com/image.jpg
Mistake #3: Ignoring Image Format Requirements
Use web-optimized formats: JPEG, PNG, GIF, or WebP. Avoid formats like TIFF or BMP.
Mistake #4: Not Including Width and Height
Always specify image dimensions. Platforms use these to optimize rendering and avoid layout shift.
Mistake #5: Oversized or Undersized Images
Images smaller than 600x314px may get rejected by Facebook. Images larger than 5MB will be rejected. Aim for 1200x630px at 50-100KB.
Testing OG Images Across Different Platforms
Facebook/Messenger
Use the Facebook Debugger as your primary validation tool. Test both desktop and mobile previews. Pay attention to how text overlays on the image.
Twitter/X
Twitter uses twitter:image tags (not og:image). However, if Twitter tags aren't present, it falls back to og:image. Test using Twitter Card Validator.
LinkedIn respects og:image but has stricter requirements. Test with LinkedIn Post Inspector. LinkedIn prefers square or near-square images.
Slack
Slack previews OG images but prefers a 16:9 aspect ratio. Test by actually posting a link in Slack (or use Share Preview for instant visual validation).
Advanced: Creating OG Images That Actually Convert
Testing is one part; creating effective OG images is another. From my experience, here are the principles of high-performing OG images:
1. Make It Visually Distinct
Your OG image appears alongside dozens of others in social feeds. Use bold colors, clear typography, and high contrast. Avoid cluttered designs.
2. Include Readable Text
Include your headline or key value proposition directly on the image. Don't rely solely on the og:title meta tag. Text should be readable at 200x200px.
3. Brand Consistently
Include your logo or brand color in every OG image. This builds recognition and trust as users scroll through their feeds.
4. Test Across Devices
Preview how your image appears on mobile (square crop), desktop (wide view), and tablet sizes. Most traffic is mobile, so optimize for mobile first.
Automation: Testing OG Images at Scale
If you manage multiple pages or products, manually testing each OG image isn't scalable. Consider these approaches:
API-Based Testing
Use APIs that parse OG tags programmatically:
This returns JSON with all detected OG tags, allowing you to validate programmatically and catch issues before deployment.
Monitoring Tools
Services like Cloudflare can monitor whether your OG images are accessible and not returning 404 errors. Set up alerts for broken images.
The Testing Checklist
Before publishing any page with social sharing in mind, run through this checklist:
- ☐ OG image URL is absolute and HTTPS
- ☐ Image dimensions are 1200x630px or larger
- ☐ og:image:width and og:image:height meta tags are present
- ☐ Image file size is under 5MB (ideally under 100KB)
- ☐ Image format is JPEG, PNG, GIF, or WebP
- ☐ Tested with Facebook Sharing Debugger (no errors)
- ☐ Tested with LinkedIn Post Inspector
- ☐ Tested with Twitter Card Validator
- ☐ Manually tested by sharing in Slack or Discord
- ☐ Image displays correctly on mobile and desktop
- ☐ Text on image is readable at small sizes
- ☐ OG title and description are compelling
Final Thoughts: Why This Matters
I've seen countless high-quality articles buried because their OG images were broken or poorly designed. Conversely, I've watched mediocre content get massive reach because someone took time to craft a compelling OG preview.
Your OG image is often the first impression potential readers have of your content. It's your chance to stop the scroll and convince someone to click. Testing ensures that impression is exactly what you intended.
The good news? Proper OG testing takes minutes once you know the tools. Use the methods in this guide, and you'll ensure every shared link previews perfectly across every platform.
Ready to Perfect Your Social Media Previews?
Test your OG images instantly with Share Preview. Get real-time validation across all platforms and never publish a broken preview again. Also explore our LinkedIn optimization tools and AI content prompts to amplify your sharing impact.
Test Your OG Images Now →