Ask HN: Would you use a service that generates OG images via one meta tag?

Most sites don’t bother with Open Graph images for every page (blog posts, product pages, docs, etc.), which leads to boring or broken previews on Twitter/LinkedIn/Slack.

I’ve been experimenting with a hosted service where you add just one meta tag like:

<meta property="og:image" content="https://uselinkshot.com/acc_123/tmp_456?url=https://yoursite.com/page" />

When someone shares your page, the OG image is generated dynamically (via browser rendering), cached with stale-while-revalidate, and served quickly. You can set up templates for consistent branding, titles, etc.

This avoids:

Manually designing images for each page

Running your own Puppeteer/Playwright setup

Adding heavy infra for what’s essentially a small but important detail

My questions for HN:

Is this actually a pain point you’ve run into?

Would you trust a third-party service for OG images, or prefer rolling your own?

What would make this useful enough to adopt (API access, cache-busting, more control, pricing)?

I’d love to hear whether this scratches a real itch or is just a “nice-to-have.”