Anatomy of a Dynamic Media URL and how Dynamic Media delivers content

After your Dynamic Media assets are uploaded and published, you can copy an asset’s generated URL and paste it into your browser to see how the asset will appear to a customer. The following copied URL for a watch image is broken down by color to make it easier to read and understand.

Anatomy of a Dynamic Media URL
Anatomy of a Dynamic Media URL.

The first part of the URL in red is referencing the server domain itself. In this case, Dynamic Media is running on a generic server domain, which is https://s7d1.scene7.com/is/image/. It is easy to be able to look at a set of images and understand whether they are being served by Dynamic Media just by looking at the server domain. The URL is going to be fairly consistent. There are, however, some Dynamic Media customers that have switched over to a dedicated server domain where it might be name-of-your-company.scene7.com. A dedicated server domain is required for Smart Imaging.

The account name is the portion in purple. In this case, the account is called jpearldemo.

The asset ID or name, AdobeStock_28563982 is in green. Notice that the asset has no file extension such as .png or .jpg. When assets are ingested into Dynamic Media, the file extension is stripped out and a different kind of file is created: a pyramid-TIFF file. The pyramic-TIFF allows Dynamic Media to quickly create renditions on-the-fly.

And finally, there are some image processing parameters, ?wid=1000&fmt=jpeg&qlt=85, shown in yellow on the end.

The entire URL path is live. Try it.

With your browser window still open to the Dynamic Media URL and the watch image, let’s look closer at how you can create renditions of the image just by changing the URL.

Rendering the watch image through the URL

Begin by manually deleting only the image processing rules in the URL path; leave the server name, account name, and the asset ID or image name. Try it.

Now add an image processing parameter to the end of the URL. In the URL field, to the right of the image name, type ?wid=500, then press Enter. Try it.

Notice that a new rendition of the watch is generated. A key take away to understand from this simple exercise of changing the image’s width, is that the image seen is generated 100% dynamically.

Now change the width value of 500 pixels to 1000 pixels, and then press Enter. Try it.
The moment you press Enter, the browser goes back to the Dynamic Media Image Server. It generates a brand-new rendition of the watch, based on the new width value you just entered, then delivers the new image back to the browser, and caches it.

Dynamic Media has numerous image processing parameters that you can use to fine-tune your image assets on web pages. You can see a list of them here.

Now try adding a rotation parameter to the watch image. And the end of the URL path, immediately following wid=1000, type &rotate=90, and then press Enter. Try it.

The watch is still slightly skewed to the left. Change the rotate value of 90 to 92, and then press Enter. Try it.

Again, the moment you press Enter, a new rendition of the watch is generated nearly instantaneously. You can see the kind of performance that you get, which explains why Dynamic Media can deliver more than 800,000 image requests, per second, on a busy weekend, or major holiday.

While it is possible to change image processing parameters in a URL on an image-by-image basis, it is not an efficient method, especially if you have tens of thousands of images that make up your website. A much better approach is using image presets.