Email render address for device previews before send

An email render address gives teams a simple way to start a device preview: send the email to a MailSlurp address and review how it renders across clients and devices.

This is useful because the best preview is often the final email from the real sending tool. If your ESP, mailbox, app, or QA environment can send a test email, it can send to a render address.

MailSlurp supports render addresses under emailondevice.com so teams can trigger previews without changing the tool that creates the message.

Quick answer

Use an email render address when:

campaign teams send test emails from an ESP
designers need a quick preview from an email client
QA wants to render a staging email
reviewers need a shareable result link
the same target matrix should run repeatedly
sending is easier than exporting .eml files

For a quick first run, use Free email render. For team workflows, use device previews with named render profiles.

How a render address works

A MailSlurp render address can look like this:

marketing@acme.emailondevice.com

The local part can represent a profile, such as marketing, qa, or all. The subdomain belongs to the account. The domain is the MailSlurp render domain.

When a team sends an email to the address, MailSlurp receives the message and starts a device preview run using the configured target set.

That makes the address easy to share with marketers, QA engineers, and release owners. They do not need to know the API path or copy HTML into another tool; they only need to send the final email to the right address.

Why render addresses fit campaign workflows

Campaign teams already know how to send test emails. A render address keeps that workflow intact.

Instead of asking reviewers to copy HTML, inspect screenshots, or manually rebuild a preview, the team can:

Open the campaign in the ESP.
Send a test to the MailSlurp render address.
Wait for the device preview result.
Review Gmail, Outlook, mobile, desktop, light mode, and dark mode.
Share the result link with the launch owner.

That keeps preview review close to the real campaign output.

Profiles for different review needs

Profiles help teams keep routine checks simple.

For example:

marketing@... can run campaign-focused render targets.
qa@... can run product-email render targets.
mobile@... can focus on phone-sized views.
all@... can run the broadest review before a major launch.

Named profiles reduce manual setup and make it easier for different teams to use the same process.

They also make review intent explicit. A mobile profile can stay fast for routine checks, while an all profile can cover the broader launch matrix before a major send.

What to check after sending

When the render is ready, inspect:

first screen and CTA
desktop and mobile layout
Gmail and Outlook differences
image loading and fallback text
dark mode and light mode behavior
footer and unsubscribe content
links and tracking destinations

Pair the render result with email audit and inbox placement testing when campaign links, images, authentication, and placement also matter.

FAQ

What is an email render address?

An email render address is an address that starts a device preview when you send an email to it.

Can I use a render address from my ESP?

Yes. If the ESP can send a test email to an address, it can send to a MailSlurp render address.

Can different teams use different render profiles?

Yes. MailSlurp profiles let teams map local parts, such as marketing or qa, to different preview target sets.

Where should I start?

Use Free email render to try the send-to-render workflow, then create a MailSlurp account for named profiles and repeatable device previews.

Email Render Address: Send Campaigns to Device Previews