Meta image templates vs Emberfeed: is free enough?

Meta now lets you brand catalog images for free. In Commerce Manager you can build an image template: the product photo, its price and sale price, your logo and text on a background you choose. In Ads Manager, dynamic overlays add price, discount and free-shipping labels to Advantage+ catalog ads. If Meta is the only place your catalog runs and that is what you want on the image, use Meta's tools. They cost nothing and read prices straight from your catalog.

We make Emberfeed, a paid tool that also designs catalog images, so weigh this accordingly. Below: what Meta's tools do (checked against Meta's own help pages on September 30, 2026), where they stop, what Emberfeed costs you that Meta doesn't, and when 25 € per feed per month is worth paying.

What Meta's own tools do

Image templates in Commerce Manager

Image templates are the newest option and the reason this question exists. In Commerce Manager you pick your catalog, open the Catalog tab, go to Image templates and click Create, starting from a blank canvas or one of Meta's starter templates. A template is a stack of layers:

• Product image(required): the main image or one of the first three additional images, with optional background removal and "crop to fit". More product layers show more photos.
• Catalog fields:Meta's help names title, brand, description, price, current (sale) price and custom labels.
• Your own additions: a JPG or PNG such as a logo, free text, and stickers (a circle, rectangle or square with its own text).
• Background: a color behind everything else.

Catalog field, image and text layers also have conditional display: you set a rule on a product attribute (Meta's example is price) and the layer only appears on products that meet it, with no code. The design starts at 1:1, and a 4:5 version is a copy of it that you adjust.

You pick the template per ad in Ads Manager, in a Sales campaign with product data turned on. Templates work with single image and carousel ads, not collection. Meta also tells you to turn off background generation (it would replace your template) and to keep image touch-ups on so 4:5 templates can deliver to Feed and Reels placements. One caveat: Meta says the feature "is being gradually introduced and may not be available to you yet."

Dynamic overlays in Ads Manager

Dynamic overlays are the older, simpler tool: up to four labels built from catalog data (price, strikethrough price, percentage off, and free shipping when the item's shipping cost is 0.0 in the catalog). You pick a rectangle, pill, circle or triangle, the colors, font and position, or let Meta add the most relevant overlay automatically. Space is tight: 13 characters in a rectangle or pill, 6 in a circle or triangle. The limit that matters most is placement: dynamic overlays only show on Facebook Feed (which has included the Friends tab since March 2026), not on Instagram, Stories or Reels.

Frames are being retired

The custom frame, one transparent 1:1 PNG laid over every product, is being replaced by image templates and will not be available after October 30, 2026. Frames are not available on Instagram placements either. If your ads still use one, move the design before that date.

What all of them need

All three are part of Meta's catalog ads. Meta's requirements for Advantage+ catalog ads are a catalog in Commerce Manager (inside a business portfolio) and a Meta pixel (or the SDK, for apps) connected to it. Emberfeed does not change that: its feed becomes the catalog's data source, and the pixel is still yours to set up. Either way, check the ad's Advantage+ creative settings. Background generation is on by default for eligible advertisers, and Meta's template instructions say to switch it off so it does not replace your design.

Where Meta's tools stop

The limits follow from where the design lives. Meta applies templates and overlays when it builds the ad; the image_link in your feed still points at the plain product photo. That is why they are free, and it is also why:

• They only exist on Meta. Google Shopping, TikTok, Heureka, Zboží.cz and Glami read your feed, not your Meta ads, so none of them sees the design.
• The logic is show or hide. Conditional display toggles a layer by a rule on a product attribute. It is not a template language.
• The editor works with layers, not HTML or CSS.
• Coverage has gaps. Templates skip collection ads, and overlays skip everything except Facebook Feed.
• Feed fixes stay inside Meta. Commerce Manager's data rules (change capitalization, map a field, find and replace, set a default, regex replace) and product sets only change what Meta's catalog sees.

None of this matters if you only advertise on Meta. It matters when the same products have to look right in several places.

When Emberfeed is worth 25 € a month

Emberfeed works on the feed instead of the ad. It imports your product feed, renders each product's main image through a template and serves a new feed URL whose image links point at those renders. The design is in the feed, so it goes wherever the feed goes. Six cases where that is worth paying for:

1. One source feed, several platforms

One Emberfeed feed serves one platform, and the Duplicate button copies it for another platform, with its own filters, field rules and template. From one shop export:

• Meta: a branded template with price, sale price and logo.
• Google Shopping: a clean copy, because Google rejects promotional overlays on image_link. It serves the original photos or a plain template (white background, product filling the frame).
• TikTok: its own copy, whose rendered image links end in .jpg or .png, as TikTok's catalog expects.
• Heureka, Zboží.cz and Glami: SHOP/SHOPITEM XML with clean product photos, which is what their image rules ask for.

Each copy is a separate feed at 25 € a month. The free three months cover one feed of up to 1,000 products; after that, a Meta and Google pair is 50 € a month. Why the Google copy has to stay clean: the promotional overlay error.

2. Designs that follow your data

Emberfeed's HTML/CSS templates use Handlebars, so they can branch on the fields in your own feed (a material, a custom label, a delivery date), not only the ones Meta lists, compare numbers and combine conditions, with a computed discount percentage on top. The old and new price only on sale items, a badge for new arrivals and a tag for cheap products that are in stock:

{{#if sale_price}}
  <span class="was">{{groupPrice price}}</span>
  <span class="now">{{groupPrice sale_price}}</span>
{{else}}
  <span class="now">{{groupPrice price}}</span>
{{/if}}

{{#if (eq custom_label_0 "new")}}
  <div class="badge">New in</div>
{{/if}}

{{#if (and (lt (priceNumber price) 50) (eq availability "in stock"))}}
  <div class="tag">Under 50</div>
{{/if}}

To be fair to Meta: its layer editor shows or hides layers by a rule without code, while Emberfeed's drag-and-drop editor has no per-product conditions. In Emberfeed the logic lives in HTML/CSS templates, which Claude can write for you.

3. HTML and CSS instead of a layer panel

If a layout can be written in HTML and CSS, it can be rendered: flexbox, gradients, rounded badges, type sized to the length of the title. You choose the canvas size (the drag-and-drop editor has presets for 1080×1080, 1080×1350 and 1080×1920), and HTML/CSS templates can use your own brand font uploaded as TTF or OTF. The trade-off: Emberfeed renders one image per product per feed, the main image, while a Meta template can carry a 1:1 and a 4:5 version of one design.

4. Fixing the feed itself

Filters (AND/OR groups of conditions on any field) decide which products go out. Field rules rewrite values before they are served: append text, find and replace, fill a field from a Handlebars template, or set it with an if/then/else. They change the XML the platform downloads, each copy keeps its own set, and every product is checked against the target platform's required fields and format rules. If Meta is your only channel, try Commerce Manager's data rules first.

5. The Czech comparison engines

Heureka, Zboží.cz and Glami do not read the RSS format Meta and Google use; they expect SHOP/SHOPITEM XML. Emberfeed imports and serves that format, with a preset for each engine. Meta's tools do not reach these channels at all. Channel notes: Heureka, Zboží.cz, Glami.

6. Letting Claude do the work

Emberfeed's MCP server has 22 tools. With it, Claude can read your feeds and products, draft an HTML/CSS template and preview it on your real products, write filters and field rules, set the output format and run validation. Claude designs the template; the images are your real product photos composed into it. Setup: connecting Claude to Emberfeed.

What Emberfeed costs you that Meta doesn't

• Money.25 € per feed per month, for every platform copy. Meta's tools are free.
• Price freshness.Meta's labels and catalog-field layers follow your catalog data. A price inside an Emberfeed image is part of the picture: it updates after Emberfeed's hourly refresh from your shop, Meta's next fetch of the feed and Meta downloading the new image. (Meta only re-downloads an image whose URL changed, so Emberfeed gives a render a new URL whenever the product or the template changes.) If your prices move several times a day, leave the price to Meta's overlay or template.
• Meta's image advice. Meta's product image specifications recommend against text over the product, promo codes and time-sensitive details such as temporary price drops in catalog images. It is a recommendation, not a rejection rule, but a render with a price in it goes against it. If the same catalog runs a Facebook or Instagram shop, the badge shows there too.
• Another link in the chain. Your catalog reads Emberfeed's feed URL instead of your shop's, and Meta downloads every image from Emberfeed.
• Things only Meta does. AI background generation, picking the most relevant overlay automatically, and conditional layers without code.

Side by side

How to decide

1. Meta is your only catalog channeland you want a price, sale price, discount label or logo on the image: use Meta's image templates, plus dynamic overlays for Facebook Feed. Don't pay for a tool.
2. Your prices change several times a day:keep the price in Meta's overlay or template, whatever else designs the image.
3. The same products also run on Google Shopping, TikTok or the Czech engines, each from one source feed: that is what Emberfeed is for.
4. The design needs real logic on your data, or HTML/CSS:Emberfeed's HTML/CSS templates, written by you or by Claude.
5. The feed needs filtering or fixing beyond Meta:Emberfeed's filters and field rules. For Meta alone, Commerce Manager's data rules come first.

You can also mix them: Meta's templates for your Meta ads, and Emberfeed only for the feeds Meta's tools cannot reach, such as a clean Google feed or Heureka. More on the Meta side in Meta catalog ads with Emberfeed and how Advantage+ catalog ads pick products.

Sources

Meta Business Help Center pages, read on September 30, 2026:

• Create image templates for ads using product media
• Add dynamic overlays in Advantage+ catalog ads
• Add a frame to product images in Advantage+ catalog ads
• Advantage+ catalog ad requirements
• Product image specifications for catalogs
• Add product data rules in Commerce Manager
• Create an Advantage+ catalog ad with background generation