FastOG vs ogdynamic: A Canvas You Design In, or a Plugin That Reads Your Catalogue?

Short answer

ogdynamic is a design tool with an image API attached. You lay out a card on a free-form canvas — layers, nested groups, flexbox and grid, 103 Google Fonts — mark the layers your data should control, and every variation renders from a URL on their infrastructure. Their WordPress plugin connects your site by OAuth and maps each content type to a canvas you designed there.

FastOG is the other shape. Install the plugin from WordPress.org, connect the store, pick a starting look per page type, and product, category, shop and blog-post pages serve a designed cover built from the live catalogue. Nobody opens a canvas, because there is no canvas to open.

That is the whole difference. If you want to design the card yourself, layer by layer, ogdynamic is the closer product and this page says so below. If the requirement is that every product link carries a correct, current card without anyone designing anything, the plugin is the shorter path — and the free tier is how you find out.

What each product is actually for

Responsibility ogdynamic FastOG
What you buy A canvas editor and URL-based image API; the WordPress plugin is one client of it A WooCommerce plugin, backed by a render service and cache
Who designs the card You, on a free-form canvas Nobody — 47 curated templates, chosen per page type
What triggers a product cover A template mapping per post type in wp-admin, values pushed to their renderer The plugin, reading the product on each request
Reading live price, sale price and stock Mapped WooCommerce fields: title, price, regular and sale price, SKU, stock status, rating, review count, categories, tags, attributes Read per request from WooCommerce, including compare-at price and stock badges
Templates 36 templates across 11 categories, plus any canvas you design 47 selectable templates, including ecommerce, product, fashion and seasonal looks
Who prints the og:image tag Their plugin, with an SEO-coexistence list covering Yoast, Rank Math, AIOSEO, SEOPress, The SEO Framework, Squirrly and Slim SEO The plugin, through Yoast, Rank Math, AIOSEO or SEOPress filters, printing first
Where the render runs Their Rust engine, delivered from their CDN FastOG render service, served from FastOG cache and edge
Sizes and formats Open Graph 1200×630, X, square, story and Pinterest presets; webp, png, jpeg 1200×630 covers for product, category, shop and blog-post pages
Signing None required to render — a canvas URL plus query parameters is the API HMAC-signed URLs; the plugin signs for you, the API requires it
Published pricing No pricing page as of 1 November 2026; the terms describe a free tier with a monthly generation limit visible in the dashboard Free Community plan to 100 items, paid plans from $19/month
WordPress.org installs Fewer than 10 active, 374 downloads since 29 May 2026 1,374 downloads since 24 September 2026
Languages Not published Plugin and Studio in 27 languages

The row that decides the project is the second one. A canvas tool asks a person to make a design decision once, then asks them to keep mapping fields into it as the catalogue changes. A catalogue-driven plugin removes that decision. Neither is free: the canvas buys control, the plugin buys the absence of work.

The mapping work, stated plainly

With ogdynamic the flow is: design a canvas, publish it, open the WordPress admin, choose it for a post type, then map each template field to a WordPress source — post title to the headline field, featured image to the background, author to the byline. Fields that resolve to nothing are dropped before the render URL is built (ImageGenerator::filter_params() in the GPL plugin source), so a product with no price does not leave a gap in the card: the canvas renders the default its designer set for that layer. That is friendlier than a hole, and it still means a placeholder value can appear where a price should be.

For one post type that is ten minutes. For products, categories, the shop archive and blog posts it is four mappings, and each one is a thing to re-check when a template is edited or the catalogue gains an attribute someone wants on the card.

FastOG's plugin does the branching itself. Product, category, shop and blog-post covers are selected from the page type being rendered, so the merchant builds no per-page URLs and maps no fields. Each cover URL is content-addressed: when the data behind it changes, the URL changes, so the cache gets a new address while the product permalink stays the same. The mechanics are in og:image caching.

What ogdynamic does better

Be clear about this before installing anything:

  • The canvas is real. Layers, nested groups, flexbox and CSS grid, absolute positioning and edge anchors, z-order, per-corner radius, shadows, filters, transforms and blend modes. FastOG has no free-form canvas at all. If you have a designer and a strong opinion about the layout, ogdynamic gives you the surface to express it.
  • Rendering needs no signature. Every public canvas has a permanent URL and query parameters override the dynamic layers. That makes it trivially usable from a spreadsheet, a script or an agent, with no key exchange. FastOG's API path is HMAC-signed; the plugin hides that, but a developer poking at the API will feel it.
  • Preview matches production. Their editor preview runs the same Rust engine compiled to WebAssembly, so what you design is what the URL serves. That is a genuinely good trust signal for a design tool.
  • Wider than link previews. Their headline is email banners, product images and social images as well as OG. If you need one vendor for a Mailchimp banner and a product card, that breadth is the reason to pick them.

What FastOG does better

  • It reads the catalogue. No OAuth, no per-post-type mapping, no field-by-field wiring: install, connect, choose page types.
  • A real commercial model. Free Community covers up to 100 items with four base templates plus the Black Friday and Seasonal Offer product templates, no card and no watermark. Paid plans start at $19/month for 250 items and 24 curated templates. ogdynamic publishes no pricing page, so a store cannot budget for it before signing up.
  • Signed render URLs. A scraped FastOG URL cannot be re-signed to burn someone's render capacity. ogdynamic's render URLs need no key by design, which is convenient and also means the cost control sits entirely on their side.
  • Breadth of the working parts — 47 templates, Node and PHP signer SDKs, diagnostics for link previews that do not show, cache behaviour, WhatsApp cropping and og:image ownership, in 27 languages.
  • Install base. 1,374 downloads in about five weeks versus 374 in about five months. That is not proof of quality; it is proof of which one other merchants are trying.

Where ogdynamic is the better buy

If the job is "design branded images for email, social and product pages from one template system", ogdynamic is a canvas-first product and FastOG is not a substitute. Same if you want an agent to render images with no signing step, or if you have design capacity and want control down to the anchor point.

If the job is "my WooCommerce product links should not look broken on WhatsApp, and the card should show today's price", the canvas is a detour. The plugin is the thing.

A practical decision rule

Use ogdynamic when a person must design the image and the set of variations is small and known.

Use FastOG when the images are a function of the catalogue — many products, prices that change, covers that must stay current without anyone touching them.

Either way, verify the result the same way: one effective og:image tag in the live HTML, a public 200 image response, current product values in the rendered cover, and a stable canonical product URL. The Free OG Image Tester renders the FastOG templates with your own data, no signup required, and WooCommerce stores can install the plugin and generate covers from the catalogue.

Sources and implementation notes

FastOG-specific claims are based on the WooCommerce plugin implementation and its integration tests. ogdynamic claims are taken from their published pages on 1 November 2026 and from the WordPress.org listing of the same date; where their pages disagree with each other (canvas size limits differ between the features page, the homepage FAQ and the API docs) no figure is repeated here.

Try it free — no signup required

Preview and test dynamic OG images in seconds.

Open the Free OG Image Tester