Asset Library Basics: Images for Email Templates
A short practical guide to uploading and reusing images in the email app's asset library — the storage behind every image you drop into a template.
Every image you use in an email template — a logo, a product photo, a banner — comes from the same place: the app's asset library, backed by shared bucket storage rather than a per-template upload with no memory of what you've already added.
Uploading an image
Images go in through the app's upload endpoint, and from there they're listed and retrievable through the library's list and fetch routes. In practice you'll rarely touch these routes directly — the Studio's asset picker calls them for you when you're inserting or swapping an image inside a template — but it's useful to know that what you're building is a real, persistent library, not a one-off attachment tied to a single template.
Reusing images across templates
Because uploads land in one shared library, an image you add while building one template shows up as an option the next time you're picking an image anywhere else in the app. If your business has a standard logo, a consistent header banner, or a handful of product photos you use across several campaigns, upload them once and reuse them from the picker every time afterward, rather than re-uploading the same file into each template you build.
What belongs in the library
Logos, product photography, banners, and any other image content you expect to reuse across more than one email are the clearest fit. For a genuinely one-off image tied to a single campaign you'll never repeat, uploading it still works the same way — there's no separate "temporary" upload path — but it's worth a light mental note that your library will accumulate images over time, so giving files sensible names before upload makes them easier to find later, rather than scrolling through a list of generic filenames months on.
Keeping the library manageable
A library that grows without any pruning eventually makes the picker slower to search through. A reasonable habit is a periodic pass — every quarter, or whenever you're doing a broader template refresh — to check for images that were uploaded for a campaign that's long since ended and are unlikely to be reused, and clear those out. This isn't urgent maintenance, but it's the kind of small housekeeping that's much easier to do a little at a time than all at once after the library has grown into hundreds of unlabeled images.
Starting point
If you're setting up the email app for the first time, upload your core brand assets — logo and any standard header or footer imagery — before you start building templates. Having them in the library from the start means every template you build afterward can pull from the same consistent set, instead of each one accumulating its own slightly different upload.