MAILCRAFT
Home Features Pricing About Blog Contact Log in Get Started →
Email templates & design

How to Test an Email Before Sending: Rendering, Links and Fallbacks

Open pink envelope with a blank white card, like an email checked before it is sent

To test an email before sending, run the same pre-send routine. Every time. Check CSS support, links, personalization fallbacks, the plain text version, images and dark mode, then send tests to real inboxes. Did your last campaign go out with a button that broke in Outlook and a greeting that read “Hi ,”? That routine would have caught both before anyone else saw them. Below is one ordered checklist you can repeat before every holiday send, no matter how busy the week gets.

Why do emails look different in Gmail, Outlook and Apple Mail?

Short answer: every email client renders HTML and CSS its own way. Code that looks perfect in one inbox can fall apart in the next. Gmail publishes documentation on the CSS it supports. The Can I email reference lists which HTML and CSS features each client handles. My rule for HTML email testing is simple: look a property up there before you rely on it. Rounded corners and background images behind buttons are typical examples.

Buttons are where this hurts most. A bulletproof button (a table-based or padded link styled with plain inline CSS) usually holds up better than one built from fancy CSS alone. And if the styling does fail? The reader still gets a clickable block of text, not a dead image.

Email testing checklist: what to check before pressing Send

Same seven checks, same order, every single time. That way the routine doesn’t depend on your memory or your mood that day:

  1. CSS support in the clients your subscribers use
  2. Every link and UTM tag
  3. Merge tag fallbacks
  4. The plain text version
  5. Images and their alt text
  6. Dark mode
  7. A test send to yourself and to a small seed group

Save it as a document, or pin it as a note to your campaign template. Why bother writing it down? Because in the busy week before a sale, a written pre-send email checklist is the only thing that stops someone from quietly skipping step four.

Check links, buttons and UTM parameters

Click every link in the delivered test message. Not in the editor. A link that works fine in the builder can still come out mangled in the actual email. Then check that the UTM source, medium and campaign values match across all links, or your analytics will happily split one campaign into three.

Open each landing page and confirm three things: it loads, the offer is still live, and it isn’t a 404. Then test the button as a link. The whole shape should be clickable, not just the words, and it should go where the label promises. Also hunt for leftovers from earlier work. Staging URLs. That link to last year’s holiday sale (it happens more often than anyone admits).

Set fallbacks for merge tags and personalization

Every merge tag needs a default value. Otherwise a missing first name turns into “Hi ,”. Most platforms let you set merge tag fallback values right on the tag, which beats scrubbing the contact list after the damage is done.

How do you check them? Create a test contact with empty fields on purpose: first name, plus any custom fields you use for city, last order or loyalty level. Send yourself the campaign as that contact. And write greetings that still sound natural when the fallback kicks in, so “Hi there” fills in for the name without reading like a robot wrote it.

Plain text, alt text and dark mode: the fallbacks readers see

Blocked images, stripped HTML, an inbox that flips to dark mode. In all three cases readers see your fallbacks, not your design. So test those too. Some people only ever read the plain text part, and it has to stand on its own.

  • Plain text: it should read in a sensible order and show full URLs. MailCraft generates an automatic plaintext fallback, but read it once anyway. Where the order or wording feels off, edit it into a proper plain text version.
  • Images: give each one meaningful alt text, and never put the key message only inside a picture. WCAG is the accessibility standard for contrast and alt text, and honestly, it pays to run regular accessible email design checks against it.
  • Dark mode: use a logo on a transparent background and button colors that stay legible when the inbox inverts them. That’s how you keep logos readable in dark mode.

Test email in different email clients with real inboxes and a seed group

The email preview in your editor is a decent first pass. But the real email rendering test happens in inboxes you control. Start in the builder anyway: MailCraft’s live preview and preview across devices show the desktop and mobile layouts, so you can sort out spacing and stacking before the first test send.

Next, set up your own Gmail, Outlook and Apple Mail accounts and open every test on both desktop and phone. Then add a small internal seed group. A few colleagues who get every test and reply with screenshots of anything that looks weird. Fix what they find, resend, check again. Once you know how to test an email before sending, the holiday rush stops being a gamble. It’s just routine.

FAQ

How many test emails should I send before a campaign?

As many rounds as it takes to get one clean pass after your last edit. Any change to the code or content means one more test send. Yes, even if all you did was fix a price or swap a link.

Is the preview in my email builder enough?

No. The builder preview catches layout and mobile issues, but it can’t tell you how a specific client treats your CSS. Always finish with real inboxes, desktop and phone.

What is the most common thing to forget in an email testing checklist?

Empty personalization fields and the plain text version, by a mile. Neither shows up in a normal preview, so they slip through. Test with a contact whose fields are blank, and read the plain text part before every send.