How to Preview Omnisend Emails in Gmail, Outlook, iPhone, and Android
Preview an Omnisend test email in Gmail, Outlook and phone apps with MailSlurp. Learn when personalization and image checks need a controlled campaign send.
Use with your tools
An Omnisend product email needs to keep its images, prices and shop button readable after it leaves the editor. A desktop or mobile preview helps while designing, but Gmail, Outlook and the phone apps your shoppers use can display the delivered email differently.
Checking each revision by hand means opening it in those apps and collecting another set of screenshots. MailSlurp is an email testing platform with automated device previews that brings the selected client captures together, so reviewers can compare the same message before the campaign goes out.
How automated device rendering works
Choose the devices and email services you want to test, and MailSlurp gives you a special email address. Send your campaign to that address. MailSlurp opens the email in the selected apps and webmail services, then captures screenshots automatically.
The screenshots come back together, ready to compare across phones, tablets and computers. Check the layout, images and buttons, then share a result link so your team can review the same version of the email.
Quick answer
To test an Omnisend email across clients and devices:
- Open Device Previews in MailSlurp and create a render.
- Select the Gmail, Outlook, Apple Mail, iPhone, Android, and dark-mode targets that matter to your audience.
- Choose Use selected and copy the complete MailSlurp render address.
- In Omnisend, open the campaign editor and choose Preview & test > Send test email.
- Enter the render address and choose Send.
- Return to MailSlurp, open the waiting view with I have sent my email, and wait until every selected target is Ready.
- Compare the screenshots and correct the campaign before launch.
This tests the message Omnisend sends in test mode. For recipient-specific content and campaign image delivery, use a controlled campaign send as described below.
Before you begin
Save the campaign revision you want to review. You'll also need device previews available in your MailSlurp workspace and enough preview credits for the selected clients.
Omnisend's Dynamic Preview checks contact values inside the editor. An ordinary test email does not include real contact or event data: personalization uses its fallback or appears empty. Selecting a contact in Dynamic Preview does not turn the test email into a personalized campaign send.
How the Omnisend test path works
Use Send test email for the initial layout check. When approval depends on populated product recommendations, discount codes or other dynamic content, send the campaign to a segment containing only your controlled test contacts. For an automation, use the corresponding test event and restrict the workflow to those contacts.
Omnisend's preview and testing instructions explain both paths. Review the segment's actual membership before a regular send; the screenshots here follow the editor's test-email path.
For an event-populated example, follow the Omnisend abandoned-checkout test. It traces a two-product Shopify checkout into an actual automation email, then compares its phone and Outlook captures and checks the received recovery link.
Step 1: Create a MailSlurp device preview
Open the new device preview form. Expand the target selector and choose the apps your shoppers use. Gmail.com is the browser target; Gmail Android and Gmail iOS check the phone apps. Add the relevant Outlook and Apple Mail targets, with light and dark variants where available.
Check the selected-target count and make sure a saved profile has not added unwanted clients. Then choose Use selected and copy the complete address under Send your email to this address. Copy it after choosing your targets, and use the address from your own workspace.
Step 2: Prepare the final Omnisend message
Open the campaign you intend to send and save the subject, preview text, body, images, links and footer. Use Dynamic Preview for the contact or event data described above.
The example shown in Omnisend below is a coffee promotion with a large product image, a sale heading and a shop button. The image and heading should remain visible, and the button should be easy to find on a phone. Your own test should include the finished content rather than an empty template.
Step 3: Send the Omnisend test email
In Omnisend, open the campaign editor and choose Preview & test > Send test email. Then enter the render address and choose Send. Use only the active MailSlurp render address for this device-preview run.
Wait for Omnisend to confirm acceptance, then check receipt in MailSlurp. Omnisend adds a preview marker to the test subject; use the campaign name to identify the matching message.
Step 4: Wait for every client to finish
Return to MailSlurp and choose I have sent my email to open the waiting view. Receipt starts the render automatically. When the matching message shows RUN CREATED, choose View results and wait until every required target displays Ready.
If a target reports a capture failure, inspect that target's status and use its retry action where available. Keep the completed captures, and check the existing receipt and run before sending another copy.
Step 5: Inspect the delivered renders
Open the highest-risk screenshots at full size and compare clients when needed. Check:
- headline wrapping, body width, and reading order
- mobile stacking and horizontal overflow
- hosted image loading, cropping, dimensions, and alternative text
- button contrast, width, spacing, and tap area
- font fallbacks and line-height changes
- Outlook Classic spacing and table alignment
- light- and dark-mode contrast
- footer, physical address, unsubscribe, and preference links
For Gmail, compare the selected browser and phone apps separately. The Gmail preview guide explains how those targets differ and how to inspect a light/dark comparison; a completed browser result does not cover Gmail on a phone.
Omnisend's image-display guidance notes that editor tests use temporary image links that can fail in Gmail or Outlook web. If a product image is absent, repeat the check with a controlled campaign send before concluding that the design itself is broken. Keep that result separate from the editor test so you can tell which sending path produced it.
If one client breaks, correct the Omnisend campaign and send the revised message to a new MailSlurp render run so the approval evidence clearly belongs to the latest version.
Omnisend email preview checklist
- The latest saved Omnisend revision was sent.
- The subject, preview text and content match the saved revision.
- Personalized or event-based content was checked through the appropriate contact or event path.
- Every priority web, desktop, mobile, and dark-mode target is Ready.
- Images load and scale without clipping.
- Buttons remain readable and easy to tap.
- Outlook Classic preserves the intended hierarchy.
- Footer and unsubscribe content are visible.
- The run was repeated after the last material edit.
Troubleshooting
MailSlurp does not detect the email
Copy the active render address again, confirm Omnisend accepted the send, and make sure the address was not shortened or changed.
Personalization is blank
An editor test has no real contact or event data. Check the values in Dynamic Preview, then use a controlled campaign or automation send when you need those values in the delivered email. Repeating the same editor test will not populate them.
An image is missing in one client
First check whether this was an editor test using temporary image links. Compare a controlled campaign send in the same client. If it still fails, check the delivered image URL, public access, dimensions and alt text before editing the layout.
Outlook spacing differs from Gmail
Outlook Classic uses a different rendering engine from many web and mobile clients. Use email-safe table structure where needed, set explicit image dimensions, and rerun each correction.
FAQ
How do I preview an Omnisend email in Gmail and Outlook?
Create a MailSlurp device preview, copy its render address, and send the final Omnisend test email to that address. MailSlurp captures the delivered message in the selected Gmail and Outlook targets.
Can I preview Omnisend emails on iPhone and Android?
Yes. Include iOS Mail, Gmail iOS, Outlook iOS, Gmail Android, and Outlook Android in the MailSlurp target set.
Does the Omnisend editor preview replace email client testing?
The editor is useful while composing. MailSlurp adds client-specific screenshots of the delivered message so reviewers can see rendering differences outside the editor canvas.
When should I rerun the preview?
Rerun after changing copy, contact data, images, links, layout, sender details, footer content, or campaign settings. Approve only the latest delivered version.
After visual approval, continue with the Omnisend inbox placement and spam score guide to measure where the campaign lands.