Approved campaign data
in every asset
Design branded marketing templates once and generate campaign assets, social banners, and performance reports across every required dimension.
Free account, no credit card
Built for marketing workflows
Social Media Graphics
Map approved campaign copy and images into templates sized for each social placement.
Open Graph Images
Create page-specific Open Graph images from titles, authors, product values, and maintained brand assets.
Campaign Reports
Place reviewed analytics values, chart data, and written summaries into a recurring PDF report.
Email Assets
Render header images and campaign banners from the copy, offer, audience, and dimensions you provide.
Ad Variations
Submit rows of approved copy and images across required ad sizes. Track failures and review results by variation.
Brand Collateral
Reuse approved layouts for one-pagers, case studies, and sell sheets while content changes by record.
How it works
Approve the template and profiles
Start from the gallery or your own HTML. Add brand assets, define each output size, and test real campaign edge cases.
Map reviewed campaign data
Use a connector, webhook, or API to supply the copy, images, analytics values, and identifiers each template expects.
Render, review, and distribute
Track each image or PDF, complete the required approval, and route it to the scheduler, email tool, storage, or team drive.
Separate brand rules from campaign values
Templates hold the approved colors, fonts, logo rules, spacing, and shared layout. Campaign records supply the copy and images that change. Use roles, history, and explicit approval to control who can alter either side of that boundary.
Generate PNG, JPEG, AVIF, or WebP images at named dimensions. A batch can group the output set, while each finished image remains one render. Review every profile after a brand or platform requirement changes.
A template encodes the brand choices it was built and approved to carry. It cannot judge whether campaign copy, imagery, claims, or a new placement meets brand policy, so keep those checks in the content review process.
Template Versioning
Publish and select template versions deliberately. Keep existing workflows pointed at the intended version while testing a replacement.
Brand Asset CDN
Store fonts, logos, and reusable images as managed assets that templates can reference through the CDN.
Multi-Format Output
Use one content record across several output formats and sizes, and group related renders in a batch when useful.
Team Permissions
Assign template, asset, and account access by role so content work does not require sharing API credentials.
Marketing workflow examples
Blog publish to social graphics
- The CMS emits the chosen publish or approval event.
- The workflow validates the title, author, image, and page URL.
- cloudlayer.io renders the selected Open Graph and social profiles.
- The results move through review and into the publishing workflow.
Campaign report to PDF
- A scheduled workflow collects the approved reporting period and metrics.
- It validates chart inputs and maps them into the report template.
- cloudlayer.io renders the PDF.
- The workflow routes the result to the chosen channel and storage path.
A rebrand changes future renders, not published files
Update the brand record, shared assets, and templates, then test and approve each output profile. New renders use the approved changes. Existing ads, posts, downloads, and email assets stay where they were published until your workflow replaces them, so keep an asset inventory with the campaign.
Four assets, one template each, all reading the same brand values. Change a value and every frame below redraws.
4 assets rendered from 4 templates, all reading the same brand record.
- Northwind Meet the new release
Email header Campaign send · 1200 x 400 px - Northwind Meet the new release
One-pager Sales handout · 210 x 297 mm - Northwind New release
Display ad Google Display · 300 x 250 px
The four frames above demonstrate separate proportions rather than permanent platform rules. Store each campaign's required width, height, format, crop, and safe area in a named profile. Confirm those values against the destination before launch because platform requirements change.
How many assets does one campaign really need?
Count channels, placements, creative variants, and languages before choosing plan volume. A product launch on 4 channels with 3 placements each and 2 languages produces 24 finished files before test renders or corrections are added.
Where the multiplication comes from
- Channels. List the paid, organic, email, site, and other destinations in the actual campaign plan. Each can have its own delivery rules.
- Placements inside a channel. A channel may require several aspect ratios or placements. Record the dimensions published for the campaign date.
- Variants for testing. 2 headlines against 2 images is 4 creatives per placement, not two.
- Languages and regions. Each locale can repeat the output set, and its copy length or imagery may require a separate review.
Translate the set into render usage
Separate template design from routine production. The designer owns the reusable composition and its edge cases. Campaign operations supply approved values and request the profiles needed for that launch.
The 24-file example can be grouped in a batch, but each finished output still uses 1 render. A later copy change uses new renders only for the profiles and variants you request again.
At 20 campaigns a month with 24 final assets each, the final set uses 480 renders. Add proofs, failed inputs, corrections, and other account workflows before choosing a plan.
Why do generated assets get rejected at upload?
Destinations can reject, crop, or recompress an asset when its dimensions, aspect ratio, format, file size, or safe area does not fit the placement. Encode reviewed requirements in named profiles, and confirm them again when the platform changes its rules.
- Story safe area
- Keep text and key imagery outside the interface areas published for the selected story placement.
- Link preview
- Use the current preview dimensions and test how the destination crops the image in each surface you rely on.
- Display ad units
- Create only the units in the approved media plan, using the ad network's published size and file rules.
- Pixel density
- Set device scale when the destination and file-size budget call for denser raster output.
- Minimum legible type
- Choose a minimum from the actual placement and test the asset at its displayed size instead of only on the design canvas.
- Print handout
- Set the requested page size, margins, bleed, and printer marks, then proof the rendered PDF with the printer.
What happens when the copy is longer than the design allows?
Sample copy rarely shows the longest value the template will receive. Decide whether text wraps, clamps, resizes, or changes the composition. Then test that rule with real headlines and translations before the template enters routine production.
The four things a layout can do
- Wrap. The block grows and pushes what follows. Reserve enough space or let the surrounding composition respond to the added lines.
- Shrink the type. Set a minimum based on the final display size. When copy reaches that floor, use another rule instead of making it smaller again.
- Truncate. Clamp only where the content owner has approved omission. A cut headline can change meaning, so do not make this an accidental fallback.
- Reflow the composition. Use CSS layout rules to adjust image and text regions together when the selected profile has room for a responsive composition.
Use browser layout tools for content changes
HTML and CSS templates can use flexbox, grid, calculated sizes, and line clamping. Choose the rule that fits the asset, and test the rendered output rather than assuming browser layout alone makes every content value safe.
The visual designer and code editor share the document model. Protected source regions preserve markup the visual editor does not rewrite. That lets a template author combine visual work with explicit CSS behavior where the layout needs it.
Images need their own rules. Define aspect ratio, fit, crop, and focal treatment for each profile, then test portrait, landscape, low-resolution, and missing-image cases from the real campaign feed.
Before a template enters rotation, run at least 5 deliberate cases: the longest approved headline, a long translation, a portrait image, a landscape image, and a missing image. Add any channel-specific edge cases from the campaign plan and inspect every output profile.
Decide what a campaign change should rerender
Not every edit affects every output. A price may appear in paid ads and email banners but not in the Open Graph image. A legal line may apply only to one region. Record which fields each profile reads so a late change produces the needed files without silently leaving a published asset stale.
Build the dependency map
- Name the source fields. Give the headline, offer, dates, locale, legal copy, image, and tracking URL stable keys.
- List the profiles that read each field. Keep the relationship in campaign configuration or code rather than in somebody's memory.
- Track the published destination. Store where each approved result was sent so the replacement workflow has a target.
- Keep the render identifier. Link each file back to the campaign version and source values that produced it.
Handle a late change in stages
Update and approve the source value first. Resolve the affected profiles from the dependency map, then submit those renders as one tracked set. A set of 6 replacement files uses 6 renders, even when every file comes from the same campaign record.
Review the new set against the campaign version it will replace. Check copy, crop, destination size, required text, and the URL inside any QR code. Only then hand the files to the publishing or ad-operations workflow.
Keep the old asset according to the campaign's retention rules. A replaced file may still be needed to explain what ran, reconcile reporting, or investigate a claim later. Generation creates the new file; it does not remove the old one from external platforms.
Questions, answered
How do I generate social images for every blog post?
Build and approve a template, then send each post's title, author, image, and destination size. Review the generated result before passing it to the publishing workflow.
Can I produce different sizes for each platform?
Yes. Use named output profiles or separate templates for each placement. Each finished size is its own render, even when the outputs reuse the same content and brand assets.
Do I need a designer for every campaign?
A designer or template owner builds and tests the reusable layout. Other team members can supply approved copy and images without editing the design, subject to workspace roles and review steps.
Can I automate campaign reports?
Yes. Schedule the workflow, supply reviewed analytics values and chart data, and render the report template. Route the PDF through the same approval and delivery process used for other reports.
What sizes should a campaign asset set actually cover?
Cover the placements in the approved campaign plan and use the dimensions published by each destination. Keep those values in named profiles so they can be reviewed and changed without rewriting campaign copy. Test safe areas, crops, and file-size rules before launch.
What happens when a headline is longer than the design allows?
Define that behavior in the template. CSS can wrap or clamp text, adjust layout, or scale type within limits you choose. Test the longest approved headline, translations, missing images, and both portrait and landscape source images before using the template.
How many renders does a campaign use?
One finished asset uses 1 render. A launch on 4 channels with 3 placements each and 2 languages produces 24 files and uses 24 renders. Add test and correction runs, then compare the monthly total with the plan allowance.
How do we roll out a rebrand across assets already published?
Update the shared brand assets and templates, test each output profile, and approve the new versions. Then rerender the assets selected for replacement. Files already published do not update by themselves, so track where each active asset lives.
Test one campaign asset set
from approved data
Choose one campaign and verify its templates, sizes, copy limits, image crops, review steps, and publishing path.
No credit card required.