> For the complete documentation index, see [llms.txt](https://ortuspdf.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ortuspdf.ortusbooks.com/readme.md). # Introduction The Ortus PDF Extension is a Lucee Extension that will bring enhanced PDF tags and features to any Lucee CFML engine like cfpdfform, cfpdfformparam tags and much more. ## Ortus PDF Extension v2.x Docs The Ortus PDF Lucee Extension adds the missing PDF capabilities you were longing for to any Lucee engine and enhances some PDF capabilities. The extension contains several new CFML built-in tags and functions to help you manipulate and work with PDF documents. ### Requirements * Lucee 5.1.0 and above ### Commercial Product This Lucee extension is a commercial product by Ortus Solutions. You will need to purchase a license: ### Features In A Nutshell * `cfpdfform` tag implementation compliant with Adobe ColdFusion * `cfpdfformparam` tag implementation compliant with Adobe ColdFusion * Ability to export PDF form data into: * Native CFML Structures * XML String * XML File * FDF File * JSON (Ortus Feature) * Ability to pre-fill PDF form data from: * Native CFML Structures * XML String * XML File * XML Objects * JSON objects * Allows the ability to flatten PDFs after populating them with data * Manipulates existing forms created in Adobe® Acrobat® and Adobe® LiveCycle® Designer * Ability to stream generated PDFs to browser * Support for embedded forms (New since v2.1.0) * Much More!! ### Support The Ortus PDF Extension is a commercial product by Ortus Solutions. If you have purchased a license, you are entitled to customer support. You can visit our support page to contact us or create an issue in our bug tracker. * Support Page: * Bug Tracker: --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://ortuspdf.ortusbooks.com/readme.md?ask=&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 `build a script that syncs our docs to a CMS` 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.