The CraftMyPDF alternative for WordPress Open Graph images
CraftMyPDF is a PDF and image generation API with Canva imports and template-based rendering for documents and graphics. SleekPixel solves a narrower job: every WordPress post gets its own OG image generated on save, with the template living inside wp-admin.
♾️ Lifetime License available
A PDF-first API is an awkward fit for per-post OG cards
CraftMyPDF is built around document generation. Its template editor was designed for PDFs first, with image output added so the same template can produce a PNG or JPEG for marketing graphics. It accepts JSON payloads, supports Canva imports for the design step, and exposes a REST API plus a Make and Zapier integration. For teams generating invoices, reports, and contracts at scale, it is a well-shaped tool.
Using it for WordPress Open Graph images means picking up the rest of the document-generation machinery to solve a much smaller problem. The WordPress integration has to build a JSON payload from the post, call the API on save_post, wait for the response, download the PNG, attach it to the post, then emit the meta tags. Each save adds an external dependency and a metered render to a workflow that lives inside WordPress.
SleekPixel takes the direct path. The template editor is inside wp-admin, the renderer is Playwright running on the WordPress server, and the output is a media library attachment wired straight into the OG and Twitter meta tags. There is no API call, no JSON payload to maintain, and no per-render charge.
Workflow
How a CraftMyPDF API call becomes a WordPress save
Capture the template spec
Recreate the design in SleekPixel
Enable auto-generation
Drop the API dependency
Comparison
SleekPixel vs CraftMyPDF at a glance
save_post hookDifferences
What changes when you move off CraftMyPDF
The CraftMyPDF way
- Designed for PDFs and documents first, with image output as a secondary mode
- No native WordPress integration; requires custom code or an automation scenario
- Templates live in the CraftMyPDF dashboard, not inside WordPress
- Per-render billing meters every OG image, including bulk regenerates
- Field bindings come from the API payload, not WordPress post data directly
The SleekPixel way
- WordPress-native template editor and renderer
- Bindings to post fields, ACF, Meta Box, and Pods without a JSON payload
- Renders on the WordPress server through Playwright, no API call
- Format-specific dimensions for OG, Twitter, Instagram, Pinterest
- Output stored as a media library attachment, OG meta tags emitted automatically
Features
Three things that actually change how you work
Templates designed in wp-admin
The template editor lives inside WordPress. Layers bind to the same post fields editors already maintain, so there is no separate dashboard to keep in sync and no JSON schema to hand-write.
Save-time render, no API call
Playwright renders the image on the WordPress host when a post is saved. The pipeline does not depend on an external service or webhook completing in time for the share preview to update.
Format-specific output
The same template produces OG, Twitter, Instagram, and Pinterest variants in the right dimensions. Each variant is stored as its own attachment and emitted on the matching meta tag.
Migration
Moving from CraftMyPDF to SleekPixel
1. Identify the CraftMyPDF templates used for OG
In the CraftMyPDF dashboard, list the templates that the WordPress integration calls. Note the layout, fonts, and which payload fields they read. That set is the spec for the SleekPixel templates.
2. Rebuild templates inside wp-admin
Use the SleekPixel template editor to recreate each layout and bind layers to post title, excerpt, author, featured image, and any custom fields equivalent to the JSON payload fields.
3. Run the backfill
SleekPixel includes a one-time bulk regenerate so the existing archive picks up the new templates without re-saving each post by hand.
4. Disable the CraftMyPDF webhook
Turn off the Make, Zapier, or custom code that posts to CraftMyPDF on save. SleekPixel emits the OG and Twitter meta tags directly, so the external dependency drops out.
Audience
Where teams move from CraftMyPDF to SleekPixel
WordPress sites using CraftMyPDF only for OG
Teams that adopted CraftMyPDF for documents and stretched it to cover social cards usually find SleekPixel a better fit for the WordPress half. The PDF pipeline keeps running on CraftMyPDF, the OG pipeline moves into wp-admin.
Sites with thousands of posts or products
Per-render billing turns a bulk regenerate into a line item. SleekPixel renders locally with no marginal cost, so iterating on the template or refreshing the archive does not need a budget approval.
Operations teams consolidating WordPress tooling
When the goal is to keep publishing-side jobs on the WordPress host, an OG pipeline that depends on an external API stands out. SleekPixel brings that piece in line with the rest of the stack.
The bigger picture
Why the WordPress side of an OG pipeline belongs in WordPress
Document generation and per-post social cards look similar from the template angle and live in different worlds operationally. A PDF or marketing graphic typically gets built once on demand, in response to a form submission or a CRM event, and the render-on-API-call model fits naturally. A WordPress OG image gets built every time a post is saved, sits in the media library next to the rest of the site's assets, and needs to be in place before the URL is shared.
Forcing it through an external API turns a publish-flow step into a distributed system with its own dependencies. CraftMyPDF makes complete sense as a documents tool, and many teams adopt it for that primary use, then stretch it sideways to cover OG because it can technically produce a PNG. That stretching is where the cost shows up: the dashboard is on a different host, the templates are maintained separately from WordPress, the per-render meter counts every bulk regenerate, and the failure modes of the API now apply to the publish path.
SleekPixel keeps the OG pipeline local. Templates live where editors already work, the renderer runs on the WordPress server, the output is an attachment, and the meta tags update on save. The document pipeline keeps running on CraftMyPDF where it belongs, and the OG pipeline stops being a cross-stack dependency.
Questions
Common questions about switching from CraftMyPDF
No. CraftMyPDF's main job is generating PDFs from templates against JSON payloads, and that remains the right tool for invoices, contracts, reports, and similar document workflows. SleekPixel does not produce PDFs and is not trying to. What it replaces is the slice where a team has been using CraftMyPDF's image output to cover the WordPress OG image pipeline. That slice becomes a WordPress template plus an automatic save-time render, while the document pipeline stays on CraftMyPDF.
 Not directly. The SleekPixel template editor is HTML and CSS at the layer level, so a Canva file would need to be translated rather than imported. In practice the layouts most teams use for OG are simple enough to rebuild in the wp-admin editor in a few minutes, and the resulting template is easier to maintain because it lives in WordPress next to the data it renders against.
 In the WordPress media library as real attachments, on whatever storage the site already uses. There is no SleekPixel cloud, no remote URL dependency, and no risk of an external service outage breaking the share preview. If the media library is fronted by a CDN, SleekPixel's attachments go through that same CDN like any other upload.
 Yes. A single template can output multiple format-specific variants in the right dimensions for each platform. The renderer produces one attachment per variant and the meta tags point at the right size for each network automatically, with no extra configuration per post.
 The plugin ships with a managed Playwright runtime and a fallback path. On most modern WordPress hosts the renderer runs without extra setup. For hosts that block headless Chromium entirely, the documentation covers a remote-render mode that keeps the template and data inside WordPress while delegating the actual rendering to a worker.
 Bulk regenerate processes posts in batches and runs in the background. A large archive takes longer in absolute terms, but the local model means there is no per-render fee and no quota to watch. Iteration on the template stays cheap, which usually matters more than absolute speed for OG images that only get refreshed when the design changes.
 SleekPixel emits OG and Twitter meta tags for posts it has rendered. Most SEO plugins respect an existing OG image on the post; the documentation covers Yoast, Rank Math, and SEOPress explicitly. In practice the SEO plugin either yields to SleekPixel's tags or points at the generated attachment, and the two settle without conflict.
 Yes. SleekPixel only touches the WordPress OG image flow. CraftMyPDF continues to run the PDF pipelines, the marketing graphics flows that live in Make or Zapier, and any non-WordPress integrations. The migration is scoped to a single use case and does not require the CraftMyPDF account to be cancelled.
 Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout