Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.
SOLVED

AEM Linkshare downloads assets in individual folders instead of all in root folder directly

Avatar

Level 3

Hi All

AEM Linkshare functionality when multiple assets within a folder is shared and downloaded, the assets are inside another sub-folder instead of all assets directly inside the parent/root folder. Is this a recent change in OOTB Link share functionality?

Is there a configuration to download all assets in the same root folder instead of respective sub-folders?

For example, DAM folder /content/dam/test has assets a.jpg & b.jpg, when folder test is shared via Share Link functionality to an author and downloads the folder, then extracts it to find folder with name a.jpg and b.jpg inside these folders, assets a.jpg and b.jpg exists.

The expected result is directly inside extracted folder test, the assets a.jpg and b.jpg must be available. Is this possible?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @SrikanthPo3,

This is the expected out-of-the-box (OOTB) behavior of AEM Link Share functionality, especially in:

  • AEM as a Cloud Service (AEMaaCS)

  • AEM 6.5.x (SP13+ onwards, more noticeable in SP19+)

When sharing a folder or selecting multiple assets using Link Share, the download ZIP is structured to wrap each asset inside a subfolder named after the asset.

Adobe's official documentation outlines this behavior:

"Assets view downloads the selected assets as a zip file. Assets view creates a sub-folder in the parent zip file, with the same name as that of the asset, for each asset that you select to download."Experience League | Adobe

This information is available in the Adobe Experience Manager documentation.

To answer your question: There is No official OOTB configuration exists today to flatten the ZIP structure for Link Share downloads - neither in AEMaaCS nor AEM 6.5.

As an alternative solution: May be you can override or extend the com.day.cq.dam.core.impl.servlet.AssetDownloadServlet or similar service used in link sharing and flatten the ZIP structure during runtime using a custom ZIP packager.

Hope that helps!


Santosh Sai

AEM BlogsLinkedIn


View solution in original post

4 Replies

Avatar

Level 5

Hi @SrikanthPo3 ,

This behavior is part of AEM’s out-of-the-box (OOTB) Link Share functionality, introduced in AEM as a Cloud Service (AEMaaCS) and in later versions of AEM 6.5+. When multiple assets are shared either by selecting them individually or by sharing a folder AEM preserves the folder hierarchy in the generated ZIP file. Each asset is placed inside its own subfolder named after the asset. This ensures structure and avoids naming conflicts during download.

As of now, there is no OOTB configuration in AEM (including AEMaaCS) to flatten this structure when generating shared download links.

Avatar

Correct answer by
Community Advisor

Hi @SrikanthPo3,

This is the expected out-of-the-box (OOTB) behavior of AEM Link Share functionality, especially in:

  • AEM as a Cloud Service (AEMaaCS)

  • AEM 6.5.x (SP13+ onwards, more noticeable in SP19+)

When sharing a folder or selecting multiple assets using Link Share, the download ZIP is structured to wrap each asset inside a subfolder named after the asset.

Adobe's official documentation outlines this behavior:

"Assets view downloads the selected assets as a zip file. Assets view creates a sub-folder in the parent zip file, with the same name as that of the asset, for each asset that you select to download."Experience League | Adobe

This information is available in the Adobe Experience Manager documentation.

To answer your question: There is No official OOTB configuration exists today to flatten the ZIP structure for Link Share downloads - neither in AEMaaCS nor AEM 6.5.

As an alternative solution: May be you can override or extend the com.day.cq.dam.core.impl.servlet.AssetDownloadServlet or similar service used in link sharing and flatten the ZIP structure during runtime using a custom ZIP packager.

Hope that helps!


Santosh Sai

AEM BlogsLinkedIn


Avatar

Community Advisor

@SrikanthPo3 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!


Aanchal Sikka

Avatar

Level 3

Hi @aanchal-sikka 

Apologies for late reply.

This issue is resolved after removing the custom link share servlet implementation was removed, we customized link share functionality to handle couple of custom renditions for PSD files.