When a B2C Commerce Dynamic Imaging Service image URL fails, times out, or looks wrong, check the source file, the full URL, and the limits in Dynamic Imaging Service.
Also use this guidance to migrate from other hostnames and external digital asset management (DAM) services.
File size, timeout, Content Delivery Network (CDN) and non-CDN behavior, and 4xx or 408 responses are documented under What Limits and Caching Rules Apply? and Dynamic Imaging Caching. Use this topic for troubleshooting steps. The numeric limits stay in that topic.
How Do I Troubleshoot a Broken, Slow, or Missing Image?
In B2C Commerce, start with the image URL the storefront requested.
In the browser, copy the full imgsrc URL and open it in a new tab. If a transform is expected and you don’t see /dw/image/v2/ in the path, the template may point to the static file or a host that does not use the Dynamic Imaging Service. Use URLUtils and MediaFile as described in How Do I Create an Image Transformation URL for B2C Commerce Images?.
If the HTTP status is 4xx on the image request, recheck the parameter rules in URL Structure and Order of Operations and the Supported Transformations table. Common causes: a duplicate ? in the query string, empty sw= or sh= values, an incomplete set of crop or overlay parameters, out-of-range values, or an oimg that fails the length, encoding, or host rules in the Supported Transformations table.
If the source file is missing for a view type, update the image assignment in Assign Images to Products, not only the transform query.
Slowness or Timeouts
In B2C Commerce, a slow image is often a cold cache or a transform that is too expensive.
The first cold request can be slower. After the CDN cache is warm, repeat loads should be faster. See Dynamic Imaging Caching.
In nonproduction environments, Firefox Tracking Protection can block some first fetches. See the browser note in What Limits and Caching Rules Apply?.
How Do I Migrate from Another Image Host?
In B2C Commerce, use this section to migrate from an external digital asset management (DAM) service, for example Adobe Scene7.
When you replace a historic infrastructure or vendor CDN hostname, don’t hand-edit a new edge host without an approved pattern from your program. Regenerate correct URLs with URLUtils and MediaFile, or from a community helper for your vanity storefront domain, as described in Community Product Image Wrapper.
This mapping is rough. Verify every parameter in Which Transformations Are Supported?. Adobe Scene7 is one example. Use this mapping when an external DAM service uses this kind of query string.
Typical Scene7-style
Typical Dynamic Imaging Service direction
wid=400
scaleWidth / sw=400 in your transform or query.
hei=400
scaleHeight / sh=400.
fmt=jpeg or fmt=png
Output file extension and, when needed, format / sfrm, as in the Format row of Supported Transformations.
qlt=80
quality / q=80, or omit q when you keep the default of 80.
For a third-party digital asset manager (DAM), export a large master image, upload it to the correct B2C Commerce library and view type for your feed, run your import and replication jobs, and then point the storefront at URL generation through URLUtils and MediaFile, or a community helper. Stop deep-linking the old vendor CDN after cutover.
When you open a case with Salesforce Support, include a full repro URL (path and query), realm and site context, the expected and observed HTTP status or bytes, and what you already tried from this topic.
j