Only for the WordPress OG image use case. RenderForm is a generic image and video generation API that fits a wide range of SaaS automation flows, and many of those flows are not WordPress-shaped. SleekPixel replaces the slice where RenderForm was being called from a WordPress site to produce per-post OG images. If the team also uses RenderForm for video rendering, lead-magnet PDFs, or non-WordPress workflows, those keep running on RenderForm. The WordPress-specific pipeline moves into SleekPixel and drops the API dependency for that job.

On the WordPress host itself, through a Playwright runtime that the plugin manages. When a post is saved, SleekPixel resolves the template against the post data, renders the page in headless Chromium, and writes the resulting PNG to the media library as an attachment. There is no external API call, no webhook to wait on, and no separate billing meter. The render runs against the WordPress server's resources, so the cost shape is the same as serving the rest of the site.

Yes. Each template can output multiple format-specific variants, so the same post produces OG, Twitter, Instagram square, Pinterest pin, and other dimensions from one template. The renderer applies the right canvas size and emits each variant as its own attachment. The meta tags pick up the correct variant for each platform automatically.

SleekPixel is image-only. Per-post OG video cards are an unusual ask, and the supported social platforms still expect static images for the main share card. If the project needs templated video rendering as part of a broader marketing pipeline, RenderForm remains the right tool for that piece. SleekPixel and a video-rendering service can coexist without overlap.

RenderForm is metered per render with a plan tier on top. A WordPress site that publishes daily, runs a bulk regenerate, or maintains a large archive can run up the render count quickly. SleekPixel is a flat plugin license with no per-image cost, so the cost stays predictable regardless of how many posts get re-rendered or how large the archive grows.

Yes. Every save triggers a re-render against the current template and current post data. A bulk regenerate is also available for when the template changes and the whole archive needs to pick up the new design. The bulk job runs locally and has no marginal cost, so design iteration stays cheap.

Yes. The template editor exposes a picker for core post fields, taxonomies, and the major custom-field plugins, so a slot can bind directly to an ACF field, a Meta Box field, a Pods field, or a custom taxonomy term. The renderer reads the value on save and writes the result to the media library, with no per-post copy step.

They coexist cleanly. SleekPixel only owns the WordPress save-time OG pipeline. RenderForm continues to handle the marketing automation, lead-magnet, and video rendering flows that live outside WordPress. The migration only touches the WordPress integration, not the rest of the RenderForm account.