Why do my Klaviyo product image and text stay cramped side by side on phones?

Separate the mobile layout from the content source

Klaviyo documents Split as two columns and Columns as one to four, both stackable on mobile. Table blocks do not stack. Static tables keep a fixed layout, but personalization, event or catalog tags can still vary their contents.

A narrow text column beside a product photo may therefore be behaving according to its block type. Before compressing the message further, decide whether side-by-side presentation is necessary on a phone. The important outcome is a recognizable product followed by readable information and an understandable action.

Keep data behavior separate. A fixed launch feature can contain personalized words without becoming a variable-length order list. Conversely, an order table's changing row count is not just a visual arrangement that can be replaced with two fixed panels.

For the documented block capabilities and stacking comparison, see How to use a table block in an email.

Illustrative exercise A: rebuild one launch feature

A fictional lamp launch has one approved photograph and one explanatory passage. Desktop presentation is acceptable, but mobile leaves room for only a few words per line. Evaluate rebuilding that feature with a stackable Split or Columns layout rather than shrinking the whole paragraph.

For an image-and-text pair, inspect Split's two-column arrangement; choose Columns if the design needs other block types or a different supported column count. These are layout choices for this fixed feature, not instructions to duplicate it once for every possible purchase.

Check the stacked reading sequence: product identity, useful explanation, then action. Compare the approved lamp crop at the narrow width, and make sure conditions remain native readable text. Stacking should not move an important qualifier away from the offer it limits.

1. In a controlled draft copy, add an appropriate Split or Columns layout from Blocks for this fixed feature.
2. Move the approved fixed photograph and native text into that layout, retaining the correct link and qualifier. Do not replace a variable order list with fixed cards.
3. Keep the same selected preview data and compare desktop and mobile, then inspect the actual authorized test delivery before release. This exercise has not been executed.

Illustrative exercise B: preserve a changing order list

A second message summarizes orders containing different numbers of products. Replacing its dynamic table with three hand-built product cards would only suit a selected sample. Preserve the list-driven row behavior while investigating a mobile presentation suitable for that message.

Inspect which row content is essential: correct product identity, the required order information and its matching image. Remove only genuinely optional decoration, not quantities or necessary distinctions. If the existing design remains unreadable, ask for a suitable dynamic implementation rather than quietly converting it into fixed content.

Use both a short and a longer product name, and compare one-item and multi-item examples. A layout that accommodates one compact title may still fail when several long names appear. Do not treat the fixed launch-feature solution as proof that the transactional list has been repaired.

If rows must follow an actual order, use the dynamic order-row guide to preserve the collection and alias while solving the layout separately.

Compare the same message at both widths

Keep the same selected data while comparing desktop and mobile. That makes cramped wrapping easier to distinguish from a different product or personalized value. Check picture identity, text order and the button's association with the correct item.

For the fixed feature, judge the new stacked arrangement. For the dynamic list, also judge row completeness. A pleasant screenshot cannot substitute for both tests.

These illustrative exercises involved no email send, Klaviyo account operation, live preview, publication or paid test. They do not describe an Itemlume integration or establish behavior in every recipient's email client.

Illustrative exercise: fixed feature stacking versus variable-order preservation

These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.

Download review worksheet (CSV)