Managed Image Layer for Email
Mark Robbins, software engineer at Customer.io, on the email coding stack
The real opening is to turn email images from static files into a managed asset layer. In email, CSS image tricks often break across Outlook, Gmail, and other clients, so the safer move is to crop, resize, compress, and version the image before it ever enters the template. That pushes more of the creative workflow into infrastructure, and makes the email builder stickier because design, QA, and delivery start from the same source asset.
-
Parcel and Customer.io were already moving toward a shared creation stack, where components update every future message from one central system. An image CDN fits that same logic. Change the asset once, then every email using it ships the latest size, crop, and brand treatment without hand editing templates.
-
Cloudinary is the clearest product model. It lets teams deliver assets through URL based transformations and a CDN, so one original file can produce many email safe versions on demand. That matters in email because reliability comes from preparing the image before send, not from hoping each client renders CSS the same way.
-
This also expands Parcel beyond coding into content operations. The same component system that can output HTML, AMP, text, landing pages, SMS links, and WhatsApp flows from one source can also pull from one managed image layer, giving marketers and developers a single production pipeline instead of scattered files and manual exports.
The next step is message creation software absorbing more of the media stack. The winner will not just help teams write email code, it will host assets, transform them for each channel, and keep every downstream message on brand from one system, which turns a narrow email editor into a broader cross channel content engine.