Assets & tasks / PRACTICAL ANSWER
Why Does Overriding the Width and Height in My Shopify image_tag Change the Product Card's Layout Even Though the CDN Image Is Unchanged?
Shopify image_url and image_tag affect different parts of image delivery. image_url requests a CDN resource, while image_tag generates HTML attributes, including width and height. Changing the latter can alter the image's intrinsic layout information even when the downloaded image bytes remain unchanged.
Separate the URL from the generated HTML
Inspect the Liquid expression and the final rendered img element. Record the image URL, HTML width and height attributes, computed CSS dimensions and actual downloaded file dimensions.
Shopify documents that image_tag automatically generates width and height attributes based on the image URL's dimensions and aspect ratio. These attributes can be explicitly overridden.
The filter also documents that providing only one of the two parameters results in only that attribute being added. This matters when a developer assumes Shopify will always preserve both dimensions automatically.
Do not confuse an HTML width attribute with a request for a larger CDN file. The resource URL and its transformation parameters remain a separate part of the implementation.
Inspect reserved geometry and CSS sizing
HTML image dimensions help the browser establish an intrinsic aspect ratio before the image finishes loading. CSS can then determine the displayed size and fitting behavior.
If a developer overrides the attributes with a ratio that differs from the actual image, the browser's initial layout assumptions may no longer match the intended presentation.
Inspect the image's computed width, height, aspect ratio and any CSS constraints. A theme may explicitly size the image, so changing HTML attributes will not always produce the same visible result.
Distinguish three observations: a changed card width, a changed reserved image height and a changed crop inside an otherwise stable box. They point to different CSS or markup mechanisms.
Hypothetical portrait lamp with incorrect dimensions
Hypothetical illustration—not an executed browser test: a fictional product card uses a 600 × 900 portrait lamp image. The CDN URL remains unchanged throughout the comparison.
Version A uses HTML dimensions consistent with the source's 2:3 aspect ratio. Version B overrides the HTML attributes to width=600 and height=600, suggesting a square ratio.
The proposed investigation records the initial placeholder geometry, final image box and surrounding purchase-control position. If the card initially reserves square space and later expands or changes layout, inspect the mismatch between HTML dimensions and CSS behavior.
If the image remains in a stable square box but crops the lamp, investigate object-fit rather than describing the result as a layout shift.
The example does not assert that every browser or theme must shift in response to the override.
Restore truthful intrinsic information
Use dimensions consistent with the intended resource and let the theme's CSS establish the desired card presentation. If the card must be square, specify a deliberate container and fitting policy instead of falsifying the image's intrinsic proportions.
Check the page before and after image loading, then repeat after changing gallery views. Verify that quantity and purchase controls do not unexpectedly move.
Do not request a new image merely because the markup advertises the wrong ratio. Preserve the approved product photograph and repair the rendering contract.
Keep a record of the exact generated HTML, selected CDN URL, CSS dimensions and final visual outcome. An unchanged network image can still participate in a changed layout because its HTML and CSS presentation changed.
Record your own observations
The filled rows are illustrative examples. Use the blank row for your own files and observations.
| Hypothetical version | CDN resource | HTML dimensions | Ratio | Observation to inspect | Decision |
|---|---|---|---|---|---|
| A | 600 × 900 lamp | 600 × 900 | 2:3 | Reserved and final geometry | Reference |
| B | Same resource | 600 × 600 | 1:1 | Initial geometry versus final layout | Investigate mismatch |
| Square presentation | Same resource | Accurate intrinsic dimensions | CSS box may be 1:1 | Crop versus stable container | Use deliberate fit policy |
What the references establish
- Shopify Developers — image_tag Liquid Filter: Documents generated width and height attributes, explicit overrides and behavior when only one attribute is supplied.
- Shopify Developers — image_url Liquid Filter: Establishes the separate CDN image transformation mechanism.
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
- Shopify Developers — image_tag Liquid Filter · Review date not separately recorded
- Shopify Developers — image_url Liquid Filter · Review date not separately recorded
Frequently asked questions
Does image_tag width: 600 request a 600-pixel CDN image?
Do not assume so. image_tag controls generated HTML attributes; image_url is the documented CDN transformation filter.
Can wrong HTML dimensions cause a crop rather than a layout shift?
The result depends on the CSS. Inspect whether the element box changes size or whether object-fit crops the image inside a stable box.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in CartVisual.
Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.
Create account and open this workspace Check pricing and creditsStart with free concept and copy planning after sign-in. Image and video generation require available credits; review the quote before starting.
Already have an account? Open the workspace.