How to Test Emails: Preview, Litmus, and Email on Acid Alternatives

Published July 11, 2026

The email that looked perfect — until it didn’t

You designed a beautiful email. You previewed it in the builder. It looked great. You sent it to your list — and then the complaints roll in. The button doesn’t work in Outlook. The hero image is cut off in Gmail. The text overlaps on older Android clients. The layout that looked flawless on your screen is broken for a chunk of your audience.

This is the central truth of email: what you see in your editor is not what your readers see. Email clients render HTML differently, images load or don’t, dark mode inverts colors unpredictably, and mobile clients resize everything. Testing is how you close that gap — catching rendering problems before they reach your list, not after.

What email testing actually is

Email testing is the process of checking how your email renders across the many environments your readers use — different email clients (Gmail, Outlook, Apple Mail, Yahoo), different devices (desktop, mobile, tablet), different operating systems (Windows, macOS, iOS, Android), and different modes (light and dark mode).

It has several layers:

1. Preview testing. Looking at the email in your builder’s desktop and mobile preview. Fast, but limited to the builder’s rendering engine.
2. Inbox testing. Sending a copy to your own email accounts across multiple clients and devices. More realistic, but limited to the accounts you have.
3. Rendering testing. Using a service that screenshots your email across dozens of client/device combinations simultaneously. The most thorough approach, and what tools like Litmus and Email on Acid are built for.
4. Dark mode testing. Checking specifically how the email looks when the client inverts colors — a surprisingly common source of broken designs. See Dark Mode Email Design.

Why it matters

• Rendering varies wildly across clients. The same email can look perfect in Apple Mail, acceptable in Gmail, and broken in Outlook — all at once. See Why Outlook, Gmail, and Apple Mail Render Differently.
• Broken emails damage trust and engagement. Readers who see a broken layout assume you’re unprofessional — or worse, that the email is spam. They close it without reading.
• Mobile is the majority. Most emails are opened on mobile. If you only test on desktop, you’re testing for the minority of your audience.
• Dark mode is widespread. Many readers use dark mode by default. An email designed for light backgrounds can become unreadable when inverted.
• You can’t unsend. Once an email goes to your list, the broken version is what they see. Testing is your only chance to catch problems.

How to test emails thoroughly

1. Start with builder preview. Check the desktop and mobile preview in your editor. This catches obvious layout issues — overflow, misalignment, broken spacing — before you invest in deeper testing.

2. Send a test to your own inbox. Send a copy to email accounts you control across different clients — a Gmail account, an Outlook account, an Apple Mail account. Open each on both desktop and mobile if you can.

3. Check on a real phone. Desktop inbox previews hide mobile problems. Open the test email on your phone, ideally one-handed, the way a reader would. Can you read the text? Can you tap the buttons? Does anything overflow?

4. Test dark mode. Toggle dark mode on in your email client and re-check the email. Do text and backgrounds still have enough contrast? Did logos or images with transparent backgrounds disappear?

5. Check image loading. Many readers have images blocked by default. Disable images in your email client and look at the email — is the alt text readable? Does the layout still make sense without images?

6. Verify links and tracking. Click every link in the email. Make sure they go where they should, and that tracking parameters are correct.

7. Check the subject and preheader. Look at the inbox preview — the sender name, subject line, and preheader snippet as they appear together. See Email Preheader Text for guidance.

8. Use a rendering service for high-stakes sends. For important campaigns, use a service that screenshots your email across 40+ client/device combinations. Litmus and Email on Acid are the established options. These catch rendering issues in clients you don’t personally have access to — especially the many versions of Outlook.

9. Test the unsubscribe link. Make sure it works, and that it leads to a functioning preference page or opt-out flow. A broken unsubscribe link generates spam complaints.

10. Check email size. If your email is close to 102KB, Gmail will clip it. See Why Gmail Clips Your Emails. Keep the file size well under that threshold.

Common testing mistakes

• Testing only in the builder preview. The preview shows one rendering. Your readers see dozens of different ones.
• Testing only on desktop. Mobile is the majority of opens. Skip mobile testing and you miss the biggest audience.
• Forgetting dark mode. An email that works in light mode can be unreadable when inverted — test both.
• Not testing with images disabled. If your email relies on images for layout or meaning, readers with images blocked see a broken or empty message.
• Skipping the unsubscribe link. A broken unsubscribe generates spam complaints, which damage deliverability.
• Testing once and assuming it’s done. Email clients update their rendering engines over time. An email that worked last year might break in a new client version. Re-test important templates periodically.

How to test emails built in Temway

Temway includes built-in testing tools that cover the first and most important layers:

1. Use the Desktop and Mobile preview as you build. The split view shows both layouts in real time, so you catch layout problems — overflow, misaligned columns, tiny text — as you design, not after.

2. Send a test copy to your inbox. Temway’s test send delivers a copy to your own email address, so you can open it in your real email clients and on your phone. This is the most realistic preview short of a paid rendering service.

3. Check the preheader and subject in your inbox. When the test email arrives, look at the inbox preview exactly as a reader would — sender name, subject, and preheader snippet together. This is the only way to verify the inbox impression.

4. Toggle dark mode in your email client after receiving the test send, and check whether colors and contrast hold up. See Dark Mode Email Design for what to look for.

5. Verify your email size. Emails built with Temway’s blocks produce efficient output, but if you add many large images, check the total size to stay safely under Gmail’s 102KB clipping threshold.

6. For full rendering coverage, export and use a rendering service. When your email looks right in Temway, export the HTML and paste it into a service like Litmus or Email on Acid for a comprehensive cross-client screenshot check. This catches issues in clients you can’t test locally — especially the many Outlook versions.

Where to go next

• Understand why clients render differently: Why Outlook, Gmail, and Apple Mail Render Differently.
• Learn how clean source compiles to cross-client HTML: What Is MJML?.
• Prepare for dark mode: Dark Mode Email Design.
• Keep size under control: Why Gmail Clips Your Emails.