What are dynamic images?

Last updated: 13.08.2025


dynamic images

Auto-generate landing page visuals, social media banners, ecommerce sales pages and more with our API and CRM integrations

Functionality

Dynamic images simplify repetitive marketing and sales tasks, such as creating new ads for each sale or SEO pages for different cities or landing pages for cold outreach.

Integrate Wafrow with your existing CMS and CRM to create a seamless, personalized experience across emails, landing pages, and mobile apps.

No engineer? No problem. No designer? No problem. No translator? No problem.

Use Cases for dynamic images

Travel firm needs city specific SEO / SEM landing page headers

Use your own images or AI with brand guidelines

Header Image for city specific landing pages

Ecommerce firm wants to integrate live Shopify / Klaviyo data

Easily pull in your inventory data or external content like google maps reviews

Rug with one left and question asking should we hold it for you? Rug with on sale tag and question asking should we hold it for you Josh?

SaaS SDRs need custom emails and landing pages for each cold outreach

Add logos and text custom to each client

SDR Cold outreach to Nike SDR cold outreach to Netflix

D2C firm wants personalized creatives for their referral program

Use personal data from your CRM to create targeted email campaigns and landing pages for AB testing

Referral invite from Alisha for a 75 EUR discount on your next hotel trip Referral invite from David for a $20 discount on your next hotel trip

Image Rendering Strategies

Wafrow supports two distinct strategies to render personalized images depending on your delivery model:

1. Pre-render (Generate & Store)

The image is rendered immediately upon API request, and the binary blob is returned in the response. Your system must store the result (e.g., upload to Amazon S3, your CRM's media library, or CMS) before the email or message is dispatched.

Aspect Details
Volume Model 1 Million sends = 1 Million renders
Best For Platforms that require a concrete, static image URL or an email attachment at send time.
Trade-off You pay the rendering cost for every send, including unopened emails.

2. Lazy-render (Recommended for Scale)

Nothing is generated at send time. Instead, you embed the Wafrow endpoint URL directly inside your email's <img> tag. The image is rendered dynamically on the first HTTP request — i.e., when the recipient actually opens the email client.

Aspect Details
Volume Model 1 Million sends ≈ 200K–400K renders (assuming 20–40% email open rate)
Best For High-volume email campaigns and newsletters at any scale.
Bonus If you make a mistake in a template, you can fix it in the editor after sending the email, and unopened emails will render the corrected version!

What Next?