You publish your Dynamic Media assets by selecting the assets you have already uploaded and selecting Publish or Quick Publish. After your Dynamic Media assets are published, they are available to you for including in a web page by way of a URL or by way of embedding code on the page.
You can also instantly publish assets that you upload – without any user intervention. Or, you can selectively publish those assets. See Configure Dynamic Media. Or, you can selectively publish assets to either Dynamic Media or Adobe Experience Manager, mutually exclusive of each other, using Selective Publish at the folder level. See Work with Selective Publish in Dynamic Media.
In the Card View, a small globe icon appears directly below an asset’s name and to the left of the date and time to indicate that it is published. In the List View, a Published column indicates which assets are published or which are not.
If an asset is already published, then you move the asset to another folder, and republish from its new location, the original published asset location is still available, along with the newly republished asset. The original published asset, however, is “lost” to Experience Manager and cannot be unpublished. Therefore, as a best practice, unpublish assets first before you move them to a different folder.
If you intend to publish video assets immediately after encoding them, make sure that encoding is done. When videos are being encoded, the system lets you know that a video processing workflow is in progress. When video encoding is done, you can preview the video renditions. At that point, it is safe for you to publish the videos without incurring any publishing errors.
See also Link URLs to your web application.
For detailed information on publishing a set or asset, see Publishing Assets.
Experience Manager now supports the delivery of all Dynamic Media content (images and video) over HTTP/2. That is, a published URL or embed code for the image or video is available to be integrated with any application that accepts a hosted asset. That published asset is then delivered by way of HTTP/2 protocol. This method of delivery improves the way browsers and servers communicate, allowing for better response and load times of all your Dynamic Media assets.