Help Center
How can we help? πŸ‘‹

Image Hosting

The Email Love Figma Plugin automatically hosts your email images on our CDN when you export your designs. This feature saves you time by eliminating the need to manually upload images to your email service provider.

Β 

How Image Hosting Works

When you export an email from the plugin, your images are automatically uploaded to Email Love's servers and served through our global CDN (Content Delivery Network).

Export Process

  1. Select your email frame in Figma
  1. Click the Export button
  1. Choose your email platform (e.g., Braze, HubSpot, Klaviyo)
  1. Ensure the "Upload images to Email Love servers" option is enabled (this is the default setting)
  1. Export your email

Your images will now be hosted on Email Love's CDN and referenced in your exported code.

Image Optimization

When you use Email Love's image hosting, we automatically:

  • Serve images globally: Our CDN delivers images quickly across different countries
  • Apply light compression: We compress images while retaining quality to ensure fast download times in email clients
  • Optimize delivery: Images are optimized for email client compatibility and performance

Understanding Image Access

Important limitations:

  • There is no centralized repository where you can browse all your hosted images
  • Images remain visible in your Figma files
  • This differs from traditional email builders or ESP image libraries where you can browse uploaded assets

Export Methods and Image Hosting

ESP Integrations (Braze, HubSpot, Klaviyo, etc.)

When exporting directly to an ESP integration, images are automatically hosted on Email Love servers by default. You'll see URLs in your code that look like this:

https://emaillove-assets-cdn.com/...

HTML or MJML Download

When downloading HTML or copying code:

  • By default: Images export as a zip file that you'll need to upload manually
  • With image hosting enabled: Check the "Upload images to Email Love servers" box to have images automatically hosted

Special Case: Loops Integration

The Loops integration works differently:

  • Images must be exported as a zip file alongside the MJML code
  • When you upload the folder to Loops, images are hosted on Loops' servers instead of Email Love's servers
  • This is a Loops-specific requirement

Identifying Hosted Images in Your Code

You can verify that images are hosted on Email Love's CDN by looking at the image URLs in your exported code:

html

<img src="https://emaillove-assets-cdn.com/[unique-id]/image.png" />

If you see emaillove-assets-cdn.com in the URL, the image is hosted on our servers.

Benefits of Using Email Love Image Hosting

  • Saves time: No need to manually upload images to your ESP
  • Global performance: Fast image delivery worldwide through our CDN
  • Automatic optimization: Images are compressed and optimized for email
  • Simplified workflow: Export and send without extra steps
  • Scalable: We host thousands of images every month

Best Practices

  • Keep image hosting enabled for the fastest workflow
  • Use this feature for all email exports unless your ESP requires otherwise (like Loops)
  • Remember that once hosted, images don't appear in a browsable library
  • If you need to reference a specific hosted image, you can find the URL in your exported code
Did this answer your question?
😞
😐
🀩