Media
5 items
Description
Preview how your link will look when shared, and what each platform substitutes when the page has no og: tags. OG Preview shows how a page will look when its link is pasted into a messenger — before you send it. NO SERVERS, NO ACCOUNTS, NO TRACKING This extension has no backend. There is nothing to sign up for, nothing to log into, and nowhere for your data to be sent — because no server belonging to this extension exists in the first place. No analytics, no telemetry, no crash reporting, no third-party SDKs, no ads. No remote code: every line that runs is inside the package you install, and it is all open source. The page you are inspecting is read locally, in your browser. The preview cards are rendered locally. The result lives in the popup and is gone the moment you close it — nothing is uploaded, nothing is kept. The only network requests are the ones your browser would make anyway: loading the address you asked about, and loading that page's own preview image so its real dimensions and file size can be measured. Both go straight to the site being inspected. No proxy, no middleman, no analysis service. Your two settings — which platform cards are visible, and light or dark theme — are stored locally on this device and never synced. NINE PLATFORMS FROM ONE PAGE See how a shared link will look across nine of today's most popular messaging apps and social networks, all rendered side by side in a single popup. Each mock-up follows that platform's own display rules: whether the image becomes a wide banner or a small square thumbnail, whether the description is shown at all, and what is left when there is no image. WHEN THE og: TAGS ARE MISSING Crawlers do not give up — they guess, and every platform guesses differently. OG Preview walks the same fallback chains and labels where each value came from: • Title: og:title → twitter:title → JSON-LD → <title> → <h1> → hostname • Description: og:description → twitter:description → meta description → JSON-LD → the first real paragraph on the page • Image: og:image → twitter:image → JSON-LD → the largest image in the markup → apple-touch-icon • Site name: og:site_name → application-name → JSON-LD publisher → hostname • URL: og:url → canonical → the actual address FOUR PANELS • Preview — nine platform cards from a single page • Issues — a scored checklist: missing tags, title and description lengths, image dimensions, aspect ratio, file weight, http vs https images, og:image:width that disagrees with the real file, twitter:card mismatches, og:url pointing at another domain • Tags — every resolved value with a badge showing whether it was declared or substituted, plus every meta tag on the page grouped by family • Code — a ready-to-paste <head> block, pre-filled with what was found TWO WAYS TO READ A PAGE • Current tab — reads the live DOM, so tags injected by JavaScript and real image dimensions count • URL field — fetches the raw HTML with no JavaScript executed, which is what a crawler actually sees If a card looks fine in the first mode but falls apart in the second, your tags are rendered client-side and messenger crawlers will never see them. That single comparison explains most "why is my preview broken" cases. WHY THE PERMISSIONS LOOK BROAD Reading page metadata requires access to the page, and checking any address you type requires permission for any address. That is the whole of it: requests go only to the site you are inspecting, and the data never leaves your machine. The source is public — you can verify all of the above rather than take it on trust. NOTE The cards are faithful mock-ups, not screenshots of the real apps. Platforms adjust their layouts over time, and several cache previews for days — after fixing your tags, use that platform's own official tool to refresh its cached preview.