IMG.LY: Blog

CE.SDK v1.77 Release Notes

Neslihan — Wed, 01 Jul 2026 00:00:00 GMT

CE.SDK v1.77 is a workflow, typography, and platform release focused on making editing faster, more expressive, and more flexible across web, mobile, and backend environments.

This release brings keyboard shortcuts and better typeface discovery to the web, expands text styling and editing workflows on mobile, and improves performance for large photobook-style scenes. Lastly, you can add a branded photo camera to mobile!

Let’s dive in.

Create and Edit Faster

Speed Up Editing with Keyboard Shortcuts

CE.SDK now ships with keyboard shortcuts in the web editor, with 30 shortcuts out of the box for selection, editing, text formatting, zoom, undo, and playback.

Need something custom? Register your own through the cesdk.shortcuts.set API with single keys, modifier combinations, or multi-step sequences. Each shortcut can be scoped to a specific part of the UI so it only fires when it should.

Users can move faster without leaving the canvas, with shortcuts that match the tools they already know.

→ Keyboard Shortcut List & Documentation

Find the Right Typeface Faster

The web editor now comes with typeface browsing. Users can search, filter, and navigate typefaces more easily, making large font libraries feel more structured and easier to manage.

For your product, this means: a more polished typography experience without needing to build your own font discovery UI.

→ Customize Fonts Documentation

More Expressive Typography

Shape Text Around Paths for Web & Mobile

CE.SDK now supports text on curves, including the APIs and layout behavior needed to place and render text along circular and curved paths.

This opens up more expressive typography workflows for logos, badges, invitations, and other layout-driven designs. Now available for Web, iOS & Android.

For your product, this means: users can create more flexible text layouts directly in the editor instead of switching to external design tools.

Edit Text Documentation:
→ Web
→ iOS
→ Android

Bring Richer Text Workflows to Mobile

This release also expands how text is created and styled across iOS and Android.

Text and paragraph style presets are now available on iOS and Android. Apply and reuse consistent text styles without restyling everything from scratch.

Inline text run editing is also new. Select part of a text block and style just that portion, without affecting the rest.

Have More Control over Text Layout APIs

CE.SDK v1.77 also extends text positioning and layout capabilities through engine APIs.

This makes advanced text placement, alignment, and layout behavior easier to control in integrations that need more precise typography handling, including multilingual and design-heavy workflows.

→ Upgrade to v1.77

Mobile Creation Workflows

Remove Image Backgrounds on iOS and Android

Background removal is now available on iOS and Android. The same plugin your web editor uses, now on mobile.

For your product, this means: users can remove image backgrounds without leaving your app, on any platform you ship on.

→ Android Background Removal Documentation
→ iOS Background Removal Documentation

Add a Photo Camera to iOS and Android

Photo Camera is now part of CE.SDK on iOS and Android. Users capture photos and videos, then move straight into editing — all inside your app.

Useful for listing flows, content creation, document capture, or any mobile workflow where capture and editing need to feel like one thing.

For your product, this means: one less integration to manage, and a creation flow that stays inside your product. From taking a photo to a finished edit.

→ iOS Camera Configuration Documentation
→ Android Camera Configuration Documentation

Improvements

Import Richer Documents With Higher Fidelity

Our importer packages now preserve more of the structure and styling that matter in real-world design files.

PDF importer now keeps inline-styled text together as a single editable block while preserving mixed weights, styles, and colors.
PSD importer now supports Photoshop stroke layer styles and improves fallback behavior for off-canvas text.
PPTX importer now imports text decorations and nested lists. This includes your Canva designs exported as PPTX.
IDML importer can now import embedded PDF and Adobe Illustrator graphics as editable blocks instead of placeholders.

Imported content stays more editable, more faithful to the source, and requires less cleanup after import.

→ Explore Importer Demos

Export Print PDFs with Transparency & Vectors

Print-ready PDF export now supports PDF/X-4, preserving live transparency and vector text for more faithful, standards-compliant print workflows.

Handle Large Photobook Projects More Smoothly

We improved performance for large, image-heavy scenes such as photobooks and other complex multipage projects, reducing bottlenecks and keeping editing workflows more responsive as scene complexity grows. Users can smoothly work on and scroll through larger projects.

→ Explore Photobook Solutions

Developer Experience

Extend Your Mobile App with Plugins

This release makes it easier to extend your mobile app with add-on features and more customizable editing flows on iOS and Android.

Build more tailored mobile editing experiences with options like:

adding background removal on iOS and Android
integrating AI image generation on iOS and Android
building custom Android plugins to extend editor behavior
packaging mobile features as reusable plugin modules that are easier to integrate and maintain

→ iOS Background Removal Documentation
→ Android Background Removal Documentation
→ Android Custom Plugin Documentation
→ iOS AI Image Generation Documentation
→ Android AI Image Generation Documentation

Make Error Handling Easier to Understand

We improved error reporting with structured errors and better surfacing through bindings, making integration issues easier to diagnose and handle.

Update to Node.js 22

Node.js 22 is now the minimum supported version. Node.js 20 stopped receiving security updates in April 2026, so we strongly recommend upgrading to a supported version.

Changelog

All performance improvements, breaking changes, and fixes are in the v1.77.0 changelog.

Thank you for building with IMG.LY.

The Best GenAI Models for Web-to-Print: A Buyer's Guide

Jan — Fri, 26 Jun 2026 00:00:00 GMT

No single generative model is “best” for web-to-print. The right pick depends on the specific job, and print has jobs that screen-first leaderboards don’t measure. A model that tops a general image-quality benchmark can still be useless for print if it can’t render legible text, can’t output vector, or shifts hard out of CMYK gamut.

This guide gives you the criteria that actually matter for print, a scoring rubric to apply them, and a model-by-model read on where each one wins. The goal is to route each task to the model that fits it, which is why a model-agnostic (“bring your own model”) integration matters more than any one provider’s marketing.

How to read this guide. The criteria and rubric are the durable part. The model roster moves monthly: treat the specific model notes as a snapshot, and re-run the rubric against current versions before you commit. The per-model benchmark scores come from IMG.LY’s print benchmark suite, which we’re opening to early-access subscribers soon (sign-up at the end of this guide).

Why print needs its own criteria

A web-to-print product sells a physical object. That changes what “good” means:

The output is measured at 300 DPI on a substrate, not at 72 PPI on a retina screen.
Color is CMYK and spot, not sRGB.
Logos and type must scale and stay crisp: vector, not pixels.
The customer is a non-designer, so the model has to be controllable enough to stay inside a template.
And because it’s a commercial product sold to a customer, the licensing of the output carries real legal exposure.

General benchmarks (LMArena-style human preference, aesthetic scores) miss most of this. The eleven criteria below are built around it.

The eleven evaluation criteria

1. Output type and format: raster vs. vector

Why it matters for print: Logos, icons, line art, and type need to scale to any size and print crisply. Raster can’t; vector can. A model that outputs (or can be cleanly traced to) native SVG / vector is uniquely valuable for the print-specific elements that screen apps don’t care about.

What to test: Can it produce vector natively? If not, how cleanly does its output vectorize? Does the vector survive into PDF/X as real paths?

2. Resolution and maximum dimensions

Why it matters: A ~1024px generation is ~3.4” at 300 DPI. Large-format and even A4 need far more. Native max resolution, and how well the model holds detail when upscaled, determines whether you can print the output at size without a quality penalty.

What to test: Native max output dimensions; detail retention at 4×/8× upscale; effective printable size at 300 DPI.

3. Visual quality and fidelity

Why it matters: The baseline. Realism, coherence, absence of artifacts, anatomical and structural correctness. Crucially, how it holds up under print’s unforgiving close inspection: banding, mushy detail, and plasticky textures show more on paper than on screen.

What to test: Side-by-side preference on print-representative prompts; artifact rate; detail at print scale.

4. Text and typography rendering

Why it matters: Print is full of words, and most models garble text inside images. For anything where text-in-image is unavoidable (a generated poster, a label motif), legibility and kerning are make-or-break. Best practice is still to set real type as a separate layer, but some jobs need it baked in.

What to test: Legibility of short and long strings; correct spelling; kerning; multi-line; non-Latin scripts.

5. Prompt adherence and controllability

Why it matters: Non-designers need predictable results, and templates need the output to land where it’s told. Controllability spans prompt adherence, image-to-image / inpainting / outpainting, style and reference-image conditioning, and seed stability for repeatable results.

What to test: Does it honor constraints? Quality of edits (generative fill, expand, object removal)? Reference-image fidelity? Same-seed reproducibility?

6. Color accuracy and CMYK-readiness

Why it matters: Vivid RGB outputs clip hard in CMYK and shift on press. Models that stay closer to printable gamut, and outputs that convert predictably, mean fewer surprises and less soft-proofing friction.

What to test: Gamut coverage vs. CMYK; shift magnitude after ICC conversion; behavior on brand-critical colors and near-whites/blacks.

7. Transparency and background handling

Why it matters: Merch, stickers, die-cuts, and product compositing need clean subjects on transparent backgrounds and accurate edges (hair, glass, fine detail). Native transparent output and clean cutout edges save a manual masking step.

What to test: Native alpha output; edge quality on hard cases; cutout-path readiness.

8. Responsiveness / latency

Why it matters: Two very different bars. In an interactive editor, anything over a few seconds breaks flow. In a batch/VDP run, throughput and concurrency matter more than per-image speed. The right model differs by context.

What to test: P50/P95 latency at your resolution; throughput under concurrency; cold-start behavior.

9. Cost per generation

Why it matters: Unit economics. A few cents per image is invisible for interactive one-offs and brutal across a 100k-recipient VDP run. Price has to be weighed against quality for the specific job. You don’t pay flagship prices for a draft thumbnail.

What to test: Cost per image at your resolution/step settings; cost of edit vs. generate; volume pricing.

10. Consistency and repeatability

Why it matters: Brand work needs the same input to yield the same (or controllably similar) output, and product likenesses must not drift. Seed control, character and style consistency, and low variance separate “brand-safe” models from “slot-machine” ones.

What to test: Variance across runs at fixed seed; character/style consistency across a set; drift on iterative edits.

11. Commercial licensing and IP safety

Why it matters: You’re selling the printed output. Commercial-use rights, training-data provenance, indemnification, and content/safety filtering are legal exposure, not fine print. A model that’s brilliant but legally murky is a non-starter for a product customers resell.

What to test: Commercial-use terms; indemnity; provenance/transparency; enterprise and data-handling terms; content-filter behavior.

The scoring rubric

Score each model 1–5 on each criterion, then weight by your use case. Suggested weights for the three most common web-to-print contexts:

Criterion	Interactive design tool	High-volume VDP / automation	Merch / POD
1. Vector / SVG output	High	Medium	Medium
2. Resolution / max size	High	High	High
3. Visual quality	High	Medium	High
4. Text rendering	Medium	High	Medium
5. Controllability / editing	High	High	High
6. CMYK-readiness	High	High	High
7. Transparency / cutout	Medium	Low	High
8. Responsiveness	High	Medium (throughput)	High
9. Cost per generation	Medium	High	Medium
10. Consistency	Medium	High	High
11. Licensing / IP	High	High	High

Scoring scale: 1 = unusable for print · 2 = weak · 3 = workable with mitigation · 4 = strong · 5 = best-in-class.

Drop your internal benchmark numbers into the matrix below. The qualitative notes give you a starting hypothesis to test, not a substitute for your own runs.

Models by job

New models ship faster than any ranking can keep up with, so this section is organized by job, the way you actually route requests. Models are drawn from the roster currently wired into CE.SDK’s AI plugins.

Job A: Text-to-image (generate a new asset)

Candidates: Recraft V3, Recraft 20B, Seedream V4, Nano Banana, Nano Banana Pro, GPT Image 1, Ideogram V3.

Model	Stand-out for print	Watch-outs	Benchmark
Recraft V3	The print specialist: native vector/SVG generation, strong text rendering, brand-style controls. Often the single most print-relevant text-to-image model.	Verify max raster resolution for large-format jobs.	… coming soon
Recraft 20B	Faster, cheaper Recraft tier. Good for interactive iteration before a final Recraft V3 render.	Quality step-down vs. V3.	… coming soon
Seedream V4	High visual fidelity and resolution; strong general-purpose hero imagery.	Text rendering and vector are not its strength.	… coming soon
Nano Banana / Pro	Fast, controllable, strong prompt adherence; Pro for higher quality. Good interactive default.	Confirm commercial-licensing terms for resale.	… coming soon
GPT Image 1	Strong instruction-following and comparatively reliable in-image text; good for layout-aware generation.	Latency and cost on the higher side for interactive use.	… coming soon
Ideogram V3	Best-in-class text rendering: the pick when legible words in the image are non-negotiable (posters, typographic art).	Less suited to photoreal product scenes.	… coming soon

Routing heuristic: logos, icons, and typographic art go to Recraft V3 (vector). Words-in-image goes to Ideogram V3 or GPT Image 1. Photoreal hero imagery goes to Seedream V4 or Nano Banana Pro. Fast interactive drafts go to Recraft 20B / Nano Banana.

Job B: Image editing (adapt a customer’s asset)

Candidates: Flux Pro Kontext, Flux Pro Kontext Max, Nano Banana Edit, Nano Banana Pro Edit, Qwen Image Edit, Gemini Flash Edit, Seedream V4 Edit, GPT Image 1, Ideogram V3 Remix.

Model	Stand-out for print	Watch-outs	Benchmark
Flux Pro Kontext / Max	Strong instruction-based editing with high subject preservation: change one thing without wrecking the rest. Good for generative fill/expand and targeted edits.	Max tier costs more; budget per edit.	… coming soon
Nano Banana Edit / Pro Edit	Fast, controllable edits; good interactive default for object removal and swaps.	Verify edge quality on fine detail.	… coming soon
Qwen Image Edit	Strong editing with good text handling during edits.	Validate commercial terms.	… coming soon
Gemini Flash Edit	Low latency: the responsiveness pick for interactive editing.	Quality trade-off vs. heavier models.	… coming soon
Seedream V4 Edit	High-fidelity edits matching its generation quality.	Heavier; weigh latency.	… coming soon

Routing heuristic: precise “change X, keep everything else” goes to Flux Kontext. Fast interactive edits go to Gemini Flash Edit / Nano Banana Edit. Edits that must preserve in-image text go to Qwen Image Edit.

Job C: Specialized print operations

These aren’t single “models” so much as task pipelines, but they belong in the routing table:

Task	Approach / model	Note
Vectorize (raster → SVG)	Vectorize plugin / Recraft vector	The print-critical one: protects logos and PDF/X vector output.
Background removal	`@imgly/background-removal` (in-browser)	On-device, instant, privacy-preserving. Feeds cutout paths.
Image correction & DPI	Perfectly Clear plugin + DPI validation	Auto-corrects exposure, color, sharpness, and noise; validation flags undersized images. Prefer high-res native generation over upscaling.
Text generation / copy	Claude Sonnet 4.6, GPT-4.1 Nano	Headlines, rewrites, per-recipient VDP copy.
Text-to-speech / sound	ElevenLabs (where relevant)	Less common in print; relevant for multi-channel campaigns.

The quick-reference picks

If you skip the rubric and just want today’s defaults, this is the snapshot we’d start from. Treat it as the hypothesis your own benchmarks confirm or overturn, not a verdict.

Print job	Pick	Why
Logos, icons, line art, anything that must scale	Recraft V3	The only major model with native SVG/vector output. Everything else hands you pixels to trace. Vector survives into PDF/X as real paths and prints sharp at any size.
Legible text inside the image (posters, labels, packaging motifs)	Ideogram V3, with GPT Image 1 / Nano Banana Pro close behind	Ideogram was built around typography; kerning and spelling hold where most models produce letter-shaped mush. Still, bake text in only when you must: real type as a separate editor layer beats all of them.
Photoreal hero imagery at print size	Seedream V4 or Nano Banana Pro	Resolution is the print bottleneck. Seedream V4 generates up to 4K natively (about 13.6” at 300 DPI before any upscaling); Nano Banana Pro outputs 2K/4K. A 1024px generation from anything else is a 3.4” image betting on the upscaler.
”Change X, keep everything else” edits	Flux Kontext Pro / Max	Best-in-class instruction-following edits with subject preservation, which is critical when the asset is the customer’s product photo and “the AI improved it” means a reprint. The Nano Banana family is the consistency pick for variants of one subject.
Interactive drafts (speed and cost)	Recraft 20B, Gemini Flash Edit, base Nano Banana	In an editor, a 20-second generation is a bounce. Draft cheap and fast, then re-render the final with the heavyweight. The customer never needs to know two models were involved.
Data sovereignty / self-hosting	Qwen-Image / Qwen Image Edit	Apache 2.0 open weights. For European operators and government buyers who won’t send customer uploads to a US API, “we can run it ourselves” beats a quality delta.
VDP copy and headlines	Claude Sonnet 4.6	Cheap enough per recipient at 100k-mailer volume, and strong at length-constrained rewriting: the “fit this text frame” problem.

Two of those rationales carry more weight than the rest.

Vector is the criterion that decides printability. Screen products never need vector, so general models never optimized for it, and Recraft sits almost alone on the one measure that determines whether a logo prints cleanly at size. If you adopt a single routing rule from this guide, make it this one.

Resolution and color are pipeline problems the model can only start. No model outputs CMYK; every one generates sRGB. “CMYK-readiness” is really about how hard a model’s palette clips on conversion, and your ICC and soft-proofing pipeline owns the rest. Same with DPI: pair every generation path with validation and a dedicated upscaler rather than trusting native output. You can swap the model whenever you want; the print-correctness layer around it has to stay put.

One roster note: Adobe Firefly isn’t wired into CE.SDK’s plugin roster today, but for licensing-sensitive enterprises its trained-on-licensed-content and indemnification story is the strongest answer to criterion 11. Include it in your own evaluation if criterion 11 dominates your weighting.

A worked decision: which model wins for your product?

The rubric resolves to a different answer per context. Three quick reads:

Interactive design tool (non-designers personalizing templates). Weight responsiveness, controllability, and vector. Likely stack: Recraft 20B / Nano Banana for fast generation, Recraft V3 for final vector, Gemini Flash Edit for interactive edits. The customer iterates fast and the final asset is print-clean.
High-volume VDP / automation (100k personalized mailers). Weight cost, throughput, consistency, and licensing. Likely stack: a cost-efficient generation model at high concurrency, Claude Sonnet 4.6 for per-recipient copy, seed-locked for repeatability, all run headless. Per-unit cost dominates the decision.
Merch / POD (user art on physical products). Weight transparency/cutout, resolution, and quality. Likely stack: background removal plus cutout for subjects, upscaling for resolution, Seedream V4 / Nano Banana Pro for generated designs, with hard licensing checks because the output is resold.

In every case, the conclusion is the same: no one model wins all three. The advantage is in being able to route each task to the model that wins it, and to swap models as better ones appear, without re-architecting your editor.

What makes per-job routing practical: native plugins + the AI Gateway

A criteria-driven, route-per-job strategy only works if switching models is cheap. If wiring in a new model means a new API integration, new auth, new key management, new error handling, and new billing plumbing every time, you’ll quietly standardize on whatever you integrated first, and inherit its weaknesses on every job it loses.

CE.SDK is built to avoid that:

Every image model in this guide is natively supported as an AI plugin. Text-to-image and image editing run as drop-in providers inside the editor, not bespoke integrations you build and maintain. Background removal, vectorization, and image correction (Perfectly Clear) ship as their own plugins, and text generation routes through built-in Anthropic and OpenAI providers. Adopting Recraft for vector, Ideogram for text, and Flux Kontext for edits is configuration, not three separate engineering projects.
The AI Gateway gives you one unified surface to every model. Instead of stitching together a dozen provider APIs, key schemes, and rate-limit behaviors, you call models through a single managed layer. That’s what turns “route each task to the best model” from an architecture diagram into a one-line config change, and what lets you swap a model the day a better one ships, without touching your editor or your print pipeline.
Outputs land inside the print pipeline, not beside it. Whatever model produces the asset, it flows into locked templates with bleed, safe-area, and DPI constraints, then through CMYK / spot-color / PDF/X-3 export. The model is interchangeable; print correctness is not. Print-on-demand company The Print Bar and direct-mail platform PostBuddy both built on this pipeline, embedding CE.SDK rather than maintaining their own print editor.

So the “best model” question is no longer a one-time, high-stakes bet on a single provider; it’s an ongoing optimization. The benchmark scores below tell you which model to route each job to today, and the native-plugin and Gateway architecture is what lets you act on that answer and revisit it when the scores change next quarter.

The IMG.LY print benchmark matrix

IMG.LY is building a print benchmark suite that scores every model in this guide against all eleven criteria, on print-representative prompts, with the weighted totals per use case already worked out. It is rolling out to early-access subscribers first. Subscribe to our newsletter to get the full scored matrix, and the test set behind it, before it is public.

Model	1 Vector	2 Res	3 Quality	4 Text	5 Control	6 CMYK	7 Transp.	8 Speed	9 Cost	10 Consist.	11 License	Weighted (Interactive)	Weighted (VDP)	Weighted (Merch)
Recraft V3
Recraft 20B
Seedream V4
Nano Banana Pro
GPT Image 1
Ideogram V3
Flux Pro Kontext
Gemini Flash Edit
Qwen Image Edit

The IMG.LY print benchmark suite is coming soon

Every model scored 1–5 across all eleven print criteria, with weighted totals per use case. Early-access subscribers get it first.

The criteria and the routing logic above stand on their own. The scored numbers are what the suite adds: a measured, repeatable answer for each cell, refreshed as models change.

Bottom line

Pick criteria before you pick models. For web-to-print, the criteria that screen benchmarks ignore (vector output, print resolution, CMYK behavior, text legibility, licensing) are exactly the ones that decide whether a beautiful generation is a sellable print. Score the current models against those criteria for your context, route each job to the model that wins it, and run it all through CE.SDK’s native AI plugins and AI Gateway so re-routing tomorrow, after the next leaderboard reshuffle, is a config change rather than a rebuild.

Companion piece: How to Leverage Generative AI in Web-to-Print covers the use cases, integration patterns, and print-specific pitfalls behind these model choices.

How to Leverage Generative AI in Web-to-Print

Jan — Fri, 26 Jun 2026 00:00:00 GMT

Web-to-print sells self-service: your customer designs a postcard, a flyer, a t-shirt, a packaging label in the browser and orders it without a designer in the loop. For years, though, the self-service stopped at the hard part. Someone still had to supply a usable image. Someone still had to know what 300 DPI meant. When they didn’t, the file landed on a prepress desk to be fixed by hand.

One operator we spoke to put it bluntly: his designers spend roughly 40% of their time fixing customer artwork rather than creating templates. Tom Rowe of The Print Bar described what that looks like at the design step: “Our brand didn’t match our experience. You could see it in our bounce rates.”

Generative AI changes the economics of that hard part. It can turn a prompt into a usable asset, lift a 72-DPI logo to something printable, and strip a background in the browser before a human ever sees the file, removing the specific friction that kept self-service from being self-service in the first place.

It can also go wrong: aimed carelessly, the same models produce beautiful screen images that fall apart on press. This post is about the difference between the two: the use cases worth building, and the print-specific realities you have to design around.

The shift: from “upload a print-ready file” to “describe what you want”

The old web-to-print contract asked the customer to arrive with a finished, technically correct asset. That filter excluded most of the market: the CRM manager, the franchise owner, the small-business buyer who “knows Canva because they make their wedding invitations on it” but has never opened InDesign and never will.

Generative AI moves the burden of production off the customer. Instead of “upload a 300 DPI CMYK image with 3mm bleed,” the ask becomes “type what you want on the card.” The editor, not the customer and not your prepress team, becomes responsible for turning intent into a production-safe file.

That principle runs through everything below: AI is most valuable in web-to-print where it removes a step the customer was never qualified to do. The closer a use case sits to it, the more it returns.

The use cases worth building

1. Generate on-brand imagery from a prompt (text-to-image)

This is the most obvious win. A customer needs a hero image, a background, a seasonal motif, or a product scene, and doesn’t have one. Text-to-image generation lets them describe it and get options in seconds, without a stock-photo license hunt or a design request ticket.

In a print context the point is unblocking the order, not novelty for its own sake. The customer who would have abandoned at “I don’t have a good image” now keeps going. Models like Recraft V3, Seedream V4, Ideogram V3, and the Nano Banana family each have different strengths here (covered in depth in the companion guide, The Best GenAI Models for Web-to-Print), but the integration pattern is the same: generation feeds a placeholder inside a locked template, so the output lands inside your bleed, safe-area, and brand constraints automatically.

Watch out: generated images are usually delivered at screen resolution, often around 1024px. That’s fine for a business card photo, marginal for an A4 flyer, and unusable for large-format. Pair generation with upscaling (below) and size validation before you let it reach export.

2. Adapt and extend customer-supplied images (image-to-image, generative fill/expand)

Customers rarely arrive with an asset that fits your canvas. It’s the wrong aspect ratio, it has the wrong background, or it’s a portrait crop where you need a landscape banner. Image-to-image editing and generative expand (outpainting) solve the most common case: extending an image to fill bleed or a different SKU’s dimensions instead of stretching or letterboxing it.

This is quietly one of the highest-value print use cases, because aspect-ratio and bleed mismatches are a top source of prepress rework. Generative fill also handles object removal (“take the coffee cup off the desk”), background swaps, and clean-up: the edits a non-designer can’t do in any tool they own.

Watch out: outpainting invents pixels. On a brand asset or a product photo, “invented” can mean “wrong.” Keep generative expand to backgrounds and ambient areas. Never let it reconstruct a logo, a face, or a product the customer is actually selling.

3. Background removal and cutouts for mockups and merch

Background removal is the workhorse. For merch and print-on-demand it’s the difference between a customer’s snapshot and a clean subject that drops onto a t-shirt, mug, or sticker. IMG.LY runs this in the browser (via the open-source @imgly/background-removal package), which matters for two reasons: it’s instant enough for an interactive editor, and the customer’s image never has to leave the device.

Paired with the cutout plugin, background removal also feeds the literal cut lines for die-cut stickers, labels, and packaging, turning a removed background into a production path.

Watch out: browser-based removal is excellent on clear subjects and struggles on hair, glass, and fine fringes. For a print product that will be inspected up close, expose a manual refine step rather than trusting the mask blindly.

4. Vectorize raster art into print-scalable graphics

This is the use case print people care about most and screen-first builders forget. A customer uploads a logo as a small, jagged PNG. Printed at size, it’s mush. Vectorization (AI raster-to-SVG) traces it into clean, resolution-independent paths that scale to any output size and reproduce crisply on press.

Vectorize is also how you get logos and simple graphics into a state your PDF/X pipeline can preserve as vector, instead of rasterizing everything and throwing away the scalability you vectorized for. Recraft V3 is notable here because it can generate natively vector output rather than only tracing after the fact.

Watch out: vectorization is great for logos, icons, and flat art. It’s the wrong tool for a photograph. Detect the asset type and route photos to upscaling, not tracing.

5. Resolution and image quality: upscaling, correction, and DPI repair

The single most common web-to-print failure is a low-resolution image: the 72-DPI photo that looks fine on screen and prints as a blurry mess. Two different AI operations fix it, and it pays to keep them straight, because they solve different problems.

Upscaling (super-resolution) raises the actual pixel count, reconstructing detail to lift a small image toward a printable size. It’s a generative step you route to a dedicated model, the same way you route a text-to-image prompt; the strong upscalers can take a 1024px generation to 4K. Reach for it when the source is simply too small for its placed size.

Image correction is the other half, and it ships in CE.SDK today as the Perfectly Clear plugin. It auto-corrects exposure, contrast, color, tint, sharpness, and noise in a single pass. It won’t add pixels, but it gets the most printable result out of the pixels you have, which is what a dim, soft phone photo usually needs more than raw resolution.

Tie both to your DPI validation. When the editor detects an image below your minimum threshold for its placed size, offer to correct or upscale it instead of just blocking export. You convert a dead end into a one-click fix, the kind of “they don’t need to know what DPI is” experience operators are chasing.

Watch out: upscaling fabricates detail. It rescues marginal images; it can’t conjure a sharp 4-megapixel product shot from a thumbnail, and correction can’t add resolution at all. Set honest thresholds, and still warn when the source is hopeless.

6. Copy and variable text generation (text + VDP at scale)

Generative text earns its place in two spots. First, as a writing aid inside the editor: headline options, a tagline, a “make it shorter / more formal / fit this space” rewrite for the non-writer staring at an empty text box. Second, and more powerfully for print, in Variable Data Printing: generating or localizing per-recipient copy across thousands of personalized postcards, mailers, or labels from a single template.

VDP is the highest-leverage place to use generative text: generate the variants, merge them into print-ready files in headless mode, and run the batch.

Watch out: generated copy needs guardrails. Length limits so it doesn’t overflow the text frame, tone and brand constraints, and a human-review gate for anything legally sensitive: pricing, claims, regulated industries.

7. Template adaptation and auto-resize across SKUs

A print catalog is the same design across many sizes and substrates: the same campaign as a postcard, a flyer, a poster, a social tile. AI-assisted resize and re-layout adapt one master design to every SKU’s dimensions, reflowing content intelligently instead of scaling it blindly. Combined with locked templates, you expand SKUs without re-authoring each one.

Watch out: reflow decisions still need brand rules. Lock what must stay fixed (logo size, safe area, mandatory legal text) so the AI rearranges within your constraints, not over them.

8. Guided prepress correction

Instead of rejecting a bad file after the fact, use AI to catch and fix problems inside the editor: flag the low-res image and offer to upscale it, detect text outside the safe area and nudge it in, notice a near-white “white” that won’t print and correct it. The same problems your prepress team used to fix by hand get caught here, before the order is placed.

Watch out: auto-correction must be transparent and reversible. Show the customer what changed and let them undo it. Silent “helpful” edits to someone’s artwork erode trust fast.

9. Localization and market variants

For franchise networks and multi-market brands, AI translation plus regeneration of localized imagery and copy turns one approved master into 12 market versions, each print-ready and on-brand, without a translation agency or 12 design tickets. A 200-location franchise can ship 200 localized flyers with the same brand guideline enforced by the editor on every one.

Watch out: machine translation in regulated or legal copy needs human sign-off, and text expansion (German runs roughly 30% longer than English) will break tight layouts unless your template frames can flex.

10. Realistic product previews

Generative and 3D-assisted mockups show the design on the actual product: the shirt, the mug, the folded brochure, the box, not an abstract artboard. Operators consistently tie this to higher conversion and fewer “will this look right?” support tickets, because the preview matches what arrives on the doorstep.

Watch out: a preview that’s prettier than the print sets up a disappointed customer and a reprint. Calibrate mockups to real output, including substrate color and finish.

The print-specific realities

Most generative models are built for screens. Print adds requirements the web doesn’t have, and the ones below are where projects most often break.

Resolution and DPI

Generated images typically arrive at around 1024px. At 300 DPI that’s about a 3.4-inch image: fine for a business card, not for a poster. Always validate output resolution against placed size, and route undersized assets through upscaling before export. Treat raw generation resolution as a starting point, not a deliverable.

Color: sRGB in, CMYK out

Models generate in RGB. Print is CMYK, plus spot colors. The vivid blues, greens, and oranges that look great on screen sit outside the CMYK gamut and will shift on press. Your pipeline, not the model, owns this: convert with the right ICC profile, validate against the print provider’s color requirements, and preserve named spot colors through to the PDF/X. Show the customer a soft-proof so the shift isn’t a surprise on delivery.

Vector vs. raster (and the “everything got rastered” trap)

Most models output raster. For logos, type, and line art that need to scale and print crisply, raster is the wrong format, and a PDF that rasterizes all text and vectors is, in one operator’s words, “death for the printer.” Use vector-native generation (e.g. Recraft) and vectorization for the elements that need it, and make sure your export keeps vector and text as vector with CMYK values preserved (PDF/X-3), not flattened to pixels.

Text rendering inside images

Generative models are notoriously unreliable at rendering legible text inside an image: garbled words, invented letters, wrong kerning. For anything that must be readable in print, don’t bake text into a generated image. Generate the imagery, then set real, editable, vectorizable type as a separate layer in the editor. If you must generate text-in-image, Ideogram and Recraft are the stronger choices; see the companion guide.

Brand safety and guardrails

Let customers generate anything and you lose brand control. Box generation inside locked templates instead: it fills a defined placeholder, within fixed margins, alongside a logo and palette the customer can’t move. A franchisee can change the headline and the photo; the logo size, position, and safe area stay locked. AI expands what the customer can create without expanding what they can break.

Commercial and licensing rights

A web-to-print product is sold. That makes the IP status of generated assets a question you have to answer before you ship. Does your model provider grant commercial-use rights to outputs? Are there indemnities? Does training-data provenance create exposure for a customer reselling the printed product? Pick models and providers whose commercial terms you’ve actually read, and surface usage terms where they matter.

Cost and latency (the unit economics)

Every generation costs money and time. In an interactive editor, a 30-second generation is a broken experience. In a high-volume VDP run, a few cents per asset multiplied by 100,000 recipients is a real line item. Match the model to the job: a fast, cheap model for interactive iteration, a higher-quality (slower, pricier) model for the final render. Cache aggressively. The companion guide scores models on that trade-off.

Data privacy and sovereignty

Customer-uploaded images can be sensitive: faces, IDs, confidential product designs. Browser-based processing (background removal, some editing) keeps data on-device. API-based generation sends it to a third party, which has GDPR and data-residency implications, especially for European customers and government buyers who “prioritize a European vendor for data sovereignty.” Be explicit about what runs locally vs. in the cloud, and choose providers accordingly.

Hallucination and consistency

Generative output is non-deterministic. The same prompt yields different results, and details drift. For brand assets, product likenesses, and anything a customer will compare against reality, constrain hard (reference images, seeds, image-to-image rather than free generation) and keep a human gate on the outputs that matter.

How IMG.LY approaches it

All of these constraints point the same way: AI is a step inside a print pipeline, not a feature bolted onto an editor. A few principles shape how CE.SDK handles it:

Model-agnostic by design. The AI plugins connect to any third-party model or API: bring your own model. You’re not locked to one provider’s quality, price, or licensing terms. You route each task to the model that wins it, and swap models as better ones ship every few weeks.
The AI Gateway provides managed access to models for editors, so you’re not stitching together a dozen API integrations and key-management schemes yourself.
Generation lands inside the print pipeline. Outputs flow into locked templates with bleed, safe areas, DPI thresholds, and brand constraints already enforced, then through a CMYK / spot-color / PDF/X-3 export that keeps vectors and text as vectors. The model never gets to bypass print correctness.
Drop-in generative features. Background removal, generative fill, image-to-image, vectorize, and text-to-image are available as plugins, so you adopt the use cases above incrementally rather than rebuilding your editor.
Headless mode runs the same generation and export server-side for batch and variable-data runs.

The result is the experience operators actually want to sell: the customer describes what they want, the AI does the part they were never qualified to do, and the file that reaches the press is print-correct because the pipeline enforced it, not because the customer got lucky. For the product-level view of this stack, see AI for Print on Demand.

What customers are doing with it

High-volume print and direct-mail platforms are already building on this foundation. IMG.LY powers print and personalization workflows for operators including Postbuddy (personalized direct mail), Swiss Post, Digitas, and HP, alongside hundreds of smaller print, merch, and franchise platforms.

The pattern that recurs in those conversations is narrow and specific: AI removed a bottleneck. The prepress team that fixed 40% of incoming files now lets the editor catch problems upstream. The customers who bounced at “I don’t have a good image” finish the order. The franchise network that needed a designer for every local variant generates them inside guardrails. It comes back to the point from the top: AI pays off where it deletes a step the customer couldn’t do and the operator didn’t want to.

Where to start

You don’t need all ten use cases on day one. The highest-ROI starting points, in order:

Background removal: instant, in-browser, immediately useful for any merch or photo product.
Image correction and DPI validation: catches and cleans up weak uploads before they ever reach the printer.
Generative expand / fill: kills aspect-ratio and bleed rework.
Text-to-image into locked placeholders: unblocks the “I don’t have an image” abandoner.
Vectorize: rescues logos and protects your PDF/X output.

Each one removes a documented source of friction or rework. Add them inside locked templates and a real CMYK/PDF/X pipeline, and self-service web-to-print finally works the way it was always sold: the customer really can do it themselves.

Next: which models to actually use. See the companion guide, The Best GenAI Models for Web-to-Print: A Buyer’s Guide, for a criteria-based comparison across output quality, vector/SVG support, text rendering, color, responsiveness, and cost.

13 Questions Teams Ask Themselves Before Choosing IMG.LY

Marc — Fri, 19 Jun 2026 09:00:00 GMT

Most teams evaluating an in-app editor arrive with the same shortlist of questions. These are the 13 that come up most across 600+ customers and 28 structured interviews, each answered straight, with the numbers behind it.

Why integrate an editor instead of building our own?

A production-ready SDK turns months of editor engineering into a couple of weeks of integration. Building an equivalent editor in-house runs 6 to 12 months and ties up two or three senior developers. The median IMG.LY customer reaches production within just 14 days, roughly 13× faster than the in-house route. For fast-moving companies especially, staying on your core is what pays off. Time spent on the editor is time not spent on what actually sets your product apart.

Can’t we just use an open-source library like Fabric.js, Konva, or Polotno?

You can, and some companies do. The problems start once you need more than a drawing surface. Open-source canvas libraries give you that surface and little else, no text on a path, no video timeline, no background removal, no cross-platform parity, and no ready-made UI. You build all of that yourself, and then you own the maintenance forever. The library is free, the year of senior engineering it takes to reach production quality is not.

It was very buggy, lack of features, not looking good, and we decided to not go deeper.

Engineering lead at a company that evaluated open source before CE.SDK

CE.SDK gives you the engine and the UI in one SDK, with the same rendering across web, iOS, and Android. If you want the full breakdown, we put open source next to building and buying in our Fabric.js comparison.

How fast can we realistically be in production?

A working prototype usually takes about two days, and a production-ready integration around two weeks. That time goes into wiring the existing SDK and API into your product and styling it to fit. Our AI developer tooling accelerates the process even more, giving your AI coding assistant full CE.SDK context for the integration. For fast-moving companies, this can be a real booster. Plai went from deal to live in about a month, then quickly scaled to thousands of ad campaigns with the new editor in place.

Every design edit request lands on my team. How do we scale that?

You stop being the bottleneck. Instead of your team producing every asset, users edit themselves inside your product, so output scales with your user base, not your headcount.

When you're dealing with a graphic designer who has a queue of work, you usually need to wait.

Product lead at an IMG.LY customer

The digital agency Digitas built its dealer portal on CE.SDK, and removing that bottleneck led to 85% of videos being created fully in-app, with active users making 3× more than before. None of that work routes through a design team.

The same engine also scales without anyone editing at all. Run it headless and it generates assets automatically. One template plus your data renders thousands of on-brand variants through the API. PostBuddy, for example, does exactly this. Its users choose a template, upload a CSV, and the engine auto-generates thousands of personalized, print-ready postcards, with no one editing a single one. Self-serve covers the one-offs, automation covers the scale.

Our users aren’t designers. How do we keep results on-brand without manual review?

With guardrails you set. Templates, locked brand elements, and constraints let a non-designer produce polished, on-brand work by default, because the editor only exposes what you allow. The output can even beat the professionals.

I built a better-looking asset in the portal than the agency ever did.

Martin Röhr — Senior Project Manager, Digitas

Nobody has to check the output later, because the guardrails already did.

We already have an editor. Is replacing it worth the costs?

The editing experience is part of the sale. When the flow is smooth, more users finish what they start, and completion is conversion. A clunky editor quietly costs you sales.

"Our brand didn't match our experience. You could see it in our bounce rates," says Tom Rowe, and the difference is easy to spot: "you can tell when competitors are using the old platform just by looking at it."

Tom Rowe — Product & Engineering, The Print Bar

When the status quo quietly costs deals, the editor should not be treated as a nice-to-have, but as an essential.

Will it match our product’s look and feel?

Yes, and that fit is exactly what an SDK gives you. The UI is fully customizable. You can theme it, restyle it, or drive the engine from your own interface in a headless setup. It acts as a native part of your product instead of a third-party tool bolted on. Swiss Post, which runs over a million personalized postcards a year on it, confirms this, calling CE.SDK “the only solution allowing a specialized, on-brand UI.”

We ship on web, iOS, and Android. Do we need three different tools?

No. One creative engine renders identically across web, iOS, and Android, so a template built on one platform looks the same on every other and your team keeps one mental model instead of maintaining three separate integrations. You build once instead of rebuilding the editor per OS.

Our users want AI features. Do we have to build those too?

AI editing ships inside the editor, not as a separate project. Background removal and generative tools like text-to-image and image-to-video are ready to use, and CE.SDK is bring-your-own-model, so you plug in the providers you want instead of running inference yourself. That can move the top line on its own.

We are seeing a 10x increase in new signups month over month in May — that was due to the fact that you can now auto-generate really beautiful-looking ads from scratch.

Hikari Senju — Founder & CEO, Omneky

Where does our users’ data actually go?

By default, processing happens client-side, in the browser or on the device, so images and video never touch our servers. For customers with strict data-security requirements that is often a deciding factor, and it is increasingly named as a must-have in AI-driven research. Nothing leaves the user’s machine unless you deliberately choose a server-side workflow. And since IMG.LY is based in Germany, GDPR compliance and EU data residency come built in.

If we build on this, are we locked in?

It is a fair concern, and a different one from whether the vendor sticks around. Your designs and templates stay yours. You can export both your scenes and the rendered output, as PNG, JPEG, PDF, and the scene file itself, and you can run the engine on your own infrastructure, fully headless if you want. You are integrating a component, not handing your data model to someone else, and switching the component out later is possible.

Can we depend on this provider when it matters?

IMG.LY is an established company based in Germany, with a real team of people behind the product rather than a side project that could disappear next quarter. 600+ organizations, from startups to large global enterprises and government agencies, run the SDK in production, together generating around 500 million creations a month. Names on that list include Mercedes-Benz, Lufthansa, SAP, Polaroid, and Ticketmaster. You also get a dedicated contact who stays reachable when you need help, not an anonymous ticket queue, and the SDK keeps shipping new capabilities release after release, so the foundation you build on only gets stronger.

How do we know it’ll work before we’re all in?

You don’t have to trust the pitch, you can prove it yourself. The trial is self-serve. A developer can spin up an account and start building with the real SDK without going through sales, then judge the integration and the docs firsthand. It doesn’t need to take long either, thanks to the AI developer tooling that helps your assistant generate accurate integration code. That’s how most teams who picked IMG.LY decided, because seeing it run in your own stack removes the guesswork before you commit.

Recognize a few of these?

These are exactly the questions a careful team should ask before building on someone else’s technology. If you’re working through them, we’re glad to help: try the SDK yourself or contact our team. Reaching out is no commitment, and we’re happy to dig into your specific case. And to see how it played out for other companies, our case studies offer interesting insights.

CE.SDK v1.76 Release Notes

Neslihan — Fri, 05 Jun 2026 15:17:25 GMT

With this release, the mobile video timeline gets a meaningful upgrade, background removal comes to Android, and a set of engine improvements tighten text, shape, and font-size handling across platforms.

Let’s jump in!

Edit Multi-Clip Timelines on iOS and Android

The mobile video timeline now supports multiple clips per foreground track. Long-press any clip to drag it within a track, across tracks, or into a gap to create a new track. Split, trim, and move are all gap-aware and respect locked clips.

For your product, this means: users can manage their video edit the way they’d expect, organizing clips in a single track instead of working around single-clip limitations.

→ Video Editor Starter Kit – iOS
→ Video Timeline Docs – iOS

→ Video Editor Starter Kit – Android
→ Video Timeline Docs – Android

Remove Backgrounds on Android

The Background Removal plugin is now available for Android. Users can remove backgrounds from images directly in the editor, without leaving the app or sending images to an external server.

For your product, this means: Android users get the same background removal capability that was already available on web, closing a gap for teams building cross-platform photo editing experiences. Users stay in your app for design tasks.

→ Android Background Removal Docs

New Plugin: Turn PDFs into Editable Designs

A new plugin and demo lets you import PDF documents directly into CE.SDK and turn them into fully editable designs.

With that, users can bring existing PDF assets into your editor without rebuilding them from scratch, opening up workflows around template reuse, document personalization, and print editing.

→ Try the Demo

Improvements

Set Font Sizes in Pixels or Points
v1.76 adds per-scene font-size unit control. Choose pixels or points for a scene, and CE.SDK font-size APIs and editor UI follow that unit across all platforms.

Set Different Line Spacing Per Paragraph
Each paragraph in a text block can now have its own line spacing, instead of every paragraph sharing the same setting.

Add Precise Strokes to Texts

Style text outlines down to the last detail! The same controls you’d expect on any shape, now on text and captions too.

Tweak stroke position (inner, outer, center), dash patterns, cap styles, and corner joins directly on text and caption blocks.
→ Text Effects Docs

Draw Better Lines
Lines are now true line shapes. You can control how the ends of lines and dashes are styled (round, flat, or square), instead of working around lines behaving like thin rectangles.

Control Where Images Sit Inside a Block
New APIs let you control how image fills align inside a block when using Contain or Cover fill modes. Useful for templates where the inserted image’s aspect ratio is unknown. Also available for cropping in the web editor.

Changelog

v1.76 includes a significant number of improvements across platforms. See the full changelog for the complete list.

Thank you for building with IMG.LY.

CE.SDK v1.75 Release Notes

Neslihan — Fri, 22 May 2026 12:18:08 GMT

v1.75 is an engine release. Four new capabilities across media support, color workflows and smarter canvas and selection behaviors.

Let’s dive in!

Import Animated PNGs

CE.SDK now supports APNG import. Animated PNG files load and behave in line with GIF import, giving you a second animated format to work with in your editor.

→ Supported File Formats Docs

Pull Dominant Colors from Images on the Canvas

The engine can now extract the most prominent colors from an image already placed on the canvas. The data is available programmatically, ready to feed into palette suggestions.

→ Colors in CE.SDK Docs

Control How Far Elements Can Move

Define how far elements can be dragged beyond a page or parent boundary. This is now fairly simple with new movement constraint APIs.

Allow partial overflow where it makes sense while keeping content inside the intended editable area everywhere else.

This means more precise control over template behavior. Useful for any use case where content boundaries need to be enforced.

→ Movement Constraints API Docs

Improvements

Reach Elements Hidden Behind Transparent Images

Clicks now pass through transparent image areas to the element underneath. Selecting stacked elements just got easier.

Instead of selecting the top image, the click passes through to the element below. Now, users can reach and select elements from overlapping images without trouble.

Changelog

v1.75 includes bug fixes across the engine, web, iOS, and Android. See the full changelog for the complete list.

CE.SDK v1.74 Release Notes

Neslihan — Fri, 08 May 2026 08:53:50 GMT

v1.74 is a web-focused release. Color and Gradient editing gets a full rebuild, closing gaps with popular editors. And PDF export takes a meaningful step forward for professional print workflows.

Edit Gradients with Full Control

The color input system in the web editor has been rebuilt. The user-facing result: gradient editing now works the way you’d expect it to.

Create and edit linear, radial, and conical gradients
Add and remove gradient colors, and switch between gradient types without losing the colors. Color picking now works consistently across all contexts: fill, stroke, shadow, and text.

Build and refine complex gradients entirely within your editor, without relying on external tools.

→ Explore Gradients Documentation

Export Print-Ready PDFs Without Extra Steps

Professional print workflows have a high bar for color fidelity. v1.74 raises CE.SDK’s output to meet it.

Spot colors are written as device CMYK in the exported file, matching what professional print pipelines expect.
Overprint on text is preserved correctly.
You can now opt out of ICC profile embedding in the print-ready PDF plugin when your workflow doesn’t need it.

Take exported PDFs directly into production with less manual intervention, making CE.SDK a stronger fit for workflows where color fidelity is a real purchasing factor.

→ Print-Ready PDF Plugin Documentation
→ Export to PDF Documentation

Improvements

Edit Vectors with Precision

Vector editing now feels more precise and easier to control, with better bend handles, live corner rounding, mirrored handles for new points on curved paths, new anchor snapping, and clearer tooltips throughout the editing flow.

Align Elements with Snapping Guides

Snapping guides have been refined to better show what is being aligned, using bounded guide segments, clearer visual distinctions, and new anchor-to-anchor feedback, making object placement and path editing more predictable and easier to understand.

Developer Experience

Web Demos Are Now Starter Kits

Every web demo is now a Starter Kit. That means 46 fully-fledged, clonable app templates. Starter Kits are production-ready configurations complete with the toolbars, behaviors, and workflows a real product needs.

Clone it, run it, build from there.

Whether you need the core Design, Photo, and Video Editors (and their powerhouse Advanced variants), specialized industry kits for Apparel, or AI-optimized workflows for generative assets, there is now a clonable app for every use case.

→ Explore Web Editor Demos
→ Starter Kit Documentation

Changelog

v1.74 includes fixes across the engine and web editor. See the full changelog for the complete list.

How 600+ Teams Shipped Creative Editing in 14 Days

Jan — Tue, 28 Apr 2026 21:15:17 GMT

The IMG.LY Impact Report

Based on a self-reported customer survey, 28 structured customer interviews, and IMG.LY’s published customer case studies. External benchmarks cited in context.

600+ companies from startups, over Fortune 500s to government organizations run creative editing on IMG.LY, collectively producing 500 million creations every month. The median customer goes from first SDK access to a working prototype in 2 days and a production-ready feature shipped inside a single 14-day sprint. Those self-reported medians run roughly 13× faster than the 6-month industry baseline for building an equivalent editor in-house, and around 6× faster than stitching together an open-source toolkit.

The time-to-market number is the entry ticket. What those 600+ customers do after shipping, how the editor changes their pricing, funnel, team velocity, and competitive position is what this report is about.

Methodology note. Time-to-prototype and time-to-MVP figures are self-reported by IMG.LY customers in a recent customer survey. All named customer outcomes are drawn from IMG.LY’s published case studies, where the customer has reviewed and approved the specific figures cited. Quantitative ranges and anonymous quotes come from 30 structured customer interviews (2024–2026); individual customers are not identified.

What Customers Unlock

1. Ship in days, not quarters

A working prototype takes an average of two days, a production feature often just a single sprint. Customer interviews put the alternative, an in-house build, at 6–12 months with 2–3 senior developers, consistent with the cost bands documented in IMG.LY’s Build vs. Buy guide and independently with the Standish Group CHAOS Report, which finds only 31% of software projects succeed on time, on budget, and with full scope… and under 10% for large projects.

Plai went live in about a month where their founder had estimated “months and months” for an in-house build. Optimizely, serving 1,000+ enterprise customers, described the integration as “one of the quickest projects we’ve worked on.”

Time to a production-ready MVP

14 days vs. 6 months: how long it takes to ship creative editing

Median time from project start to a production-ready creative editor, by integration path.

Sources. CE.SDK figure (14 days) is the self-reported median from an IMG.LY customer survey; individual results vary with scope and team. In-house (180 days) and open-source (90 days) figures are midpoints of the ranges documented in IMG.LY's Build vs. Buy guide, cross-referenced with customer interviews (N=28).

2. Open new pricing and market tiers

Embedding an editor changes the customer’s own unit economics. It unlocks a self-serve tier where users previously needed a designer in the loop, lowers the price floor, and opens markets where manual production was the binding constraint.

Plai doubled annual revenue and now generates 30,000+ ad creatives monthly on the platform. Postbuddy measured a 4× A/B-test improvement after moving direct-mail creation in-app, a lift that funded expansion into Sweden and Norway. In an anonymized interview, one customer described the change plainly: “We can lower our prices for the base product, it’s cheaper for clients who can use self-service.”

3. Lift your own conversion and engagement

In-context editing keeps users inside the product, shortens time-to-value, and removes the “export to Photoshop” detour that quietly leaks trials. The effect shows up directly in sign-up and trial-to-paid numbers.

Omneky recorded a 10× month-over-month increase in new sign-ups after embedding CE.SDK. In a separate interview, one customer described 400–500 organic trials per month with roughly $65–70K of opportunity evaporating at an 8% trial-to-paid rate tied largely to editor friction, the number that made their own build-vs-buy case close itself.

4. Free your design, marketing, and support teams

The cost saved by an editor isn’t only on the engineering line. It shows up in designer queues that disappear, support tickets that drop, and marketing teams that stop waiting on the bottleneck.

ImageBank X compressed a recurring asset-prep task from 15 minutes to 2 minutes, an 87% reduction per task. Halio.ai enables financial advisors to produce 30 days of branded content in 30 minutes. Interview customers describe the same pattern in plainer language: “happier marketing teams,” and, of the post-launch support burden, “the things the sales team had to deal with all day are just gone.”

5. Compound instead of freeze

This is where the engineering-economics story earns its keep. An in-house editor is a snapshot: the team ships what’s feasible in the window, then expends time and money just to keep it alive. Atlassian’s 2024 State of Developer Experience Report (N=2,100+) found 69% of developers lose eight or more hours per week to inefficiencies (about 20% of their time) with technical debt as the primary cause. Stack Overflow’s 2024 Developer Survey (N=65,437) independently found 62% of developers rank technical debt as their single biggest frustration.

CE.SDK customers don’t pay that tax. New capabilities such as AI background removal, text-to-image, object add/remove, style transfer arrive as modular plugins, not re-architectures. One interviewed customer, who had spent a year building their own editor before switching, described maintaining it as “a full-time job and our main product isn’t editing.” Every month an in-house team spends on maintenance is a month IMG.LY customers get new capabilities shipped to them. The feature gap widens, not narrows.

Editor capability over 24 months

In-house builds freeze. CE.SDK customers compound.

An in-house editor ships at the snapshot the team can afford and then plateaus under the weight of maintenance. CE.SDK customers absorb new capabilities (AI background removal, text-to-image, object remove, automatic subtitles) as modular plugins each quarter.

Build in-house

CE.SDK customer

Illustrative. The CE.SDK trajectory reflects the cadence of major capability releases shipped to customers without re-architecture. The in-house trajectory reflects the typical build-then-maintain pattern documented in customer interviews and corroborated by the Atlassian 2024 State of Developer Experience Report (69% of developers lose 8+ hours per week to inefficiencies, primarily technical debt).

6. Become deal-eligible and privacy-credible

Some categories require an editor to win the deal at all. One interviewed customer received a written RFP rejection that read: “the other provider has an editor, you don’t.” That single moment approved their budget to buy.

For regulated buyers, fintech, healthcare, government, enterprise, client-side processing is a procurement requirement, not a feature. CE.SDK’s default client-side execution means customer data never leaves the browser, which makes the editor defensible in categories where server-side alternatives are blocked.

Swiss Post producing 1 million+ personalized postcards annually on the platform described CE.SDK as “the only solution allowing a specialized, on-brand UI.”

The economics, in one table

The cost gap between building and buying isn’t just wider on day one, it widens over time. Every month an in-house team spends maintaining the editor is a month IMG.LY customers compound new capability on top of what’s already shipped. The table below summarizes the 3-year picture. For the full cost methodology, including the open-source path and the senior-developer rate assumptions, see IMG.LY’s Build vs. Buy guide.

	Build In-House	Open Source + Glue	CE.SDK
Working prototype	2–6 months	1–2 months	2 days (self-reported median)
Production MVP	6–12+ months	3–6 months	14 days (self-reported median)
Team required	3–5 senior developers	1–2 senior developers	1 developer for integration
Year-1 development cost	$100K–$500K+	$150K–$400K	License + integration
Annual maintenance	$75K–$125K (15–25%)	$50K–$100K	Included
3-year TCO	$525K–$1.4M+	$300K–$700K+	Fraction of build cost
Cross-platform parity	Build per platform	Typically web-only	Web, iOS, Android, Desktop, Server

Source for build and open-source cost bands: IMG.LY’s Strategic Guide to Creative Editing: When to Build, When to Buy. Cross-referenced against BLS May 2024 wage data - median software-developer wage $133,080, 90th percentile $211,450 - and aggregated maintenance benchmarks (Pegotec, 2026). Time-to-prototype and time-to-MVP for CE.SDK are self-reported medians from an IMG.LY customer survey; individual results vary with scope, team, and platform target.

When building in-house still makes sense

This report defends one conclusion, so here is the honest counterweight.
Build your own creative editor if all of the following are true:

Creative editing is your core product, and your unique IP lives inside the editing experience itself.
Your requirements are genuinely non-standard, i.e. no off-the-shelf SDK supports your rendering or interaction model.
You have surplus senior engineering capacity that isn’t needed on differentiated work elsewhere.
Time-to-market is not competitive in your category, nobody else is shipping similar capability.

If any one of these is false, the economics above generally make buying both cheaper and faster.

Methodology

Time-to-prototype and time-to-MVP (2 days, 14 days) are self-reported medians from an IMG.LY customer survey. Individual results vary with team experience, integration scope, and platform target.

In-house and open-source timeline ranges are drawn from 28 structured customer interviews conducted between 2024 and 2026, cross-referenced against IMG.LY’s Build vs. Buy guide. Interview customers are not identified; quantitative ranges reflect the distribution of answers across the set.

Named customer outcomes (Plai, Omneky, Optimizely, Swiss Post, ImageBank X, Halio.ai, Postbuddy) come from IMG.LY’s published case studies, where the customer has reviewed and approved each cited figure.

External benchmarks are drawn from:

U.S. Bureau of Labor Statistics, Occupational Outlook Handbook, Software Developers (May 2024)
Atlassian State of Developer Experience Report (2024) (N = 2,100+ developers and engineering leaders, in partnership with DX and Wakefield Research)
Stack Overflow 2024 Developer Survey (N = 65,437 developers across 185 countries)
Standish Group CHAOS Report
Aggregated software-maintenance benchmarks from Gartner, IEEE, and industry practitioners, summarized in Pegotec (2026) and Vention Teams.

Frequently asked questions

How long does it take to integrate CE.SDK?
The median customer in our survey reports a working prototype within 2 days and a production-ready MVP within a single 14-day sprint. Self-reported; varies with scope and team.

What do IMG.LY customers unlock beyond faster shipping?
Five additional outcomes: new pricing and market tiers enabled by self-serve editing; lifted trial-to-paid and sign-up conversion; reduced design, marketing, and support load; a roadmap that compounds instead of freezes as AI features ship as plugins; and deal eligibility in procurement categories that require an embedded editor or client-side processing.

Can AI coding agents like Claude Code accelerate CE.SDK integration further?
Yes. IMG.LY publishes a set of specialized CE.SDK Agent Skills portable knowledge packs that give AI coding assistants expert-level understanding of the SDK before they write a line of code. The skills cover framework-specific documentation lookup (React, Vue, Svelte, Angular, Next.js, Nuxt.js, SvelteKit, Electron, Node.js, Vanilla JS), feature implementation (/cesdk:build), conceptual explanations (/cesdk:explain), and a builder agent that autonomously scaffolds complete CE.SDK applications from a natural-language description.

How much does it cost to build a creative editor in-house?
Published industry benchmarks and customer-reported estimates converge on $100K–$500K+ initial development over 6–12 months with 3–5 senior developers, plus 15–25% of that cost annually in maintenance. 3-year TCO typically lands between $525K and $1.4M. See our Build vs. Buy guide for full methodology.

What percentage of developer time is spent on maintenance?
Atlassian’s 2024 State of Developer Experience Report found 69% of developers lose 8+ hours per week to inefficiencies, about 20% of their time, primarily to technical debt. Gartner reports that 55–80% of corporate IT budgets go to maintaining existing systems.

What is the failure rate of custom software projects?
The Standish Group CHAOS research finds only 31% of software projects succeed (on time, on budget, full scope); 50% are challenged, 19% cancelled outright. For large projects specifically, success rates fall below 10%.

Custom software project outcomes

Only 31% of custom software projects succeed

Across tens of thousands of tracked projects, the Standish Group CHAOS research finds the majority of custom software is late, over budget, reduced in scope, or cancelled outright.

31%

Successful

On time, on budget, with full scope.

50%

Challenged

Delivered late, over budget, or with reduced features.

19%

Failed

Cancelled before delivery.

~25% of IMG.LY customers failed at building a creative editor in-house

In our customer interviews (N=28), roughly one in four customers had attempted to build a creative editor in-house (or stitch one together from open-source), and abandoned the attempt before adopting CE.SDK.

Source. Standish Group CHAOS Report. For large projects specifically (the size band most in-house creative-editor builds fall into), success rates drop below 10%. IMG.LY customer figure is drawn from 28 structured customer interviews conducted between 2024 and 2026.

How many companies use IMG.LY CE.SDK?
600+ customers including startups, Fortune 500 companies, and government organizations collectively produce 500 million creations per month on the platform.

What platforms does CE.SDK support?
Web (React, Angular, Vue, Svelte, Next.js, Nuxt.js, SvelteKit, Vanilla JavaScript, Electron), Mobile (iOS/Swift, Android/Kotlin, React Native, Flutter, Ionic, Cordova), and Server (Node.js headless mode for batch automation).

Starter Kits: A New Way to Use and Configure Our Editor

João — Wed, 22 Apr 2026 17:14:54 GMT

When we built the first version of CE.SDK’s mobile editors, we optimized for speed and ease of integration. We designed a set of ready-made solution editors: Photo, Design, Video, Postcard, and Apparel Editor. Each is built around the use cases we believed would meet the needs of most of our customers. With one component and a license key, you had a full creative editor running in your app. That approach got products to market fast, and for many teams it was exactly the right starting point.

But products evolve, and so do the needs around it.

As integrations matured, teams needed deeper configuration, more granular control, and the ability to shape the editor into something uniquely theirs. What starts as “give us a working photo editor” becomes “give us our photo editor.”

That’s why, starting with CE.SDK v1.73 on iOS and Android, CE.SDK evolves from a set of preconfigured solution editors into a single, flexible Editor foundation paired with Starter Kits: complete, working editor projects that you own, customize, and control entirely.

Here’s what that means and why it’s worth it.

What changed

Previously, you integrated CE.SDK by dropping in a solution-specific component: PhotoEditor, DesignEditor, VideoEditor, ApparelEditor and PostacardEditor. Each came with built-in UI, default behaviors, and preconfigured toolbars. You could adjust some of it through configuration APIs, but the foundation was managed internally by our SDK.

With v1.73, those components are replaced by a single Editor entry point that starts minimal without any configuration and a set of Starter Kits that provide the full experience you’re used to.

Each Starter Kit matches a previous solution: Photo, Design, Video, Postcard, and Apparel. You download it, drop it into your project, and you have the same editor as before.

With Starter Kits, the setup becomes explicit and lives in your own codebase. Instead of relying on built-in defaults inside a prebuilt solution, you start from a ready-made configuration structure that you can inspect, own, and change directly.

And if none of the starter kits match your needs, you can build your own editor from scratch using our configuration directly.

Before, you were always starting from one of the predefined solutions and trying to bend it to fit your use case, which was limited and often frustrating. Now, the building blocks are there for you to assemble however you want.

What are the benefits?

The full picture in one place

Configuration used to be spread across multiple APIs and documentation pages. It wasn’t always clear what you could customize, where to find the right setting, or whether a particular behavior was even exposed for modification.

With a starter kit, the configuration is the documentation. Open the configuration file, and you see every callback, every toolbar item, every setting, the complete scope of what the editor does.

This also makes production behavior safer. Critical parts of the editor setup are now explicit in your code rather than implied by SDK defaults. Your team can see exactly what is configured, why, and review changes through your normal development process.

More control and capability over your editor

Starter kits unlock customizations that were simply not possible before: restructure how the editor initializes; inject custom logic between loading phases; defines layouts from the ground up; build workflows that are unique to your product; and more.

The old configuration APIs drew a line between “customizable” and “not customizable.” Starter kits erase that line. If you can see it in the code, you can change it.

In simple terms, you can now adapt the editor to your product, instead of adapting your product to the editor, and this was one of our main drivers.

Opt in, never opt out

Until now, an SDK update could introduce visible changes to your editor, like a new toolbar button, a different menu option, a changed default, without you asking for it. Your release process had to account for UI changes that came from a dependency, not from your team.

With CE.SDK v1.73, that dynamic is reversed. SDK updates bring new features, engine improvements, performance gains, and bug fixes. But your editor UI stays exactly as you left it. New features and components become building blocks you adopt on your own schedule, documented, with examples, and ready when your implicit decide to add them. Nothing shows up in your product unless you put it there.

Two paths, your choice

Start from a Starter Kit
Download the one that matches your use case, run it, and customize from there. Each kit is a proven, production-ready structure that handles the complexity of editor setup so you don’t have to figure it out from scratch. Most teams will take this path.

Build from scratch
If you have very specific requirements or prefer to architect everything yourself, the Editor view accepts raw configuration directly. The starter kits serve as comprehensive, living reference implementations. Even if you never use them directly, they show you exactly how every piece fits together.

The engine you rely on hasn’t changed

It’s worth saying clearly: the core of CE.SDK, the rendering engine, export pipeline, asset handling, performance characteristics, and everything that powers the creative experience is unchanged. We improved how you configure and integrate the editor, not what powers it.

The Tradeoff

The old one-component integration was genuinely convenient for getting started. With starter kits, you have a small module in your project, a handful of well-organized files that you own and maintain.

We believe this is the right tradeoff for any team building a real product. The moment you need to customize anything you’ll be able to clearly structured and to modify without limits.

At its core, this change is about moving from implicit behavior to explicit control, and we believe that is the better long-term contract with our customers. Your editor should not change in meaningful ways unless you decide it should. Your upgrade path should be predictable. And your team should be able to understand the integration by reading its own code.

Getting Started

We’ve written detailed migration guides that walk through every change with before-and-after examples. Each guide also links to the starter kit repositories for your platform:

	iOS	Android
Migration Guide	Upgrading to v1.73	Upgrading to v1.73
Photo Editor	GitHub	GitHub
Design Editor	GitHub	GitHub
Video Editor	GitHub	GitHub
Postcard Editor	GitHub	GitHub
Apparel Editor	GitHub	GitHub

We’re here to help with the transition. If you have questions, reach out to our support team or open an issue on the starter kit repositories.

CE.SDK v1.73 Release Notes

Neslihan — Tue, 21 Apr 2026 13:29:35 GMT

v1.73 is a mobile-focused release. The main act is our new architectural foundation for iOS and Android: Starter Kits give you full ownership of your editor configuration. On the engine side, CE.SDK now supports SVG export across all platforms.

Own Your Mobile Editor — Not Just the Config

The old model was simple: drop in a solution component (PhotoEditor, VideoEditor, DesignEditor), pass a license key, ship. For most teams, that was exactly the right starting point. Fast to integrate, zero configuration overhead, a full editor running in your app within hours.

As products matured, though, teams needed more. Deeper customization. Granular control over behaviors. An editor that felt like theirs.

That’s what Starter Kits for Mobile addresses.

The prebuilt solution components are replaced by a single Editor entry point and a set of Starter Kits: complete, working editor projects for each use case that live in your codebase, not ours. Set it up in minutes.

For your product, this means: you can adapt the editor to fit your product, not the other way around.

Everything Is In Your Code Now
Each Starter Kit is a real editor project, not a thin config wrapper. Every toolbar item, every callback, every loading phase is written out explicitly in files you own.

That means your team can read the integration, review changes to it, and understand exactly what the editor does and why. No more hunting through SDK internals to figure out why something behaves the way it does.

SDK Updates Stop Touching Your UI
Previously, updating CE.SDK could introduce new buttons, changed defaults, or different menus without you asking for them. Your QA had to catch it.

That dynamic is reversed now. Engine improvements, bug fixes, and performance gains come through updates as before. But your editor UI stays exactly where you left it. New features arrive as optional building blocks, documented and ready when you want them.

No More Customization Ceiling
The old configuration APIs had a line between what you could change and what you couldn’t. Starter Kits remove that line entirely. You can restructure initialization, inject custom logic between loading phases, and build workflows specific to your product.

If you can see it in the code, you can change it.

If none of the five kits match your needs, the Editor view accepts raw configuration directly.

Migration

This is a breaking change on both iOS and Android. Migration guides cover every change with before-and-after examples.

→ Android Migration Guide
→ iOS Migration Guide

Starter Kit Repositories

Editor	iOS (Swift)	Android (Kotlin)
Photo	GitHub	GitHub
Design	GitHub	GitHub
Video	GitHub	GitHub
Postcard	GitHub	GitHub
Apparel	GitHub	GitHub

Export Vector Designs as SVG

Until now, users working with vector content in CE.SDK had no path to get that content out as a vector file. CE.SDK v1.73 adds SVG export via the image/svg+xml MIME type.

Text is exported as vector paths for consistent rendering across environments regardless of font availability. Drop shadows, blur, effects, and embedded raster images are rasterized and included as embedded images within the SVG output.

→ Exporting Blocks Engine Guide

Changelog

See the full changelog for the complete list.

Thanks for building with IMG.LY.

Join 3,000+ creative professionals who get early access to new features and updates. Subscribe.

PowerPoint Online: Native PPTX Editing in the Browser with CreativeEditor SDK

Klaudia — Fri, 17 Apr 2026 11:21:14 GMT

Organizations can now create workflows where presentations stay editable inside their own platforms: content management systems, collaboration tools, educational platforms, and SaaS applications, without switching to external editing software each time.

PowerPoint Import Capabilities

IMG.LY SDK enables importing PPTX files directly into browser-based workflows.

Import functionality
Existing PowerPoint files can be loaded directly into CE.SDK. The importer interprets the PPTX structure (text, images, shapes, and formatting), and converts each slide into an editable CE.SDK scene. Files can come from uploads or your own storage systems.

Editing interface
Once imported, slides become CE.SDK design scenes. Users can change content freely using CE.SDK’s editor, which keeps the structure intact, including text hierarchies and slide ordering.

What gets preserved: Text formatting (font families, sizes, colors, bold, italic), shapes (rectangles, ellipses, custom vector shapes), images, gradient fills, shadow effects, gradient backgrounds, groups, z-order, and theme colors are all carried over from the original PowerPoint file.

Editing Capabilities for Presentation Workflows

The browser-based editor includes the essential features needed for everyday presentation updates:

Text editing: Change text and adjust typography: fonts, colors, alignment, sizes, etc.
Visual element manipulation: Move, resize, rotate, and reorder shapes, images, and text boxes
Layer management: Adjust stacking order to control which content appears on top
Slide navigation: Rearrange slide order and quickly move between slides
Content addition: Add new images, shapes, or text elements when needed
Styling options: Edit fills, borders, and other visual properties

This helps teams refresh outdated content, localize presentations, update brand assets, or adapt a single deck to many different use cases, all without leaving the platform.

What’s Not Supported

The importer focuses on the most common presentation elements. Some PowerPoint features don’t carry over:

Tables — Table content is skipped on import; a workaround is to ungroup tables in PowerPoint before importing
Charts — Chart visualizations are not imported
SmartArt — Diagram graphics are not imported
Animations and transitions
Slide masters and layouts
Audio and video
Comments and notes
Background images — solid colors and gradients are supported, but image backgrounds are not

For presentations that rely heavily on these elements, it’s worth reviewing the output after import and making adjustments in CE.SDK.

Workflow Improvements with PowerPoint on the Web

Why this matters for real workflows:

Less switching between tools: Users can make changes right inside the system where the presentation is stored. It’s faster and reduces confusing file versions.

Accessible anywhere: Works on any modern browser, making editing possible on devices without native PowerPoint support.

Lower dependency on desktop software: Teams don’t always need Microsoft PowerPoint licenses just to update a slide or fix small mistakes.

Faster corrections: Updates become quick tasks. Improving slides doesn’t need to slow things down, especially for marketing or sales content.

Aligned with existing processes: Versioning, commenting, and permissions stay right where the content lives, which really simplifies collaboration.

Browser-Based Editing vs. Desktop PowerPoint

The browser-based editor covers the most common editing needs. PowerPoint on desktop still handles specialized features the importer doesn’t cover.

Capability	Browser-Based Editor	Desktop PowerPoint
Installation requirement	None — opens in the browser	Requires installation
Platform compatibility	Works on any device with a modern browser	Windows, macOS
Core content editing	Yes, for supported elements	Fully supported
Advanced features	Tables, charts, SmartArt, animations not supported	Complex animations, transitions, macros, advanced design
Integration	Easy embedding into web apps	Requires file transfer flow
Access speed	Instant, no launch time	Depends on local system
File compatibility	Imports PPTX; outputs CE.SDK scenes	Native PPTX with extended features
Collaboration	Connects with existing web-based systems	Microsoft ecosystem required
Network requirement	Can be edited offline	Can be offline

For straightforward content updates (text changes, image swaps, visual tweaks), the browser-based workflow handles most everyday needs. For presentations that rely on tables, charts, animations, or other advanced PowerPoint features, desktop PowerPoint remains the right tool.

Technical Implementation for Developers

The SDK handles PPTX parsing and slide rendering in the browser as CE.SDK scenes.

Fast integration: Setup usually takes hours or days, not months, since all the hard parts are already covered by the SDK.

Customizable interface: Developers can enable or disable features, apply brand styling, and connect to authentication and storage systems already in use.

Platform-agnostic: The package works in both browser and Node.js environments with no file system dependencies, using pure ArrayBuffer handling.

Controlled infrastructure: Everything runs where your platform runs, and you keep full control of data processing and access.

Use Cases Across Industries

EdTech: Students edit presentations directly in learning platforms without software installation.

CMS platforms: Teams update brand assets and sales decks in the same place they manage all other content.

Collaboration tools: Everyone works on the same version of a file without downloading and re-uploading.

SaaS products: Presentations become part of the workflow, not a separate step.

Creative agencies: Client slides can be adjusted quickly without leaving project management systems.

Getting Started

Try PowerPoint editing in the browser using our demo, or get started with CreativeEditor SDK to explore the full feature set.

CE.SDK v1.72 Release Notes

Neslihan — Fri, 03 Apr 2026 10:47:49 GMT

CE.SDK v1.72 is a massive design and creative capabilities release: Edit vector paths in your web editor. Generate AI images on mobile. Record voiceovers on iOS and Android, and format text with lists, underline, and strikethrough across every platform. Design and video scenes unify into a single editing surface on Web.

Let’s take a look!

Edit Vectors with Precision on the Web

CE.SDK now lets users edit any shape at the path level.

Select a shape and enter Edit Path mode. Manipulate individual anchor points and curves. Move nodes, bend segments, add or remove points. Lastly, apply fills, gradients, and colors.

In this example, we build our figure from a simple polygon shape:

Build custom icons, illustrations and detailed layouts directly in the web editor, without leaving your app.

→ Explore Vector Path Editing Documentation

Design and Video Editing In One Editor

Web users can now work across design and video in a single scene. Everything you can do in design mode, you can do in video mode too.

For your product, this means a simpler, more coherent editing experience for users who work across both formats.

Note: The feature toggle shown in the video is coming to our demos soon. It is not part of the default CE.SDK setup.

→ Visit CE.SDK 1.72 Migration Guide

Generate AI Images on Android and iOS

The AI image generation plugin now ships on iOS and Android.

This is the first mobile AI plugin for CE.SDK. Users can generate images directly inside the mobile editor through custom plugin panels, without leaving the creative workflow.

For your product, this means: you can now deliver AI-powered creative features on mobile with the same plugin architecture already available on web. One capability, every platform.

→ Try Android Mobile Demo
→ Try iOS Mobile Demo

Record Voice-Overs on Android & iOS

Tell your story by giving your videos a voice. iOS and Android users can now record their voice directly over video clips.

Layer multiple voiceover tracks on the timeline. Perfect to record engaging videos, like creators work in TikTok and Reels.

→ Try Android Mobile Demo
→ Try iOS Mobile Demo

Decorate Text On All Platforms

Updates for text editing land simultaneously across platforms:

Use Bullet and Numbered Lists to structure text with ordered and unordered lists. Underline and strike text, including custom underline colors.

Improvements

Rename Pages with Double Click
Web users can now rename pages directly on the canvas with a double click, without navigating to a separate settings panel.

Place Elements Anywhere with Infinite Canvas
Web Users can now place elements outside page boundaries. The canvas extends beyond the page, giving users a flexible workspace to park assets, build off-canvas elements. Work more freely without being constrained to the page frame.

Changelog

See the full list of fixes and breaking changes in the v1.72.0 Changelog and 1.72.0 Migration Guide.

Thank you for building with IMG.LY.

AI Design Agents and Creative Automation: How to Ship a Full Campaign Without a Designer

Klaudia — Wed, 01 Apr 2026 10:14:03 GMT

You have your files, hooks, Google Ads data but still can’t actually launch a campaign because you have to go to a designer for the final assets.

That gap is exactly where campaign momentum dies. Not at the strategy stage or in copy but at the last mile, when everything is ready except the thing people will actually see.

Luckily, it no longer has to.

The AI Marketing Stack Has a Design-Shaped Hole in It

Most marketing workflows have been quietly transformed over the last two years. Copy generation, audience segmentation, keyword research, performance analysis - all of it runs faster now, with less manual input. A solo marketer can do what used to require a team. Except for one part.

Design hasn’t moved. The workflow is still: write a brief, hand it to a designer, wait, review, revise, wait again. Then do the same thing in three more formats because the 1:1 you approved doesn’t fit Stories, Display, or LinkedIn. That loop can take days. And it doesn’t matter how good your AI-generated copy is if it’s sitting in a doc waiting for someone to have bandwidth.

This isn’t a resourcing problem. Hiring more designers doesn’t fix the structural issue; it just adds capacity to a fundamentally slow process. The problem is that the tools built for design weren’t designed for the workflow a modern marketer actually runs. They expect a designer at the keyboard. They don’t expect a marketer with a campaign brief and a conversation window.

The result: campaigns that are otherwise fully automated still stall before they ship. The bottleneck moved from copy to creative. And most teams haven’t noticed yet, because design delays feel normal. They’ve always been there.

What an AI Design Agent Actually Changes

An AI design agent is an autonomous AI system, not a prompt-response tool. It plans, reasons, and executes design tasks independently. Given a goal, it breaks that goal into steps, uses the tools available to it, retains context across the session, and can self-correct when the output isn’t right. That’s the category: a system that drives the workflow rather than waiting for instruction at each step.

Most design agents deliver speed. The handoff that used to take days can happen in minutes. But the output is still a deliverable: a file you receive, use as-is, or move somewhere else. Most operate inside existing tools or generate assets you work with elsewhere. The speed is real, the editability usually isn’t. If something needs to change, you’re back to prompting from scratch.

CoDesign sits differently. It doesn’t hand you a finished asset. It gives you a working starting point on a real canvas. Layers, text boxes, placeholders - real assets you can continue to work with, in the same conversation, without leaving the session.

Brand consistency gets handled at the foundation. Load your brand kit once, including colors, fonts, logo, and layout rules, and every output that session respects those constraints. You’re not eyeballing hex codes or hoping the font looks right. The rules are applied from the start, not checked at the end.

Multi-format adaptation is where the time savings become concrete. A campaign that runs across Instagram, Google Display, LinkedIn, and print doesn’t produce four separate briefs and four separate rounds of designer revisions. You describe the formats you need, and the agent adapts the work. The campaign stays consistent across all of them.

The biggest shift isn’t speed, though that’s real. It’s that you stay in creative control throughout. There’s no handoff moment where you lose the thread and have to re-explain the brief to someone else. The context lives in the conversation.

How to Run a Campaign Production Session with CoDesign

This is the actual sequence. Walk through it once and the workflow becomes repeatable.

1.Start with the brief. Open CoDesign and describe the campaign in plain language. Audience, objective, platform, tone, any constraints. The more specific you are here, the less iteration you’ll need later. Treat it like briefing a senior designer who hasn’t worked with your brand before.

2.Generate copy variations before you open the canvas. Use whichever AI writing tool you already work with (ChatGPT, Claude, or whatever is in your stack) to produce multiple copy directions: headline hooks, body copy, CTAs. Get four or five versions per element. Copy and design are separate steps that feed into each other. Having real options ready before you start the design session means CoDesign has something specific to work with, not a blank brief waiting to be interpreted.

3.Feed the brief to the AI design companion. With copy variations ready, ask CoDesign to generate initial ad designs. Describe the format, the hierarchy you want, any layout preferences. You’ll get structured, editable designs on the canvas. Not a rendered image, but a working starting point with real layers.

4.Apply your brand kit. If you haven’t already, load your brand assets: logo, color palette, type system, approved imagery. The agent applies these rules to the designs. Every output from this point respects your brand standards automatically.

5.Adapt across formats. Tell the agent which formats you need. The social variant, the display variant, the vertical for Stories, the square for feed. Watch the layouts adapt to each context, maintaining the campaign idea and brand consistency across dimensions. If the hierarchy needs adjusting for a specific format, describe what’s not working and the agent fixes it in conversation.

6.Refine in conversation. This is where the canvas-based approach earns its value. You’re not generating new versions from scratch. You’re iterating on what’s already there, in the same session. “Move the logo to the bottom right. Try the headline in the lighter weight. Swap this layout for something with more white space.” Each exchange builds on the last, so the conversation stays grounded in what’s on the canvas rather than starting over from a new prompt.

7.Export and ship. When the designs are approved, export in the formats your media plan requires. The session context lives with the file, so if something needs to change post-launch, you’re not starting from zero.

One honest note: the quality of the output is proportional to the quality of the brief. Vague prompts produce generic starting points. Teams that invest two minutes in a specific, structured brief consistently get more usable first outputs than teams that describe the campaign in one sentence and expect the agent to fill in the gaps.

This Is What Closing the Loop Actually Looks Like

Design agents don’t replace designers. They remove the bottleneck that sits between strategy and execution.

The marketer who used to wait three days for ad assets can now produce a full campaign set in a single session. The designer who spent half their week on format resizes and small-copy tweaks can spend that time on the work that genuinely requires their judgment. That means brand-defining creative, campaign concepts, and anything where taste and experience are the actual input.

It was never about willingness to collaborate. The tools just didn’t allow for anything else. Every design change, no matter how small, had to go through a handoff. A headline adjustment on a banner resize does not need a creative director. A resize from 1:1 to 9:16 does not need a brief, a Slack message, and a 48-hour turnaround.

Thanks to design agents conversation shifts. It moves from “can you make this” to “how should this look.” And that’s a way more interesting conversation.

Interested in trying IMG.LY CoDesign? Reach out to our team.

What Is an AI Design Agent?

Klaudia — Mon, 30 Mar 2026 04:52:01 GMT

The phrase “design agent” is being used in two completely different ways right now, and the confusion is worth clearing up before either meaning becomes the default. Search for it today and you’ll mostly find AI design agencies - services firms that use AI in their process. That’s a reasonable business, but it has nothing to do with what this article is about.

The second meaning, a design agent as a category of AI tool, is the one that matters for product builders, developers, and creative teams trying to understand where AI-assisted design is actually going. That’s what we’re defining here: what it is, how it works, how it differs from tools you already know, and why the distinction matters if you’re building or evaluating creative software in 2026.

First, What an AI Design Agent Is Not

An AI design agency. This is a services firm that uses AI tools in its creative process. It’s a completely different category - a service, not a tool - and it’s the most common result you’ll find when you search “design agent” right now.

An AI image generator. Midjourney, DALL-E, and similar tools produce images from text prompts. They generate a single output from a single instruction.

An AI feature inside a design tool. Figma’s AI suggestions, auto-layout assistance, and background removal are AI features. They augment a manual workflow making specific tasks faster.

A design automation pipeline. Server-side systems that batch-generate assets from templates are automation, not agency. They’re fast and scalable, but they don’t converse, can’t interpret an ambiguous brief, and don’t refine their output in response to feedback. The confusion here is understandable: modern automation systems use AI models internally and can produce polished, varied-looking results that are easy to mistake for something more intelligent. But give one an ambiguous brief and it either fails or produces something technically correct that misses the point entirely. Give a design agent the same brief and it asks a question. That distinction - executing a fixed process versus reasoning about intent - is what separates the two categories.

The distinction matters because “design agent” is becoming a meaningful category term, and what it actually describes is different enough from all of the above that collapsing the distinctions creates real confusion, both for people evaluating tools and for people building products.

AI Design Agent - a Working Definition

There is no settled definition of an AI design agent yet, the term is still early. Based on what we see in the tools that genuinely deliver on the promise, three properties distinguish a real design agent from something that merely resembles one:

1. Autonomy. The agent takes multi-step actions without requiring a human instruction at each step. Given “create a five-page product catalog in a Scandinavian minimal style,” it works out the layout, typography, and image placement independently and produces the result.

2. Conversational interface. The agent communicates in natural language. It can ask clarifying questions, explain what it’s done, and accept follow-up instructions. The interaction feels like briefing a designer, not operating software.

3. Refinement loop. The agent takes feedback across multiple conversation turns: “make the typography lighter,” “apply the brand’s warm color palette”, and updates the design accordingly. This iterative loop is what separates a design agent from a one-shot generation tool.

A tool that has all three of these properties is a design agent. A tool that has one or two is something else; probably useful, but in a different category.

How an AI Design Agent Works in Practice

An abstract definition only takes you so far. Here’s what a fully implemented design agent workflow actually looks like, drawn from a real demo of IMG.LY CoDesign.

Step 1. The user opens CoDesign. The agent interface - a chat panel - sits alongside the canvas. They’re in the same window.

Step 2. The user types a brief: “Here’s a CSV of five products from our furniture brand. Generate one landscape catalog page per product — two-column grid, full-bleed photo left, typography-led layout right. Clean, minimal. Think Hay, Muuto, Frama.”

Step 3. The agent processes the brief, the data, and any brand context it has access to. It generates a five-page catalog in the editor: product names, descriptions, prices, photo placeholders, layout structure consistent across all five pages.

Step 4. The user reviews the output and follows up in the chat: “Nice. Pre-fill the photo placeholders with black-and-white product photography, soft contrast.”

Step 5. The agent updates the design. The user manually adjusts one headline, corrects a price, and exports.

The full workflow, from brief to print-ready output, took minutes rather than hours. The user never left the tool. The agent handled all structural and stylistic decisions. The human handled final judgment and small corrections.

But generating layouts from a brief is only part of what a design agent can do. In the same chat interface, the agent can build functional decision-making tools directly inside the editor. Ask it to create a Color Themes panel, and it produces a working component: five named presets, each one applying a complete color theme across the entire design in a single click. The user doesn’t switch to a settings screen or manually update individual elements. The agent has built the control they need, right where they need it, as part of the same conversation. That’s a meaningfully different capability: not just producing a designed output, but constructing the tools that let the user make better decisions about that output as they finalize it.

This table is meant as a fair comparison, each column represents how these tool categories actually behave today:

Capability	AI Image Generator	AI Design Features	Design Agent
Takes a brief	Prompt only	No	Yes
Produces editable layouts	No	Partial	Depends on a tool
Multi-step autonomy	No	No	Yes
Conversational refinement	No	Limited	Yes
Brand / context awareness	No	Partial	Yes
Iterative across a session	No	No	Yes

The pattern here isn’t that design agents are better at everything - it’s that they operate at a different level of the workflow. Image generators and AI design features are task-level tools. A design agent is a workflow-level tool.

The Autonomy Slider: Why Human Control Still Matters

One of the most important design decisions when building or evaluating a design agent is how much autonomy the AI exercises by default.

Full autonomy is fast. The agent makes all decisions and presents a finished output. But it can produce results that don’t match the user’s actual intent, especially when the brief is ambiguous or the stakes are high.

Minimal autonomy is safe. The agent only suggests, the human decides everything. But at that point, you’ve lost much of the value of having an agent in the first place.

The best implementations give users what you might call an autonomy slider: the ability to let the agent run with full independence on some tasks, take targeted direction on others, and step aside entirely when the user wants to edit manually. The right level of autonomy depends on the task and the user’s confidence, not a fixed setting applied uniformly across every interaction.

For any design agent, this means the interface needs to let the user reach in and adjust manually, mid-workflow, without losing what the agent has already done. The agent and the editor have to exist in the same environment. Separate windows with an export step between them break the loop entirely.

Where AI Design Agents Create the Most Value

Not every creative workflow benefits equally from an AI agent. The scenarios where design agents consistently create the most value tend to fall into three categories:

High-volume, high-variation creative production. Marketing teams producing dozens of ad variants, e-commerce teams generating product imagery at scale, publishers creating template-based content in bulk. A team can brief the agent once: brand colors, copy, format specs, and get 40 properly formatted variants back in the time it would have taken to manually produce three, each one consistent with the last.

Non-designer users who need professional results. Not everyone who needs to produce a designed output is a designer. Marketers, retailers, operations teams, small business owners - they know what they want but don’t have the tools or time to build it manually. A design agent gives them a way in that doesn’t require either.

Expert designers who want to explore faster. Experienced designers using the agent to generate starting points, explore multiple directions quickly, or offload the time-consuming production work while retaining full control over the final result. A designer can spend 20 minutes reviewing six distinct layout directions the agent generated from a single brief, rather than a full afternoon building each one from scratch.

These aren’t exhaustive categories, but they represent the use cases where the workflow-level shift actually changes what’s possible, not just what’s faster.

A Different Kind of Design Tool

A design agent makes creative work faster and more accessible. For designers who want to explore more directions in less time, and for non-designers who have always known what they wanted but lacked the tools to build it.

That’s what IMG.LY Codesign is built around. It’s in early access now, inside a fully featured design editor - get in touch for early access.

Vibe Design Tools Compared

Klaudia — Sun, 29 Mar 2026 03:51:56 GMT

Vibe coding gave non-technical people the ability to build software by describing what they wanted. The same shift is now happening with vibe design. For the first time, a marketer, a retailer, or a small business owner can create a professional design exactly to their specification just by explaining it to an AI. No design skills required. No external tool. No waiting for a designer to become available.

This article compares four tools leading that shift - what they do well, where they differ, and how to choose between them.

Tools Built for Creators

These tools represent the current state of standalone vibe design software. Each is genuinely good at what it does. The differences come down to what kind of work they’re built for.

Google Stitch

Google Stitch is an AI-native design canvas from Google Labs, launched for public beta in early 2026. It accepts text, voice, images, and code as input and produces high-fidelity UI designs and interactive prototypes on an infinite canvas. Its design agent can reason across an entire project rather than just the current frame - a meaningful step beyond tools that only operate on one screen at a time.

Stitch introduces a DESIGN.md file format for exporting and importing design rules across tools, and it connects to Cursor, Claude Code, and Gemini CLI via an MCP server. It’s available free during beta with monthly generation limits, and it’s clearly aimed at UI/UX designers and developers building product interfaces - not marketing or graphic design work.

Figma Make

Figma Make takes natural language prompts or existing Figma designs and produces working prototypes and web apps - functional code, not just mockups, with optional Supabase backend integration. Because it lives inside Figma, it has access to your existing design libraries, component systems, and tokens from the start.

It’s best understood as a rapid ideation and prototyping tool. It generates interactive, working outputs fast, but the code benefits from developer review before going to production. It’s distinct from Figma Sites, which handles actual publishing. AI credits are required for usage.

Lovart

Lovart is a standalone AI design agent founded by a former ByteDance senior product director. Its scope goes well beyond graphic asset creation: from a single prompt, it can generate brand identity systems, UI mockups, video content, packaging designs, and full marketing campaigns. It uses a proprietary MCoT (Mind Chain of Thought) reasoning engine designed to mimic how a creative director thinks - analyzing business context, target audience, and brand requirements, not just aesthetic style.

Its infinite canvas continuously analyzes all assets present to maintain visual consistency across an entire project, and outputs are compatible with Figma, Photoshop, and After Effects. Lovart is positioned for marketing creatives, solo designers, and small creative teams who need to produce full campaigns without a large agency.

Adobe Firefly Boards

Adobe Firefly Boards is Adobe’s AI-first collaborative ideation canvas, built for creative professionals who need to move quickly from inspiration to concept. It lives inside the Adobe Firefly web app and mobile apps (iOS and Android), and syncs with Creative Cloud so work can move from moodboard to production without switching platforms.

The core of Boards is an infinite multimedia canvas where you bring in text prompts, reference images, video clips, and Adobe Stock assets, then generate across all of them at once. What makes it unusual is the model breadth: Boards gives you access to Adobe’s own Firefly models alongside partner models from Runway, Pika, Luma AI, Google Veo, Black Forest Labs, and others, all inside the same workspace. Outputs are images, video clips, text overlays, and assembled mood boards or storyboards, and every generated asset carries Content Credentials that automatically record which AI model produced it.

Canva Magic Studio

Canva Magic Studio is a suite of more than 15 AI-powered tools embedded directly into the Canva editor on web, mobile, and desktop. It’s not a separate app. If you’re already a Canva user, you’re already inside Magic Studio.

The suite covers writing, image generation, video creation, format switching, and multi-language translation, all accepting text prompts, uploaded media, documents, and existing canvas elements as input. Brand Kit integration is what distinguishes it from more isolated AI generation tools: when you generate a design through Magic Design, it pulls from your saved Brand Kit (logo, colors, fonts) rather than producing something generically styled. That keeps AI-generated output on-brand without manual cleanup.

The trade-off is structural. Canva outputs are flat exports within a consumer-grade editor, not structured design objects you can manipulate at the element level. Generations are fast and on-brand, but the editing ceiling is Canva’s editor. For users who need granular creative control or complex asset structures, that’s a real constraint, not just a preference.

IMG.LY CoDesign

IMG.LY CoDesign is AI-powered design companion built for creators and teams producing marketing materials, branded content, social assets, and multi-format campaigns. What sets it apart from other standalone tools is how it treats AI output: every element CoDesign generates is a structured, editable design object on the canvas - not a flat image to export and rebuild elsewhere. Move a headline, swap a font, resize a block, change a color - directly in the same tool that generated it.

The agent and the editor aren’t two modes. They’re the same tool. You can prompt a direction, refine it in conversation, and take over the canvas directly at any point - without switching tools, exporting, or starting over. CoDesign also goes beyond the canvas: ask it to build a brand panel, a form-based template, or a custom configurator, and it builds that too - directly inside the editor, from the same prompt interface.

Here is a quick demo to showcase what IMG.LY CoDesign can do.

Vibe Design Tools at a Glance

	Google Stitch	Figma Make	Lovart	Adobe Firefly Boards	Canva Magic Studio	IMG.LY CoDesign
Primary use	UI/UX design from prompts	Prompt-to-prototype / app	Full campaign and brand creation	AI-first concepting and moodboarding	AI design generation inside Canva editor	AI-assisted design for creators and teams
Where it lives	Google (standalone web app)	Inside Figma	Lovart (standalone)	Adobe Firefly web + mobile; syncs with Creative Cloud	Inside Canva (web, mobile, desktop)	IMG.LY
Input types	Text, voice, images, code	Text, existing Figma designs	Text, images, brand briefs	Text, images, video, Adobe Stock assets	Text, images, video, documents, existing design elements	Text, images, CSV, brand kits
Output type	UI designs and prototypes	Interactive prototypes and web apps	Brand assets, campaigns, video, packaging	Images, video, text overlays, mood boards, storyboards	Images, video, presentations, styled text, format-converted designs	Editable multi-page designs, videos, animations
Output format	Flat / exportable	Code / exportable	Flat / exportable	Flat / exportable; Content Credentials attached	Flat / exportable within Canva editor	Structured editable objects on canvas
Brand context	Manual per session	Via Figma design system	Canvas-aware within session	Enterprise Custom Models; personal library import	Brand Kit applied automatically at generation	Loaded at session start
In-chat UI generation	No	No	No	No	No	Yes
Multi-model AI	No	No	No	Yes (Runway, Pika, Luma, Google Veo, BFL, and more)	No (Dream Lab uses Leonardo.ai Phoenix)	No
Best for	Product designers, developers	Product teams in Figma ecosystem	Marketing creatives, solo designers	Creative professionals doing concepting and ideation	Non-designers and content teams needing fast, on-brand output	Creators and teams needing editable AI-generated design

For a detailed breakdown of how Canva Magic Studio compares to CoDesign specifically, see Canva Magic Studio vs. CoDesign.

How to Choose

The criteria here aren’t about feature counts. They’re about the kind of work you’re doing.

Choose Google Stitch if you’re a product designer or developer building UI and want an AI agent that reasons across your whole project, not just individual screens. It’s the most technically connected of the six (MCP server, code input, DESIGN.md export), and it’s clearly built for product interface work.

Choose Figma Make if you’re already in the Figma ecosystem and want to go from prompt to working prototype fast. It inherits your design system automatically, which removes a lot of setup friction, and it outputs functional code rather than static designs.

Choose Lovart if you need to produce full creative campaigns (brand identity, packaging, video, marketing assets) from a single prompt. Its MCoT reasoning engine and canvas-level consistency analysis make it particularly strong for high-volume marketing creative work.

Choose Adobe Firefly Boards if you’re a creative professional working inside the Adobe ecosystem who needs to generate and align on large volumes of visual concepts before moving them into production. It’s the right call for designers, photographers, and creative directors doing serious concepting work that will ultimately land in Photoshop, Premiere, or Illustrator.

Choose Canva Magic Studio if you need fast, on-brand creative output and your users aren’t designers. Magic Studio’s Brand Kit integration means generated designs pull from your saved colors, fonts, and logos automatically: no cleanup, no manual adjustment. It’s not the tool for pixel-level creative control, but for marketing teams and content creators producing high volumes across multiple formats and channels, that’s rarely the priority.

Choose CoDesign if you need AI-generated output you can actually edit. Every element lands on the canvas as a structured design object (headline, image block, color field), not a flat export. That matters when the brief changes, the brand needs adjusting, or the output needs to become ten variations rather than one. For creators and teams producing branded content at scale, that editability is the difference between a starting point and a finished asset.

CoDesign is in early access. Be among the first to prompt a direction and walk away with a design you can actually use. Talk to our team to learn more.

CE.SDK v1.71 Release Notes

Neslihan — Fri, 20 Mar 2026 20:37:43 GMT

v1.71 is a design capabilities release. Animations arrive on iOS, completing motion design across every platform. The web editor gets free layout mode. Variable fonts land across all platforms.

Let’s dive in!

Add Animations to Your iOS Video Editor

Add dynamic motion to your text and design elements with CE.SDK for iOS. Our Animations for design blocks (images, shapes, stickers) come with a comprehensive library. This release also ships with a sleek UI.

Comprehensive Animation Library
Access a full suite of in, out, and loop animations, mirroring the capabilities of our animation for Web and Android.

Tailored Motion Controls
Fine-tune animations like duration, easing, direction, and more.

→ iOS Animation Documentation
→ Try the iOS Video Editor Demo
→ Download the iOS Demo App

Design Multi-Format Scenes with Mixed Page Sizes

In your web editor, every page in a scene can now have its own dimensions. If enabled, the resize panel automatically adapts to your selection. Resize one page or all pages at once.

For your product, this means: users can design across multiple formats in a single session. Social post, banner, side by side.

One Font File, Every Weight: Variable Font Support

Our engine now supports variable fonts! A single font file can represent multiple weight and style variants, eliminating the need to load separate files for each.

For your app this means: leaner asset loading, more typographic flexibility, and better brand consistency for users working with modern type systems.

→ Variable Fonts Docs

Improvements

Stay Focused on a Simplified Video Timeline
The web video timeline now focuses on the active track by default, hiding other tracks to reduce visual noise. Users can still access everything, but the default view keeps attention on what they’re actually editing.

Full Changelog

All performance improvements, breaking changes, and fixes are in the v1.71.0 Changelog.

Thank you for building with IMG.LY.

What Is Vibe Design? The Definitive Guide for Product Builders, Designers, and Creative Teams

Klaudia — Fri, 20 Mar 2026 17:23:51 GMT

Vibe Design - A Concept That Just Got a Name

Creative work has always involved describing an idea and having someone skilled make it real. Vibe design follows the same principle, except the “someone” is AI, ready whenever you are, no brief needed. You describe what you want through text, images, brand assets, or sketches, and the AI generates the design. You direct the process; the tool handles the making.

The term itself is not new but was brought into mainstream use in early 2026 by Google via their Stitch announcement, and within a day it was appearing across The Register, CNBC, and TechRadar. The practice it describes had been building for well over a year, in Figma’s AI features, in generative design tools, in the growing number of products letting users create from a prompt rather than from a toolbox.

Today, we’ll define what vibe design actually is, traces where the idea came from, and explains what it means for people building products.

Where the Term Comes From: Vibe Coding’s Design Sibling

To understand vibe design, it helps to start with the concept it’s directly descended from: vibe coding.

Former Director of AI at Tesla and co-founder of OpenAI, Andrej Karpathy coined “vibe coding” in early 2025 to describe a shift in how developers work with AI-generated code. The idea: instead of writing implementation yourself, you describe what you want in natural language and an AI writes the code. The developer’s role shifts from implementation to direction. You stop thinking about how things are built and focus entirely on what you want to create.

Vibe design is the same shift applied to visual creation. Instead of opening a design tool and manually placing elements, adjusting colors, choosing fonts and spacing, you describe what you want (in words, or by uploading a reference image, a photo, a sketch, a brand kit), and the design takes shape. The phrase “vibe coding design” captures this lineage neatly: it’s the same intent-first principle, moved from engineering into the visual layer.

The underlying movement had been gathering momentum since AI image generators went mainstream, accelerating rapidly as tools like Figma Make, Lovart, and now Google Stitch brought the concept directly into design workflows. The label arrived late to a trend that had already changed how a lot of creative work gets done.

What Vibe Design Actually Means: A Working Definition

Here is a working definition that holds up across tools and use cases:

Vibe design is a creative workflow in which the primary input is intent (described in natural language or visual references) rather than manual manipulation of design tools. The designer’s role becomes one of direction, curation, and refinement rather than construction.

Three things define a genuine vibe design workflow:

1. Intent-first input. The starting point is a brief, a description, a reference image, or a combination, not a blank canvas and a toolbox. You’re communicating what you want, not building it.

2. Generative execution. An AI interprets that intent and produces a designed output: a layout, a color scheme, a complete page, a set of variations. The construction step is handled by the system.

3. Human refinement in the loop. The human stays involved throughout, approving directions, adjusting outputs, steering away from things that don’t work. The AI handles execution; the human handles judgment.

What vibe design is not: it’s not simply using an AI image generator to produce pictures. Image generation is one possible input into a vibe design workflow, not the workflow itself. Vibe design produces editable, structured design outputs (layouts, components, documents, campaigns), not static images. The output is something you can work with, not just something you can look at.

How It Differs from AI-Assisted Design

“AI-assisted design” has covered a lot of ground over the past few years: autocomplete for design tokens, background removal, content generation within a layout. These are useful additions to a manual workflow. But in all of them, the designer still drives. AI is a tool called on for specific tasks while the human remains in the seat.

Vibe design flips the ratio. The AI drives the initial creation; the human steers and refines. It’s a different relationship with the tool, not a faster version of the same one.

The distinction matters because it changes three things:

What skills are most useful. Writing clear, directed prompts and making fast curatorial judgments matters more than knowing every keyboard shortcut.
What the workflow looks like. You’re reviewing and steering outputs rather than constructing from scratch.
What software is relevant. Vibe design tools are built around a different interaction model than tools built to accelerate traditional manual design.

Vibe Design in Practice: Three Scenarios

The best way to make this concrete is to show what an AI design workflow built around vibe design actually looks like. These three scenarios cover the range of contexts where it’s becoming relevant.

Scenario 1: A Marketing Team, No Designer Available

A marketing manager at a mid-sized e-commerce brand needs a product launch campaign for social media. There’s no designer available this week. They’re tied up on a bigger project.

She opens the creative tool embedded in their marketing platform, uploads the product photo and the brand guidelines, and types: “Create a campaign for our summer collection, clean, minimal, white space heavy, headline-driven.”

She receives a set of formatted, brand-consistent assets sized for each social channel. The layouts are on-brand. The typography follows the guidelines she uploaded. She adjusts the headline copy on two of the assets and swaps one background color. The whole thing takes 12 minutes.

No design skills required. No third-party tool. No waiting for a designer to become available. The campaign goes out on schedule.

Scenario 2: A Designer Exploring Variations

A senior designer is working on a brand campaign for a luxury lifestyle client. She’s settled on a layout she likes, but she can’t land on the right color direction. Everything she’s tried manually feels either too cold or too safe, and exporting variations to compare them side by side is eating time she doesn’t have.

Instead, she types a single instruction into the agent chat: “Add a panel on the left with five color theme presets I can click to instantly apply to my design.”

The agent builds the panel directly inside the editor. Five named presets (Warm Sand, Midnight, Rose Quartz, Forest, Slate Blue), each applying a complete color theme across the entire design in one click: backgrounds, accents, headings, body text, all updated together. She works through all five in under a minute and finds the direction she was looking for without typing another prompt.

The variation-exploration workflow, at its most useful, doesn’t just produce more outputs; it builds the tools you need to make the decision faster.

Scenario 3: A Product Team Embedding Creative Capability

A print-on-demand platform serves retailers and small brands who need to produce product catalogues regularly but don’t have in-house design resource. One of their customers (a retailer for a furniture brand) opens the editor, pastes a CSV of five products into the agent chat, and describes the layout style she wants: two-column landscape, typography-led, minimal, referencing the aesthetic of Hay, Muuto, and Frama.

The agent generates a complete five-page catalogue inside the editor, one page per product, consistent layout throughout, with product names, descriptions, prices, and photo placeholders already in place. She follows up in plain language: “Pre-fill the photo placeholders with elegant product photography, make them black and white, soft contrast.” The agent updates all five pages. She adjusts one headline manually and exports.

The Vibe Design Tools Shaping the Space Right Now

Several tools are explicitly built around this workflow.

Tool	What it does	Where the agent lives	Best for
Google Stitch	Voice and text prompts to UI design	Google’s standalone tool	UI/UX designers, developers
Figma Make	Prompt to prototype inside Figma	Inside Figma (standalone)	Product designers working in Figma
Lovart	AI design agent for graphic creation	Lovart’s standalone platform	Marketing creatives, solo designers
IMG.LY	Design companion for all types of design works and tasks	IMG.LY Codesign studio	Designers, marketers, brand owners

Google Stitch is built around the idea that UI design should start with a conversation. You describe a screen (its purpose, the actions it needs to support, the general feel), and Stitch produces an interface design you can refine. It’s aimed at developers and UI/UX designers who want to move faster in the early stages of building a product interface. Where it works well is in getting from a rough idea to a structured screen layout without having to make every decision from scratch.

Figma Make extends the environment that product designers already work in. Because it lives inside Figma, it has access to your existing components, tokens, and design system. The prompt-to-prototype workflow is useful for designers who want to explore how a brief might translate into a working layout without manually composing every frame. Its biggest advantage is that the output lands directly in a space where a full design team can take over.

Lovart is focused on graphic and campaign creation rather than UI or product design. It’s built for the kind of work that marketing creatives and solo designers do a lot of, producing visual assets for social, campaigns, brand activations. The emphasis is on speed and aesthetic quality for graphic outputs rather than on structured, component-based design systems.

IMG.LY brings a design companion together with manual canvas edits - each element created by AI can be manually moved, changed, or adapted. It maintains brand and template context throughout the generation process, redefining the meaning of templates - from simple asset with placeholders, to true brand guideliness. Excels at number of import and export options, making a great options for true graphic and asset designs.

Where Vibe Design Has Limits

Vibe design works well when there’s something to work from, like a reference image, a brand kit, or an existing visual direction. When there’s genuinely nothing to draw from, outputs tend toward the generic. A completely new brand identity with no existing visual language is a poor fit for a vibe design workflow; that kind of work still benefits from the deliberate, decision-by-decision process of traditional design.

It’s also less suited to accessibility-critical UI, where precise specification (contrast ratios, touch targets, interaction states) matters more than mood or aesthetic direction. A generated layout might look right without being accessible, and catching that requires careful manual review.

Finally, the more technically constrained the brief, the more refinement the output will need. Vibe design compresses the path to a starting point; it doesn’t always compress the path to a final, production-ready output. Teams that go in expecting to iterate will get more out of it than teams that expect to export and ship.

The Human Element: Vibe Design Is Not Autonomous Design

A common concern about vibe design workflows is that they reduce the role of skill and judgment in creative work. The evidence so far points the other way.

The most effective workflows keep the human firmly in control of direction, curation, and final judgment. The AI generates; the human decides what’s good, what fits the brief, what needs to change. Removing that layer doesn’t improve outcomes; it just produces more output with no quality filter.

What changes is not whether human judgment matters, but at which stage it matters most. In a traditional design workflow, judgment is exercised continuously, at every click, every color choice, every alignment decision. In a vibe design workflow, judgment operates at a higher level: Is this the right direction? Does this match the intent? What needs to change?

The craft is still there. The instruments are different.

A Shift That’s Already Underway

Vibe design isn’t a trend arriving from the future. It’s a name for a shift that’s been building for several years and just became visible enough to label properly.

The creative AI tools exist. The workflows are being adopted. The user expectation is forming. Naming the practice in 2026 didn’t create the movement; it just gave it a shared vocabulary that makes it easier to talk about and build toward.

If what you’re looking for is a balance between manual control of the output and power of AI generation, IMG.LY Codesign might be the right fit for you. Talk to our team to see how it can fit inside your stack.

Make Your Docs Agent-Ready: Compiling MDX into Markdown

Mirko — Wed, 11 Mar 2026 14:38:44 GMT

TL;DR: The 7x Efficiency Gain

We rebuilt our documentation pipeline to treat AI agents as a first-class audience. By natively compiling MDX into clean, fully-resolved Markdown (rather than heavy HTML or unresolved source code), agents and LLMs can now ingest our docs 7x faster and with far higher accuracy.

Test it yourself:
Request our docs with the Markdown accept header to see the agent-optimized view:

curl -s -H "Accept: text/markdown" https://img.ly/docs/cesdk/js/settings-970c98/

The Documentation Mismatch: Humans vs. Agents

If you build developer tools today, you have two distinct audiences: human engineers and the AI agents they use to write code. Recently, we realized we were treating them exactly the same.

Our docs pipeline is built on MDX and optimized for the browser. But when an LLM tries to ingest a page, it has to wade through navigation chrome, layout wrappers, and raw JSX. We didn’t just need a “clean text” mode; we needed a fundamentally different architecture.

Humans vs. Agents: A Comparative Overview

Feature	Humans (Browser)	Agents (Context Window)
Primary Format	HTML + CSS + JS	Clean Markdown
Navigation	Visual UI (Sidebar/Tabs)	Explicit links + hierarchy
Context	Implicit (Site layout)	Explicit (Frontmatter + headers)
Constraints	Performance / Core Web Vitals	Token / Context Window budgets
Payload Size	~222 KB	~31 KB (7x smaller)

The Problem: Why HTML and Raw MDX Fail Agents

1. HTML is expensive “Chrome”

A documentation site is an application. Even static sites ship navigation chrome, scripts, and styling hooks. For AI, this is “token noise.” You are paying for bytes that provide zero value to the LLM and forcing the agent to reconstruct a hierarchy that you already had at authoring time.

2. Raw MDX is unresolved source code

Serving raw MDX files doesn’t solve the problem either. MDX is for maintainers. It is full of imports and unresolved dependencies. Our documentation often pulls code from external, tested repositories:

## Initialize the Engine
<CodeBlock file="examples/getting-started/src/index.ts" lines="12-24" />

In the browser, this renders beautifully. In raw MDX, it’s a pointer to a file the agent cannot see. The actual code isn’t there.

The Solution: Treat Markdown as a Compilation Target

We stopped thinking about this as “exporting text” and started treating it as what it really is: a second build target.

Old Pipeline: MDX (Source) → HTML (Browser View)
New Pipeline: MDX (Source) → HTML AND MDX (Source) → Markdown (Agent View)

Why we didn’t just “convert” HTML

We tried rendering to HTML and then running a converter. It failed at code blocks. Syntax highlighting adds spans and wrappers around tokens; reversing that into clean, trustworthy code is nearly impossible.

<pre><code class="language-js">
  <span class="token keyword">const</span>
  <span class="token variable">engine</span>
  ...
</code></pre>

By working at the AST (Abstract Syntax Tree) level before rendering, we avoid this entirely.

Implementation: Transforming MDX at the AST Level

Rather than trying to reconstruct meaning from rendered markup, we preserve it directly. We built a remark plugin that transforms MDX at the MDAST level.

import { remark } from 'remark';
import remarkMdx from 'remark-mdx';
import remarkStringify from 'remark-stringify';
import { remarkTransformForExport } from './remarkTransformForExport';

const processor = remark()
  .use(remarkMdx) // Parse MDX/JSX nodes
  .use(remarkTransformForExport, {
    baseUrl: '[https://img.ly/docs/cesdk/](https://img.ly/docs/cesdk/)',
    paths: resolvedPathMap,
  })
  .use(remarkStringify); // Back to markdown

const markdown = await processor.process(mdxContent);

The Component Contract

Every MDX component must define how it exports to the agent view. We colocate the transform directly with the component: Aside.astro (Human UI) ↔ Aside.toMarkdown.ts (Agent logic).

Example: Aside Component → Blockquote

Input: <Aside title="Pro Tip">Use the basePath...</Aside>
Output: > **Pro Tip:** Use the basePath...

Example: Resolving Code References This is the most critical transform. Instead of a file pointer, the agent gets the actual, inlined code block fetched during the build process.

When you strip the sidebar and footer, you lose context. We reintroduce “navigational chrome” as text-native primitives at the top and bottom of every Markdown file:

---
title: 'Working with Filters'
platform: 'react'
url: '[https://docs.example.com/react/guides/filters/](https://docs.example.com/react/guides/filters/)'
---

> You’re reading the React docs. For the full corpus, see llms-full.txt.

## **Path:** [Home](https://docs.example.com/) > [Guides](https://docs.example.com/guides/)

[Self-contained Page Content]

---

## Continue Reading

- [Color Adjustments](https://docs.example.com/react/guides/color-adjustments/)
- [API Reference](https://docs.example.com/api/)

Lessons for Scaling Agentic DX

If you maintain docs at scale, “optimizing for bots” is no longer optional. It is the new standard for Developer Experience (DX).

Don’t serve HTML and hope: Reverse-engineering structure is hard for AI. Give it the structure directly.
Every component needs an identity: If a component carries meaning, it needs a Markdown equivalent. If it’s just layout, unwrap it.
Resolve everything: Assume zero ambient context. Links must be absolute, and code must be inlined.
Content Negotiation: Use the Accept: text/markdown header. It is becoming the industry standard for tools like Claude Code and OpenCode.
The Single-File Corpus: In addition to per-page files, generate a llms-full.txt that concatenates everything. Some agents prefer one large fetch over a crawl.

By acknowledging that AI agents are a primary consumer of our documentation, we’ve made our SDK significantly easier to integrate. The future of docs isn’t just “readable”. It’s “storable and traversable.”

Note: We built this for CE.SDK. The implementation uses Astro and Vercel, but the approach is framework-agnostic.

CE.SDK v1.70 Release Notes

Neslihan — Tue, 10 Mar 2026 16:08:17 GMT

Fresh off v1.69 (our biggest developer experience release yet), v1.70 now strengthens what’s already there. The Android video timeline gets a professional-grade overhaul, iOS and Android gain video duration controls. Under the hood, significant stability improvements across every platform.

Let’s dive in!

Edit Videos with Clarity on Android

These updates to the Android video timeline improve how editing looks and feels for your mobile users.

Use Real Audio Waveforms for Accurate Video Editing

Audio clips now display actual waveform visualization, replacing the previous placeholder. Users can see exactly where audio peaks and drops, making precise edits faster and more intuitive.

→ Explore Audio Waveform Docs

Keep Your Timeline Clutter-Free

Images, stickers, and shapes now display one thumbnail per clip, instead of repeating across the track. The timeline is cleaner and easier to read, keeping complex video compositions tidy on mobile screens.

Keep Text Visible Throughout Your Timeline

Text clips now show their actual text content alongside the clip label, so users can identify and navigate text layers without opening each one.

Improvements

Set Video Duration Limits on iOS and Android
You can now define minimum and maximum video duration constraints directly in CE.SDK on both iOS and Android.

Timeline markers make the boundaries visible to users while they edit, and export validation ensures clips meet the defined limits before rendering.

Edit Colors like a Pro – in One Panel

The color panel for web is now unified: preview, saved colors, and custom editing controls all live in one place. Users can pick, adjust, and reuse colors in a single continuous workflow, without a separate modal or extra clicks.

CMYK Color Mode for Web
Additionally, the web editor supports restricting the color picker to a specific color mode: RGB, CMYK. When CMYK is enforced, elements using a different color mode show a clear convert option rather than broken inputs.
New pages, asset library blocks, and fill type switches automatically convert colors to match the configured mode.

Full Changelog

All technical details, breaking changes, and migration notes are in the v1.70.0 Changelog.

Thank you for building with IMG.LY.

CE.SDK v1.69 Release Notes

Neslihan — Fri, 27 Feb 2026 18:29:53 GMT

v1.69 is the biggest developer experience release we’ve shipped. Agent Skills collapse the time from idea to working editor from days to under a minute. Production-ready Starter Kits eliminate days of boilerplate setup. PPTX and Canva Importer lets users bring their existing designs directly into your editor. And a comprehensive video overhaul across Web, iOS, and Android closes the gap between CE.SDK and native professional editing apps.

Let’s dive in!

Introducing IMG.LY Agent Skills for CE.SDK

The biggest change to CE.SDK’s developer experience since launch.

AI agents have changed how developers build. With Agent Skills, CE.SDK works natively with your AI agent.

Install the plugin for Claude Code or Cursor and your AI coding agent becomes a CE.SDK expert with bundled access to guides, API references, and starter kits across 10 web frameworks. No external services, no MCP servers, no context-switching.

What your developers can now do:

/cesdk:build — Describe a use case in plain language. The agent detects the framework, pulls the right starter kit, and scaffolds a working project autonomously.
/cesdk:explain — Ask any CE.SDK implementation question and get answers adapted to the specific framework and experience level.
/cesdk:docs-[framework] — Retrieve guides and API references directly from the IDE, without leaving the editor.

For your product, this means: developers prototype in minutes, not days. Non-technical team members can now build and extend functional editors independently. And onboarding new engineers to CE.SDK shrinks from a multi-day ramp to a single session.

→ Quick Start & Full Announcement
→ Explore Agent Skills Documentation

Launch in Minutes with Production-Ready Starter Kits for Web

Previously, getting CE.SDK running in a real product meant adapting complex demo projects: stripping features, adjusting architecture, and undoing assumptions baked into example code.

Starter Kits replace all of that with pre-configured, production-ready editor UIs.

Specialized kits for Photo, Video, and Design editors are scoped, clean, and immediately deployable. Each kit starts with a focused feature set. You explicitly opt in to what you need, so your UI stays performant and your users don’t see capabilities they can’t use.

For your product, this means: a functional, shippable editor in minutes rather than days of setup. Clean architecture from day one, without accumulating technical debt.

→ Explore Starter Kit Documentation

Let Users Bring Their PPTX & Canva Designs to CE.SDK

Some customers don’t start from scratch. They have existing creative assets locked inside PowerPoint and Canva, and until now, bringing those into CE.SDK required manual recreation.

The new PPTX Importer removes that barrier.

Users can import native PowerPoint files or export Canva designs as PPTX and bring them directly into your CE.SDK-powered editor, with layouts, elements, and structure intact.

→ Try the PPTX Import Demo
→ View PPTX npm

Professional-Grade Video Editing Across Platforms

This release expands CE.SDK’s video features across web & mobile platforms.

Control Video Speed (iOS & Android)

Users can now adjust the playback speed of video and audio clips via a dedicated Speed UI. This has been one of the most-requested mobile features and is now available on both platforms.
→ View Video Speed Documentation iOS
→ View Video Speed Documentation Android

Create Video Groups in the Timeline (Web)

Multiple clips can now be combined into a single manageable unit with synchronized timing, trimming, and a unified timeline representation.

This enables complex, multi-layer content production and speeds up the design process.

Video Timeline Now Grows Automatically (Web)

The timeline now automatically adjusts its height based on content. Manual track configuration is gone, and complex projects are easier to pick up for your new users.

Use a Clutter-Free iOS Timeline (iOS)

Non-video tracks now show a single thumbnail per clip, reducing clutter in multi-layer timelines on your iOS app.

Full Changelog

See all technical details, breaking changes, and performance improvements in the v1.69.0 Changelog.

Thank you for building with IMG.LY.