PDF Viewer component not visible on the page (6.5 version)

[_Anon_ymous_]

I have added PDF viewer component on page, after authoring the component it's not visible, have made changes on configuration what other posts suggested but no luck. Please help me out.

[MonalikaKapoor]

Hi @_Anon_ymous_,

Could you please ensure that the PDF Viewer component version you are using is compatible with AEM 6.5. According to the PDF Viewer Component documentation, the component should be compatible with AEM 6.5. Make sure that your AEM instance has the necessary version of the Core Components installed.

[_Anon_ymous_]

Hi @MonalikaKapoor ,

I’ve received the trial client ID, and the PDF Viewer is working, but I’m noticing that some features like download, print, dock, and undock are not functional.

Can anyone confirm if the PDF Viewer trial provides access to only a limited set of features, or is there something else I might need to enable these options?

Thanks in advance!

[giuseppebag]

hi @_Anon_ymous_, have you checked if the component requirements are satisfied? Please take a look at the "Context Aware Config" section of its documentation:

clientId - Required - the client key obtained by registering for the view sdk api - https://www.adobe.com/go/dcsdks_credentials

[AmitVishwakarma · Accepted solution]

Hi @_Anon_ymous_ ,

Root Cause Possibilities:

1. Missing clientId for Adobe PDF Embed API
2. Incorrect Context-Aware Config (CAConfig) path
3. Core Components version incompatible
4. PDF URL not set or invalid
5. Browser blocking insecure content (HTTP PDFs on HTTPS site)
6. Missing Dispatcher Rewrite Rules (if applicable)

1. Check Client ID Configuration

Based on your screenshot, clientId is present: 28b07c6be4d544f...
Ensure this is from Adobe’s PDF Embed API registration: Get clientId

2. Correct Context-Aware Configuration (CAConfig)

Make sure the PDF Viewer component is inheriting the config.
Your configuration should be under:

/conf/<your-site>/settings/wcm/core/components/pdfviewer/v1/pdfviewer

Ensure the page where you’re placing the PDF viewer has CAConfig properly set in Page Properties > Advanced > Context-aware Configuration Path pointing to /conf/<your-site>.

3. Core Components Compatibility

Your AEM 6.5 must have Core Components 2.12.0+.
Verify installed version:

http://localhost:4502/system/console/bundles/com.adobe.cq.core.wcm.components.core

Upgrade if needed: Download Core Components

4. Check Component Authoring
Did you provide a valid PDF URL in the component dialog?
It must be a publicly accessible PDF (or within AEM DAM).
If PDF path is relative or missing, the component won’t render.

5. Check Browser Console

Inspect browser Console (F12) for errors like:

Invalid Client ID
PDF URL not found
Mixed content error (HTTP PDF on HTTPS site)

6. Dispatcher Configuration (If Used)

Ensure that PDF MIME types are allowed in Dispatcher.
Add in dispatcher.any:

/0040 {
   /type "allow"
   /extension "(pdf)"
}

Flush Dispatcher Cache if needed.

Quick Test (Bypass All Issues)

Place PDF URL from AEM DAM:

/content/dam/your-site/sample.pdf

Open page in Preview mode.
If still blank → It’s likely CAConfig or Client ID not linked properly.

Use Embed Mode (Debug)
In the component dialog, enable Embed Mode and inspect the iframe being rendered. If the iframe is not rendered, it’s definitely clientId or PDF path issue.

Regards,
Amit Vishwakarma