Inbox-Friendly Campaigns: Compress Images and Convert Attachments for Better Email Performance

Email is a weird little universe. Your message might look gorgeous in your design tool, perfectly spaced, perfectly branded… and then it lands in someone’s inbox and behaves like it’s trying to conserve battery life.

Because it is.

Email clients are cautious, picky, and sometimes straight-up ancient. They don’t just judge your subject line and copy. They judge how fast your message loads, whether it triggers clipping, and whether it feels smooth on a phone held one-handed over a sink.

If your campaigns have started feeling heavy, sluggish, or mysteriously underperforming, the fix is often less “new strategy” and more “lighter assets.”

This guide is the practical version: how to compress images, handle retina without doubling weight, and decide when attachments should be links instead.

Why “heavy” emails underperform

A heavy email doesn’t just load slowly. It changes how people experience your brand. It’s the difference between “that was easy” and “I’ll look later,” which is marketing’s polite version of never.

Load time and engagement

If your hero image takes a while to appear, the email feels broken for a moment. People scroll past it, lose interest, or simply delete. And on mobile data, the pain multiplies.

Fast-loading emails get read. Slow-loading emails get treated like chores.

Deliverability friction and clipping behaviors

Some inboxes are more forgiving than others, but size still matters.

Large emails can trigger clipping in certain clients, meaning the message is cut off with a “View entire message” link. That’s not just annoying. It can affect how people interact with your content, and it can interfere with tracking pixels or footer content you actually need to be seen.

Also, anything that feels “heavy” can add subtle deliverability friction. Not in a dramatic “you’re blocked” way, but in the sense that you’re asking inboxes and devices to do more work to render your message.

Mobile constraints

Mobile is the true judge.

On a small screen, people scroll quickly. Images need to appear immediately and look crisp without being massive. Attachments need to be easy to open without forcing someone into a five-step download journey that feels like paperwork.

If you optimise for mobile, the desktop experience usually improves too. The reverse is not always true.

Email images: practical optimization rules

You don’t need perfect numbers. You need sensible defaults that keep campaigns light and sharp across major clients.

Recommended pixel dimensions for headers and content blocks

A common mistake is exporting assets at “website hero” sizes and dropping them into email. Email layouts are narrower.

A comfortable, broadly safe approach:

• For full-width email headers, aim around 600 to 700 px wide for standard layouts.
• If your template is designed for wider modern layouts, you might go higher, but you still want to be intentional about it, not accidental.
• For content images inside the email body, export close to the actual display size rather than dropping in huge originals and hoping the client scales them nicely.

The big idea is simple: don’t ship pixels the email can’t display.

Retina handling without doubling file weight

Retina is where people accidentally make emails obese.

The usual approach is to export images at roughly 2x the display size so they look sharp on high-density screens. The problem is that if you do this without compression, your file sizes balloon instantly.

A more balanced approach is to use 2x exports selectively. Logos, icons, and anything with sharp edges benefit most. For big photographic headers, you can often stay closer to 1.5x or use a controlled compression step to keep the file size sane.

Retina sharpness is great. Retina file weight is not.

Format choices for email clients (what actually renders reliably)

Email clients are conservative. Reliability matters more than novelty.

In practice:

• JPG is usually best for photos and gradients.
• PNG is best for logos, icons, or anything requiring transparency and crisp edges.

Modern formats like WebP are a different story in email, and we’ll address that in the FAQs. The main takeaway is: don’t choose a format because it’s trendy. Choose it because it consistently renders in inboxes.

If you want a quick and controlled way to reduce image weight before you drop assets into your ESP, this image compressor from documents.io is an easy step in your workflow.

Attachments: when to attach vs when to link

Attachments have a certain old-school charm. They also have a habit of turning a simple email into a mini obstacle course.

The rule of thumb is: attach when you absolutely need to, link when you can.

PDF compression for sendability

If you’re attaching a PDF, assume it’s bigger than it needs to be.

A “print-ready” PDF is often dramatically heavier than a screen-optimised version. If it’s intended to be read on a phone, it should be exported for screens. That usually means downsampling images, avoiding unnecessary embedded fonts, and using a web-friendly preset.

Your goal is a PDF that opens quickly and scrolls smoothly, not a brochure that’s ready for a printing press.

Converting heavy attachments into shareable formats

Sometimes the best email attachment isn’t an attachment at all. It’s a conversion.

If someone only needs a quick reference table, a single page, a screenshot, or a lightweight version of a document, turning a heavy file into a more shareable format can remove friction instantly.

The key is to match the format to the job. If it’s meant to be skimmed, make it skimmable. If it’s meant to be saved, make it easy to save without eating storage.

Using hosted files without hurting tracking and UX

Hosted files can be a win because they keep your email lighter. They also give you more control: you can update a hosted asset without re-sending the email.

But you want to do it without creating a “where am I?” moment for the reader.

A good hosted-file experience feels simple: click, open, done. Use clear anchor text so people know what they’re getting, and make sure the hosted page loads fast and looks good on mobile. If tracking matters, use UTM parameters and verify that your analytics are recording the click-through properly.

Build workflow for marketers

This is where campaigns become repeatable. A workflow beats “remembering” every time.

Export from design tools in the right size first

The most underrated trick is exporting at the right size before you do anything else.

If you export a massive image and then compress it, you’re doing extra work. If you export it close to the size you actually need, compression becomes gentler and the result looks cleaner.

Design tools make it easy to export big because big feels safe. For email, big is usually just heavy.

Compress in a controlled step

Compression works best as a deliberate step, not a desperate one.

Pick your quality target, compress, then do a quick visual check, especially around text overlays, gradients, and sharp logo edges. If something looks off, you don’t need to guess wildly. You just adjust slightly and re-export.

This is also where having a consistent tool helps, because it removes decision fatigue. If you need one, here’s that image compressor again: https://documents.io/image-compressor

Test in major clients and on mobile

Email rendering is famously inconsistent, so testing isn’t optional. It’s the price of admission.

At minimum, test on:

• A major webmail client
• A major desktop client
• A phone (ideally both iPhone and Android if you can)

You’re looking for obvious breakages, but also subtle performance issues: slow-loading images, weird scaling, and anything that makes the email feel heavy.

Fixing common problems

Blurry logos, jagged edges, and banding

Blurry logos usually come from resizing in the email client instead of exporting at a crisp size. If the logo is important, export it at the exact display size (or 2x for retina), and use PNG when you need sharp edges.

Jagged edges often appear when a graphic with sharp lines is over-compressed in the wrong format. That’s a sign to switch formats or reduce compression slightly.

Banding, those stripey gradients that appear in skies or smooth backgrounds, usually comes from aggressive JPG compression. Increase quality a bit and test again.

“Why is my email clipped?” and what to do

Clipping usually happens because the email is too large in HTML size, not just because images are heavy. But heavy images can contribute indirectly, especially if they’re embedded in ways that increase the overall payload.

The fix is usually a combination of simplifying HTML, reducing repeated code, and optimising how assets are referenced. If you’re seeing clipping, treat it like a signal: the email is carrying more than it needs to.

FAQs

What’s a good target size for email images?

A practical target for most email images is under 200 KB, with larger headers sometimes landing around 300 to 500 KB if they’re photo-heavy and full-width.

You don’t need to hit tiny numbers. You need your email to load quickly on mobile without compromising visual quality.

Do any email clients support WebP?

Some environments do, but email support is inconsistent enough that WebP isn’t a reliable “default” for campaigns today.

If you want maximum compatibility, stick to JPG and PNG for email images. If you’re experimenting, do it carefully, test thoroughly, and make sure you have fallbacks.