Vidstack is a modern, framework-agnostic video player favored by developer-led WordPress builds, headless setups and React-on-WordPress front ends. It does not prescribe how the video metadata is stored; that lives in the surrounding post on the WordPress side. Title, duration, hosting provider, captions reference, episode tags, all of it sits in post meta and gets passed into the player on render.

That same surrounding post is the natural home for the share image, but nothing renders the share image by default. A new episode published with Vidstack as the player shares with whatever OG the theme or the headless front end provides, which is almost always a generic banner. The detail and care that went into the player setup ends at the player, and the social preview stays disconnected from the work.

SleekPixel runs on the WordPress side regardless of how the front end is rendered. It reads the post meta the Vidstack embed already depends on, and on save it renders a 1280 by 720 thumbnail and 1200 by 630 OG card with the video title, duration, episode mark and brand wordmark. The card gets stored in uploads and set as og:image on the post URL, so every share (whether the front end is classic WordPress or a Next.js client) gets a real branded preview.

Headless and developer-led WordPress builds tend to over-invest in the playback experience and under-invest in the share surface, because the share surface is hidden by the platform and never feels broken until someone notices it months in. Vidstack gives the player real flexibility, but it does not produce share images, and most headless front ends settle for a default OG that says nothing about the video being shared. SleekPixel lives on the WordPress server and writes the og:image as part of the post save.

Whichever front end consumes the post (a classic WordPress theme, a Next.js head, an Astro head) inherits the right preview automatically, since the og:image is part of the post URL not the front-end render. Episode and series metadata bind to the same slots they bind to in the player, so the card reads like the player and the player reads like the card. The brand carries through every share without the team writing a separate image pipeline.