HomeBlogAboutLog in

Your Embedded Comparison Form in Email Fails in Half Your Inbox. Here Is the Fallback.

The takeaway before the details

An embedded comparison form in email can look perfect in your builder and then arrive broken. Gmail reportedly strips form tags and Outlook turns your dropdown into dead text.

Here is the short version: design the plain version first and let the interactive one be the upgrade.

Field notes from a form that vanished

A client shipped a pricing comparison form inside a campaign. Dropdowns for seats. A submit button that pushed straight to a quote page.

It looked great in Mailchimp’s preview. Then the report came in. Opens were normal but clicks were close to zero.

We opened the same message in Gmail on a phone. The form was gone, stripped from the markup. The reader saw the plan names with no way to pick one.

What survives the trip into an inbox

Email clients are not browsers. They parse your HTML with strict rules and most of them throw out anything interactive on sight.

According to public reports, Gmail removes <form>, <input>, <select> and <button> tags entirely. Yahoo Mail does the same. Outlook desktop uses Word-based rendering, which ignores most positioning and background images.

Email on Acid and Litmus both report tracking this across more than 90 clients. The pattern holds. Anything that submits data is treated as a security risk and cut.

You can only plan around it.

Important fact

According to public reports, Gmail clips any message larger than 102 KB. A form with inline styles and four plan images can blow past that limit on its own, which means the bottom of your email silently disappears behind a “view entire message” link.

Build the static version first

This one habit fixes most of the problem. Open a plain text editor and write the comparison as a table with real text and real numbers.

If that table makes sense with no styling at all, it will make sense in every client.

A table also gives you copy that gets indexed and forwarded. People share comparison tables.

How the fallback should look

  • Plan or option name as the row header
  • One column per option, kept to four or fewer
  • A plain linked line under the table: “Pick your plan here”
  • The link points to the same landing page the form would have submitted to

No button styling needed. A text link with a link color renders almost everywhere.

The image trap

Some teams solve the problem by turning the form into one big image. That works until images are blocked, which happens by default in many inboxes on first open.

When images fail, an all-image form leaves the reader staring at empty space. Always set alt text that restates the offer. “Compare Starter and Pro plans, click to choose” tells the reader what they missed.

Keep the table as text under the image if you can. Then the blocked-image case still works.

One link can carry the whole thing

Interactive email forms feel clever because they remove a click. A reader who taps one clear link has already decided to engage.

Make that link the loudest element in the block. Give it a real destination with the comparison state pre-filled where possible. A URL like /compare?plan=pro&seats=10 does everything the embedded form promised and works in 100% of clients. For most recipients the fallback is the actual email.

Test in the clients that hurt

Previewing in your builder proves nothing. Send a real test to a Gmail address and an Outlook desktop install. Then look at each one on a small screen.

Two checks catch almost every failure. Does the table still line up. Does the link work when you tap it.

Set up a free Litmus or Email on Acid account and screenshot the campaign before you send.

Things to keep in mind

Some clients add padding around table cells that other clients do not. Set border-collapse and cellspacing to zero and you avoid the surprise gaps. Test the text-only version too. Some corporate servers strip HTML completely and a clean plain-text table still reads fine.

A simple way to decide

Ask one question before you build. If every interactive element disappeared right now, would this email still sell the offer? If the answer is no, the design is fragile.

Rewrite until the answer is yes. Then layer the interactive parts back in for the clients that allow them.

Action items

  • Recreate your last comparison email as a plain table with no styles and confirm it still reads
  • Run a Litmus or Email on Acid test on Gmail and Outlook desktop before the next send

Do this once and you have a template you can reuse for every offer.

Read the full guide: Embedded Comparison Form in Email: What Renders and What Gets Stripped