Question 1

Can I preview meta tags for localhost or internal development URLs?

Accepted Answer

Yes. Because this tool runs 100% in your browser without relying on remote server crawlers, you can input local URLs or paste HTML directly to inspect card formatting before launching.

Question 2

What is the recommended image size for Open Graph cards?

Accepted Answer

The recommended size is 1200 x 630 pixels (an aspect ratio of 1.91:1). This resolution ensures sharp rendering across high-DPI displays on Facebook, LinkedIn, Twitter, and Slack.

Question 3

What is the difference between og:description and meta name='description'?

Accepted Answer

The standard meta description is used by search engine crawlers like Google for SERP snippets, while og:description is specifically read by social network platforms when sharing links.

Question 4

Why does Twitter sometimes fail to render my summary_large_image card?

Accepted Answer

Twitter requires twitter:card to be set to summary_large_image along with twitter:title and twitter:image. If the image exceeds 5MB or returns a 404, it falls back to a standard text snippet.

Question 5

Does this tool store or upload my preview content to any remote server?

Accepted Answer

No. All preview rendering, character counting, and tag generation occur strictly in your local browser memory using JavaScript. No user data is transmitted.

Question 6

What happens if a page defines both Open Graph and Twitter card tags?

Accepted Answer

Twitter will prioritize twitter:* tags if present. If specific Twitter tags are missing, Twitter gracefully falls back to the corresponding og:* tags.

Metadata Configuration

Generated HTML Tags

Frequently Asked Questions