Acquia DAM
Do previews display when I upload assets?
Previews are automatically created for many supported file types when you upload assets to the Acquia DAM (Widen).
For Microsoft Office documents and PDF files, a preview of the first page displays in asset thumbnails in search results and on the Asset Details page. Open Quick View to scroll through all pages of multi-page Office and PDF files under 250 MBs in size.
For PowerPoint and PDFs over 250 MBs in size, full-length previews aren't automatically created, so you aren't able to scroll through all pages of those assets. Note that you'll see a Preview Not Available image in search results and in Quick View for PPTs and PDFs over 250 MBs in size, though an alternate preview can be uploaded. Sometimes PowerPoint documents with read-only embedded fonts don't display a preview. To fix this, remove the embedded fonts and upload the file again.
For ZIP files, previews are created based on the way files are arranged in the folder.
For AI files, previews will display when the AI file or file within an AI project archive (ZIP file) is saved as PDF compatible.
You can also listen to previews for audio files and watch full previews of videos from the Asset Details page before downloading and sharing those assets.
A gray, checkered background displays on previews for transparent (white) assets and assets with clipping paths. The checkered background makes those assets more visible in search results, collections, and the activity feed.
Previews can include watermarks. The watermark is independent of any conversion format watermarks and can be the same or different than the conversion format watermark.
PDFs are used as previews for InDesign, Illustrator, PDF, and video files that have been zipped. The PDF filename must be the same as the original filename, and the PDF must be included in the same folder.
Metadata is not imported from preview files.
Previews show up based on the number of assets you're uploading. Previews for smaller groups of files uploaded together will display before larger groups. For larger groups, you'll want to check on the previews in a few hours.
If there's a preview delay, a default image will describe the delay.
While files are uploading, a "File is Processing" preview displays until the files have been uploaded. Previews will display after files have processed. If a preview isn't available, you'll see a "Preview Not Available" image.
The time it takes to create previews varies depending on the file type and the number of files you're uploading. For each file, at least seven previews in various sizes are created, including an HTML5 file, which allows you to zoom in on details. Several file processors are used to create previews as quickly as possible.
A queue system is used for previews so processors can scale properly for small and large uploads. Smaller groups of files are given priority since metadata tagging and order may be needed immediately.
When uploading fewer than 10 files, previews for those files are placed in a high queue to be processed first. If you upload over 100 files, those are put in a low queue and processed after all files in the high queue have been uploaded.
Here's an outline of processing times based on the file type:
Processors autoscale previews based on the load at any given time across all of our customers. If several people are uploading a large number of files, new processes are automatically brought up for all cases, except for PSD files.
If a file format is not a supported file type, it will be marked as a generic binary file format. This means that the DAM could not identify the file so a preview could not be created. An alternate preview can be uploaded for unsupported file types.
If a file format is not a supported file type or if there's an issue with the file, a "Preview Not Available" image displays after upload. If a file format is a convertible (supported) format but a Preview Not Available image displays, there may be a delay in creating the preview.
If previews are missing or taking unusually long to appear after you upload an asset, the most common causes are high system load, unsupported or partially supported formats/features, issues during file processing, or problematic filenames (including special characters or emojis).
Preview generation is asynchronous and may take longer during peak system load or for very large/complex files.
The thumbnail shown during upload is a temporary placeholder. The final preview is generated only after processing completes.
Verify the file opens locally and is not corrupted.
Confirm the format and features are supported for preview. If you’re unsure, export a simpler version (for example, JPEG or PDF) and upload that to test.
Rename the file to remove problematic characters. Avoid emojis and special characters such as # % & + ? [ ] { } ( ) ; : ' " , * ! @ ^ ~. Use only letters (a–z), numbers (0–9), hyphens (-), and underscores (_). Keep the filename concise and ensure the file extension is present and correct (for example, .pdf, .jpg).
Check whether the file is password-protected or encrypted. Password-protected PDFs and archives typically cannot be previewed.
Simplify complex files where possible:
PDF: embed fonts; avoid interactive forms, multimedia, or encryption.
Illustrator (.ai): save with Create PDF compatible file enabled; consider flattening transparency or outlining fonts if previews frequently fail.
Other design files: export a PDF or image version if native-format previews are inconsistent.
Rename the file (to remove special characters/emojis) and re-upload.
Re-export the asset to a preview-friendly format (for example, PDF or JPEG) and upload that version.
Avoid uploading files inside ZIP archives if you expect an inline preview of the inner content.
If you have many uploads in parallel, try uploading fewer at a time to reduce queue pressure.
Open the asset page in a fresh browser tab after a short wait (preview generation is server-side, but a refresh can help you see the latest state).
If a preview still hasn’t appeared after an extended period and you’ve tried the steps above, contact support and include the following:
Asset ID or URL
Original filename and file type
Approximate upload date/time and timezone
Whether you renamed or re-exported the file
Any error messages you saw
Using emojis or special characters in file names or content can disrupt asset processing in Acquia DAM. This may lead to:
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Processors autoscale previews based on the load at any given time across all of our customers. If several people are uploading a large number of files, new processes are automatically brought up for all cases, except for PSD files.
If a file format is not a supported file type, it will be marked as a generic binary file format. This means that the DAM could not identify the file so a preview could not be created. An alternate preview can be uploaded for unsupported file types.
If a file format is not a supported file type or if there's an issue with the file, a "Preview Not Available" image displays after upload. If a file format is a convertible (supported) format but a Preview Not Available image displays, there may be a delay in creating the preview.
If previews are missing or taking unusually long to appear after you upload an asset, the most common causes are high system load, unsupported or partially supported formats/features, issues during file processing, or problematic filenames (including special characters or emojis).
Preview generation is asynchronous and may take longer during peak system load or for very large/complex files.
The thumbnail shown during upload is a temporary placeholder. The final preview is generated only after processing completes.
Verify the file opens locally and is not corrupted.
Confirm the format and features are supported for preview. If you’re unsure, export a simpler version (for example, JPEG or PDF) and upload that to test.
Rename the file to remove problematic characters. Avoid emojis and special characters such as # % & + ? [ ] { } ( ) ; : ' " , * ! @ ^ ~. Use only letters (a–z), numbers (0–9), hyphens (-), and underscores (_). Keep the filename concise and ensure the file extension is present and correct (for example, .pdf, .jpg).
Check whether the file is password-protected or encrypted. Password-protected PDFs and archives typically cannot be previewed.
Simplify complex files where possible:
PDF: embed fonts; avoid interactive forms, multimedia, or encryption.
Illustrator (.ai): save with Create PDF compatible file enabled; consider flattening transparency or outlining fonts if previews frequently fail.
Other design files: export a PDF or image version if native-format previews are inconsistent.
Rename the file (to remove special characters/emojis) and re-upload.
Re-export the asset to a preview-friendly format (for example, PDF or JPEG) and upload that version.
Avoid uploading files inside ZIP archives if you expect an inline preview of the inner content.
If you have many uploads in parallel, try uploading fewer at a time to reduce queue pressure.
Open the asset page in a fresh browser tab after a short wait (preview generation is server-side, but a refresh can help you see the latest state).
If a preview still hasn’t appeared after an extended period and you’ve tried the steps above, contact support and include the following:
Asset ID or URL
Original filename and file type
Approximate upload date/time and timezone
Whether you renamed or re-exported the file
Any error messages you saw
Using emojis or special characters in file names or content can disrupt asset processing in Acquia DAM. This may lead to:
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Acquia DAM