#027Tutorial4 min

Download and share a PDF report

Choose a recipient profile, prepare the printable report and save it as a PDF from your browser.

Hackaiz team · updated 21/11/2026

Illustration: a person sets up an account on a laptop.
Illustration: a person sets up an account on a laptop. Illustrative photo, not a screenshot.

01Open the analysis you intend to share

A PDF is a snapshot of one analysis, not a live view of your entire account. Start by opening the intended report and checking the target, date and analysis status. If a colleague asks about a particular release, use that release’s analysis rather than whichever report the project list opens today.

Find the Shareable report section in the analysis page. This export is built from the records written by that scan. It adapts the presentation for the chosen reader while retaining analysis limits. Exporting a report does not run missing checks or turn an incomplete result into a completed assessment.

02Choose Recipient before creating the file

The Recipient selector offers Executive, Security lead, Developer and AI security. Choose the intended reader before pressing the preparation button. These are report audiences, not a list of email contacts. Selecting Executive does not send the document to a manager, and selecting Developer does not create a code change.

Use the audience choice to prepare the discussion you actually need. A leadership review and a technical investigation do not start with the same questions. Regardless of the selected reader, retain the target and analysis context when you pass on the resulting file. Changing the presentation is not evidence that additional systems were examined.

  1. 1Open Shareable report in the chosen analysis.
  2. 2Select the intended profile in Recipient.
  3. 3Choose PDF in the Format controls.
  4. 4Press the PDF button bearing the selected audience name and wait for preparation.

03Complete the browser’s print workflow

The PDF option opens a printable report page and uses your browser’s printing facilities. It is not a separate PDF attachment sent by email. In the print interface, select the browser or operating system’s PDF destination if one is available, check the preview and save the document to the location you choose.

If Hackaiz says that the browser blocked the print window, allow pop-ups for this site and retry. If the preparation fails instead, read the error before repeatedly pressing the button. The available print destinations and the final save controls belong to your browser or device, so their wording can differ from Hackaiz’s own buttons.

Text file is the alternative format in the same section. It downloads the prepared report as a text document rather than opening the print workflow. This can be useful if printing is inconvenient on your device, but it is not a PDF. Report preparation uses credits; consult the application’s credit information rather than assuming repeated preparations have no effect.

04Review the saved document before sending it

Open the saved PDF and verify that the target, analysis context and limits are readable. Check tables and long technical passages in the print preview as well as the finished document. A saved file is independent of later changes in the workspace: if the application is checked again, the earlier PDF does not update itself.

Share the file through a channel approved by your organization and only with people who need the information. Security findings can expose internal addresses, code details or configuration weaknesses. Downloading the report does not automatically establish who may receive it. Add a short message explaining which target and analysis the document represents.

Technical exports is a separate expandable area for formats such as JSON, SARIF and Jira / Linear (CSV). Those serve data exchange needs and are not substitutes for choosing PDF. For a straightforward human handover, avoid sending a bundle of technical files when the reader only needs the prepared report.

Do not describe the PDF as a security certificate or a guarantee of compliance. It preserves technical evidence and stated limitations. If the recipient asks whether a correction has been verified, refer to the relevant subsequent analysis rather than treating the existence of a downloadable document as proof of remediation.

Frequently asked questions

Was this article helpful?

Related articles