Hello,

I am using CoffeeCup Responsive Email Designer and encountered an issue with the HTML export.

When I add images as "Local Images" in my project and export the email to HTML, the exported code does not use the local image folder (for example "images/filename.jpg"). Instead, the export automatically generates image URLs like:

http://webop.coffeecup.com/storage/emails/...

These URLs are not accessible outside the CoffeeCup environment, so the images are not displayed when the exported HTML is used elsewhere.

Expected behavior:
When exporting an email project, images that were added as local files should either:
- be exported to an "images" folder and referenced with relative paths, or
- allow the user to define a base path for images during export.

Actual behavior:
The export always replaces the paths with CoffeeCup storage URLs.

The only workaround I found was to switch all images to "Online Images" and host them manually.

Is this intended behavior or a bug?
Is there a way to export HTML with local images and correct relative paths?

Thanks in advance.

Software: CC Email Designer
OS: macOS
Version: 5.0 Build 1999

I think this is a question best answered by the CoffeeCup team, and this forum is primarily for users of the software to help each other.

You've set out the matter very clearly, and I suggest you copy it to the CoffeeCup team using Your Support Room ( https://www.coffeecup.com/help/myroom/ ).

Frank

I believe this is intended behavior rather than a bug. Email clients generally cannot access local files, so images usually need to be hosted online and referenced with publicly accessible URLs.

If CoffeeCup is replacing local image paths with its own storage URLs during export, it may be assuming that the email will be sent through its publishing workflow. For standalone HTML exports, you may need to host the images yourself and use the "Online Images" option, as you've already discovered.

That said, it would be useful if the software provided an option to export local images into an images folder with relative paths for testing and archiving purposes. Hopefully someone from the CoffeeCup team can confirm whether such a feature exists or is planned.