Content Hub FAQs

On this page we've included the answers to some common issues that you may encounter when using the Content Hub.

Supported asset types

What image types are supported?

The following image types can be uploaded to Content Hub, published and consumed using Dynamic Media. These assets can also be served statically.

File extension MIME type
jpg, jpeg, jpe, jfif image/jpeg
png image/png
tif, tiff, ptif, ptiff image/tiff
gif image/gif
bmp image/bmp
svg image/svg+xml

Which output formats does the Dynamic Media format parameter support?

Using the Dynamic Media fmt parameter you can set the format of an image to: jpg, png, gif, bmp, webp and jp2. Note that webp and jp2 are not supported by all browsers.

What video types are supported?

The following types of video files can be uploaded to Content Hub and encoded using one or more video transcoding profiles.

File extension MIME type
mp4 video/mp4
mov video/quicktime
mkv video/x-matroska
webm video/webm
mpg, mpeg video/mpg
vob video/mpeg
ts video/mp2t
ogv video/ogg
wmv video/x-ms-wmv
avi video/x-msvideo
asf video/x-ms-asf
3gp video/3gpp
rv, rv9 video/vnd.rn-realvideo
ram video/x-pn-realvideo
flv, f4v, f4pf4a, f4b video/x-flv *
  • Note that all of the major browsers will no longer support Adobe Flash from December 2020.

Audio formats

File extension MIME type
aiff audio/x-aiff
ogg audio/ogg

What video formats can I use to create video transcoding profiles?

You can set up a transcoding profile for containers including: mp4, webm, m4v, mov and wmv. A full list is shown on the video transcoding profiles page.

Note that not all containers can be used with all video and audio codecs and in most cases you will use the transcoding profiles that are already configured on your account.

Are any 3D graphics types supported?

You can upload files in the USDZ format used by Apple iOS and the GLB format used by Android and serve these statically.

File extension MIME type
usdz model/vnd.pixar.usd
glb model/gltf-binary

What other asset types (apart from images and video) can be uploaded to and published from Content Hub?

You can upload the following text types to Content Hub:

File extension MIME type
txt text/plain
csv text/csv
css text/css
html text/html
xml application/xml
json application/json
jsonp text/javascript
js application/javascript

Other types may be served statically. See the static publishing page for a full list.

Using Content Hub

I uploaded an animated GIF, but a still image is being displayed. What is the problem?

When an animated GIF is consumed using Dynamic Imaging, it is treated as a still image and only the first frame is displayed. You will need to consume the animated GIF statically to show the full animation.

Why can't I see a preview of my asset?

Preview is only supported for certain types of asset in Content Hub: images, video, text, sets and pdfs. For other types of asset, the "eye" icon is not shown on the asset's card and no preview is available.

What is the maximum file upload size?

If you upload the file manually, the file cannot exceed 100MB. If you use FTP bulk upload, then there is no limit.

What is the maximum share size when using Media Share?

You can share files up to 1000MB. See the media share page for more details.

Why can't I publish my SVG?

If no preview is shown when you upload your SVG and you cannot publish the asset, it may not be a valid SVG. The most common cause of this problem is a missing length and width attribute. Check that you have specified the SVG length and width in your SVG file.

What characters should not be included in an asset filename?

The following characters must not be included anywhere in a filename of a file ingested into Content Hub. Including one of these characters in a filename will lead to problems when ingesting the file, or retrieving the file using Dynamic Media. If you need to work with a file containing one of the characters shown below, rename it locally before ingesting into Content Hub or rename the ingested asset.

blank spaces # < > $ + % > ! ` & * ‘ | { ? “ = } / : . \ @

How do I completely delete a published asset from my site?

Just deleting an asset from Content Hub will not unpublish the asset or remove it from our Content Delivery Networks (CDNs). To completely remove an asset from your site you need to do the following:

  • Unpublish the asset using the Dynamic Media app. Unpublishing an asset will remove it from the mid-tier CDN cache as well as the origin servers.

  • Purge the asset from the CDN edge servers. If you do not purge the asset, then you will need to wait for the time to live (TTL) to expire.

  • Delete the asset from Content Hub. You may choose to keep the asset in Content Hub so you can re-publish it later.

Other topics

Which file formats can I use with the Image Recognition service?

Image recognition can be used with JPG and PNG files. No other formats are supported.

Can I run image recognition retrospectively?

The image recognition service will process assets when they are ingested into Content Hub. If you want to process assets that have already been ingested, you will need to contact Amplience support.

Can I use custom fonts?

You can use custom fonts, but these will need to be installed by the Amplience support team.

How do I specify addresses to be whitelisted for use with Virtual Staging environments?

The Virtual Staging whitelist is used to restrict access to the virtual staging environment, for example anyone viewing a visualization or preview in Dynamic Content will need to have their IP address included in the white list.

IP addresses are specified with the Account app, using CIDR notation as explained on the Virtual Staging security page. Setting up a whitelist is an admin task that is usually done by the Amplience provisioning team at the beginning of your project. If you want to make changes and do not have permission to edit your whitelist using the Account app, please contact your organization's admin user or Amplience support.

Why is a PNG that I’ve uploaded to Content Hub larger when I request it from Dynamic Media?

Your published PNG could be larger than the original for a couple of reasons:

  1. Your original PNG was indexed, you can ensure the requested version is indexed by adding: fmt.png.indexed=true into your request. See the Dynamic Media parameter reference for more details.
  2. Amplience recreates the image in the process of publishing it to increase performance/reduce latency, in the case of PNGs this can result in a larger file due to the heavily compressed nature of lossless PNG files. This can be mitigated by requesting the image in another format, or applying other transformations.