There's a popular take going around email marketing circles: stop treating email as a work of art, treat it as functional architecture, make it clean instead of fancy. It's not wrong exactly, but it's aimed at the wrong target. The problem was never good design. The problem is a specific production shortcut that gets mistaken for design.
🖼️ The Real Dividing Line
Good design and spliced design aren't points on the same scale. They're different categories of thing entirely:
- Good design is a balance of real text, real images, and real layout — built with HTML tables and inline CSS, or a proper email builder, so every element exists as markup.
- Spliced design is a finished visual composition, cut into pieces — a header image, a hero image, an offer image, a footer image — with each slice dropped into its own row and wrapped in its own link, so different sections can point to different places.
That's worth being precise about, because it's not the same as an image-map, where one single image has invisible coordinate-based hotspots layered on top. Image-maps have their own history of being unreliable in email specifically — coordinates can shift or fail to register depending on the client's rendering engine, so a tap meant for the button ends up missing or landing in the wrong zone. Slicing per section sidesteps that: each piece is its own image and its own link, so at least the links are honest and clickable.
A spliced email can look more polished than a coded one. That's exactly what makes it a trap — it looks like a design upgrade while quietly removing everything that makes an email work.
Why the Splice Breaks Things
Slicing per section fixes some problems, but the deeper ones remain — and a few only become visible once you look closely at how each slice behaves on its own.
📵 Images Off, Message Gone
Outlook doesn't load images by default. Plenty of Gmail users haven't turned on "always display images." If a whole section is one slice, that section becomes a blank box — the header slice, the offer slice, the footer slice each disappear independently. A coded section still delivers its message in plain text with images off.
Screen readers can't read it. Text baked into a picture is invisible to assistive technology. Slicing per section doesn't fix this — it just means the failure happens section by section instead of all at once. Every slice is still a flattened picture underneath.
It's unsearchable, even for the reader themselves. This is a different problem from the screen-reader one, not the same one restated. Gmail, Outlook, and Apple Mail all index the text of an email so people can search their inbox later — for a discount code, a shipping confirmation, a product name. If that text only exists as pixels, there's nothing for the search index to match against. Someone trying to Ctrl+F inside the opened email hits the same wall. And if the email ever gets archived to a "view in browser" page, image-only content won't get picked up by search engines either, since there's no text for them to crawl.
It can't reflow, it can only resize. This is the point that ties everything together: if an email looks exactly the same on desktop and mobile, it was never mobile-optimized, it just shrank. A real two-column desktop layout, built in code, restacks into a single column on a phone. A sliced section that contains a two-column comparison can only scale that whole slice down as one unit — the columns get smaller together instead of stacking, until the type is unreadable and the tap targets are the size of a grain of rice.
It ignores the "peephole" reality of how email actually gets read. Nobody sees an email the way they see a finished poster. Gmail's preview pane shows a few hundred pixels. Mobile shows one or two sections at a time. Slicing preserves a top-to-bottom visual composition for a view the reader will never actually get in one piece anyway.
Seams become a real bug source. Adjacent slices stacked in separate table rows can show a hairline gap or misalignment between them depending on the email client's rendering quirks — something that doesn't happen when a section is genuinely one coded block.
It doesn't survive dark mode or font scaling. Live text can invert color, respect a user's font-size settings, and get selected or copied. A picture of text is stuck exactly as exported, in every setting, for every reader.
📋 Built vs. Spliced, Side by Side
Laid out plainly, the practical differences show up in almost every dimension that matters for whether an email actually performs:
| Factor | Built (Coded) | Spliced (Image) |
|---|---|---|
| Images off | Message still readable | Section goes blank |
| Screen readers | Text is accessible | Text is invisible |
| Mobile behavior | Reflows / restacks | Only resizes |
| Per-link tracking | Accurate | Accurate (per slice) |
| Dark mode / font scaling | Adapts | Fixed at export |
| Rendering seams | None | Possible gaps between slices |
🎨 What a Built Email Actually Allows
None of this is an argument for boring, gray, plain-text email. A properly coded email can still have custom web fonts with sane fallbacks, rounded buttons and cards, deliberate use of photography, and a distinct, on-brand visual identity. The difference is that every piece of it is still markup. The text is text. The button is a link. The layout reflows because it was actually told how to reflow at different widths, instead of just being scaled down as a single unit.
💡 Pro Tip
Ask yourself two questions about any email before it sends: if you took the images out, would the message still exist? And if you opened it on a phone, would the layout actually change shape, or just shrink? If the answer to either is no, it's spliced, not built.
🌟 Closing Thought
Forget "simple vs. fancy" as the deciding line. Good design and spliced design were never on the same axis to begin with. A coded email can be just as visually distinctive as a spliced one — the difference only shows up the moment images are off, the screen reader runs, or the phone comes out. That's the moment that actually matters, and it's the one splicing quietly fails.
See how your own emails perform →
No credit card required. Upload your Omnisend export and see your full-year performance picture.