Skip to main content
Ink·tab
all tools

KakaoTalk · X · Facebook card preview

Check how seven platforms render your card before publishing. The URL is never fetched.

Input
Platform preview
KakaoTalk
Inktab
Inktab — 개발자의 공구상자
JSON · 정규식 · 이미지 · 색 · 시간 도구 34 종을 브라우저 안에서. 로그인·업로드 없이 한 탭…
inktab.studio

Everything happens in your browser. Nothing is uploaded.

When you'd use this

Right before you publish a blog post, landing page, or newsletter — to see how the link card will render when shared on KakaoTalk, X, Slack, and the rest. Especially useful for unpublished staging URLs, internal pages, or localhost where external tools can't reach.

Two input modes

  • Fields mode — Type og:title, og:description, og:image, og:url directly. Useful when you're still drafting the meta tags and want to test combinations.
  • Paste HTML mode — Paste your head's meta tags (or the entire page HTML) and og:, twitter:, and standard tags are extracted automatically.

Seven platform previews at once

KakaoTalk · X / Twitter · Facebook · LinkedIn · Discord · Slack · iMessage. Each platform uses different card shapes, title lengths, and image aspect ratios.

  • KakaoTalk — Square thumbnail + short title. A large share of Korean traffic comes from KakaoTalk; most global tools skip this format.
  • X (formerly Twitter) — With twitter:card="summary_large_image", a 1.91:1 large-image card. Titles around 70 characters.
  • Facebook · LinkedIn — 1.91:1 image with a meta strip below.
  • Discord · Slack — Rich embed style with a left color bar.
  • iMessage — Rounded card with a large image plus title + host.

Your URL is never fetched

Tools like opengraph.xyz or share-preview.com fetch the URL you submit and parse it server-side. That doesn't work for unpublished URLs, intranet pages, or localhost. Here the page is never fetched — you paste meta tags or fill fields directly.

The og:image URL is loaded by your browser to render the preview (no relay). Public or CORS-permitted images render in the card; private images show a "No image" placeholder.

When this isn't the right tool

  • Verifying an already-published URL's meta — opengraph.xyz is easier (paste URL, it fetches automatically).
  • Compressing the image — this tool only previews. To shrink the file, use image-compress or image-resize.
  • Invalidating the social platform's cache — Facebook / KakaoTalk debuggers handle cache busting separately. This tool is for the pre-publish preview only.

Your URL is never fetched

Most OG preview tools fetch the URL you submit and parse it server-side — unfit for unpublished URLs, internal pages, or localhost. This one only renders mockups from the meta tags you paste or fields you fill in. og:image URLs are loaded directly by your browser for the preview (never via a relay).

Frequently asked questions

How is this different from existing OG preview tools?
Tools like opengraph.xyz or share-preview.com fetch the URL you submit and parse it server-side. That doesn't work for unpublished staging URLs, intranet pages, or localhost. Here you paste meta tags or fill fields directly — the page is never fetched.
Why include KakaoTalk?
A large share of Korean traffic comes from KakaoTalk shares, but most global OG tools don't model the KakaoTalk card format. KakaoTalk truncates titles aggressively and prefers a square thumbnail — different rules from X / Facebook.
Does the og:image actually render?
Yes. The image URL is loaded directly by your browser to render the preview — so the image is fetched once from your IP (no relay). Public or CORS-permitted images render in the card; private images show only their alt text.
Which meta tags are recognized?
og:title · og:description · og:image · og:url · og:site_name · og:type · twitter:card · twitter:title · twitter:description · twitter:image · standard '<title>' · '<meta name="description">' · '<link rel="canonical">'. Priority: og:* > twitter:* > standard.