Overview
Users may find that previously copied direct asset links—for example, an older file URL such as s3.amazonaws.com/external_clips/...pdf?...—no longer open correctly, even though the portfolio itself is still available at a public-facing portfolio URL such as <your-name>.contently.com, and the same samples still appear when viewed from within the portfolio page.
This behavior typically affects direct asset-delivery URLs rather than the portfolio page itself. When one of these older links fails, the browser may display an XML-style error instead of the expected PDF or asset.
This is not necessarily evidence that the portfolio content was deleted. It is a limitation of using internal delivery links as external share links. Direct asset URLs are used by the platform to render portfolio content, and in limited cases they may change over time as part of platform or infrastructure updates. Because of that, they should not be treated as permanent public-facing links.
The supported long-term sharing method is the public portfolio URL. If the portfolio should remain private, the supported workaround is to export the portfolio as a PDF and share that file instead.
Solution or Explanation
Direct file URLs used to display portfolio content are not a supported long-term sharing method for external distribution.
If a user copies and shares an individual asset URL instead of the portfolio’s supported public URL, that direct link may stop working later even though the portfolio page itself still functions normally.
Supported sharing options
1. Use the public portfolio URL for long-term external sharing
If the goal is to share portfolio work with editors, recruiters, or other external viewers, the supported method is:
- Complete the portfolio.
- Submit it for public visibility review through the documented approval process.
- Wait for approval from the Creative Marketplace team.
- Share the public portfolio URL instead of sharing direct links to individual PDF assets.
This is the supported stable workflow because the portfolio URL is the intended external entry point, even if underlying delivery links for individual items change later.
2. Use a PDF export if the portfolio must remain private
If the portfolio should not be public, the supported workaround is to export the portfolio from the browser as a PDF and share that exported file.
This is a workaround rather than a permanent sharing model. A PDF export is only a snapshot of the portfolio at the time it was created. It does not update automatically when the portfolio changes.
3. Re-add PDF items when needed
If a sample should appear as a PDF item inside the portfolio, add it using the supported PDF import flow rather than relying on a previously copied direct file URL.
4. Update outdated portfolio items when necessary
If a portfolio item points to an outdated or incorrect destination, update it from the Portfolio area by re-adding the sample with the correct link and archiving or hiding the outdated version.
Example
A user may have previously shared a direct link that looks like an individual asset file, such as an older s3.amazonaws.com/external_clips/...pdf?... URL.
If that link is no longer valid, opening it may show a browser message such as:
This XML file does not appear to have any style information associated with it.
In this situation, the portfolio page itself, for example <your-portfolio>.contently.com, may still load normally, and the item may still be accessible from within the portfolio. The problem is the previously copied internal direct asset link, not necessarily the portfolio content.
Verification
Use the following checks to confirm the correct resolution path:
- Open the portfolio page itself.
- Open the affected sample from within the portfolio interface.
- Confirm that the sample still appears and opens there.
- Check what is being shared externally:
- If the shared link is an old direct asset URL, replace it with the public portfolio URL if the portfolio is approved for public visibility.
- If the portfolio must remain private, create and share a fresh PDF export instead.
A successful outcome means the user is no longer relying on an old direct asset URL for external sharing.
Additional Notes
- A public portfolio requires approval through the documented public-visibility process.
- Direct asset-delivery URLs should not be positioned as permanent public links.
- If a user wants individual PDF samples to appear properly inside the portfolio, use the supported PDF upload flow.
- If the issue is that a portfolio entry itself points to an outdated destination, update the entry from the Portfolio section rather than the Projects section.
- This article applies when the portfolio page remains available but older copied direct asset links fail. If the portfolio page itself is unavailable, investigate that as a separate issue.