Why are WooCommerce image-width controls missing from the Customizer?

Why the controls disappear

The Customizer does not necessarily expose image-width controls for every theme. When a theme declares the widths used for product images, that declaration can hide the corresponding width controls. The missing control is therefore evidence about ownership, not proof that WooCommerce has stopped generating product images.

Keep two measurements separate. A requested file size is the pixel size an image may be prepared at, while the CSS layout width is the space the browser gives the image. A product image can be downloaded at one width and displayed at another, so changing uploads will not automatically correct a layout-width problem.

Use a non-destructive fixture

Work on a test copy of one owned product asset or an equivalent staging product. Record the active theme, the image’s current displayed width at each relevant responsive view, and the available image variants shown by your media or inspection tools. Do not delete existing media while diagnosing the owner of the setting.

Inspect the theme’s product-image sizing documentation or configuration, then inspect the CSS layout around the product image. Look specifically for a theme-declared width and for responsive candidates that are smaller than the rendered space. The exact place where a theme exposes its declaration varies, so do not assume that a missing Customizer field has a universal replacement.

1. 1. Duplicate the product or use a staging copy, and select one representative product image.
2. 2. Note the current Customizer state: record whether an image-width control is absent, present, or present but ineffective.
3. 3. Identify the active theme’s declared product-image width, if the theme documents or exposes one.
4. 4. Compare that requested image width with the CSS layout width and with the responsive image candidate actually selected by the browser or inspection tool.
5. 5. Change only the owner’s setting on the test copy, then inspect the same view again.

Branch on the evidence

If a theme declaration is present and the Customizer control is absent, treat the theme as the owner. Change the theme’s documented product-image width, or ask the theme maintainer where that declaration is managed. Do not keep searching for a WooCommerce control that the theme intentionally replaces.

If no theme declaration is found and a WooCommerce image-width control is available, use that WooCommerce control on the test copy. If the selected responsive candidate is narrower than the CSS layout, investigate the generated image sizes rather than changing CSS alone.

If the requested image width is adequate but the displayed image is still wrong, the next action is CSS or responsive-selection diagnosis. If the requested width changed, existing thumbnails may still reflect the old sizing; regenerate old thumbnails only after confirming the desired width and retaining the original files.

Illustrative exercise

Illustrative exercise: define Asset A as a product photo whose selected responsive candidate is 600 pixels wide, and define Asset B as the same product photo prepared at 1200 pixels wide. These values are illustrative only. The test view has a CSS image area of 900 pixels wide.

Compare A and B only after recording which candidate the browser selects. Pass means the selected candidate is suitable for the 900-pixel CSS area, the product image is not visibly constrained by an undersized source, and the setting was changed in the layer that owns it. Fail means the theme still declares a smaller width, the browser still selects Asset A for that view, or the layout remains wrong despite an adequate source; follow the relevant branch above.

Acceptance condition

Accept the change when the test copy shows the intended product image at the target responsive view, the inspected candidate is not narrower than the CSS layout requirement, and you can name the owner of the effective width: the theme declaration, the WooCommerce control, or the CSS/responsive selection layer. Only then apply the confirmed setting to the live product asset and regenerate older thumbnails if the confirmed sizing change requires it.

Scope of the documentation

The official references below support tool behavior and feature boundaries. The test fixture, branching decisions and acceptance criteria are Itemlume editorial recommendations; citation does not imply endorsement. Illustrative sizes, names and timings are not your production specifications.