How to Save a Web Dashboard as a PDF with Clickable Links for a Client

The most reliable way to save a web dashboard as a PDF is to use its own Export, Download PDF, or Print Preview command. If it has no suitable export, open the browser print dialog and choose its built-in Save as PDF destination. Set the filters and reporting period first, then inspect the saved PDF and click the links your client will need. Link preservation depends on the dashboard and export route, so do not assume every link survived.

A PDF is usually a static snapshot of the dashboard at export time. If the client needs live data, filters, or drill-downs, send an authorized dashboard link as well and confirm the recipient has access. ScreenshotNeo is a website screenshot API and MCP server from ScreenshotNeo; it can capture web pages as images or PDFs, but a screenshot does not replace a dashboard’s interactive sharing permissions.

1. Prepare the dashboard view

Open the dashboard in the state you intend to share. Apply the correct filters, selections, date range, and page or sheet.
Wait for charts, embedded content, and data refreshes to finish. Check for loading indicators or error states before exporting.
Record the reporting period and, if relevant, the export date. A PDF records a point in time; it will not update when the underlying dashboard changes.
Check whether the dashboard has multiple pages or sheets, scrollable visualizations, or embedded cards. Some exporters include only the currently open page, sheet, or visible portion.

For example, Amazon QuickSight describes its PDF as a snapshot of the current sheet and says to repeat the export for each sheet you need. Salesforce CRM Analytics likewise prints the current filters and selections; only the open dashboard page and the visible area of a scrollable widget print. See the QuickSight PDF export guide and Salesforce dashboard printing guide.

2. Use the dashboard’s native PDF export first

Look in the dashboard menu, toolbar, or Share panel for Export, Download PDF, Print, or Print Preview. Native export is usually the best starting point because it may provide dashboard-specific options such as page size, orientation, filter inclusion, or a print-oriented layout. The controls and requirements vary by product, role, plan, and administrator settings.

Dashboard	Documented route	Things to check
Amazon QuickSight	Choose Export > Generate PDF or Download as PDF, depending on the report flow, then download when it is ready.	Export each sheet needed. In one documented flow, the prepared download is temporary and expires after five minutes. See the interactive dashboard export guide and PDF export guide.
Elastic Kibana	Choose Export and select PDF. Optionally enable its print format for a printer-oriented, multi-page layout.	PDF/PNG reporting is a subscription feature and requires the relevant reporting privilege. The report captures the currently displayed dashboard state; data tables and Discover sessions may include only visible data. See Elastic’s dashboard sharing and export documentation.
Salesforce CRM Analytics	In dashboard preview, choose the overflow menu, then Print Preview; choose Print to open the browser dialog.	Salesforce documents Chrome-only support for this workflow. Scrollable widgets print only their visible area, and only the currently open dashboard page prints. Full-width and background graphics options can affect the result. See the Salesforce instructions.
Adobe Workfront	Choose Dashboard Actions > Print Preview, then use the browser’s print options.	Adobe warns that formatting may change and columns can be cut off. Inspect the output carefully. See Workfront’s dashboard export guidance.
ClickUp	Open the dashboard and choose the download icon or ellipsis menu, then Download PDF.	Cards are arranged in two columns; embedded cards are excluded. Availability and limits vary by plan and role. See ClickUp’s PDF instructions.
IBM Cognos Analytics	From the open dashboard, choose Share > Export, set page size and orientation, optionally include filters, and select Export.	A browser print window then opens. Make its paper size and orientation match the settings chosen in Cognos. See IBM Cognos dashboard PDF export instructions.

These are examples, not universal menu labels. A product update, deployment type, or account role may change the available route. Follow the instructions shown in your dashboard’s own help when its controls differ.

3. If there is no suitable export, print to PDF

Open the dashboard in the browser and set its intended filters, date range, page, and visible scroll position.
Open the browser’s print dialog. The keyboard shortcut is commonly Ctrl+P on Windows or Linux and Command+P on macOS; menus and shortcuts can vary.
Choose the browser’s built-in Save as PDF or equivalent PDF destination. Do not select a physical printer by mistake.
Choose page size and orientation. For wide dashboards, try landscape first. Adjust scale, margins, and page breaks until labels remain readable.
Enable background graphics only if the dashboard needs its colors or shaded regions to convey meaning. Check the preview because backgrounds can affect readability and file size.
Save the file, then open that exact PDF in a viewer and inspect every page.

Browser labels and available print controls differ by browser and operating system. Some dashboard services first show their own print preview before opening the browser dialog. IBM Cognos, for instance, documents matching the page size and orientation between its export panel and the browser print window. Browser printing is a fallback, not a guarantee that the page will preserve the dashboard’s original layout or all of its content.

4. Tune layout and verify the pages

Use the print preview and the saved PDF to check whether the page is legible at normal viewing size. Avoid shrinking a wide dashboard until every column fits if that makes the labels unreadable; multiple pages or a focused dashboard view may be clearer.

Orientation and paper: Landscape often gives wide charts more room. Use a larger page only if the client can read it on screen or print it.
Scale: Try the browser’s fit-to-page option if content is clipped, then check whether the resulting text is too small.
Margins and page breaks: Adjust them to avoid splitting chart titles, legends, or tables across pages.
Backgrounds: Include background graphics when they carry meaning, then verify color contrast and ink-heavy areas.
Completeness: Check every expected page and sheet, long tables, scrollable widgets, embedded cards, and visualizations that load asynchronously.
Context: Ensure the PDF shows the intended date range and filter state. Include that period in the filename or handoff note.

Exporters differ in what they include. Elastic documents a print layout with multiple A4 portrait pages, while ClickUp says embedded cards are excluded from its PDF. Adobe Workfront warns that some formatting can change and columns may be cut off. Check the specific service’s documentation and the resulting file rather than assuming a dashboard export includes every on-screen element.

5. Test clickable links in the saved PDF

Do not treat clickable links as guaranteed. A dashboard’s native PDF exporter may use a different rendering path from the browser print dialog, and support can vary across platforms and viewers. Open the saved file in the PDF viewer your client is likely to use and click each important link, including links in chart annotations, text cards, or tables.

Test the links in the actual delivered PDF, not just the dashboard preview.
Confirm each link opens the intended destination and does not require an account your client lacks.
Check whether the link text is visible and descriptive when printed; a bare URL or clear label is easier to interpret than an unlabeled hotspot.
If an essential link is absent or unreliable, include the URL in the accompanying email or notes and provide an authorized live dashboard link when appropriate.

Browser PDF behavior should be treated as something to verify, not a cross-platform promise. Mozilla’s support material and issue tracker describe browser PDF link behavior and caveats; the final check is the PDF your client will receive. See Mozilla Support’s discussion of links in saved PDFs and the related Firefox issue report.

6. Decide whether the client also needs the live dashboard

Send a PDF when the client needs a portable record of a particular view. Send a live dashboard link when the client needs to change filters, drill into data, or see updates. Often the useful handoff is both: the PDF for a fixed reference and an authorized dashboard link for exploration.

Confirm recipient access before sharing. Elastic notes that a Kibana link requires access to the instance unless anonymous access is configured. Amazon QuickSight notes that dashboard access also provides access to associated data, so grant access deliberately. A PDF can also contain sensitive information after it is downloaded; share it only with the intended recipients. See Elastic’s sharing documentation and QuickSight dashboard sharing guidance.

7. Handoff checklist

The PDF contains the intended filters, time range, pages, and sheets.
Charts and tables finished rendering before export.
Titles, legends, labels, and columns are readable and not clipped.
Important links have been clicked and checked in the saved file.
The filename and handoff note identify the reporting period.
The note says the PDF is a snapshot and includes a live link if the client needs interactivity.
The recipient can access the live dashboard, and that access is appropriate for its underlying data.

Or skip the browser setup

If your task is to capture a web page for a PDF or visual handoff and you do not need to configure a headless browser, ScreenshotNeo’s API documentation describes its website screenshot API. One GET request can return a screenshot or PDF; the example below uses the documented request shape and saves an image response.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Replace the sample URL with a page you are authorized to capture and keep your API key private. ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture; each of those cleanup steps can be turned off. Bot checks, blank pages, and failed loads are never billed, and response headers identify the page verdict and billing status. An MCP server lets AI agents use screenshot tools. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. See the documentation for request options and PDF configuration.

Troubleshooting

Symptom	Likely cause	What to do
Dashboard content is missing from the PDF	The exporter captured only the open page or sheet, or omitted embedded content.	Export each required sheet or page separately and check the product’s documented exclusions. For scrollable widgets, see whether only the visible area is printable.
Columns or chart edges are cut off	The print width, scale, or orientation does not fit the dashboard.	Try landscape, a wider paper size, adjusted margins, or the service’s print layout. Use multiple pages if scaling makes text too small.
PDF has blank charts or loading indicators	The dashboard had not finished rendering or its data request failed.	Wait for rendering and data refresh to complete, verify the dashboard itself shows data, then export again. Check that embedded resources are not blocked.
Colors or shaded regions disappeared	Background graphics are disabled in the browser print dialog.	Enable background graphics if the colors are necessary, then review contrast and output pages again.
Links do not work in the PDF	The export path did not preserve them, the link is not a real hyperlink, or the viewer handles it differently.	Test in another suitable PDF viewer and inspect the source dashboard link. Include important URLs in the handoff note if they are not preserved.
PDF export option is missing or denied	The product, plan, role, or instance privileges may not enable export.	Check the product’s plan and role requirements or ask the dashboard administrator to enable the appropriate export access.
Export is queued but no file appears	A service may prepare reports asynchronously, or the download link may expire.	Check its downloads or reporting page, wait for completion, and download promptly. QuickSight documents a five-minute availability window for one export flow.
Browser print has an unexpected layout	Print styles and browser or operating system settings differ from the dashboard screen.	Use the service’s native export if available. Otherwise review print preview, paper size, orientation, scale, margins, and background settings before saving again.

Performance, reliability, and cost

For a one-off client handoff, native export is usually the shortest route. Browser printing adds a rendering path that can vary with browser and print settings. Large dashboards, many visualizations, or slow data queries can take longer to render; wait for the dashboard to settle before exporting, and split a very wide view into readable pages if needed.

Export availability and cost are platform-specific. The research does not establish a general price for dashboard PDF export, and some products require particular plans or privileges. Check your account’s product terms before relying on scheduled or repeated exports. Keep the saved PDF and the live dashboard permission model in mind as separate handoff artifacts.

FAQ

Does saving a dashboard as a PDF preserve its filters?

It can preserve the view that was active at export, but this depends on the platform. Set filters first and inspect the PDF; some exports can also include a filter summary.

Can a client interact with a PDF dashboard?

Usually not in the same way as the live dashboard. A PDF is generally a fixed view; provide an authorized live link for filters and drill-downs.

Should I test every link or just the main one?

Test every link the client is expected to use. Export behavior can differ between links in text, visualizations, and other dashboard elements.

What should I send if a PDF link is not clickable?

Include the destination URL in the email or handoff notes, and share a live dashboard link if the recipient is authorized to access it.