Reads The Actual File
We sniff PNG, JPEG, GIF, and WebP magic bytes to measure real pixels — not the og:image:width tag a CMS may have set wrong.
OG Image Dimension Validator
टीएल;डीआर: OG Image Dimension Validator checks verify og:image and twitter:image pixel size, ratio, and weight. so you can confirm the current issue, understand when it matters, and move directly into the next fix without leaving the browser.
Confirm your social images are the right size before they break a card.
अद्यतन किया गया
Loading tool interface...
Real pixel dimension parsing 1200x630 and 1.91:1 ratio check Minimum 600x315 size floor File-size and format validation Live social card preview
What does OG Image Dimension Validator do?
The OG Image Dimension Validator fetches your page, reads the `og:image` and `twitter:image` tags, downloads each image, and parses its true pixel dimensions straight from the file header. It then grades every image against the dimensions, aspect ratio, and file-size rules that Facebook, LinkedIn, and X use to render large preview cards.
Why it matters: Declared `og:image:width` and `og:image:height` tags are just hints — platforms read the real pixels. An image that is actually 800x800 or a stretched banner will be cropped, downgraded to a tiny thumbnail, or dropped entirely, no matter what your meta tags claim. This tool measures the file itself so you catch the mismatch before a campaign goes live.
The 1200x630 / 1.91:1 standard: Large summary cards want a 1200x630px landscape image at roughly a 1.91:1 ratio. Anything below 600x315px loses the large card. Squares and portraits get cropped. The validator flags each of these conditions per image.
Pre-launch QA: Run a blog post or landing page before publishing to confirm the share image renders at full size on every platform instead of as a blank or pixelated box.
Asset pipeline audits: Catch CMS or CDN resizers that silently re-encode your 1200x630 hero into an undersized or oversized file, and spot images that exceed platform weight limits and slow scraper fetches.
When should you use OG Image Dimension Validator?
OG Image Dimension Validator is most useful when you need a direct answer on a live URL or draft before you change templates, ship content, or rerun a wider audit.
इस टूल का उपयोग कैसे करें
- 1 Enter the page URL you want to validate.
- 2 We read og:image and twitter:image and download each asset.
- 3 Real pixel dimensions are parsed from the PNG, JPEG, GIF, or WebP header.
- 4 Review per-image pass, warn, and fail grades with a live preview, then fix and re-test.
What should you do next?
After confirming dimensions, validate the rest of your social metadata with the Open Graph Checker and review your full tag set with the Meta Tag Checker. Then move to the related checks below to confirm the fix on the live canonical page.
आपको क्या मिलता है
Per-Image Grading
Every og:image and twitter:image gets its own pass, warn, or fail across dimensions, aspect ratio, and file size with a clear reason.
Catches Silent Downgrades
Flags undersized, square, oversized, or heavyweight images that quietly break large cards before your audience ever shares the link.
Frequently Asked Questions
OG Image Dimension Validator के बारे में उत्तर
The recommended og:image size is 1200x630px at a 1.91:1 aspect ratio. That resolution qualifies for large summary cards on Facebook, LinkedIn, and X, while anything below 600x315px loses the large card and falls back to a small thumbnail.
Because social platforms measure the real pixels, not your meta tags. The og:image:width and og:image:height tags are hints that scrapers can ignore, so this tool downloads each image and parses its true dimensions from the file header to catch mismatches between what you declared and what you actually shipped.
Yes, it validates og:image and twitter:image separately. Each image is fetched, measured, and graded on its own, so you can confirm your X card and your Open Graph card are both correctly sized even when they point to different assets.
The validator parses PNG, JPEG, GIF, and WebP dimensions directly from the file header. It identifies the format from its magic bytes and reads width and height without fully decoding the image, then also reports the file size so you can spot assets that exceed platform weight limits.