Oracle Eloqua Email Image Sizes and Optimisation Guide

Oracle Eloqua image sizes for one, two, three and four columns

Oracle's Design Editor documentation provides specific image guidelines based on the number and arrangement of email columns. This makes Eloqua unusually clear about practical starting dimensions, although padding, customised templates and individual block settings can still affect the available space.

The 2x values are calculated production examples, not separate mandatory Oracle requirements. Use the visible column size as the starting point.

Use Eloqua Design Editor image blocks and Auto Fit correctly

Oracle's Design Editor allows marketers to drag an image component into an email, select an existing image or upload a new asset, and configure its sizing, alignment, padding, links and alternative text.

The Auto Fit setting adjusts image proportions to fill the available content block. Turning Auto Fit off allows the image width to be scaled within the block while preserving its proportions. These are presentation controls, so the original file should still be resized and optimised before upload.

• Start with the documented width for the relevant Eloqua column.
• Check content-block padding before approving the final visible dimensions.
• Choose left, centre or right alignment that matches the campaign layout.
• Add meaningful alt text and verify the destination of linked images.
• Review responsive-validation notifications generated by the Design Editor.

Calculate 1x, 1.5x and 2x Eloqua campaign images

A 600px full-width Eloqua banner can use a 900px source at 1.5x or a 1200px source at 2x. For an image displayed in a 300px product column, the corresponding source widths are 450px and 600px.

Optimise each version and compare visible detail before deciding whether 2x is justified. Read the Retina Email Images Guide for a full explanation of display width and pixel density.

Review the Eloqua 360px mobile view and responsive visibility

Oracle states that the Design Editor mobile view sets the email width to 360px. This provides a concrete preview reference, particularly when checking banners, stacked columns and responsive typography.

A 600px desktop banner should still communicate its purpose after the layout becomes narrower. Product tiles that appear side by side on desktop may stack or change their visible proportions depending on the template.

Oracle also documents Hide in Mobile and Hide in Desktop options for supported content components. These can help present a dedicated mobile crop or simplify a crowded desktop composition, but Oracle advises marketers to test the relevant clients and ensure a sensible fallback.

• Inspect the image at Eloqua's documented 360px mobile preview width.
• Test other practical phone widths rather than treating 360px as universal.
• Check whether mobile-specific content stays understandable when hiding rules are unsupported.
• Keep campaign-critical information available as accessible text wherever possible.

Prepare images differently for Design Editor and custom HTML emails

Design Editor campaigns use Eloqua's visual components, while custom HTML emails give developers direct control over table layouts, image markup, fallback behaviour and responsive CSS. The image source still needs to match its real display context in either workflow.

<img src="https://example.com/eloqua-event-hero-1200.jpg"
     width="600"
     alt="Register for the customer experience webinar"
     style="display:block;width:100%;max-width:600px;height:auto;border:0;">

When a 1200px source is intended to occupy a 600px table cell, the visible width should remain explicit. Review any dynamic content, tracked links or template-specific image substitutions in the final generated message.

Organisations that also maintain Salesforce campaigns can compare the Salesforce Marketing Cloud email image guide for Content Builder and subscriber-level QA considerations.

Handle Outlook behaviour, image blocking and accessible alt text

Oracle specifically recommends alternative text because some email clients do not download images automatically. This matters for Outlook recipients, accessibility tools and campaign previews where images are temporarily unavailable.

Use alternative text that explains the purpose of an informative image. A product image might identify the product, while a linked promotional banner can describe the action or campaign offer. Keep important deadlines, prices and calls to action available outside images where practical.

• Use explicit widths and proportional heights in custom HTML email layouts.
• Test relevant desktop, web and mobile Outlook versions.
• Check transparent logos against light and dark surrounding colours.
• Provide a background-colour fallback when a background image is unavailable.
• Inspect image links and ensure keyboard and screen-reader users can understand them.

Test Eloqua campaign images with real contacts and real inboxes

Eloqua's preview can show how email content changes for different contacts and screen sizes. Oracle notes that the preview does not replace testing across actual email clients. Use representative contact records to check dynamic content and verify every important image variation.

1. Confirm the correct image size for each Design Editor column or HTML table cell.
2. Review responsive notifications and fix any flagged image behaviour.
3. Preview the campaign using contacts from relevant audience segments.
4. Switch to the 360px mobile view and inspect stacked content.
5. Send test emails to Gmail, Outlook and Apple Mail environments used by your audience.
6. Verify image quality, alternative text, destination links and dark-background visibility.
7. Recheck any nurture programme or automated campaign using the same shared assets.

For wider advice on file weight and email-client compatibility, see our complete Email Image Size Guide.

Common Oracle Eloqua image-preparation mistakes

• Using a 600px source in every column, even when the image displays at 150px or 200px.
• Assuming Auto Fit automatically reduces the original image download size.
• Preparing a 1200px Retina source without controlling its visible HTML width.
• Treating Eloqua's 360px mobile preview as a complete cross-client test.
• Relying on hide rules without checking fallback behaviour.
• Leaving alt text empty on important campaign images.
• Following obsolete integration guidance without checking the current Eloqua release.

Frequently asked questions about Oracle Eloqua email images

Official Oracle Eloqua image and mobile documentation

• Oracle Eloqua image sizes and Design Editor image blocks
• Oracle Eloqua 360px mobile editing view
• Oracle Eloqua mobile and desktop content visibility
• Oracle Eloqua contact and device email previews

ImageOptimise is independent and is not affiliated with, integrated with or endorsed by Oracle.