The Email Arrived Different: Who Changed It and What to Do
Seven distortions between your editor and the inbox
Mailvex · 4 September 2026 · 5 min read
Between your editor and the recipient inbox an email passes through two systems, and each makes changes. Your sending platform rewrites links and adds its own code; the mail provider may clip the message and strip part of the styling. Below are seven typical distortions: who causes them, which are normal and which you can control.
Three stages, changes at each
It helps to picture the journey as three stages. In the first you build the email and export the HTML. In the second your sending platform receives it, processes it and sends. In the third the recipient mail provider accepts the message and renders it in its client.
Changes happen in the second and third stages, and their nature differs. The sending platform alters the email deliberately — to count clicks and satisfy legal requirements. The mail provider alters it out of necessity — for security and because of its rendering engine limits.
Separating these two sources matters: the first can be negotiated through settings, the second has to be accounted for while coding.
Seven distortions and who causes them
Seven distortions cover almost every case. Find yours in the first column.
| What changed | Who changed it | What to do |
|---|---|---|
| Email cut off mid-message | the mail provider, weight above the threshold | remove excess code, stay under 100KB before handing it over |
| Styling disappeared | the client stripped external styles | write styles inline rather than in a separate block |
| Links became unfamiliar | your sending platform rewrote them for click tracking | this is normal, but verify each one still lands where it should |
| A foreign footer appeared | the platform added its own details and unsubscribe | configure or remove it in the sending settings |
| Text shifted to the next line | the font was replaced by a wider one | fallbacks with similar width |
| Colours inverted | the recipient dark mode | set colours explicitly and add dark mode meta tags |
| Images did not load | the client blocks them | alt text, meaning in the copy rather than in images |
Note the second column: half the changes come from the sending platform rather than the recipient inbox. Which means part of the problems are solved by settings, not by rebuilding the email.
What your sending platform does
A sending platform does three things to an email, all of them predictable.
It rewrites links. Every link is replaced with an address on the platform, which records the click and then forwards the person onward. It looks unfamiliar but it is normal — otherwise there would be nothing to collect click statistics from.
It adds its own code. An open-tracking pixel, a footer with legal details and an unsubscribe link. Hence an important consequence: an email that weighed 95 kilobytes for you can cross the clipping threshold after processing.
Aim not at the limit itself but at a margin: keep the email under 100 kilobytes before handing it to the platform, and the added code will not push it over.
What the recipient mail provider does
The recipient mail provider works the other way — it does not add, it removes.
It strips external stylesheets and anything it considers unsafe. It blocks image loading until the person allows it. It clips the message if it exceeds the threshold. It inverts colours in dark mode.
You cannot negotiate with it, but you can code so there is nothing to strip: styles written inline, meaning held in the copy rather than in images, weight kept within bounds.
What you control and what you do not
Let us separate these explicitly, so no effort goes into the impossible.
- you control: email weight, inline styles, alt text, font sizes, dark mode behaviour
- you configure: the platform footer, link rewriting, the tracking pixel
- you do not control: image blocking, stripped external styles, colour inversion in some clients
- you do not control: how the email looks to someone reading in plain-text mode
The last point is worth holding onto: part of your audience sees emails with no styling at all. If the message still makes sense that way, the structure is right.
How to test before sending
Test the email after it has passed both stages, not before.
- export the HTML and import it into your sending platform
- send a test to yourself rather than looking at the preview
- check the weight after import — it will have grown
- click every link and confirm it lands where it should
- open on a phone and in dark mode
- turn off image loading and read it again
The second point is critical. The preview inside a sending platform shows the email before the tracking code and footer are added. The real appearance is only visible in a test message that reached an actual inbox.
How a builder handles this
Several distortions in the table are removed while building rather than afterwards. Inline styles, weight control, dark mode behaviour, alt text — all of that goes into the email from the start.
In Mailvex the compiler writes styles directly into the tags, so there is nothing to strip. Email weight is visible while building, with a margin for the platform code. Dark mode is configured separately, and a test send to your own address runs from the editor — you see the email in a real inbox before it goes to your list.
Build an email that arrives intact.
Browse templatesFrequently asked questions
Why are the links in my email not mine anymore?
Your sending platform replaces them to count clicks: the person first lands on a platform address which then forwards them onward. This is normal behaviour and can be turned off in settings, but you lose click statistics.
The email was cut off mid-message, what do I do?
Its weight exceeded the mail provider threshold. Remember the platform adds its own code after you: an email at 95 kilobytes can cross the line. Keep it under 100 kilobytes before handing it over.
Why does the preview not match what arrived?
The preview shows the email before the platform tracking code and footer are added, and without processing by the recipient client. The real appearance is only visible in a test message that reached an actual inbox.
