> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/cli/pdfsecure/installation.md).

# Installation & Setup for PDFSecure

Download PDFSecure Command-line Application from www\.apryse.com. Unzip the file, copy the license for registration. Get the demo version for evaluation. Easily uninstall by deleting the folder. The Ap

**PDFSecure** Command-line Application is supplied as a download from a distributor or directly from [www.apryse.com](https://www.apryse.com). The release is packaged as a .zip file. (pdfsecure.zip). Unzip the archive in the desired location and make sure to preserve the directory (folder) structure when extracting the archive. In order to register the software, copy the license file provided to you into the "pdfsecure" folder.

## Demo Version Installation

If you wish to evaluate the product, you can [download the demo version](/cli/get-started/download.md) of the product without any serial number or license key. The limitation of the evaluation version is that all output pages will have demo stamps.

## Uninstalling PDFSecure

To remove PDFSecure from a computer, simply delete the "pdfsecure" folder.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/cli/pdfsecure/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.